ABCDEFGHIJKLMNOPQRSTUVWXYZAAABACADAEAFAGAHAIAJAKALAMANAOAPAQAR
1
Driven by..Document section
Product need in a PRD
Design need in a PRD
Engineering need in a PRD
Chat
Ratings tool
Customer Platform
Banking Product
Fraud & Safety
Fraud & Safety
Home Shortcuts
Order Improvement
Order System
Image sharing
B2B Comms
Archiving
Ratings page
Loyalty
Block codes
KYC Flow
Count of section
Description
2
1ProductClear Title16
Clear PRD title that anyone can understand
3
2ProductAuthor, date & status12
So know who to contact and if recent update made
4
3ProductRACI9
List of roles, people and statuses
5
4ProductDocument list7
Single place with all docs listed e.g design, asana, content, dashboards
6
5ProductCompany Product Principles4
Details of what principles applied and why
7
6BusinessShort TLDR (WHY)6
2-3 line summary of what this PRD is (especially the WHY)
8
7BusinessProblem statement16
Deep dive into business driver behind change (preferably from business teams)
9
8BusinessOKR Alignement7
What OKRs is this effecting
10
9BusinessImpact Analysis5
Analysis showing how this change will impact certain key numbers
11
10BusinessSuccess metrics13
Numbers that will change if this is successful
12
11BusinessCompetitive benchmarking6
How are competitors solving for this?
13
12ProductProposed Differentiation1
How are we going to be better than competition?
14
13R&DCustomer Research6
What customer research has been done to validate hypothesis?
15
14R&DDesign considerations6
Any pointers for designers e.g. message format
16
15ProductMinimum scope & phasing10
MVP/MoSCoW and any phasing + whats out of scope and how this fits into team's roadmap
17
16ProductRequirement: overview16
Product requirement of solution to implement (flowcharts, user stories)
18
17ProductRequirement: contraints3
Contraints that must be implemented for solution to work
19
18ProductRequirement: user stories8
List of user stories for engineering to implement
20
19ProductRequirement: UX/UI13
URL or screenshots of proposed experience
21
20ProductRequirement: Data & Analytics5
List of important data and events to track
22
21CS&OpsRequirement: Support/Ops plan2
e.g. how will tickets be handled?
23
22ProductRisk register7
List of risks and proposed mitigations e.g. legal, security, compliance
24
23ProductRollout plan8
Milestones, dates, owners, status & experimentations
25
24ProductPost Launch activites1
Impact analysis or research planned to validate impact
26
25ProductDependancies2
What other teams are we dependant on and how are we ensuring completion of those parts
27
26ProductQ&A6
Record of common Q&A
28
27ProductDecision Log2
Log all decisions made over time (can be in Asana?)
29
28ProductGlossary2
Terms used so reader doesnt need prior knowledge
30
29ProductProject Tool URL6
Link to project tool/company wide tracker for all non engineering tasks
31
30ProductChange Log1
List of significant changes to document
32
31ProductInternationalisation1
Explaination how this caters for different country/regions
33
RatingSections found as % of all52%48%45%52%52%42%42%39%42%35%32%29%26%26%16%13%37%
35
36
Keep doing..
Stop doing..
37
Team A
Have state and owner at top of doc so I know any time where this is
Team F
No clear structure to document for reader to follow the flow
38
Team A
Product principles clearly stated
All
Documents just stopped with no end.. should have final status and where to look for result
39
Team B
Clear structure with coloured headings makes easier to follow
Most
Support/Ops condiderations seemes too be missing from many PRDs
40
Team C
Clear entry points into flows showed with UI helps give clearer context to reader
Most
Doc dates didn't have year so couldn't tell if say 'May 21' or 'May 20'
41
Team D
Having a glossary helps reader be clear on terms used if complex domain e.g. GoFin
Most
Don't mention product principles at all
42
Team A
Asana links in ALL their PRDs
43
44
Not all 29 sections found are required in all PRDs, but some are absolute MUSTs
45
46
PRD MoSCoW Legend
47
Must have in any PRD and most people do
48
Must have but most today don't
49
Should have where it makes sense
50
Could have in a PRD where necessary
51
52
JTBD: Create a good PRD
53
Minimise likelihood reader confused
54
Minimise likelihood design doesn't have enough info about problem & constraints
55
Minimise likelihood readers don't feel connection to known business goals
56
Minimise likelihood engineering don't understand and need many sessions to explain
57
Minimse likelihood others say it's a bad PRD
58
Minimise time it takes to know what is a good PRD in my new company
59
Minimise time it takes to get started writing my PRD
60
Minimise time to make my PRD look clean and easy to read
61
Minimise the time to ensure my PRD has a good structure
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101