PRD one-pager template
A product requirements doc on one board: problem, goals, non-goals, users, requirements, metrics, risks and timeline.
Use this templateFree, opens in your browser. No sign-up.
What's on the board
- Problem
- Who has the problem? · Evidence: tickets, interviews, data
- Goals
- Outcome we want, measurable · Why now?
- Non-goals
- What this release will NOT do
- Target users
- Primary persona · Secondary persona
- Requirements
- Must: … · Should: … · Could: …
- Success metrics
- Primary metric + target · Guardrail metric
- Risks & open questions
- Biggest assumption · Open question + owner
- Timeline & milestones
- Design done · Beta · GA
- Stakeholders
- Decider · Consulted: eng, design, sales, support
How to use this template
- Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
- Double-click any box to change its text. Replace the examples with your own content.
- Add notes fast. Press S for a sticky note in the middle of your view. A sticky is a box like any other: link it, recolour it, resize it.
- Paste a table. Paste comma- or tab-separated text and it becomes a table. Tab moves to the next cell and adds rows as you go.
- Let Smart Assist draft the next step. Turn on Suggest, finish a label and pause: the next steps appear as dashed ghosts. Tab keeps them, Esc dismisses them.
Good for
- prd
- requirements
- product manager
- spec
- pm
- Planning a quarter or a release
- Prioritising a long backlog with a shared method
- Connecting outcomes to the work that should move them
Related templates
Now / Next / Later roadmap
An outcome-based product roadmap without fake dates: what we're doing now, next, later, and what we're not doing.
RICE prioritization
Score features by Reach, Impact, Confidence and Effort to rank a backlog with numbers instead of opinions.
Opportunity solution tree
Connect one outcome to customer opportunities, candidate solutions and the experiments that test them.
North Star metric tree
Break your North Star metric into input metrics a team can move, and the levers behind each one.
Non-functional requirements
Measurable quality attributes — availability, performance, security, recovery and more — with how each is verified.
UML use case diagram
Actors, the system boundary and the use cases they take part in, with «include» and «extend» relationships.