Your Objective Isn't an Outcome
I was reading someone’s strategy whitepaper recently that listed “Outcomes / Benefits / OKRs” as a sub-title, separated by slashes, as if they were interchangeable. I asked the author what the difference was. They couldn’t describe it.
The same confusion came up last week during a workshop I was leading. Someone shared their OKR, and the room debated whether their objective was an outcome.
It’s OKR season for a lot of us right now. And when these terms are conflated, teams end up optimizing for the metric rather than the problem.
Outcome, Benefit, Objective — in that order
These aren’t synonyms and work in a sequence.
Outcome: The change in user behavior we’re trying to create.
A customer resolves a billing issue without calling.
Benefit: The business value that results from the outcome.
Reduced call volume, lower cost-to-serve.
Objective: The measurable target that tells us if we’re getting there.
Reduce billing-related calls by 20% in Q2.
When we start with the objective instead (”reduce calls by 20%”), our team might just make it harder to find the phone number. That hits the metric but misses the outcome entirely.
When we start with the outcome (”users resolve issues without calling”), we’re solving for the right thing.
Why this matters right now
The way I frame it: outcome first, then the benefit, then the objective. If I can trace the objective back to the outcome, the OKR measures something that matters. If I can’t, it might be a vanity metric.
What’s an OKR you’ve seen where the objective and the outcome got confused?