An output is something your team builds or does: a feature, a release, a redesign, a migration. Outputs are usually visible and largely within your control. Outcomes are different, they are the evidence that the work mattered. An outcome is the change that work was supposed to create. More customers complete a task. More customers return to the product. Fewer customers call support. Outcomes are harder to produce, harder to measure, and harder to fake. The crux of product management is realising that your attention needs to be on creating outcomes. Once this realisation fully hits, you’ll notice how it shapes everything you do.
Output thinking persists because shipping feels like progress. Something exists that did not exist before. The team overcame obstacles. The deadline was met. It feels good. You finished a thing. You should be proud.
But shipping is not success. Shipping is merely the moment your bet meets reality. The harder question comes afterwards: was this worth doing at all? Did it change behaviour, reduce pain, create value, or improve the system in any meaningful way? Most things do not work exactly as we expect. Outcome orientation is honest about that. Output orientation lets us turn a blind eye to it. As Peter Drucker put it plainly: “There is nothing quite so useless as doing with great efficiency something which should not be done at all.”
Product managers always work with constraints: time, money, expertise, organisational patience. The job is not to get more things through the machine. The job is to make better choices about where scarce effort should go.
When you optimise for output, it can feel as though you are solving that problem. More releases. More features. More visible progress. But activity does not prove that resources were well spent. It only proves that resources were consumed. Outcome thinking forces the reckoning into the open. It asks whether the work changed something that mattered for customers and for the business. That question is uncomfortable. It is also the question that gives the discipline its purpose.
Once you commit to outcomes over output, the rest of the work changes shape. Strategy becomes a way of choosing which changes matter most. Discovery becomes a way of reducing uncertainty before you spend too much. Measurement becomes a way of learning whether reality agreed with your assumptions. Team autonomy becomes meaningful because teams are no longer merely handed tasks; they are trusted to pursue a result.
That is why this idea sits underneath so much of product management. It changes what you prioritise, how you talk to stakeholders, how you decide what to stop, and how you know whether to keep going. But they all begin here: with the belief that making something is not enough. The work only matters if something changes.
This is also where the job gets hard.
Outcome orientation means being measured on your contribution, not your activity. It means standing behind your bets and learning from them when they fail. Autonomy is attractive because it creates freedom, but it’s frightening because it creates accountability. Focusing on outcomes puts your judgement on public trial. That is not a side effect of the discipline. It is the discipline. If you want to become great at product management, then this is what it asks of you. You have to care whether the work mattered, and you have to be willing to find out.
That is the bargain: more freedom, more judgement, more responsibility, more impact. Not everyone takes it. This article is for those who do.