PRD Writing Language
5 exercises — Practice writing problem statements, hypotheses, acceptance criteria, and scope boundaries in professional product management English.
0 / 5 completed
1 / 5
A PRD begins with: "We will build a one-click payment integration using Stripe because users abandon checkouts." A senior PM asks you to critique the problem statement. Which assessment is most accurate?
A problem statement belongs entirely in the problem space — it describes what is wrong and why it matters, without naming the solution.
When a PRD opens with "we will build X using Y", it skips the most important thinking: validating that X is actually the right solution to the problem. Strong problem statements quantify the pain (abandonment rate, revenue impact, support tickets), cite evidence (user research, analytics), and leave the solution open for discovery. This creates room for the team to challenge assumptions and find better solutions than the first one proposed.
Key vocabulary:
• problem statement — defines the user pain, its scope, and business impact; solution-agnostic
• problem space — the domain of unmet needs and pain points; explored before committing to solutions
• solution space — specific product ideas and implementations; entered after validating the problem
When a PRD opens with "we will build X using Y", it skips the most important thinking: validating that X is actually the right solution to the problem. Strong problem statements quantify the pain (abandonment rate, revenue impact, support tickets), cite evidence (user research, analytics), and leave the solution open for discovery. This creates room for the team to challenge assumptions and find better solutions than the first one proposed.
Key vocabulary:
• problem statement — defines the user pain, its scope, and business impact; solution-agnostic
• problem space — the domain of unmet needs and pain points; explored before committing to solutions
• solution space — specific product ideas and implementations; entered after validating the problem