## Why Must a Product Goal Be Achieved or Abandoned Before Starting the Next One? It enforces discipline, preventing constant reprioritization and unfinished work from lingering. If it’s important, finish it; if not, stop revisiting it. > [!metaphor] > Starting a new Product Goal while keeping the old one lingering is like texting your ex “just to check in.” If they were truly worth it, you wouldn’t have left, and going back only drags out the mess. </br> Finish what matters or walk away—don’t keep reopening old goals you’ve already moved past. ## Works Consulted 1. [Product Goal](https://www.scrum.org/resources/product-goal) | Scrum.org | Accessed 23 Jul. 2025. 2. [[Prompted to Learn]] Study Session | Explored 22 Jul. 2025 | Recall the rule that only one Product Goal can exist at a time ## Connections follows:: [[1.3b One Product Goal Keeps the Team Moving in a Single Direction]] topics:: [[Product Goal]], [[Focus]] ![[Footer]]