Client stories
These notes are from people who sat through a readout or a workshop. They mention the work we actually did. Ratings widgets would not add anything useful here.
They noticed that our new split-bill step was opened by night-shift cashiers and almost never by the lunch rush. We had been arguing about button colour. The hour was the actual story.
Nurul H., operations lead, Klang Valley food-order app — feature adoption study
The launch readout was shorter than I wanted. Two pages, no theatre. It did stop us from calling the first afternoon a success when the rest of the week was empty.
Arjun P., product owner, neighbourhood retail app — launch readout
I still think they asked for too many interviews with parents who never opened the sports thread. Those calls were awkward. They also changed what we told teachers to write in the old broadcast.
Farah M., school-app coordinator, Selangor — feature adoption study
The event map review embarrassed us in a useful way. Our rest timer and end-shift confirmation shared one overflow tap. We had been celebrating a menu open as if it were rest.
Wei Ling, dispatch lead, ride-hailing crew — event map review
A longer account: the savings pocket
A digital wallet team in Petaling Jaya asked us to read a new savings pocket six days after launch. We refused the six-day window and waited through a payday Friday. First-open counts were already in their slides. Money actually moved into the pocket for a thinner group, mostly people who already kept a separate envelope habit offline.
The written account named that group and named the people who opened the pocket, looked at the number, and left it empty. The team did not add a second pocket. They changed the first explanation on the screen so that “open” and “put money in” were no longer treated as the same act in their own meetings.
If your story would need us to invent a score out of five, we would rather not publish it. Commission the work instead, then decide what you are willing to have said aloud.