# Writing PRDs — Exercises

## Exercise 1: Problem vs Solution

**Task:** For each statement, label it as a **problem** or **solution**. If it's a solution, rewrite it as a problem statement.

1. "We need a search bar in the header."
2. "Users spend 5+ minutes trying to find the export option, often giving up."
3. "Add a dark mode toggle to settings."
4. "New users abandon the onboarding flow at step 3 at a 40% rate."

**Validation:**
- [ ] Problems focus on pain, context, and impact
- [ ] Solutions are rewritten to describe the underlying problem
- [ ] No solution language in problem statements (no "we need," "add," "implement")

**Hints:**
1. Problem = who, what pain, why it matters
2. Solution = the proposed fix (feature, button, page)
3. "Users can't find X" is problem; "We need search" is solution

---

## Exercise 2: Write a JTBD

**Task:** Pick a feature you know (real or hypothetical). Write a Jobs To Be Done statement using: *When [situation], I want to [motivation], so I can [outcome].*

**Validation:**
- [ ] Situation is specific (context, circumstance)
- [ ] Motivation is the goal or need
- [ ] Outcome is the benefit or result
- [ ] The statement is about the user, not the system

**Hints:**
1. Start with "When I..." — the situation grounds the job
2. "So I can" ties the action to value
3. Avoid feature names; describe the job in user terms

---

## Exercise 3: Make Metrics SMART

**Task:** These metrics are vague. Rewrite each as a SMART metric (Specific, Measurable, Achievable, Relevant, Time-bound). Include baseline, target, and timeframe where possible.

1. "Improve user satisfaction"
2. "Reduce time to complete onboarding"
3. "Increase engagement"

**Validation:**
- [ ] Each metric names a specific measure
- [ ] Baseline and target are included (or justified if unknown)
- [ ] Timeframe is stated
- [ ] Metric is actionable (you could track it)

**Hints:**
1. "Improve" → improve what? NPS? CSAT? Task completion?
2. Add numbers: "from X to Y by [date]"
3. If baseline is unknown, note "TBD—measure first"

---

## Exercise 4: Write Non-Goals

**Task:** For a feature you're familiar with (e.g., "user profile export"), write 3–5 non-goals. These are things stakeholders might assume are in scope but are explicitly out.

**Validation:**
- [ ] Non-goals are concrete (not "everything else")
- [ ] Each is plausible scope creep
- [ ] Language is clear: "We will NOT..."
- [ ] At least one addresses "nice to have" vs "must have"

**Hints:**
1. Think: What would stakeholders ask for? "Can we also...?"
2. Non-goals prevent "while you're at it" creep
3. "Phase 2" or "Future consideration" can be non-goals

---

## Exercise 5: Minimal PRD Draft

**Task:** Draft a minimal PRD (1–2 pages) for a small feature. Include: Problem, Goals, Non-Goals, Success Metrics, and 2–3 User Stories. Use the PRD structure from the content.

**Validation:**
- [ ] Problem statement is problem-focused, not solution-focused
- [ ] Goals and non-goals are explicit
- [ ] Success metrics have baseline/target/timeframe (or TBD noted)
- [ ] User stories follow "As a / I want / So that" format
- [ ] Document is readable in under 5 minutes

**Hints:**
1. Start with the problem—everything else supports it
2. Keep each section concise; 2–3 bullets each
3. Open questions are fine—list them explicitly