Product Signal Mapping
The core craft: event grammar, property discipline, journey overlays, and a readout that a director can follow without a translator.
The table of work
Each programme is a short, marked sequence. You submit maps; we return them with a red pen. None of these pages sell a payment — they describe the work so you can decide whether the desk is for you.
The core craft: event grammar, property discipline, journey overlays, and a readout that a director can follow without a translator.
Build cohort charts that behave like a forecast. You will learn why a 30-day curve can look healthy while a Tuesday-installed slice is already cold.
A leaking conversion path is rarely a single villain. This studio hunts dropped properties, duplicated steps, and SDK silence after a release.
Write an experiment note that names the decision, the guardrail, and the thing you will not claim. Aimed at product pairs who present to sceptical leads.
iOS and Android sessions refuse to behave like web. Map backgrounding, permission prompts, and store-install provenance without inventing ghost users.
Tell us the app, the stack, and the argument you keep losing in meetings. We will point to a programme or tell you honestly if you need an engineer before a course.
Ask the desk