## How Can Teams Recognize When Their Work Isn’t Creating Value? By analyzing customer behavior, satisfaction metrics, and direct feedback, teams can uncover whether delivered features are achieving the intended outcomes. >[!metaphor] >Launching new features without checking customer response is like opening a restaurant and noticing everyone leaves half their meal untouched. The kitchen may be working hard, but the plates tell the real story; something isn’t hitting the mark.</br> >In the same way, teams need to analyze customer behavior, satisfaction metrics, and feedback to see if their work is actually delivering value, not just output. ## Works Consulted 1. [Why Customer Outcomes Matter](https://www.youtube.com/watch?v=rVeJMarPnUk) | Scrum.org | Accessed 26 Dec. 2024. ## Connections follows:: [[3.4 Delivering Features Does Not Guarantee Value]] topics:: [[Metrics]], [[Feedback]], [[Customer Satisfaction]], [[Customer Satisfaction Gap]], [[Customer Value]], [[Outcome]] Tactic | [[5.1d Outcome Thinking Aligns Scrum Teams With Real Needs]] -> Using an impact map can help ensure that PBIs are tied to outcomes and measures before starting the work which makes it easier to validate we're delivering the intended value after the fact. ![[Footer]]