Journey Atlas
Twelve weeks to design, defend, and operate customer journey reporting inside a real app. You bring a product. We bring critique, a grammar for paths, and a reporting cadence that survives contact with finance.
Who it is for
Product managers, analytics ICs, and growth leads who already ship an app and are tired of funnel slides that hide retries. You should be able to query your event stream or work beside someone who can. We do not teach SQL from zero.
Engineering partners are welcome. Marketers who only need campaign tagging usually find the Taxonomy Atelier a better fit.
What you leave with
- A living event dictionary with owners and deprecation rules
- A path model that includes loops, backgrounding, and payment retries
- A drop-off diagnosis that separates bugs from product problems
- A two-page narrative plus chart pack, written for humans
- A monthly reporting cadence with named readers and decisions
Modules
Event inventory and naming contracts
Catalogue what you fire today. Name collisions, duplicate “view” events, and campaign tags that leaked into product schema. You draft a contract: required properties, forbidden properties, and who may add a new event.
Identity and session stitching
Anonymous to logged-in joins, family-shared devices, and what a “session” means when Thai users background the app to copy a PromptPay reference. We will not pretend one user equals one phone.
Path grammar without vanity loops
Allowed states, illegal shortcuts, and how to draw backtracks so they remain visible. Default Sankey charts are treated as a first draft, not a deliverable.
Drop-off diagnosis
Where volume dies, which deaths are instrumentation, and how checkout retries should appear. Thai payment flows are a standing example, not a special guest week.
Reporting packs for product and growth
Two pages of narrative, a small chart set, and a decision log. If a PM cannot defend the pack in stand-up, it goes back for another pass.
Governance: what not to track
Privacy, retention windows, and the discipline of deleting events. A journey report that vacuums every tap is not sophisticated; it is a liability.
Instructor
Pichaya “Pim” Thongchai
Pim spent nine years in product analytics in Bangkok, including a stretch owning checkout instrumentation for a payments-heavy consumer app. She moved the teaching desk to Koh Chang in 2021. She still reviews every Atlas homework herself; guest readers join for Android identity and subscription windows.
Teaching language is English. Thai product examples are first-class. She is precise about sloppy event names and will say so in writing.
Informational fee
THB 62,000
Atlas Desk includes twelve live seminars, office hours, written critique, recordings for six months, Reading Room access, and twelve months in the alumni writing circle. Vendor licences and warehouse implementation are not included. This site does not take payment; we invoice after a seat is confirmed. See fees and refunds.
From people who sat the desk
Week four’s identity homework showed our iOS and Android “user_id” were not the same grain. Painful. Necessary. I still think the reading list could drop one of the older papers.
Arisa K. · PM, ride-hailing · Bangkok
Short version: we stopped presenting one funnel. Finance still got a number. Product finally saw PromptPay stalls.
Mira S., product lead
Questions we actually get
Do you teach GA4 or web analytics?
No. Journey Atlas stays inside mobile and in-app journey reporting. We will mention web only when an app opens an embedded browser. If your brief is a GA4 property rebuild, this is the wrong studio — that limitation is intentional, not an oversight.
How much time should I reserve each week?
Plan for one live seminar (ninety minutes) plus three to five hours of homework on your own event stream. Launch weeks are hard; recordings exist, but skipped critique does not get rewritten later for free.
Can my whole team join one seat?
One Atlas Desk seat is one participant. A second colleague may sit in on seminars quietly if you ask first; they do not receive homework critique. Teams who need a shared intensive should look at Island Residency.
What if our instrumentation is a mess?
That is a normal starting point. If names are so broken that path work would be fiction, we may suggest the Taxonomy Atelier first and credit part of that fee if you continue into Atlas within nine months.
Is there a certificate?
We will write a completion letter describing hours and artefacts for your L&D file. We do not issue a university diploma or a vendor badge.