Service model
Measurement playbooks
Repeatable sequences we use on engagements—so your team can keep the discipline after we leave.
-
Surface-first event design
Pick one product surface. List user intents before UI widgets. Assign an owner and required properties on the same day the name is coined.
-
Live-stream path walk
Reproduce one conversion path on real devices while watching the event stream. Log silent misses with reproduction steps before anyone debates product copy.
-
Identity continuity sweep
Trace anonymous-to-known stitching across web, app, and login. Flag timezone cutoffs that invent new cohort days for Korea-based calendars.
-
Release replay checklist
After each ship, rerun the path script and confirm step events still fire. Treat a failed replay as a release defect, not a product insight.
-
Frame the decision
We open with the shipping question you cannot answer cleanly—disputed funnel, drifting retention, or a surface about to ship without agreed events.
-
Apply the matching playbook
Blueprint, path verification, or continuity review—whichever fits. Scope stays narrow so artefacts arrive while the decision is still open.
-
Handoff and optional office hours
You keep the sheets and scripts. If the next sprint needs a steady review voice, Measurement Office Hours continues the same playbooks monthly.
Ready to apply one?
Most teams begin with a Product Event Blueprint. If a single conversion path already argues with reality, ask for Conversion Path Verification instead.