
You're working on a product with several known user frustrations, and different teams are advocating for different fixes. You have usage data, behavioral signals, and some qualitative feedback, but not every problem is equally important to solve first.
How do you use data to decide which user problem is worth solving first?
Ability to identify real user pain points from noisy signalsJudgment in prioritizing problems rather than featuresUse of jobs-to-be-done to frame the underlying needUse of product diagnosis to connect pain to business impact