Activation KPI Design in five artefacts, not a poster.

1. First-value verb

Activation is the first action a new user would recognise as “the app working.” It is not a session, not a permission grant, not an impression. In Thailand we often land on things like first PromptPay receive, first completed ride with a rating skipped or given, or first listing with a photo and a price. If two people on the team cannot say the verb in one breath, it is not ready.

2. Cohort window with a written why

The clock starts at a named origin event (usually first open after install, sometimes KYC pass). The window is 24 hours, 7 days, 30 days, or a custom clock tied to a real cadence — payroll day, weekly market, monthly bill cycle. We write who is harmed if the window is too short. Grocery and ride-hailing can live on 24 hours. Wealth and insurance almost never can.

3. Three-layer tree, twelve events or fewer

Layer A is the activation KPI itself. Layer B is the two or three precursors that must happen. Layer C is the quality gates that block first value (camera permission, KYC failure, empty search). Everything else — feature adoption, upsell, referral — lives on another dashboard. Event sprawl is how activation dies in Mixpanel.

4. Counter-metric

A number that would rise if someone cheated the KPI: share of first-value events fired from a forced modal, average seconds on screen before the event, refund rate within 24 hours. Without a counter-metric, a prompt can “fix” activation overnight.

5. Friday review, forty-five minutes

Cohort size, activation rate, counter-metric, one surprise, one decision with an owner. If the meeting needs a war room, the tree is still wrong. This ritual is taught in the flagship studio and in Weekly Activation Review Rituals.