Naming law
Object, action, and tense. Why prefixing every event with User is usually a confession that nobody owned the noun. Students rewrite twelve events from a provided “haunted” catalogue.
Flagship programme
The Release Lattice
Ten weeks in which your app’s catalogue is treated as a bound book: named, versioned, and occasionally retired in public.
What you leave able to do
- Propose a naming grammar that covers a new screen without inventing a second dialect.
- Log each production release as an event with a version, owner, and dual-write window.
- Choose cohort windows that match how your product actually sleeps, including weekend quiet.
- Document identity joins as lossy, including iOS reset and a shared household tablet.
- Hand engineering a deprecation note instead of silently overwriting history.
This is not a click-path certificate for a single vendor. Interfaces move; a poorly named signup_success follows you for years.
Modules
How the ten weeks are spent
The release as an event
Ship notes are not a Slack habit. We model version, surface, and rollback as first-class telemetry so a later cohort can be cut by what actually landed.
Property dictionaries
Types, enumerations, and the difference between a missing property and a legitimate null. The dictionary becomes a contract QA can fail a build against.
Identity without theatre
Anonymous IDs, known users, and the household iPad. We measure what a stitch drops, then write the caveat in language a trustee could read.
Cohort windows
D1, D7, and “returned in the billing month” are moral choices. Students pick windows that match the product, then defend the people those windows ignore.
Dual-write and deprecation
When an event’s meaning shifts, history is not a suggestion. Students draft a notice with an overlap window and a date the old name dies.
Warehouse and console in one sentence
How to keep a vendor screen as a drafting table while the warehouse remains the filing cabinet. Light SQL, heavy discipline.
Paywall telemetry after review
Store rules change the events you are allowed to fire. We practise a catalogue that survives review without going mute on trial conversion.
Student catalogue critique
Each seat presents a real or reconstructed slice. The room annotates; the instructor does not rescue a weak name.
The board paragraph
A lattice is not an argument until someone writes the sentences that should sit above it. Alumni leave with a paper, not a screenshot.
Instructor
Imogen Fairley
Imogen taught measurement inside a Glasgow subscription fitness app for seven years before opening the Cobleland house. She still marks catalogues with a pencil. She does not consult on ads buying, and she will not pretend a last-click graph is a climate.
A limitation you should know
What this programme will not cover
We do not teach web analytics, GA4, or server-side tag managers for marketing sites. We do not implement your warehouse. Students who arrive hoping for a Mixpanel certification leave disappointed — and we would rather say that here than in week three. SQL appears, but as a reading skill, not a bootcamp.
Questions we are asked
Before you write
Can two colleagues share one Lattice Seat?
No. Critique does not clone. A second person needs a second fee, or they may sit in an Observation Gallery Pass and listen without presenting.
Must I bring live production data?
No. A reconstructed or redacted catalogue is welcome. You must not submit personal data of end users you are not entitled to process.
Is there a certificate?
You receive a letter stating that you completed The Release Lattice and the dates. We do not sell badges, and we do not guarantee a commercial lift.
What if my product is mostly a website?
This is the wrong house. We will say so in the first reply and will not take a fee to discover it later.
“Week six of dual-write was slower than our engineering calendar wanted. The overlap still saved a quarter of history we would have overwritten.”Priya Shah · Principal PM, Leeds fintech · The Release Lattice
★★★★☆ 4.2
“Marked like a dissertation. I wanted more warehouse hours than they give.”Anonymous · client in health tracking
“Imogen made us retire three activation events that had been reporting a tick while measuring a paint job. I did not enjoy the afternoon.”Marcus, Bristol