## Why Do Outcomes Require More Effort to Measure Than Outputs? Outcomes require more effort to measure than outputs because outcomes reflect changes in user behavior or experience, not just activity. They’re not directly observable in the same way outputs are. While outputs can be instantly counted (like features shipped), outcomes depend on _what happens after_—whether users adopt the feature, find value in it, or change how they behave. That requires deeper, ongoing insight through interviews, telemetry, feedback, and time. You’re measuring _effect_, not effort—and that’s inherently more complex. >[!metaphor] >Measuring outcomes is like checking if a plant is thriving—not just if you watered it. You have to observe growth, resilience, and fruit over time, not just the action of pouring water. </br> Outcomes take more effort to track because they depend on long-term effects, not short-term activity. ## Works Consulted 1. [Outputs or Outcomes](https://www.youtube.com/watch?v=gxKBh7q0oOs) | Scrum.org | Accessed 26 Dec. 2024. 2. [Customer Outcomes](https://www.scrum.org/resources/customer-outcomes) | Scrum.org | Accessed 23 Jun. 2025. ## Connections follows:: [[6.1 Outputs Are What You Produce; Outcomes Are the Impact]] topics:: [[Metrics]], [[Outcome]], [[Output]], [[Adoption]], [[Telemetry]], [[Feedback]] ![[Footer]]