How I work
Fixed scope, written deliverables, few meetings.
The same four steps every time. The diagnostic covers the first three in ten business days. Stewardship is the fourth, and it is optional.
Align
Days 1-3
Before: Everyone defines success differently
After: A KPI tree your whole team agrees on
Interview the people who make product decisions. Map the flows. Write down what success means.
Instrument
Days 4-7
Before: Events are missing, broken, or meaningless
After: Reliable events with clear naming and owners
Design the event schema. Set up QA. Ship tracking that means the same thing to everyone.
Ship
Days 8-10
Before: Dashboards exist but nobody uses them
After: The few dashboards people keep opening
Build the activation, retention, and core metric views. Train your team. Present to leadership.
Steward
Ongoing, separate agreement
Before: Analytics quality degrades over time
After: Definitions that stay true as the product changes
Monthly reviews, measurement plans for releases, and the naming and QA discipline that stops drift.
Cadence and requirements
Weekly or fortnightly check-ins
One short call to review progress, unblock, and reorder priorities. Everything else is written.
Async by default
Most of the work happens in a shared document, your Slack, or your tracker. Meetings only when a decision needs one.
One decision owner
One person who can sign off on KPI definitions, priorities, and trade-offs.
Tool access
Read access for the diagnostic; write access during a build. I work in your existing stack where it is one I know.
Engineering time for builds
About a quarter to half of one engineer during a Spine Build Sprint, for the instrumentation work.
Deliverables you keep
- Event schema cookbook
- dbt starter models
- QA harness & testing framework
- Runbook & documentation
- Dashboards & reports
- Governance templates
All documentation, code, and frameworks are yours to own and change. No proprietary tools, no lock-in.
Questions people ask before the fit call
Start with a fit call
Tell me what you are trying to understand or fix. I will say whether a diagnostic makes sense, and if it does not, what I would do instead.