Silent-exit week forced us to treat “verify later” as a dead end, not a clever deferral. Our first-week map lost two fake steps and gained one honest pause. I still disagree with Nalinee on how strictly we should name in-app messages as steps, but the dictionary is now something I can hand to engineering without apology.
Flagship · 11 weeks
Path Cartography Studio
One live app surface. One pruned dictionary. One map with named dead ends. Taught from Khlong San for product and analytics people who are tired of funnels that only look like journeys.
What you walk out with
- An event dictionary for one surface with aliases retired in writing
- A path map that distinguishes steps from screens, including at least two silent exits
- A twenty-minute review script your PM can interrupt without the map collapsing
- A one-page limitation note: what this map is not allowed to claim
We assume you already ship events. If you have never instrumented an app, start with Funnel Grammar for Mobile Screens, then return.
฿47,800 per seat
Eleven Thursday sessions (18:30–21:00 ICT), plus two Saturday labs. Remote seats join the same clock. No checkout on this site — write the desk to reserve a seat.
Modules
- Week 1–2 · Event inventory without the graveyard Export, dedupe, and kill names that only exist because a redesign renamed a button. You cannot map what you will not name once.
- Week 3 · Path versus pageview A tap is not automatically a step. We mark decorative UI and keep only decisions that change the next option.
- Week 4–5 · Silent exits and dead-end screens “Complete later,” empty states that look finished, and the KYC pause that never returns. Field examples from Thai fintech and ride-hailing.
- Week 6–7 · Stitching anonymous sessions in SEA markets Shared devices, prepaid SIMs, and login that arrives late. We stitch only after the dictionary is clean.
- Week 8 · Cohort walks you can defend How to take a single cohort through the map without collapsing into one conversion percentage.
- Week 9 · Presenting maps to PMs who only want conversion A review format that survives interruption. You practise on your own surface, not a toy dataset.
- Week 10 · Limitation week What journey maps cannot claim: LTV, churn scores, and “this button caused that revenue.” We write the refusal into the deliverable.
- Week 11 · Public critique Each seat presents. Mentors and peers mark dead ends you still dressed up as progress.
Instructor
Nalinee Srisawat
Nalinee led product analytics for a Bangkok super-app’s first-week loop before founding the Path Cartography desk. She still draws maps on paper before she trusts a chart, and she will stop a review if you call a pageview a journey. She teaches the flagship in Thai and English; written deliverables are in English.
Guest critics rotate from Chiang Mai product teams and a Khlong San research studio. They are not “influencers.” They mark dead ends.
FAQ
Do I need SQL or a specific analytics vendor?
No. Bring exports from whatever you already use. We care about names and sequences, not about your warehouse brand. If you cannot export at all, wait until you can — the studio is not a tooling class.
What is the real limitation of this course?
Path Cartography Studio will not teach you to predict LTV, score churn, or automate retention campaigns. If your brief is a propensity model, look elsewhere. We stop at the map, the dictionary, and the review script. Week 10 exists so you do not oversell the work to your own company.
Can a whole squad join?
Yes, up to three seats from one surface. Beyond that the critique hour collapses. Write the desk; we will say no if the room would be too crowded.
Is the fee refundable?
See the refund policy. Seats cancelled more than fourteen days before the first Thursday are returned in full. After that, partial rules apply. Nothing is charged on this website.
Seats who already sat
★★★★★☆☆ · 7/8 on the internal desk board
Limitation week was the part I did not expect to need. We almost claimed the new KYC screen “drove” activation. The critique stopped that sentence. The studio is slow on purpose; if you want a dashboard makeover in a fortnight, skip it.