Reviews

Not all of it was comfortable. That is in the record on purpose.

These notes refer to programmes that exist on this site. We keep one reservation in the mix because a wall of praise is usually a tracking plan with no owner.

After Event Grammar I could walk an engineer through why `button_click` had to die. We shipped eight replacements in a sprint and stopped arguing about the activation board.

— Helen Okoye, Head of Product, Bristol

The Quiet Dashboard Audit removed a tile I had been defending for a year. I was annoyed for a week. Then the Monday meeting got shorter.

— James, Manchester

★★★★☆ · 8/10 on a private alumni card

Studio sessions ran long. The retention landscape work was the piece I still use. Would have liked a cleaner template for the final readout; Miriam refused, which I now understand and still mildly resent.

— Verified seat, Cohort Telemetry Studio, spring term

We came for Retention Cartography expecting a prettier curve. We left with two cohorts we had been accidentally merging, including a TV spike from last autumn.

— client in grocery delivery

Field Notes came back denser than I wanted on a Sunday. The marked-up events were fair. I used three of the five recommended cuts.

— Sofie N., Copenhagen

Two longer notes

A product team in conversation around a laptop

Case · subscriptions, United Kingdom

The activation path that was three paths

A membership app arrived with a single “activated” flag set whenever a user opened the home feed. Cohort Telemetry Studio, module three, forced a split: opened feed, completed a saved-item, and started a billed period. Only the third predicted month-two presence.

The team did not raise conversion. They stopped congratulating themselves for feed opens. Finance accepted a narrower number because the inclusion rule could be read in a sentence. The reservation, from their PM: the Studio timetable collided with a launch freeze, so two homework passes were thin.

Colleagues reviewing work together at a long table

Case · health tracking, remote team

Seventeen events retired in a residency

Event Taxonomy Residency spent the first morning listing events that fired from a discarded onboarding. Nobody owned them. The afternoon was a grammar: object, action, context. By day three the warehouse views were still messy, but the implementation ticket was boring in the way good tickets are.

Six weeks later they wrote to say the new names survived a second product line — a companion wearable — without a second vocabulary. That letter is why the residency still opens with a funeral for unused events.