## When Should Customer Outcomes Be Defined? They should be defined early to focus product discovery and validate assumptions quickly and continuously. Early clarity supports faster learning and alignment. >[!metaphor] >Defining customer outcomes early is like setting your GPS before you start driving. It keeps you heading in the right direction and lets you adjust your route as new information comes in.</br> Early clarity ensures discovery stays focused, assumptions get tested fast, and the whole team stays aligned. ## Works Consulted 1. [Customer Outcomes](https://www.scrum.org/resources/customer-outcomes) | Scrum.org | Accessed 23 Jun. 2025. ## Connections follows:: [[6.1c Outcomes Require Deeper Insight and Feedback]] topics::[[Outcome]], [[Fail Fast]] ![[Footer]]