Outcome vs Output: measure the result, not the activity

The distinction between outcome and output is one of the most important in OKR practice. It decides whether your Key Results measure what really matters, or just what the team has shipped.

• Output: what the team ships. A feature, an article, a campaign, a training program.
• Outcome: the change produced in the real world. An activation rate, revenue, an engagement score, a user behavior.

Output vs outcome: concrete examples

In every case, the output is what the team directly controls. The outcome is what happens downstream, and depends on the output being relevant. That relevance is precisely what the outcome measures.

Why KRs must measure outcomes

• Force relevance. A team can ship 100% of its outputs without moving a single outcome. Measuring the outcome surfaces the gap immediately.
• Align effort to result. The team stops pushing deliverables and starts searching for what works.
• Distinguish Key Result and Initiative. The Initiative is the output, the KR is the outcome. Don't conflate them.

The "so what?" test

To check that a KR really measures an outcome and not an output, ask: "if we hit this KR, does anything actually change for the customer, the user, or the business?"

• If the answer is "yes, it means [concrete business result]", it's an outcome. Solid KR.
• If the answer is "well, it means we shipped the project", it's an output. Reframe.

Outcome proxy: what to do when the final impact is too far out

Some strategic outcomes only measure on 12 or 24 months. M12 retention, LTV, market share. Too distant to frame a quarter. The fix: use an outcome proxy, which is neither an output nor the final outcome, but an intermediate metric you have solid reasons to believe predicts the final outcome.

An outcome proxy isn't a compromise: it's the right tool for steering a short cycle. Provided the correlation between proxy and final outcome is explicitly validated by the team and its sponsors.

When an output is necessary but can't be a KR

Not all outputs are pointless. Some are strictly necessary (shipping a legal compliance update, deploying a piece of technical infrastructure, migrating a system). But they shouldn't appear as Key Results: they're either Initiatives in service of an outcome, or operational projects independent of OKRs.

Example: "Make our data pipelines GDPR-compliant" is a necessary, unavoidable output. It becomes:

• An Initiative in service of a customer trust Objective (the output serves an outcome).
• Or an operational project managed outside OKRs, with its own rituals (the output has no direct OKR outcome).

What's ruled out: turning that output into a KR ("Achieve GDPR compliance"). That would be a binary disguised as a KR, derailing the KR from its outcome-measurement role.

The Objective / Key Result / Initiative triad, clearly

The outcome vs output distinction clarifies the OKR triad:

• The Objective describes the qualitative ambition.
• The Key Result measures the outcome that validates the Objective.
• The Initiative is the output the team produces to move the outcome.

That chain is what separates OKRs from classic goal setting. The output (Initiative) is never the goal, it's a means in service of an outcome (KR) that serves an ambition (Objective).

The outcome trap

• The outcome can be outside the team's control. Bad KR: "Move industry NPS from 30 to 50" (not under our control). Good KR: "Move our NPS from 30 to 50".
• The outcome can be too far out in time. M12 retention is a great strategic outcome, but too distant for a quarterly KR. Prefer a shorter outcome proxy.
• The outcome sometimes looks like a KPI. True. The difference: a KR pushes an outcome toward a specific target over a cycle, where a KPI tracks continuous health.

Serendly insight: "what will be different for our customers in 12 weeks?"

A simple question to ask at start of cycle, team by team: "what will be observable, measurable, and different for our customers or our business by end of quarter?".

If the team can answer with a clear number, their KRs will measure an outcome. If they answer with a list of deliverables, their KRs will measure an output. The framing work starts there.

Frame your OKRs around outcomes that matter

Moving from output to outcome is one of the toughest qualitative leaps in OKR practice. Let's talk about how we support teams through that shift.

Request a demo