“Week four assumed more join comfort than I had. I still left with a version-filtered crash view our iOS lead would defend.”
Priya N., product analytics, Leeds
Flagship · nine weeks
Release Pulse Atelier
A live table for people who ship mobile versions and then cannot explain, on Monday, what the numbers were allowed to mean.
What you leave with
A ledger you will still use after we stop marking it.
You will be able to write a one-page Ship Signal for a version: hypothesis, three signals, one reservation, next action. You will know which store and crash delays make a 72-hour claim dishonest. You will present that page to someone who did not live the sprint.
You will not leave certified in a vendor. You will not leave with a tagged production app — that work stays on your side of the wall.
Modules
What the nine weeks actually hold
01
Name the ship
A one-line hypothesis that a sceptical engineer will not laugh at. If you cannot write it, we do not open a chart.
02
The 72-hour window
Which signals are even eligible before store lag and crash sampling settle. Practice on a sealed Chester health-tracker dataset.
03
Event grammar after a bump
Versioned events, deprecated names, and the damage of a silent rename. You will retire at least one sacred event.
04
Retention that survives a review
Calendar versus rolling windows. Why D1 after a store feature is not the same D1 as last Tuesday.
05
Crash-free without theatre
Filter to the new binary. Separate ANR from crash. Write the reservation when the sample is thin.
06
Funnel honesty
One claimed step, not a cathedral of drop-offs. Unnamed screens are treated as a defect, not a mystery.
07
Monday ledger
The page format used across the house. Sentences first. Plots as exhibits.
08
Presenting to a sceptical PM
Twenty minutes, no slide wallpaper. You practise on each other before week nine.
09
Limits of the method
What Ship Signal cannot carry: competitor ranking, quarterly OKRs, or a missing consent flag. We end on what to refuse.
Instructor
Dr Miriam Calder
Miriam spent nine years as analytics lead on a Chester health app that shipped every other Thursday and argued every Friday. She designed the first Ship Signal page after a crash-free dip was presented as a “seasonal dip” to a board that deserved better.
She marks ledgers herself. She will not pretend SQL is optional in week four; if that is a problem, Taxonomy Desk or Session Notes may be a kinder door.
From the table
★★★☆☆
The cold-reader exercise is bruising if your hypothesis was theatre. I wanted more vendor walkthroughs; the house refused, which I now understand.
Platform note · 3/5 · Release Pulse Atelier
Questions we actually get
Do I need to bring my own production app?
No. If you cannot share events, we issue a sealed dataset. If you can share, we still will not log into your tools for you.
Is this a Mixpanel / Amplitude / Firebase course?
No. Concepts transfer. Screenshots of a specific vendor are used as exhibits, not as a syllabus. If you need a button-by-button vendor course, look elsewhere.
What is the real limitation?
We cannot repair a missing consent implementation or an unnamed screen inventory in nine weeks. If your first-open event is not fired for a large share of users, the 72-hour window will look empty and we will say so. The atelier does not include engineering time to fix instrumentation; that remains your team’s work, and several students have left week two with a longer backlog than they arrived with.
Can I pay on this website?
No. Fees are informational. Seats are confirmed by email from Ashton.