Outcome Thinking

Most goal-setting runs the chain the wrong way round. It starts with action, what we plan to do, and hopes value appears at the end. Outcome thinking reverses it. Begin with the value you want (what will be observably better, and for whom?), then ask what behaviour would have to change to produce it (who does what differently?), and only then decide the action (what we do to prompt that behaviour). The action is still there; it's just no longer mistaken for the goal.

The three failure modes it prevents

The discipline exists to defeat three closely related traps. The activity trap: mistaking motion for progress, where a team is busy, shipping, and going nowhere. Solution bias: falling in love with a particular answer before understanding the problem, so the goal quietly becomes "ship my idea" rather than "solve the problem". And the measurement mirage: tracking numbers that are easy to move but disconnected from real value, which produces impressive dashboards and flat results. All three feel productive from the inside, which is exactly why they need a principle to guard against them.

Why it's the reasoning behind good Key Results

Outcome thinking is the logic that makes teams avoid task-based Key Results. "Launch the feature" is an action; "increase activation" is a behaviour change; "reach value in the first session" is the value. When a team instinctively works backwards from value, its Key Results describe the change in the world rather than the work done, and the whole OKR stops being a to-do list with ambitions attached. This is why we treat outcome thinking as foundational rather than a nice-to-have: it sits upstream of almost every other good habit in the system.

Martin’s deepest version

Roger Martin states the sharpest form of this principle: the customer is the only judge. Internal measures of success are proxies at best and theatre at worst; what actually validates a strategy is changed customer behaviour, people choosing you, paying, staying, doing something different because of what you built. Read this way, outcome thinking isn't merely a goal-setting technique. It's a discipline of intellectual honesty: it keeps you asking whether anything real happened outside the building, rather than whether you completed the plan inside it.

In practice

When a team drafts a goal, ask one question three times: "and that matters because?" Each answer climbs one rung, from action toward value, and you stop when the answer is a benefit a customer or the business would actually notice. That final answer is your outcome; everything below it's means. Teams find this uncomfortable at first, because it exposes how much planned work has no clear line to value, which is precisely the point.