From goal to metric (the chain)

The leadership deck opens with a slide titled “Key metrics.” Twelve tiles. Three are green, four are red, the rest are yellow that nobody defined. Someone asks, “Are we winning?” and the room debates colors instead of customers. An hour later the only decision is to add two more tiles for next week. That is not a metrics problem. That is a goal problem wearing a chart costume.

This is Part 1 of Metrics that matter, a series for managers and analysts who have to define KPIs that drive action, not just decorate a dashboard. We will not rewrite the basics. If you want a friendly prequel on what a KPI is and why fewer good ones beat a metric zoo, start with All About KPIs. This part builds the chain that sits under every useful KPI: objective → behavior → measure → target.

What you’ll learn

Why most “metric fights” are unfinished goal conversations
The four-link chain from objective to behavior to measure to target
How to stress-test a proposed KPI before it hits a scorecard
A worked B2B subscription example with a clear table you can reuse
Common mistakes that turn good intentions into gameable noise

Why metrics fail before the spreadsheet opens

People often start with tools. They open a BI workspace, drag fields, and hope a tile becomes strategy. Tools are fine. Starting with tools is how you measure what is easy instead of what matters. The same habit shows up when someone says “we need more data” without naming the decision. Analytics foundations keeps returning to that idea: question first, output second.

A metric is a proxy. It stands in for something you care about but cannot put on a wall as a single pure truth. Revenue is a proxy for value exchanged. Net promoter score is a proxy for loyalty and advocacy. Time to first value is a proxy for how quickly a product starts helping. Proxies are useful when you treat them as proxies. Proxies become dangerous when you treat them as the goal itself. We will talk more about gaming and Goodhart later in this series. For Part 1, the fix is simpler: write the goal chain before you lock the number.

OKR practice popularized a useful sentence shape: we want an objective, as measured by key results. John Doerr’s public writing on OKRs (and the broader “measure what matters” framing) is not a religion you must adopt. It is a reminder that vague ambition without measured progress is theater, and measured progress without ambition is bookkeeping. You can use OKRs, a strategy memo, a product brief, or a one-page goal statement. The chain below works in all of those formats.

Rule of thumb: If you cannot explain how a number connects to a behavior someone can change this month, it is a scoreboard, not a management tool.

The chain: objective → behavior → measure → target

Example:

Weak vs strong goal-to-metric chain

Filled example of the chain:

Think of four links. Skip one and the metric usually snaps under pressure.

1. Objective: what winning looks like in plain language

An objective is a direction people can repeat without a glossary. It is not a formula. It is not a dashboard title. Good objectives sound like: “New customers get value in the first week,” “Support resolves issues without endless handoffs,” or “We grow revenue without burning margin on discounting.”

Bad objectives sound like system nouns: “Improve CRM hygiene,” “Increase engagement,” “Optimize funnel.” Those phrases hide disagreement. One person’s engagement is session count. Another’s is weekly active accounts. A third’s is paid conversion. Until you finish the sentence in human language, every metric is a guess.

Write the objective as if you were explaining it to a smart colleague who does not work in your team. If they ask “so what changes for customers or the business?”, you should have an answer in one breath. If you need three slides of context before the objective makes sense, the objective is still a project plan, not a goal.

2. Behavior: what people do differently if we are serious

This is the link most teams skip. Behavior is the bridge between ambition and measurement. If the objective is “new customers get value in the first week,” the behaviors might include: onboarding calls completed within two days, in-product setup checklists finished, success playbooks used on every new account, and product fixes for the top activation blockers.

Why behavior matters: measures without behaviors become spectator sports. People watch the line go up or down and shrug. Measures with behaviors become coaching tools. A manager can ask, “Which behavior slipped?” instead of “Who do we blame for the red tile?”

Behaviors should be controllable by the people you are measuring. If your sales team cannot change warehouse shipping times, do not put shipping-driven customer satisfaction on their personal scorecard and call it accountability. Put it on the team that owns the process, or treat it as a shared constraint metric with a shared action plan.

3. Measure: the proxy you will count honestly

A measure is the number (or small set of numbers) that best stands for progress. It needs a clear population, a clear time window, and a definition you can rebuild. That rebuild habit is the same discipline you use in data quality work: if two analysts cannot reproduce the number, you do not have a metric, you have a rumor with a chart.

Choose measures that are close enough to the behavior to respond when people change, and close enough to the objective to stay meaningful. “Emails sent” is close to a marketing behavior and often far from business value. “Revenue” is close to business value and often late as a coaching signal. Part 2 of this series goes deep on leading versus lagging. For now, notice the tradeoff when you pick the measure link.

Also decide what you will not measure yet. A short scorecard is a decision. A long scorecard is often fear of choosing. If everything is key, nothing is.

4. Target: the line that turns a measure into a commitment

A target answers: what number, by when, under what assumptions? Without a target, a measure is weather. Weather is interesting. Weather does not tell you whether to change the plan.

Targets can be thresholds (“above 85% on-time activation”), ranges (“between 12 and 15 demos per rep per week”), or trajectory goals (“reduce median time to first value from 14 days to 7 days by end of Q3”). They should be hard enough to force tradeoffs and honest enough that people do not hide problems to protect a bonus.

Write the assumptions next to the target. “Assumes no major product outage and current pricing.” Assumptions prevent false panic when the world changes, and they prevent false celebration when you hit a number by changing the definition midstream.

How the chain looks in real language

Here is a compact fill-in pattern you can paste into a doc or ticket:

OBJECTIVE (plain language):
We want ________________ so that ________________.

BEHAVIORS (what changes this month):
1. ________________
2. ________________
3. ________________

MEASURE (the proxy we will count):
Name: ________________
Population: ________________
Window: ________________
Formula idea: ________________

TARGET (commitment + timing):
By ________ we will reach ________.
Assumptions: ________________
Owner who can change the behaviors: ________________

If you cannot fill a row without inventing, stop. The blank is information. It means the team does not yet agree on the goal, the work, or the definition. That disagreement is cheaper to surface in a document than in a board meeting.

Worked example: B2B product activation

Imagine a mid-market SaaS team. Leadership says, “We need better retention.” That sentence is directionally true and operationally useless. Retention is an outcome that arrives late. The team needs a chain.

Objective: New customers reach a first useful outcome inside the product within seven days of signup, so they stay long enough to expand.

Behaviors: Customer success books a kickoff within 48 hours. Product prioritizes the top three setup blockers found in support tickets. Sales stops selling packages that require unavailable integrations. Marketing clarifies the “first win” in onboarding emails.

Measure candidates: percent of new accounts that complete a defined “first value” event within 7 days; median hours from signup to first value; percent of kickoffs held within 48 hours (a leading process measure).

Target: Raise 7-day first-value rate from 42% to 60% by the end of the quarter, without counting internal test accounts, and with “first value” defined as exporting a live report (not viewing a sample dashboard).

Notice how much definition work hides in that paragraph. Population, event definition, exclusions, and timing are not pedantry. They are the difference between a KPI and a fight. Part 3 of this series turns that definition work into a one-page metric spec.

Here is the same example as a table you can adapt.

Chain link	Team draft (weak)	Team draft (stronger)
Objective	Improve retention	New customers reach a first useful outcome in 7 days so they stay and expand
Behavior	Work harder on onboarding	Kickoff within 48h; fix top 3 setup blockers; stop selling missing integrations
Measure	Engagement score	% of new paid accounts with first live report export within 7 days
Target	Go up	42% to 60% by quarter end; exclude tests; event = live export
Owner	“The data team”	CS ops owns kickoff SLA; PM owns blockers; analytics owns definition + report

The stronger column is longer on purpose. Clarity is not the same as complexity. You are paying a little documentation cost now to avoid a large political cost later.

Stress tests before you put a metric on a wall

Before a number becomes “official,” run five questions out loud.

Decision test: If this number moved 10% for the worse, what would we do next week? If the answer is “look at more charts,” you are not ready.
Behavior test: Can the measured team change the inputs without cheating the definition?
Definition test: Can two people rebuild the number from source data with the same result?
Lag test: How late does the signal arrive relative to the work? If it is very late, pair it with a leading measure (Part 2).
Side-effect test: What ugly behavior would this metric reward if people optimized only for it? Light touch here; Part 5 covers Goodhart and gaming in depth.

These tests are also a culture tool. They let analysts push back without sounding like blockers: “I can build the tile, but we have not passed the decision test yet.” That is professional, not picky.

Where this sits next to charts, SQL, and quality

A metric chain is not a visualization choice. Once the chain is solid, you still need honest charts from Charts that make sense (series slug data-viz): purpose first, then type, then axes. A beautiful activation chart with a fuzzy definition is still a fuzzy definition.

The same is true for pipelines and code. You can implement the measure in SQL, in a warehouse model, or in a small Python pipeline from the Python for analytics path. Implementation quality matters, but implementation cannot invent a missing objective. If stakeholders argue about which file is right, you may have a quality issue and a definition issue at the same time. Fix the definition on paper, then fix the data path.

Foundations still apply: if you do not know the problem you are solving, a longer KPI list will not help. The metric chain is problem framing applied to performance management.

What the chain is not

A few boundaries keep this framework from turning into theater.

The chain is not a requirement to invent OKRs if your company uses another goal system. Strategy memos, product briefs, and annual plans all work. The links still apply: what you want, what people will do, what you will count, and what “enough” looks like by when.

The chain is not a license for infinite metrics. One objective can support a small set of measures (often one primary lagging outcome plus a couple of leading process measures). If you need twelve chains for one team meeting, you probably have twelve goals, not one scorecard. That is a strategy conversation, not a BI backlog item.

The chain is also not a substitute for data fitness. You can write a perfect chain and still ship a number built on late events, broken joins, or a population nobody agreed on. When that happens, fix the definition and the pipeline together. Do not only add another tile.

Common mistakes

Starting with available fields. “We have a pageview column, so pageviews are strategic.” Availability is not importance.
Skipping behavior. The team stares at outcomes and never names the work that moves them.
Targets without assumptions. Then every external shock becomes an internal failure story.
Owning the number but not the process. Analytics “owns” the dashboard while nobody owns the kickoff SLA.
Twelve priorities. A scorecard that cannot fit on one screen often means strategy has not chosen yet.
Confusing a project milestone with a KPI. “Launch the new onboarding flow” is work. “Raise 7-day first value” is a performance measure tied to an objective.
Changing definitions mid-quarter to hit a target. That is fiction, not management. Document the change, reset the baseline, and say so out loud.
Treating the prequel as optional forever. If your team still confuses a metric with a KPI, send them back to All About KPIs before you expand the scorecard.

How to practice this week

Pick one metric that already appears in a weekly meeting.
Write the four links for it. Leave blanks if you must. Do not invent to look complete.
Run the five stress tests with a partner who is not the dashboard builder.
Rewrite the metric title as a human sentence: “We track X because we want Y.”
If the behavior row is empty, schedule a 30-minute working session with the process owner before you “improve the dashboard.”
Optional: sketch how you would query the measure (SQL or Python) only after the definition sentence is stable.

For more paths across foundations, quality, charts, and tools, use the Learn hub. Next in this series: leading versus lagging indicators, with one business example you can adapt to your own funnel.

Quick recap

Useful metrics hang on a chain: objective, behavior, measure, target.
Skip behavior and you get spectator dashboards.
Skip definition and you get meetings that argue about the number instead of the work.
Targets need timing and assumptions, not only a bigger arrow.
Stress-test decision, behavior, rebuildability, lag, and side effects before you promote a tile to “KPI.”
This series designs the system; All About KPIs remains the friendly prequel on what a KPI is.

Sources

What Matters (John Doerr / OKR resources), OKRs explained: https://www.whatmatters.com/okrs-explained
What Matters, home and Measure What Matters materials: https://www.whatmatters.com/
Analytics Made Simple, All About KPIs (prequel): https://analyticsmadesimple.com/analytics/all-about-kpis/
Analytics Made Simple, Analytics foundations: https://analyticsmadesimple.com/series/analytics-foundations/
Analytics Made Simple, Data quality for people who ship numbers: https://analyticsmadesimple.com/series/data-quality/
Analytics Made Simple, Charts that make sense (data-viz): https://analyticsmadesimple.com/series/data-viz/
Analytics Made Simple, Learn hub: https://analyticsmadesimple.com/learn/