We arrived with 400 events and left with 71 that had owners. The Event Grammar week felt pedantic until a release renamed a screen and nothing in the warehouse broke. I would still like more time on warehouse modelling; the Studio treats SQL as a means, not a subject.
What people said after the red pencil.
These notes are edited for length, not for glow. Where someone asked to stay unnamed, we kept the industry. Every remark points at a module or artefact from this house.
★★★★☆
Funnel Integrity (module 04) is the reason I recommend the Studio. The identity week was thinner than our use case — we have family accounts — and Priya said so rather than bluffing. That honesty is why the four stars, not five.
The dictionary from Governance week is the only internal doc our new iOS contractor opened without a meeting. I came sceptical of “studio” language. The work is just careful naming.
Attribution After the Cookie did not make SKAN pleasant. It did stop us from presenting a last-click slide to the board as if it were physics. I wanted a template for finance; there isn’t one, and they were right not to fake it.
Experiment Readouts taught me to write the sentence “the interval still includes harm” without sounding like I was blocking the roadmap. Two evenings assumed more statistics than our design lead had. We survived. I would sit the seminar again after a noisy launch.
Longer notes
Two case studies
When “order_placed” meant three different things
A mid-size delivery app had split checkout across native and a webview. Their north-star counted a client event that fired when the thank-you screen rendered, including failures that later refunded. During Product Telemetry Studio they moved the mint to the server on payment capture, split refunded orders into a separate event, and published the old definition as a deprecated footnote for six weeks so finance could reconcile.
What did not change: their paid-acquisition reporting. That work was out of syllabus, and they booked the attribution clinic later. The honest limitation is that eight weeks did not touch creative or bidding.
Retention captions that survived a sceptical COO
The company presented a rising D30 curve that mixed weekly and monthly reporters in one cohort. Retention as a Narrative made them split the two products, define “active” as a write action rather than a session, and write a 120-word caption for the board pack. The curve looked less flattering. The COO kept the new version because it matched support-ticket volume.
They still do not have a clean identity graph for shared inboxes. The atelier named that gap; it did not close it.