A three-week baseline with a George Town product team

The team sat a short walk from our Patani Road room. Their wrapper had been patched through several festive campaigns. Each campaign had left event names in the property — some in English, some in Malay, some with a year suffix that nobody stripped. The destination plan was two native clients sharing one new property.

Week one was the inventory. We sat with the Android lead and clicked every reachable screen in a production build, writing the visible title and the string that actually arrived in the property. Eleven screens fired nothing. Four fired a name that did not match the title. The Ramadan funnel leadership still quoted used an event that only the wrapper’s JavaScript bridge emitted.

Week two was the awkward conversation: the native rebuild had no bridge, and nobody had put that campaign event on the engineering list. We did not add scope to the rebuild. We wrote it into the baseline as a break, with the exact Monday chart that would need a footnote if they shipped without it.

Week three was the walkthrough. Engineering left with a one-page list. Product left with the sentences they would use in the board pack. The move still happened. The Ramadan comparison was retired on purpose rather than ‘fixed’ in a spreadsheet. That, for us, is a successful baseline: fewer surprises, and the surprises that remain are named.