They sat with our Android lead and clicked the live wrapper, not the Figma file. Eleven screens we still ship were silent in the property. That list arrived before freeze, which is the only reason engineering had time to name them.
What people said after the inventory, not after a launch party.
These notes refer to a specific engagement. We keep company names off the page unless a team asks to be named; the work itself is specific enough.
I asked for a continuous year-on-year line. They refused. The brief instead gave us a seam date and the three events that did not survive the native rewrite. Finance grumbled; the board pack was at least accurate.
The cutover week note told us which Monday chart to footnote. We still had a noisy first weekend — testers reinstalling the build — but we did not spend that weekend inventing a story about ‘lost users’.
The mapping sheet looked fussy until the destination vendor rejected Malay characters in two event names. We renamed them on purpose instead of discovering the hole in the first Friday report.
Half a day in the room was enough. They would not let us skip the identifier question. Our iOS and Android leads left with the same definition of a returning person, which we had never written down.
Longer note
The wrapper that still owned Ramadan
A George Town commerce team came three weeks before they hoped to freeze two native clients. Leadership still quoted a Ramadan funnel whose event lived only on the hybrid bridge. The baseline did not add that event to the rebuild; it named the chart that would have to be retired if engineering left it off the list.
They shipped without the bridge. The board pack carried the footnote. Product later said the harder conversation was the right one — they had been close to asking finance for a reconstructed comparison that would have been fiction.
The reservation we still hear, and take seriously: a baseline can feel slow when freeze is already printed on a wall calendar. Daniel Khoo in Klang Valley wanted a smooth year-on-year line; we would not draw it. That tension belongs on this page because it is part of the work.
Read the three-week Penang noteA second room: freeze week without a ghost-user story
Siti’s release group had testers wiping builds all weekend. Session counts jumped. The cutover note had already warned that reinstalls would mint new identifiers. They used the note on Monday instead of opening an incident about lost users. The destination property was still messy; the explanation was not.
If you want a similar brief
Send the app name and the freeze you are protecting. We will say whether a baseline, a cutover note, or a session is the honest next step.
Write to the practice