Parks booking analytics show a sharp drop in evening tennis reservations, but staff disagree about why. How should the Product Owner build customer insight?
Select an answer to reveal the explanation.
Short Explanation
Dashboards tell you the score; conversations tell you why the team is losing. You want both. A lonely chart or a single loud captain will send the backlog on a wild goose chase.
Full Explanation
Mixed-method insight is a core stakeholder and customer practice for civic Product Owners. When parks booking analytics show a sharp drop in evening tennis reservations but staff disagree about why, quantitative analytics surface what changed while qualitative interviews explain jobs, friction, and unmet demand. Either source alone is easy to misread—metrics without meaning, or anecdotes without scale. The Product Owner should combine the quantitative drop with qualitative interviews to inform Product Backlog order rather than waiting for a slow annual survey.
Trusting only the dashboard fails because numbers without player context invite false causal stories. Trusting only a single vocal league captain fails by elevating one anecdote over patterned evidence. Waiting for the next annual citizen survey fails because it delays adaptation while evening demand keeps falling.
Exam caveat: Pair quantitative signals with qualitative insight before major backlog moves. Operational check: For the tennis drop, pull reservation analytics by hour and site, interview a small sample of evening players and staff within two weeks, then order backlog hypotheses that explain both data and stories.