Outcomes vs. Outputs: What's the Difference and Why Does It Matter?

Teresa Torres argues that 'outcomes over outputs' is easy to state but hard to practice, because many teams still ship features while being asked to deliver impact. She defines outputs as what a team builds and outcomes as the behavior change or business result that building creates. Through examples such as Android apps, job boards, course reviews, and feature-adoption metrics, she shows how many supposed outcomes are outputs in disguise. She explains why the shift is structurally difficult, citing trust cycles between managers and teams and accountability systems that encourage sandbagging, and offers practical steps like negotiating outcomes, iterating on metrics, and pairing sentiment with behavior. The core message is that a team is only done when what it shipped has the intended impact.

01Key takeaways

• Ask what value a customer gets and measure that moment, not the easiest metric to track.
• If you can hit a metric without actually helping customers, it is probably an output in disguise.
• Avoid traction metrics that measure feature usage without judging whether that usage succeeded.
• Pair sentiment metrics with behavior metrics so teams know both where to push and where not to.
• Treat early outcomes as learning goals before setting performance targets to encourage real exploration.
• Expect your first outcome metric to be wrong and plan several iterations.

02Key sections

Defining outputs and outcomes

Outputs are things teams build and ship, while outcomes are the behavior changes or business results those outputs produce. Torres separates business outcomes from product outcomes.

Why the distinction changes how teams work

Output-driven teams are done when software ships, whereas outcome-driven teams are done only when it has the expected impact. This shifts autonomy, planning artifacts, and the opening for real discovery.

Clear-cut and tricky examples

A mobile app goal is reframed as engagement, and job-board and course-review metrics are shown to measure activity rather than value creation. Feature-adoption traction metrics are also flagged as weak outcomes.

Pairing sentiment with behavior

Sentiment metrics like CSAT or NPS lack direction on their own, so Torres recommends pairing them with behavior metrics as guardrails against harmful engagement.

Why it is hard and how to start

Trust cycles and performance-review accountability make the shift difficult, so she recommends learning goals, two-way outcome negotiation, and iterating on metrics.

03From the post

“What's the difference between outcomes vs. outputs? Walk through clear-cut and tricky examples, common mistakes, and practical steps.”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.