key: "prd" title: "t:templates.prd.title" description: "t:templates.prd.description" appliesTo: "wiki" icon: "fa-file-lines" author: "Leantime" version: "1.0.0" license: "CC0" sector: "t:templates.documents" wiki: articles: - title: "Product Requirements Document" # Inline {{ t:KEY }} substitutions handled by TranslationResolver at # consume time. Author / Date placeholders dropped — the hardcoded # version baked $author/$today into the HTML, but for a registry- # served template those need to be editable affordances, not baked. content: |
{{ t:templates.author }}
{{ t:templates.dates }}
{{ t:templates.status }} {{ t:templates.status.draft }}
| {{ t:templates.prd.responsible }} | {{ t:templates.prd.approve }} | {{ t:templates.prd.consulted }} | {{ t:templates.prd.informed }} |
{{ t:templates.prd.overview_description }}
{{ t:templates.prd.problem_description }}
1. Goal
2. Goal
3. Goal
1. Risk
2. Risk
3. Risk
Who are the target personas for this product, and which is the key persona?
| Customer | Description (interests, likes, demographics, where to find them) |
| Customer | Description (interests, likes, demographics, where to find them) |
| Customer | Description (interests, likes, demographics, where to find them) |
Instances where various personas will use the product, in context.
Describe the use case
Describe the use case
Describe the use case
When you’ve locked in your One Pager, build out your PRD. Use the finalized One Pager and the following.
These are the distinct, prioritized features along with a short explanation of why this feature is important. Briefly outline the scope, the goals, and use case.
What features have you explicitly decided not to do and why?
Include any needed early sketches, and throughout the project, link to the actual designs once they’re available.
Link to engineering technical approach document.
What are the success metrics that indicate you’re achieving your internal goals for the project? How will you measure success? You can use any goal-setting and tracking system you prefer (OKRs, KPIs, etc).
Note: Link to Analytics requirements and approach document.
What’s the product messaging that your marketing department will use to describe this product to existing and new customers? How do you plan to launch this product to the market with marketing and sales teams?
Note: Link to a larger GTM brief if available.
What factors do you still need to figure out? What problems may arise and how do you plan on addressing them?
What are common questions about the product along with the answers you’ve decided? This is a good place to note key decisions.
| Question | Answer | Asked By | Answered By |
Here’s a list of topics you must include in your PRD: