Client stories
What changed in the reports after the names were read
These notes mention a specific mismatch, a constraint, or a session. They are not scores. One of them records a limit of the engagement as well as the catalogue work.
They caught that our iOS build still sent checkout_start while Android had moved to checkout_begun after the April redesign. The funnel looked like Android users had vanished. They had not.
The rename map was the useful part. I had hoped they would also sit with engineering for the first sprint of fixes; that extra week was quoted separately, which I only understood after the findings workshop. The catalogue itself is the one we now edit.
After we joined two wallets into one app, purchase and topup_complete were both treated as the same conversion in a board report. The reconstruction listed owners and triggers so the argument stopped being tribal.
Harith went property by property through a sample where quantity arrived as a string on Huawei devices. That single type mismatch had been silently dropped for months.
The Seremban handover was two hours longer than the agenda because we argued about screen_view on the new onboarding. Worth the extra time; everyone left with the same list.
A longer note: the April checkout split
A Kuala Lumpur retail app redesigned checkout in April. Android and web shipped checkout_begun. The iOS release kept checkout_start because the ticket was filed against the visual work, not the event string. Weekly slides showed Android conversion falling. Lina Rahman’s team sent a fourteen-day production export with a source column. The validation pass listed the split on the first page, with timestamps that matched the Android store release, not a mysterious change in shopper behaviour.
They did not ask us to patch the iOS build. That remained their sprint. The useful artefact was the dated comparison: same screen, two names, one funnel that had become two. The same pattern appears whenever a product rename is treated as copy and not as a catalogue edit — which is why we keep a journal note on event names after a product rename.
After two wallets became one app
Priya Menon’s payments product joined a top-up flow from an acquired app with a native purchase flow. Board materials added the two conversions. Reconstruction listed owners and triggers so the argument stopped being about which squad “owned growth.” The leftover work was taxonomy cleanup, quoted as a separate stretch because historical series had to remain readable for finance.
If a similar split is sitting in your weekly deck, send the event names with the enquiry.