Interactive graph
Output vs Outcome
Table of Contents
Merged code is output; a user problem solved on time is the outcome PM owns.
Key Concept
- Output is what the team produced; outcome is what changed for the user or the business.
- Outcomes Over Pitch Decks judges fruit, not slides - this note splits production from impact.
- Dev dashboards love output metrics; PM asks whether the output moved the needle anyone cares about.
Level 1 - Recognize
Output is what shipped; outcome is what improved for the user or the business.
Level 2 - Explain
Like delivering a hundred flyers nobody read - output without outcome is motion with no result.
Level 3 - Use
Before close-out, name one user or business signal that should move if this release worked - not only that the build is green.
Level 4 - Connect
Resume Speaks Outcomes Not Stack applies the same test to career proof - cut lines that only list frameworks shipped.
Level 5 - Create
Write a one-line outcome hypothesis before kickoff and revisit it at retro - Measure Then Iterate when the signal is thin.
Examples
- Glad the team merged twelve PRs - support tickets on checkout did not drop; output without outcome.
- We shipped the training catalog on date - enrollment actually rose; that is the outcome the intranet project owned.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| extends | PM Mindset | Core PM judgment inside the hub |
| extends | Outcomes Over Pitch Decks | Fruit beats deck polish |
| extends | Execution | Done means outcome landed, not only build green |
| extends | Resume Speaks Outcomes Not Stack | Same test on career bullets |
