Event names as contracts
You leave with a naming sheet that product, data, and mobile can keep after the next reskin. We mark ambiguous verbs in red during critique, not after launch.
Glympton studio · Path Analysis for App Users
Most dashboards describe the path you hoped people would take.
We train teams to reconstruct the route a person actually walked: skipped screens, retraced taps, and the silent exits that never appear in a three-step funnel.
See the flagship studio63 product squads have sat a full mapping week with us since 2019.
11 weeks is the typical span of the flagship studio, including critique.
28 archived UK session libraries used as teaching material (anonymised).
2 tutors in the room for live path walkthroughs — never a lone webinar host.
What people said after they shipped a tracing change
Each note refers to a module from this studio, not a generic “course.”
“The session-stitching lab showed me why our Android and web cohorts never lined up. We still argue about taxonomy, but at least the IDs match.”
I expected a visualisation class. It is closer to instrumentation hygiene. The drop-off diagnosis homework was slow, and that slowness was the point.
Flagship
User Path Mapping Studio
A tutored programme for people who already have an analytics vendor and still cannot explain why users loop between settings and checkout. Modules cover event contracts, path vs funnel, and a written brief your engineering lead can reject or accept.
What we refuse to outsource to a template
Paths that include retreat
Back-taps, permission dialogs, and “later” banners belong on the map. A linear funnel that ignores retreat will always look healthier than the product.
Findings written for a backlog
We practise a one-page tracing note: observed route, missing event, proposed fix, and the screenshot evidence. No deck-only deliverable.
From the journal
Short essays used in class, expanded for public reading.
Reading session replay without inventing motive
Replay is evidence of motion, not of intent. A method for annotating pauses before you write a story about the user.
Drop-off is usually a path problem
When a step “loses” people, look at the routes that never entered the step, not only the people who left it.
Cohort funnels are not user journeys
Aggregates hide the loops that make support tickets. How we teach the two views to sit in the same meeting.