Brook Street studio · est. 2018

Draw the week a user actually lives, then argue about the product.

Schema Flowgrid is a teaching studio for Lifecycle Analytics for Mobile Users. We train analysts and PMs to rebuild retention as a map of windows, not a single curve that flatters the board pack.

See the current programmes

Hands holding a phone while reviewing a product interface
Field notes from a cohort clinic: the interesting drop is rarely on day seven.
38 Published cohort libraries used in class
11 weeks Flagship cartography lab, not a weekend crash
2,140 Analysts and PMs through the studio since 2018
4 clinics Public office hours each quarter, United Kingdom time

Notes from people who sat the lab

Full alumni page

I arrived with a beautiful activation dashboard and no idea why week-three paying users looked identical to week-three tourists. The Cohort Cartography worksheets forced us to split those groups before we touched SQL. The homework load is heavier than the marketing page admits, and I missed two live clinics. Still, the map we left with is the one our growth lead actually opens on Mondays.

Leah M., product analytics, Leeds

★★★★☆

Useful if you already own an event taxonomy. Less magic if your logging is a mess — they say that up front in module two.

Platform review · “lifecycle-lab-uk”

Programmes in the current term

All programmes
Analytics charts on a monitor

Flagship · 11 weeks

Cohort Cartography

Rebuild retention as labelled windows, including the awkward ones your current board metric hides.

Laptop with spreadsheets on a wooden desk

Short studio · 4 weeks

Activation Windows

Find the first 72 hours that actually predict a second week of use, without inventing a north-star overnight.

How the studio teaches

We grade maps, not slide polish.

Each cohort arrives with a live or archived mobile product. You leave with a documented schema: who is in the frame, which events are allowed to define a window, and which claims you are no longer willing to put in a QBR.

The method page walks through the same sequence we use with GB-based product teams who cannot wait for a perfect warehouse.

Read the lifecycle method

Small team reviewing notes around a table

What changes after a term

  • Windows instead of averages Day-N retention is treated as a family of windows with owners, not a single percentage that moves when you change the timezone filter.
  • Event discipline You learn which properties may define a cohort and which ones merely decorate a chart. That stops “power user” from meaning five different things in Slack.
  • A written limitation Every map we accept includes a paragraph on what the data cannot see — store reviews, offline usage, family-shared devices.

From the journal

All essays

Bring a messy event table. Leave with a map you can defend.

If you are hiring for Lifecycle Analytics for Mobile Users and need a shared language across product and data, start with the fee sheet or write to the studio.

Write to Brook Street