Home › Leadership › Dualities
Outcome Driven vs Output Driven
Leadership / Dualities · Updated Apr 2026
Measure what changed, not what was produced.
Output Driven
- Count features shipped, tickets closed, lines of code.
- Easy to measure but often meaningless.
- "We shipped 12 features this quarter."
Outcome Driven
- Measure the impact on users, business, or team.
- Harder to measure but actually matters.
- "User onboarding completion improved by 15%."
Why Output Is Tempting
- Outputs are easy to count.
- They feel tangible and safe.
- Traditional management is built around tracking output.
Why Outcomes Are Better
- A team can ship 50 features and move no metrics.
- Outcome focus lets teams find the simplest solution.
- It creates space for saying "we don't need to build that."
The Shift
Instead of "What should we build?" ask "What should change?"
Let the team figure out what to build to make that change happen.
Related