---
title: "PRD Template"
type: template
template_for: "a right-sized client PRD (bug, small task, feature, or epic)"
notion_copy: "https://app.notion.com/p/3d828f1440b98099845ce32447400604"
used_by: [write-prd]
kit: ""
date_added: 2026-10-22
last_reviewed: 2026-10-22
tags: []
---

# PRD template

Copy this file into the repo's planning docs, named `[initiative]-prd-[client]-[YYYY-MM-DD].md`. Delete this how-to block. Drop any section the size tier does not need. Do not pad a small thing to look like an epic.

**Before you draft: interview the owner.**

Read whatever the owner already gave you first. Then ask only about what is still missing, one question at a time, and wait for the answer before asking the next. Do not send a numbered list of ten questions. Do not ask about anything the brief already answers. Stop asking once you have enough to write a first pass; a gap is allowed to ship as `Proposed` or `TBD`.

**Offer options where you can.** When a question has a small set of likely answers, give the owner two to four of them rather than a blank prompt. It is faster to react to a wrong option than to write from nothing. Always end with an escape hatch, for example "or describe it in your own words" — the owner's own wording beats any option you listed, and a picked option is never a substitute for detail they wanted to give. Keep genuinely open questions open: do not offer a menu for the user flow, the key features, or anything where a list would narrow their thinking before they have started.

Work through these in order, skipping any the brief already covers:

1. **Who is this for?** The client or team, and the reader of the PRD.
2. **Who actually uses this, and what frame of mind are they in?** Not the buyer, the person in the flow. Push for the emotional state and its cause, for example anxious, rushed, sceptical, or doing this for the hundredth time today. Then ask what that should change about the tone and pacing.
3. **What is wrong today?** The current behaviour, and why it is a problem. For a bug, get the expected behaviour too.
4. **Why now?** What the change is worth, and what happens if it waits.
5. **What are the key features?** Ask the owner to walk through what the thing actually does, in their own words.
6. **What does the user do, step by step?** The flow, start to finish. If the owner cannot describe it, that is an open task for a designer, not a gap for you to invent.
7. **What is explicitly out of scope?** The best single question for stopping an epic from ballooning.
8. **What is fixed?** Constraints, dependencies, deadlines, and anything already decided.
9. **What does done look like?** How the owner will know it worked.
10. **Any refs?** Figma, tickets, recordings, competitor examples.

**Play it back, then ask permission.** Before writing anything, give the owner a short high-level recap of the PRD you are about to write: the problem, the value, the key features, the flow in a line, what is in and out of scope, and what done looks like. Keep it to a handful of bullets, not a draft. Name in one line anything still unknown that you will have to mark `Proposed` or `TBD`.

Then ask plainly: "Want me to write the full PRD from this?" Stop and wait. Do not start writing in the same message as the recap. Write the full document only after the owner says yes; if they correct something first, fold it in and re-confirm.

**Size tier (pick one, then delete the unused sections):**


| Tier              | Keep                                                                                                                                 |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| Bug / fix         | Header, Current Issue, screenshots/refs, brief Scope                                                                                 |
| Small task        | Header, Overview, Scope, Success Criteria, one Considerations block if needed                                                        |
| Feature (medium)  | Header, Overview, Why/Value, User and Mindset, Key Features, User Flow, Scope, Constraints & Assumptions, Open Questions, Success Criteria, References |
| Epic / initiative | Full template. Break User Flow into sub-flows. Cross-reference related PRDs                                                          |


**Mark every gap (do not leave a blank that looks like a decision):**

- **Resolved** — state it plainly.
- **Proposed - needs validation:** — first-pass draft the owner should react to. Default when a section is missing.
- **TBD - open task. Owner: [role]** — someone must go define this (research, flow mapping, competitive analysis).

Voice: third person, present/future tense. No first person. Bullets over prose. Skimmable in about 90 seconds. This is the client's product work, not Monico framing.

---



# [Initiative Title] — PRD


|                    |                                                |
| ------------------ | ---------------------------------------------- |
| **Client**         | [client]                                       |
| **Type**           | Epic / Initiative / Feature / Small task / Bug |
| **Status**         | Draft / In review / North Star                 |
| **Owner**          | [name/role]                                    |
| **Date**           | [YYYY-MM-DD]                                   |
| **Designs / refs** | [Figma / doc / ticket links, or TBD]           |




## Overview

[What this initiative is, in a few sentences. The shape of the work.]

## Why / Value

[The value and the justification for the effort. If RICE or roadmap context exists, distill it to why this is worth doing now. One short paragraph.]

## User and Mindset

*Who actually uses this, and the state of mind they are in when they arrive. This section governs tone, pacing, and how much the interface explains. Skip it and the work defaults to neutral product voice, which is the wrong voice for a lot of flows.*

**Who:** [The person in the flow, not the person who bought the software. Their role, their context, how often they do this, what device they are on.]

**Mindset:** [What they are feeling and thinking at the moment they enter this flow, and why. Be specific about the emotion and its cause. "Users want clarity" is not a mindset.]

**What that means for the design:**

- [A concrete consequence. Each one should be checkable in a review.]
- [Another.]

> **Worked example, delete this block.**
> **Who:** a patient opening the app to read a lab result, usually alone, usually within minutes of the notification, usually on a phone.
> **Mindset:** anxious. Before they want any detail, they want to know one thing: is something wrong. Numbers on a chart read as a verdict they cannot interpret.
> **What that means for the design:** lead with a plain-language read of the result before the raw values; say what is normal and what is not in words, not colour alone; no unexplained clinical terms; warm, direct copy with no false cheer; give a next step on every abnormal result so the screen is never a dead end.

## Current Issue

*Bug / problem PRDs only. Delete this section otherwise.*

**Current behavior:** [what happens today and why it is a problem]

**Expected behavior:** [what should happen instead]

**Screenshots / links:** [issue tracker, recordings, or TBD]

## Key Features

- [Feature.] Resolved / Proposed / TBD - open task. Owner: [role]
- [Feature.]
- [Feature.]



## User Flow

*For an epic, break this into named sub-flows. If a designer must map it, mark the whole section as an open task.*

1. [Step]
2. [Step]
3. [Step]



## Scope

**In scope:**

- [what is being done now]

**Out of scope:**

- [what is explicitly deferred, so nothing balloons]



## Constraints & Assumptions

*Answers, not questions. Technical constraints, dependencies, and facts we are building on.*

- [Constraint or assumption]



## Open Questions

*Decisions that still block or shape the work. Keep these separate from constraints.*


| #   | Question   | Owner  | Notes                            |
| --- | ---------- | ------ | -------------------------------- |
| 1   | [Question] | [role] | [what has to happen to close it] |




## Success Criteria

*Definition of done. Acceptance-style checklist or a plain "done when..." statement.*

- [ ] [Criterion]
- [ ] [Criterion]



## References

- [Related PRD / initiative]
- [Competitor example]
- [Source notes / ticket / Figma]

