Session two’s stage contracts stopped us from treating “viewed pricing” as progress. Our trial users were window-shopping on a public page.
Ploy R., product researcher · Bangkok
Flagship · Map Room Seat
Journey Signal Lab
Six weeks to take one live product surface from a messy event list to a versioned journey atlas, with critique in the room. Informational fee: ฿24,500 per person. Payment is arranged by invoice, not on this page.
Learning outcomes
By the last session you should be able to:
- Define journey stages from observed behaviour, not from the sitemap.
- Score friction against the cohort that was eligible to continue.
- Write an event taxonomy that a new analyst can extend without a meeting.
- Run a thirty-minute critique on someone else’s atlas using the studio rubric.
- Name instrumentation gaps without pretending class will close them all.
Who it fits
Product managers, researchers, and analysts who already have access to an analytics tool or warehouse. Designers are welcome if they can query or pair with someone who can.
It is a poor fit if you need SQL tutoring or a vendor implementation sprint. We will not configure Mixpanel for you.
Modules
- 01
Belief before evidence
Write the journey you think exists. Then watch ten sessions that disagree. We keep both versions on the wall.
- 02
Stage contracts
Each stage gets an entry event, an exit event, and a rule for who was eligible. Vague names get retired in critique.
- 03
Friction with a denominator
Drop-off charts without eligibility are theatre. You compute friction only for people who could have continued.
- 04
Handoffs and off-product time
Support tickets, sales calls, and warehouse waits enter the atlas as first-class columns.
- 05
Taxonomy hygiene
Rename, merge, and kill events. Produce a one-page dictionary your engineers will actually open.
- 06
Versioned atlas + critique
Ship v1.1 of your map. Sit through a public critique. Leave with a recording and a punch list.
Instructor
Waranya Srisuk
Waranya leads critique at Apifeaturegrid. She spent eight years in research and analytics at two Bangkok marketplaces before opening the studio in 2019. She still refuses to let “activation” stand as a stage name unless the team can say what the user can do next.
Guest reviewers join two sessions per cohort. They are not a substitute for Waranya’s rubric.
Informational fee
฿24,500 per person · Map Room Seat
Includes six live sessions, critique of one atlas, Field Ledger recordings, and alumni critique invitations for a year. Does not include tool licences, engineering time, or travel to Chakrpong Road.
Field Ledger alone is ฿8,900 if you only want recordings. Signal Desk is ฿68,000 per quarter for teams. See fees for the comparison.
Ask about a seat
FAQ
Do I need a specific analytics vendor?
No. Bring whatever you already query. We speak in events and cohorts, not in a single UI. You will be lost if you have no data access at all.
Is there a real limitation I should know?
Yes. Journey Signal Lab does not teach Mixpanel, Amplitude, or BigQuery syntax in any depth. If your instrumentation is broken, we will help you describe the break; we will not write the tracking plan implementation or merge your pull requests. Teams without an engineer on call often leave with a clearer atlas and the same unfixed pipeline.
Can two people from one company share a seat?
No. Each seat is one person. Signal Desk includes two Lab seats if you need a pair.
What if I miss a session?
Recordings go to Field Ledger within forty-eight hours. Critique of your own atlas cannot be fully made up; we will offer a short written note instead.
From recent Labs
The homework in week three collided with a release freeze. I turned it in late and still got a useful critique, but I would not plan a launch in the same month as the Lab.
Client in digital banking
★★★★★
Waranya would not let us keep “delight” as a column. Painful, correct, and now our atlas actually matches support tickets.
Platform-style note · April 2026 cohort