9 Jan 2026 · Teams
How three Thailand teams ship a weekly mobile test without a data science bench
Not every squad has a statistician on Slack. Several Systemtracebase alumni still ship a contained mobile test most weeks. They do it by shrinking the surface, writing the memo before the variant, and refusing to run two listing changes at once.
Chiang Mai · tourism checkout
A four-person product group uses Funnel Wiring habits: one event dictionary taped above the kettle, a freeze on new events during a live test, and a Wednesday readout that lasts twelve minutes. They do not peek daily. The PM owns the corridor sample size; engineering owns assignment integrity after a hotfix.
Phuket · hospitality wallet
Traffic is seasonal and unapologetic. They only test in-app copy between monsoon shoulders, and they park listing experiments entirely in high season. Their “weekly” cadence is weekly in the desk calendar and fortnightly in truth. Honesty about cadence is part of the craft.
Bangkhunprom alumni · consumer utility
A squad that sat in our room now rotates who writes the one-page memo so the analyst is not the only person who can explain a flat result. They invite one person from support to the readout. Support tickets became a watch metric after a permission-prompt test spiked calls without moving opt-in.
None of this requires a platform team of twenty. It requires a ritual and a veto. That is what the studio drills.