A city services suite covering 311, permits, and utilities shows high login counts but low satisfaction scores. What should the Product Owner investigate?
Select an answer to reveal the explanation.
Short Explanation
High usage with low smiles is a crowded counter, not a love story. People may have no other door. Look at why the experience is miserable instead of throwing a party for login totals.
Full Explanation
High login counts with low satisfaction on a city services suite covering 311, permits, and utilities signal vanity usage masking poor value quality—especially when the suite is the only official channel. The Product Owner should investigate why residents keep using the suite while remaining unsatisfied rather than celebrating logins. Treating logins as sufficient Current Value closes the inquiry too early. Hiding the satisfaction survey because it conflicts with the usage dashboard withholds evidence. Adding more products so usage counts rise further deepens the vanity trap. Exam caveat: Current Value includes quality of experience, not just traffic. Operational check: segment dissatisfied journeys, map pain to backlog items, prioritize fixes that raise satisfaction and task completion, and report both usage and satisfaction together so leadership cannot read one without the other. Login vanity with low satisfaction on a 311-permits-utilities suite demands investigation of value quality, not more products or hidden surveys. Report usage and satisfaction together and prioritize journeys that raise completion and reduce frustration. Segment low-satisfaction, high-login journeys across 311, permits, and utilities; pick the worst friction path next on the Product Backlog and track satisfaction for that path independently of raw logins.