PRD: [PRD TEMPLATE]

How to use this document

Use it as a checklist to make sure you cover all bases, remove anything you don’t need.

Work fast and light. A good PRD is <1000 words and it includes diagrams (that’s two pages, not including the 525 words for the template).

Write it in the open (no private documents!). Once it’s in Ready state, share it with everyone via Slack.

TL;DR

Too Long; Didn’t Read. Be answer first. If someone only reads this far, what do you want them to know?

OKRs

What company goals can we tie this work back to? What’s our prediction for how those OKRs will be impacted once this work is done? Complete the table and add an explanatory paragraph if needed.

Who?

Who are we solving this for?

What?

What problems do we want to solve? What are we not trying to solve? What’s in scope and what’s out of scope? Prevents scope creep. Bullets only.

Why?

Why are we trying to solve the problem? How do we know this is a real problem and one worth solving now? Use data or qualitative research insights where you can.

Success

What does success look like? How will success be measured?

What is it?

Roughly, what does it look like in the product? What are the requirements of a solution to the problem?

How?

What’s the experiment plan? How will we approach solving the problem?

When?

When does it ship and what are the milestones?

Alternatives

What are some alternatives that we’ve considered but we’re not recommending?

Further Reading

Any further reading or prior art goes here. E.g:

• 1 Pagers/PRDs by Lenny Rachitsky

</div><div 
  data-tab-item="Markdown"
  data-tab-group="default"
  class='tab-item '>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-Markdown" data-lang="Markdown"><span class="line"><span class="cl"><span class="gh"># PRD: [PRD TEMPLATE]

### <remove> ### How to use this document Use it as a checklist to make sure you cover all bases, remove anything you don’t need. Work fast and light. A good PRD is <1000 words and it includes diagrams (that’s two pages, not including the 525 words for the template). Write it in the open (no private documents!). Once it’s in Ready state, share it with everyone via Slack. ### </remove> | Status | Draft, Ready, Accepted, Rejected, Superseded | | — | — | | Created | @June 1, 2022 | | Owners | Tag using @ to notify. | | Reviewers | Tag using @ to notify. | ## TL;DR Too Long; Didn’t Read. Be answer first. If someone only reads this far, what do you want them to know? ## OKRs What company goals can we tie this work back to? What’s our prediction for how those OKRs will be impacted once this work is done? Complete the table and add an explanatory paragraph if needed. | OKR | Target | Projected Impact | | — | — | — | | | | | ## Who? Who are we solving this for? ## What? What problems do we want to solve? What are we not trying to solve? What’s in scope and what’s out of scope? Prevents scope creep. Bullets only. ## Why? Why are we trying to solve the problem? How do we know this is a real problem and one worth solving now? Use data or qualitative research insights where you can. ## Success What does success look like? How will success be measured? ## What is it? Roughly, what does it look like in the product? What are the requirements of a solution to the problem? ## How? What’s the experiment plan? How will we approach solving the problem? ## When? When does it ship and what are the milestones? ## Alternatives What are some alternatives that we’ve considered but we’re not recommending? ## Further Reading Any further reading or prior art goes here. E.g: - [1 Pagers/PRDs](https://www.lennysnewsletter.com/i/683946/pagers-prds) by Lenny Rachitsky