The Activation Windows module forced us to drop a seven-day proxy we had defended for two years. Painful. Correct.
Flagship laboratory
Activation Signal Laboratory
Twelve weeks to stop treating “signed up” as a product moment. You will leave with a written activation contract, a marked tracking plan, and at least one chart you are no longer willing to show the board.
Learning outcomes
- Define first value in language a new PM can defend without the founder in the room.
- Specify qualifying events and explicit exclusions (shared devices, internal testers, failed payments that retry).
- Instrument the activation path so a warehouse query reproduces the dashboard number.
- Write a board-safe note that includes lag, uncertainty, and the thing the metric still cannot see.
- Run a critique on someone else’s tracking plan using the studio’s markup conventions.
Modules
-
The lying proxy
Audit the activation metric you currently report. Most teams discover it is a funnel step invented for a pitch deck. You will document why it survives politically.
-
First value on the page
Write the job the customer would miss. Map it to screens, not to marketing language. Thai payment and LINE-first onboarding patterns are treated as defaults.
-
Activation windows
Choose a window that matches arrival rhythm. We kill automatic D1/D7 copies unless you can show the product is actually used on that cadence.
-
Event specification
Name, owner, trigger, properties, failure cases. You will submit payloads that we reject on purpose so you learn the review bar.
-
Path instrumentation
Wire the contract to live events. Guest engineer hour included for Signal Circle seats. Desk Trace students annotate a plan without live marking.
-
Readout and defence
Produce a two-page activation readout. Operator guests ask the questions your board will ask. Inconclusive results are a passing grade if the writing is honest.
Instructor
Anya Sutham
Anya leads the Activation Signal Laboratory. She spent a decade in consumer fintech product in Bangkok, including two years owning onboarding measurement after a painful KYC rewrite. She marks tracking plans like manuscripts: too vague, vendor-shaped, or claiming a moment the event cannot see.
She does not teach vendor certification. Students who need Amplitude notebook syntax or Mixpanel JQL are pointed to their own data team or a specialist clinic.
Informational fee
As part of Signal Circle, the laboratory is ฿47,400 for twelve weeks and six seats. Recordings alone sit inside Desk Trace at ฿18,900. Observatory teams may buy the activation contract work as part of a quoted quarter. There is no checkout on this site — write the studio if a seat is open. See access and refunds.
Questions we actually get
Do you teach Amplitude / Mixpanel / PostHog specifically?
No. This is a real limitation, not a humble-brag. The laboratory is vendor-agnostic. We will look at screenshots from whatever you use, but we will not certify SQL dialects, notebook syntax, or a CDP implementation. If that is what you need, budget a separate internal workshop.
Can I join without an engineer?
Yes for Desk Trace. For Signal Circle, an engineer at office hours is strongly recommended. Without one, you will finish with a precise document and an unchanged production tracker. Several alumni have said that mismatch was the painful part.
Is English the working language?
Yes. Intensives in Bangkok are also run in English. We do not currently offer a Thai-language cohort; if that changes it will be listed here first.
What if my product is B2B with a long sales cycle?
Activation still exists; it just is not a consumer “aha.” We have run the laboratory with HR, logistics, and developer-tool teams. You will spend extra time on seated vs. champion activation, which consumer templates ignore.
From people who sat the laboratory
I wanted more live SQL hours than the timetable allowed. The workbook covered the joins; it did not replace a dedicated warehouse coach. Still the only laboratory that made our event dictionary readable by design.