<aside> ❗ This is the Hustle Badger template for a PRD (Product Requirements Document). All text in italic is placeholder. You should put the title of the feature above, and also delete this box.
</aside>
Owner | [The PM who owns this PRD, first point of contact for stakeholders] |
---|---|
Team | [The team working on this PRD] |
Summary | [1 line summary of what this feature is] |
Status | [Current status, e.g. Discovery / Delivery / Roll Out / Live] |
Next Milestone | [Timing of next major milestone, e.g. Product Review 28th March] |
What we are trying to achieve with this feature. Which company goals it relates to.
The metric that we will use to measure whether the feature has been successful.
Who needs to be kept up to date on the progress of this feature, or should be giving input on it.
Responsible | The people doing the work. Usually the team |
---|---|
Accountable | The person ultimately responsible for the work. Usually the PM |
Consulted | Stakeholders that should have input into the feature. i.e. two-way dialogue |
Informed | Stakeholders that should be kept up to date, but who don’t need input into the feature. i.e. one-way dialogue |
This is the core of this section, detailing why this is important to work on, from both a user and business perspective. It likely links to other strategy documents and existing insights the team has.
Notes on what is in and out of scope, as well as any constraints that the team should bear in mind, such as a limit to the time or investment that can be made, or impact on other teams.
The key risks that the team has identified and is working to reduce.
Diagrams showing the states and screens that the user can move between. Ideally these can be embedded Figma / Miro / etc. files that are automatically kept up to date.