How to Write PRDs for Product Managers
Lesson 2
Step One: Define the Problem Clearly
Everything begins here. Before a single word of the PRD is written, the problem must be understood well enough to be stated with precision. This step is not a warm-up. It is the most important work in the entire process.
A problem that is vague at this stage will produce a PRD that is vague throughout, and a product that vaguely addresses something nobody could quite name. The discipline of this step is refusing to move forward until the problem is genuinely clear.
What this step requires you to do:
- Talk to users first. Not assumptions about users. Not secondhand accounts. Direct conversations, support tickets, usability recordings, survey responses. The problem statement must be grounded in evidence that the problem is real, specific, and worth solving.
- Separate the symptom from the problem. A low activation rate is a symptom. The underlying problem is that users do not understand what to do after signing up. Write the PRD about the problem, not the symptom.
- Write the problem statement before anything else. Not in the PRD yet. In a single paragraph, written plainly, that names the user, describes their experience, provides the evidence, and states the impact. If you cannot write this paragraph clearly, you are not ready to write the PRD.
- Ask why at least twice. The first answer to what is the problem is almost never the real problem. Push past the surface to the underlying cause before committing to a direction.
The test for this step is simple: can you explain the problem to someone unfamiliar with the product in two minutes, and do they immediately understand why it matters? If yes, move forward. If not, keep working.