outcome-vs-output

Overview

Based on Escaping the Build Trap by Melissa Perri. The "build trap" is when teams measure success by features shipped instead of value delivered. Feature factories build a lot - and move metrics very little. Perri's framework: every item in your backlog should trace to a measurable outcome. If it can't, question whether it should be built at all.

The output/outcome distinction:

• Output - something you ship ("we launched a dashboard")
• Outcome - a change in user or business behavior ("users now self-serve 40% of support queries")

Outputs are inputs to outcomes. Shipping outputs that don't move outcomes is waste.

Workflow

Step 1: List the current roadmap or backlog items

Work from the actual list. Don't audit hypothetically.

Step 2: Classify each item

For each item, ask: "Is this an output or an outcome?"

• Output: a feature, a page, a report, an integration, a tool
• Outcome: a change in what users do or what the business achieves