The tiny opportunity
A loud complaint may describe a rare, low-cost problem. · PM Drills · 07 · 30 sec–2 min
The tiny opportunity · 30 sec–2 min
Situation
A senior stakeholder hates a settings flow.
They use it twice a year and spend about one extra minute each time. Fixing it would take the team a week.
Think before scrolling
What would you verify before prioritizing it?
What evidence could make the problem more important than the initial numbers suggest?
How a strong PM thinks
Check reach and consequences beyond the complaint.
Investigate whether many users face the same issue, whether it creates errors or blocked work, and whether it signals a broader usability problem. Also check if a small change could resolve most of the friction.
If it is truly rare and low impact, defer it with a clear reason. Do not manufacture a large opportunity estimate to avoid an uncomfortable conversation.
Takeaway
A complaint is a signal, not a size estimate.
Evaluate the affected population, frequency, severity, and cost of a proportionate fix.