Product Signal Atelier
Taxonomy, funnels that survive a rebrand, retention without vanity, and a critique of your live event stream.
Mattingley · Established teaching desk
Quiet numbers. Loud products.
App Analytics, taught as a craft rather than a tour of buttons: what to fire, what to ignore, and how to sit with a cohort until it stops flattering you.
A house position
Most dashboards are theatre. We teach the wiring.
Service Packetcore works with product people who already have a stack — Mixpanel, Amplitude, GA4, a warehouse, or a patchwork of all four — and still cannot answer a straight question about activation. The gap is rarely a missing widget. It is an event dictionary that drifted, a funnel that mixes intent with accident, and a weekly ritual of screenshots nobody trusts.
We teach from a studio in Hampshire, not a campus. Cohorts stay small. Assignments use your own app when you have one; when you do not, we lend a fictional mobility product with messy logs, duplicate user ids, and a marketing team that renamed “sign_up” twice last quarter. That is the real climate of App Analytics.
On the desk this season
Curriculum worth sitting with
Four programmes currently open for enrolment. The flagship atelier is the one we still rewrite between cohorts; the rest are shorter clinics for a single wound.
61programmes delivered since 2019
4.3mean score across 73 written reviews
19 daysmedian time to a trusted weekly readout
2,847events recatalogued with students
From the room
Voices after the homework
I arrived certain our Mixpanel project was “basically fine.” Helena made us print the event list and strike anything we could not define in one sentence. We lost forty-one events. Activation finally moved because we stopped counting a settings tap as intent.
Priya N. · Product lead, Bristol — Product Signal Atelier
★★★★☆
The Mobile Funnel Clinic is dense. I wanted more iOS-specific labs than we got. Still, the ATT walkthrough saved a quarter of paid spend we were attributing to a ghost campaign.
Client in grocery delivery · Manchester
How study proceeds
Four habits we insist on
01
Name before you chart
Every programme starts with a dictionary. If an event cannot be explained to a new engineer on day one, it does not belong in a north-star funnel.
02
Cohorts over snapshots
A pretty week is not a story. We train people to hold a cohort for thirteen weeks and to write down what would falsify their reading.
03
Critique in public
Work is shown to the room. The flattering interpretation is usually the first one we retire. This is uncomfortable; it is also why the work lasts.
04
UK privacy as a constraint, not a footnote
Consent, PECR, and store-level tracking changes are part of the craft. We do not teach a 2018 playbook and then whisper “check with legal.”
Journal
Recent studio writing
DAU is not a strategy
Daily active users still appear on Monday slides as if they explained a business. They explain a habit of opening an app. That is a different claim.
Naming events that outlive the sprint
A taxonomy is a social contract. Here is how we write one that a contractor can still parse eighteen months later.
Bring the messy project. Leave with a dictionary you can defend.
Fees are published without theatre. If the atelier is the wrong scale, write to us and we will say so.