Guide
From Pain Point to Plan
Turn a real, sourced pain point into a build-ready plan without losing the evidence: score, cluster, write the problem, and hand it off.
A pain point is not a plan. This guide walks the path from a single real complaint to a plan you can actually build, without losing the evidence that made it worth doing.
Anatomy of a real pain point
A useful pain point has a person, a job they are trying to do, a failure of the current approach, and a cost. Strip out solutions and opinions; keep the underlying problem and its evidence.
Score it honestly
Rate intensity, frequency, and willingness to pay. Be skeptical: a vivid anecdote is not the same as broad, recent, paid demand.
Cluster duplicates into one opportunity
Merge quotes that describe the same underlying problem. The cluster, not any single quote, is what you prioritize.
Write the one-paragraph problem
Compress the cluster into a single problem statement. This becomes the spine of the plan and the thing you will measure against later.
Hand it to a plan
Feed the problem and its evidence into a plan: signal, then insight, then theme, then a PRD. Keep the source quotes attached so the "why" survives all the way to the build.