Output
An output is something you build—features, code, products, or releases. Outputs are the tangible deliverables that product teams create.
"I built this thing" is an output.
How does output-focused thinking differ from outcome-focused thinking?
It's easy in business—and especially among product teams—to be output focused. You focus on shipping code, delivering features, hitting your roadmap. These are all outputs.
In output-focused thinking, you start with "We are building output X because we think it will result in outcome Y." In outcome-focused thinking, you flip this on its head and start with "We want outcome Y, how might we get there?" The answer is sometimes "Build X." But sometimes the answer is "Build Y or Z." And sometimes the answer is "Don't build anything at all."
Why does shifting from outputs to outcomes matter?
The shift from managing outputs to managing outcomes represents a fundamental change in how teams think about their work. Instead of focusing on what you're building, you focus on the impact those outputs have on customers and the business.
The real value of starting with an outcome is it helps you focus on value creation rather than just output creation.
Learn more:
- Shifting from Outputs to Outcomes: Why It Matters and How to Get Started
Related terms:
- Outcomes
- Outcomes Over Outputs
- Product Outcome
Last Updated: October 25, 2025