Framework: Inputs, Outputs, & OutcomesOutcome orientation is a framework that considers inputs, outputs, and outcomes. Inputs are the resources used to produce outputs, which are the products or services delivered. Outcomes are the effects or changes resulting from the use of those products or services. This framework helps organizations focus on achieving desired outcomes rather than just producing outputs.
- Outcome-Based Roadmaps: Unleash the Power of a Shared Vision and PurposeJason explains how features "are Outputs. They are what we create." However, modern product teams need to care about "whether the thing we just shipped had the desired Outcome."
- Rethinking outcomes over outputsPaul argues that the outcome vs. output conversation needs to expand to include inputs to complete the analysis of the system. Once we're paying attention to outcomes, we can learn more about which inputs produce which outcomes, at what rate of shipping (outputs).
- Why Outcomes Over Outputs?John explains how focusing on outcomes is not a best practice for the sake of a best practice; rather, it is a high-level framework for answering the question, "what will produce the best outcomes for a business?"
Evaluating OutcomesEvaluating outcomes involves assessing the effectiveness of the products or services delivered. This can be done through various methods, such as measuring customer satisfaction, tracking changes in behavior or performance, or conducting cost-benefit analyses. It is important to use reliable and valid measures to ensure accurate evaluation of outcomes. Additionally, ongoing evaluation allows for continuous improvement and adaptation to changing needs and circumstances.
- The Loose Coupling of Decisions and OutcomesDave warns how outcomes can become influenced by externalities, but that still makes a general rule of thumb possible for evaluating outcomes: "the quality of any performance should be judged on a relative basis to others performing a similar task in a similar timeframe / market phase."