Outcome Thinking is the discipline of distinguishing what an organisation builds from the change that building creates, and from the business value that change produces.
It is one of the most practical ideas in modern ways of working, because it moves attention away from activity and towards the difference that activity is supposed to make.
INCEPTI uses Outcome Thinking across Discovery, the Leadership Bootcamp, and Change Delivery as the lens through which a team decides whether it is solving the right problem rather than simply staying busy.
The output, outcome, impact chain
Joshua Arnold’s framework separates three things that organisations routinely run together. Keeping them distinct is what makes the model useful.
Output
What the team produces: a feature, a service, a deliverable, a process. Outputs are within the team’s direct control and are easy to count.
A new onboarding programme is launched.
Outcome
The change in behaviour that follows from the output: a problem solved, a new possibility opened, a habit shifted, for a customer, user, or colleague. Outcomes are observable but not fully controllable.
New hires reach full productivity sooner and feel confident in their role within the first month.
Impact
The business value that follows from the outcome: revenue increased or protected, or cost reduced or avoided. Impact is what the organisation ultimately cares about, and it is the hardest to attribute to any single output.
Time to productivity falls, lowering cost, while stronger early retention protects revenue.
The outcome is the only point in the chain where a team can genuinely intervene. Outputs are activity; impact is a lagging signal that arrives too late to act on. The outcome sits between the two: close enough to the work to be influenced, and close enough to the value to matter.
A team that manages only outputs and financial results, and neglects the outcome in the middle, is managing the two ends of a chain while ignoring the link that connects them.
Why organisations drift towards output thinking
Output thinking is the path of least resistance. Outputs are visible, countable, and easy to put on a roadmap, so they dominate planning, reporting, and recognition. Several forces push teams towards them.
- Outputs are easier to measure: a team can count features shipped or training sessions run without agreeing on what those activities were meant to change.
- Outputs feel like progress: delivering something tangible is satisfying and reportable, even when the something makes no difference.
- Outputs map cleanly to plans and budgets: a roadmap of deliverables is simpler to commit to than a roadmap of behavioural changes whose path is uncertain.
- Accountability is usually set at the output level: teams are asked whether they shipped, not whether the shipping changed anything.
The cost of this drift is the build trap, a term popularised by Melissa Perri: organisations become so focused on producing features that they lose sight of the value those features are meant to deliver. Work accelerates while progress towards anything meaningful stalls.
Outcome Thinking in practice
Three habits move a team from output thinking to outcome thinking.
Ask what changes, and for whom
The simplest test of an outcome is whether you can name a person who behaves differently as a result. When a team describes an output and calls it an outcome, the tell is that no one can say what changes or for whom.
The remedy is a single repeated question, and then what changes?, asked until the team reaches a person doing something differently. “We will implement a new CRM” becomes “sales people spend less time on admin and more time in meaningful client conversations.”
Frame work as hypotheses, not commitments
Because the link between output and outcome is uncertain, outcome-minded teams treat a planned output as a bet: if we deliver this, then we expect this change, because of this reasoning.
This framing keeps the team honest about assumptions and makes it natural to stop work that is not producing the expected change, rather than pressing on because it was promised.
Measure the outcome, not only the output or the impact
Outcome Thinking and good measurement are inseparable. A team that wants to manage outcomes needs signals that show whether behaviour is shifting, well before the financial impact lands.
This is the bridge to leading indicators, and to Objectives and Key Results, where the Objective names the outcome and the Key Results make it observable.
Worked examples across contexts
The examples below keep the same four contexts INCEPTI uses throughout its material, so the distinction between the three terms stays visible as the context changes.
| Context | Output | Outcome | Impact |
|---|---|---|---|
| HR / People | New onboarding programme | New hires reach full productivity faster and feel confident in their role within the first month | Reduces cost through lower time to productivity, and protects revenue through stronger early retention |
| Operations | New project-prioritisation framework | Teams spend less time debating what to work on and more time delivering | Reduces cost through fewer wasted cycles, and protects revenue as critical work moves faster |
| Sales / Commercial | New CRM implemented | Sales teams spend less time on admin and more time in meaningful client conversations | Increases revenue through a higher win rate, and avoids the cost of manual reporting |
| Transformation / Change | Agile ways of working introduced | Teams collaborate across functions without waiting for escalation | Increases revenue through faster delivery, and reduces cost through fewer handoffs |
Common traps and how to avoid them
The relabelled output. A team writes an output and calls it an outcome. Apply the test: name the person whose behaviour changes. If no one can, it is still an output.
The unfalsifiable outcome. An outcome stated so broadly that nothing could disprove it, such as “customers are happier”. Tie it to an observable behaviour and a way to see it.
The impact mistaken for an outcome. Revenue and cost are impact, and they sit too far down the chain to manage directly. Find the behavioural change that would move them.
The orphan outcome. A desired outcome with no real problem or tension behind it is usually a preference dressed as a priority. Trace every outcome back to a genuine need.
How INCEPTI uses Outcome Thinking
Outcome Thinking underpins the Value lens of the four lenses framework: the question of whether an organisation is addressing the right challenges rather than producing more outputs.
It appears first in Discovery, where surveys surface whether teams can articulate the outcomes they are working towards.
It is taught explicitly in the Tailored Leadership Bootcamp’s first module, Setting Direction, where leadership teams turn their tensions into outcome-based priorities.
Throughout Change Delivery, Outcome Thinking keeps the work anchored to the difference it is meant to make.
Attribution and further reading
The output, outcome, impact framework is associated with Joshua Arnold of Black Swan Farming, whose work on Cost of Delay and business value popularised the distinction in the product and agile communities. The broader idea draws on outcome-oriented thinking from across the field, including Jeff Patton, Josh Seiden, and Marty Cagan.
Read
- Output, Outcome and Impact, by Jeff Patton.
- Outcomes Over Output, by Josh Seiden (publisher page).
- Escaping the Build Trap, by Melissa Perri (O’Reilly, 2018).
- Output vs Outcome vs Impact, on the Crisp blog.
- Black Swan Farming: Business Value, Joshua Arnold’s own writing.
Watch
- Output vs Outcome vs Impact, by Marco Avenado (YouTube).
- Start with Why, by Simon Sinek (YouTube).
- John Cutler’s North Star Metric, at ProductHead.
- Aligned Autonomy clip, by Watlow E (YouTube).