Versions Compared

Version Old Version 2 New Version Current
Changes made by

Ahmed-Tijani Umar (Unlicensed)

Ahmed-Tijani Umar (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Note: Feel free to remove any section that is irrelevant to you

Team

Owner

The PM who owns this PRD, the first point of contact for stakeholders

TPM

The team working on this PRD

EA

The team working on this PRD

QA

The team working on this PRD

Researcher

The team working on this PRD

Summary

1-line summary of what this feature is

Status

Status
titleDiscovery
|
Status
colourRed
titleDiscoveryTesting
|
Status
colourYellowBlue
titleTestingDesign
|
Status
colourBlueYellow
titleDELIVERYDevelopment
|
Status
colourPurple
titleROLL OUT
|
Status
colourGreen
titlelive

Next Milestone

Timing of next major milestone, e.g. Product Review 28th March

Problem Definition

Expand
titleObjective

What we are trying to achieve with this feature. Which company goals it relates to.

...

Expand
titleScope & Constraints

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.

Reviewed by

Status

Expand
titleRisks & Mitigation

The key risks that the team has identified and is working to reduce.

Risk

Mitigation

Solution Definition

Expand
titleKey Features

Plan of record

  1. List the features that shape the solution

  2. Ideally in priority order

  3. Think of this like drawing the perimeter of the solution space

  4. Draw the boundaries so the team can focus on how to fill it in

  5. Link out to sub-docs for more detail for particularly large projects

  6. Challenge the size to see if a smaller component can be shipped independently

Future considerations

  1. Optionally list features you are saving for later

  2. These might inform how you build now

Reviewed by

Status

...

Expand
titleDecision Log

Question

Decision made

Decider

Date

What is the question or alternatives we need to decide between

What was the decision made, and why

Who made this decision

When was this decision made

Launch Readiness

Expand
titleKey Milestones

TARGET DATE

MILESTONE

DESCRIPTION

EXIT CRITERIA

YYYY-MM-DD

✅ Pilot

Internal testing with employees only

No P0 or P1 bugs on a rolling 7-day basis

YYYY-MM-DD

🛑 Beta

Early cohort of 20 customers

At least 10 customers would be disappointed if we took it away

YYYY-MM-DD

🛑 Early Access

Invite-only customers from sales

At least 1 win from every major competitor

YYYY-MM-DD

🛑 Launch

All customers in current markets

Measure and monitor

...

Expand
titleFAQs

It's useful to answer anticipated questions from both internal stakeholders and external users ahead of the feature going live. In some situations, this might include updating your public FAQs or support documents.

Impact

Expand
titleSuccess

How much the release moved its success metrics. How much it contributed to the team's objective.

...

Expand
titleNext steps

Any follow-up actions arising from the release. Whether AB tests will be rolled out or rolled back. Further phases of developing this solution.

Changelog

DATE

DESCRIPTION