## Why Is Focusing Solely on Outputs Problematic? Focusing only on outputs can lead to a “tick box” culture where completing tasks is prioritized over delivering real user value or making a meaningful impact. Treating outputs as value leads teams to fixate on details and assume “if we build it, they will come.” This can produce many features without satisfying customer goals and may even harm the business. >[!metaphor] >Focusing only on outputs is like crossing off to-dos you added just to feel accomplished. You’re managing activity, not progress. </br> Without outcome-driven thinking, teams become efficient at doing the wrong things. ## 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:: [[3.4b Overemphasis on Output Can Obscure Customer Needs]] topics:: [[Project Thinking|Delivery Mode]], [[Outputs vs Outcomes]], [[Output]], [[Feature Factory]] Related | [[3.4b Overemphasis on Output Can Obscure Customer Needs]] -> This mindset often results in outputs that don’t actually solve customer problems. Related | [[6.1a3 Positive and Negative Customer Outcomes]] -> More does not always mean better. ![[Footer]]