What you should be able to do afterwards

  • Define install, user, and holding sets without mixing them in a dashboard filter.
  • Specify activation, habit, and lapse windows with allowed events only.
  • Produce a one-page limitation memo covering consent gaps and shared devices.
  • Defend the map in twenty minutes to someone who did not draw it.
Portrait of instructor Priya Nair

Priya Nair

Faculty lead. Previously analytics lead at a London payments app, now teaching full-time at Schema Flowgrid. She marks maps, not slide decks, and will fail a definition that treats a push open as activation.

Modules

  1. Event shelves

    Trusted, tolerated, forbidden. You submit an inventory from a real or archived mobile product. Faculty return it with red ink on autoplay and background events.

  2. Who is in the frame

    User identity, reset IDs, family sharing. GB examples include consent banners that suppress the very events you wanted for week-one windows.

  3. Activation without a paywall costume

    You propose a 72-hour window. If it is a paywall view, it comes back. The replacement must be an action the product needed anyway.

  4. Habit and lapse clocks

    Paper maps first. SQL second. We look at day-2 to day-5 drops that board packs skip because they are not a round number.

  5. Limitation memo and oral defence

    You present. A classmate restates your windows. If they cannot, you revise. Completion requires that restatement, not attendance hours.

Fee (informational)

Retention Studio pricing applies: £2,180 for the eleven-week lab, including seminars, office hours, and twelve months on the alumni clinic list. See studio fees. This page cannot take payment.

Questions we actually get

Do I need to be a SQL specialist?

You need enough SQL to join events to a user key and to filter on timestamps. Window functions help in later weeks. If you cannot yet write a GROUP BY, take Activation Windows first or pair with a teammate who can. We will not secretly turn this into a beginner SQL course.

What if our SDK is incomplete?

That is a common starting point. The lab will make the holes visible. It will not implement tracking for you. Teams who hoped faculty would “fill in events” leave disappointed, and we would rather say that here than in week six.

Is there a real limitation to this programme?

Yes. Cohort Cartography will not make a product with a weak core loop look retained. We can help you stop lying with averages. We cannot invent a reason for a person to open the app on a second Tuesday. Several learners have asked us to bless a notification cadence as a lifecycle strategy; we will not.

Can two people share a seat?

No. The oral defence is individual even when you work on one company map. Charter seats are counted per learner; see Lifecycle Charter on the fee page.

From people who sat this lab

Module two on family-shared iPads saved us from a fake teen cohort in a learning app. Priya’s notes are blunt. I still think the oral defence is too short for a messy warehouse, but the limitation memo is the artefact our legal team kept.

Jonah Reid, lifecycle analyst

Quiet student, Glasgow. I did not speak much in seminars. The marked paper map was still useful. Push-cadence discussions in week five felt rushed.