Problem
Teams use the word outcome for many different things. Revenue, customer confidence, task completion rates all matter, but they operate at different distances from a product decision.
Purpose
This framework makes the relationship among user, business, and product outcomes explicit so a team can test how it expects value to be created and exchanged.
Components
- User outcome: a meaningful improvement in a person's life, work, control, or ability to act.
- Business outcome: a durable improvement in the health or strategic position of the organization.
- Product outcome: a measurable change in user or system behavior that supports the user outcome while contributing to the business outcome.
- Leading indicators: earlier signals that show whether the conditions for the product outcome are improving.
How to use it
Write one outcome of each type without naming a feature. Connect them with a sentence: “If this product behavior changes, then this aspect of the user's reality should improve, contributing to this organizational result.” List the assumptions inside that sentence, then choose signals that could challenge them before the final outcome arrives.
Example
A customer wants to resolve a billing problem without repeating information, switching channels, or contacting support multiple times. The organization wants to reduce avoidable service costs while improving customer retention. The connecting product outcome could be an increase in customers who fully resolve eligible billing issues in a single session. Successful issue identification, completion of required steps, abandonment, escalation, and reopened cases could serve as leading indicators.
Limitations
The triplet states a theory; it does not prove causality. Outcomes can conflict, external conditions can alter results, and a measurable behavior can still be a poor proxy for value. Review the full triplet as evidence changes.