Voices
These notes refer to programmes and modules on this site. We keep one reservation in the mix because a page of applause is not evidence.
★★★★★☆ · 8/10 on an internal tool we still use
The Funnel Leak Forensics way of labelling drop-off as “duplicate event with a nicer name” paid for the intensive. We found checkout_complete firing beside purchase_ok. Finance had been reconciling by gut.
Full name + role — Leila Hart, staff engineer, mobility
Week four of Retention Telemetry Studio landed in a release freeze. I skipped a live clinic and submitted the dictionary late. The slip was allowed once, as promised. I would still warn anyone on a locked branch: the homework does not notice your calendar.
First name + city — Jonah, Leeds
Came for Session Path Cartography because design kept asking why people “wander”. The map is now on the wall. I remain unconvinced we needed quite so much talk about sampling ethics, though legal was grateful.
Anonymous client in travel
Platform note · 4.1 / 5 from 17 in-house scores
Experiment Readout Craft stopped us publishing a win when the guardrail (time-to-first-article) had quietly worsened. The memo template is the artefact I still paste into Notion. The live session overran by twenty minutes.
N. Okonkwo · editorial product, London
Case note 01
A Manchester delivery company arrived with two activation events: one from growth, one from core. Studio Bench made them write both inclusion rules on a single page. After the dictionary shipped, week-one retention dropped by a number they had never shown the board — not because the product worsened, but because the polite definition retired.
They kept Open Ledger afterwards for the templates. They did not take Patron Circle; the politics cooled once the nouns matched.
Case note 02
Under a hospital NDA, a digital health seat used the sandbox commuting app for the whole studio. The transfer still worked: they rebuilt identity joins on the sandbox, then applied the same ownership map to their private schema without exporting a row. The limitation they named in the final readout: they could not prove a production leak in class, only a method.
Margot marked the method. Their CPO later wrote that the deprecation log was the first analytics document engineering agreed to keep in the repo.
