Instructions
Product outcomes are the specific changes your product creates for users — the before/after shifts in their situation, capability, or experience. They're different from features (what the product does) and different from metrics (how you measure success). Defining them clearly keeps planning anchored to what actually matters for users.
Most founders find it easier to describe features than outcomes. But features don't tell you whether to build something — outcomes do. When you're deciding what to include in the MVP, 'this feature produces outcome X' is a much stronger argument than 'this feature does Y'. Outcomes give the team a shared north star for every build and design decision.
Be selective. If everything is an outcome, nothing is. A primary outcome is the one single chan...
