Module three forced a conversation with engineering I had been avoiding. We agreed that “plan_type” had three incompatible meanings. The sitting did not magically align the company; it made the disagreement visible.
Flagship programme
Eight weeks. A live product slice. Eleven hours of studio time. You leave with a taxonomy, a funnel that matches how people actually move, and a list of properties you are prepared to delete.
Outcomes
The Chart Table fee for this sitting is £1,180. Night Watch adds private hours at £2,640. Both are informational figures — request a place by writing to the studio. See fees and refunds.
Modules
You write what a future colleague must understand. If the sentence needs a screenshot of the UI, the name is already rotting.
Object–action patterns, forbidden interface words, and a glossary you will actually keep.
Enums versus free text, identity keys, and the politics of “just one more field.”
Steps that can fail for different reasons. Retry events that pretend to be success. The week students most often underestimate.
Anonymous to known, multi-device, and the quiet damage of a class-code or family account.
Which charts belong in a leadership room and which belong in an engineering ticket.
You propose events and properties to retire. The studio argues. Some of them stay retired.
A twenty-minute readout of your map. Miriam and two peers try to break it. You revise once.
From the room
Module three forced a conversation with engineering I had been avoiding. We agreed that “plan_type” had three incompatible meanings. The sitting did not magically align the company; it made the disagreement visible.
I wanted more time on warehouse joins. They would not give it, which was consistent with the limitation they publish. The taxonomy work still paid for the fee.
7 / 10
Excellent on naming. The live critique in week eight is sharper than the written materials. Bring a product you can actually change, or the homework feels theatrical.
Questions
No. Students arrive from Amplitude, Mixpanel, PostHog, and a few in-house stores. The sitting is about the map, not the click-path of a specific UI.
Yes. Event Cartography does not teach warehouse modelling, dbt, or reverse ETL. If your pain is in the pipeline rather than in the product analytics layer, this is the wrong room — we will tell you that in the first reply.
Two people from the same product can share a slice. Larger groups turn the map table into a status meeting, which we refuse. Night Watch is the path if a founder wants a private readout.
Recordings of the common lectures exist. The critique hours do not. Missing more than two of those usually means your taxonomy review is thinner — as Marcus in Manchester already reported on the voices page.
Place
Dates go out by email. Tell us the product surface you would bring.