Skip to main content
Output is what you build. Outcome is what changes as a result. A team can ship ten features in a quarter and move no needle that matters. Another team can ship one thing and transform their retention curve. The difference is whether they were optimising for output or outcome 📦

​
Why the distinction matters

Most product teams are measured on output by default - features shipped, velocity, story points, release cadence. These are visible, countable, and satisfying to report. They’re also a terrible proxy for value. Josh Seiden makes this case directly in Outcomes Over Output - the goal of any product initiative isn’t the thing you build, it’s the change in human behaviour that the thing enables. If behaviour doesn’t change, the output didn’t matter.

​
What an outcome actually is

An outcome is a measurable change in user or business behaviour:
  • Users complete onboarding without contacting support
  • Customers expand their subscription within 90 days
  • Support ticket volume for a specific workflow drops by 40%
These are different from outputs (“we shipped a new onboarding flow”) and different from impacts (“we grew revenue”) - outcomes sit in the middle, specific enough to measure, close enough to your work to influence 💡

​
The output trap

Teams fall into output thinking for understandable reasons. Stakeholders ask “what did you ship?” Roadmaps list features. Sprints end with demo days. The whole system rewards visibility of work, not effectiveness of work. Melissa Perri calls this the build trap in Escaping The Build Trap - organisations that value the production of features over the outcomes those features create. Getting out of it requires changing not just how teams work but how leadership measures success.

​
Making the shift

The practical change is in how you frame goals. Instead of “build X”, the objective becomes “achieve Y for users.” The team then has to discover what to build to get there - which is product discovery doing its job. OKRs done well enforce this: key results should measure outcomes, not completion of tasks 🙌 Lesson learned: the moment a team stops asking “did we ship it?” and starts asking “did it work?” - everything about how they work changes. That shift is harder than it sounds, and more valuable than almost anything else.