Client stories

These notes come from product owners who sat through a walkthrough or received a written path review. They mention the awkward parts as well as the useful ones.

The inventory showed our hotel app recorded every calendar open but almost none of the three-night stays people actually book around Gawai. That gap was hiding in a property we had labelled 'misc_date'.
Rina Bong, stays lead, a Kuching lodging app

I still think the findings session ran long. Two hours on baggage add-ons felt like a lot. It did, however, stop us renaming the same event three times before Hari Raya travel.
Daniel Koh, airline app product owner, Penang

They refused to start until we had a test login that could reach the ferry timetable. Annoying in week one. Correct, because that screen was where island tours went quiet.
Siti Rahim, tours producer, Semporna-based operator

The seasonal calendar was plainer than I expected — just weeks marked for school holidays and the northeast monsoon — and that was what our planner actually put on the wall.
Farah Ismail, operations, East Coast bus-and-stay app

A longer note: date changes after rain

A Kota Kinabalu hotel app came to us because weekend occupancy looked healthy in their booking reports while midweek island packages sat still. The walkthrough used a test guest who moved a three-night stay after a rain warning for Tunku Abdul Rahman Park.

The calendar fired an event on every open, including accidental taps. The actual stay-length change used a different name in Malay copy than in English copy, so the two language versions never sat in the same row. After the review, the team agreed to one trip-language name for “stay dates moved” and to ignore stray calendar opens when they read a week.

We did not rebuild the calendar. We wrote the inventory, sat through the argument, and left the implementation with their engineers.