Decide What to Measure Before You Decide How to Track It
Measurement strategy that defines the metrics that actually matter before any tracking implementation begins.
Where this usually breaks down
Most tracking projects start with a tool and only ask what to measure after it's half-configured, producing plenty of events firing and charts rendering that nobody actually needs. The failure is rarely technical - the tracking usually works fine, it just measures things nobody asked for, while the metric that would actually change a decision was never defined.
What this service actually solves
A measurement strategy inverts that order: business questions get mapped to specific metrics before any implementation starts. Every KPI on the resulting list has to trace back to a decision it would inform - if it doesn't, it doesn't make the list, no matter how easy it would be to track.
How we run it
We start with the decisions the business needs to make, not the data currently available, then work backward to the specific metrics and KPI hierarchy that ties them together. The resulting plan gets documented and signed off by whoever owns each decision, so there's no ambiguity later.
Capabilities & deliverables
Business Question Mapping
- Translating strategic questions into measurable proxies
- Prioritising which questions actually need a metric
KPI Hierarchy & Definition
- North-star metric selection
- Supporting and diagnostic metric layers
- Precise definitions that remove ambiguity
Measurement Plan Documentation
- A written plan mapping each KPI to its data source and owner
- Kept current as the business changes
Stakeholder Alignment
- Sign-off from whoever owns each decision the metric informs
- Resolving disagreement about what "success" means before it gets baked into a dashboard
Ongoing Recalibration
- Scheduled reviews as the business model or funnel shifts
- Retiring metrics that stopped mattering
How an engagement runs
Decision Inventory
We list the actual decisions the business needs to make, not the data it currently has.
Question-to-Metric Mapping
Each decision gets mapped to the specific metric that would actually inform it.
KPI Hierarchy Design
Metrics are organised into a north-star metric with supporting and diagnostic layers beneath it.
Measurement Plan Documentation
The mapping is written down, with a data source and owner assigned to each metric.
Stakeholder Sign-Off
Decision owners review and agree on what each metric means before it gets built.
Scheduled Review
The plan gets revisited on a set cadence, since a measurement plan built for last year's funnel does not necessarily fit this year's.
Who needs this
Teams with dashboards nobody opens
If reporting exists but nobody checks it, the problem is usually that it was never tied to a decision in the first place.
Businesses about to invest in new tracking or a data platform
Defining what needs measuring before the build starts is cheaper than re-architecting after.
Related work
We're still building out published proof for this specific service - ask us directly and we'll walk through relevant examples.
How to engage us for this
Project-based
A defined outcome with a start and end date - an audit, a migration, a campaign build, a tracking overhaul. Fixed scope, fixed price, agreed upfront.
Ongoing retainer
Continuous management and optimization once the initial build is live - campaigns, SEO, reporting, and iteration run every month under one accountable team.
Advisory
Strategy and oversight without full delivery - we review what's already running, unblock decisions, and point an in-house or existing team in the right direction.
Common questions
A dashboard is an output; measurement strategy is the decision-making work that determines what belongs on it. Skipping straight to the dashboard usually means building something comprehensive but not necessarily useful.
Having tools running and having them answer the right questions are different things. If nobody can say which decision each existing report informs, a measurement strategy pass is worth doing even with tracking already in place.
For most mid-sized businesses, mapping business questions to a KPI hierarchy and documenting the plan takes two to four weeks, depending on how many stakeholders need to align on definitions.
Whoever owns the decisions the metrics are meant to inform - that is often a mix of marketing, sales, and a business or product owner, not just whoever manages the analytics tool.
We can guarantee the process - mapping questions to metrics and getting sign-off before implementation. Whether a metric stays useful depends on the business continuing to check it and revisit the plan as things change, which is why we build in a review cadence rather than treating this as a one-time document.
That disagreement is exactly what this process is meant to surface before a dashboard gets built around one interpretation. We facilitate that conversation and document the resolution, rather than letting it stay ambiguous until a number gets questioned later.
Reporting a lot of numbers, but not sure which ones matter?
We will map your actual decisions to the metrics that inform them before recommending anything to build.
Ready to get started?
We usually reply within 24 hours.
Measurement Strategy, in detail
Measurement strategy is the process of defining which metrics actually answer the business's real questions, documented before any tracking or dashboard work begins.
Scope, area by area
| Area | What we deliver |
|---|---|
| Measurement Plan | A documented mapping from business question to specific KPI, with an owner and data source for each |
| KPI Hierarchy | A north-star metric with supporting and diagnostic metrics beneath it |
| Stakeholder Sign-Off | Written agreement from decision owners on what each metric means and what it should trigger |
How this compares
| Measurement Strategy First | Tooling First |
|---|---|
| Every KPI traces back to a specific decision it informs | Metrics tracked because the tool made them easy to capture |
| Dashboards get reviewed because they answer a real question | Dashboards get built once, then quietly stop being checked |
| Stakeholders agree in advance on what a number means | Disagreement about what "good" looks like surfaces after the fact |
Good tooling still matters - a measurement strategy just decides what the tooling should be built to answer.
What this changes for the business
- Dashboards get checked regularly because they answer questions stakeholders actually asked
- Fewer disagreements about what a metric means, because it was defined and signed off before anyone saw a number
- Tracking implementation starts with a clear brief instead of guessing what might be useful later