Creative Methods / working document
Product
Requirements
Document
Define the problem, the people and the conditions for success before a feature list takes over.
- Format
- Interactive / Markdown
- Privacy
- Browser only
- Source
- Read the notes
00
Document record
Give the working document enough context to travel.01
Why this project?
Why does this project exist? What are you trying to achieve?02
What you know
Ground the project in evidence rather than intuition.03
Problem statement
State the problem in one to three sentences. Leave solution language out.Watch for: Common mistake: describing what you want to build instead of the problem it solves.
04
Who is this for?
Name people specific enough to picture.Watch for: A role, situation and existing behaviour are more useful than a broad category.
05
Why now?
Why should this happen now rather than three months from now?06
How you will know it worked
Define success so you can answer yes or no.07
Assumptions
Name what you have assumed. Mark the guesses that could collapse the project.Watch for: An untested assumption is a risk with no owner.
08
Requirements
State requirements as problems to solve and prioritise them.09
Out of scope
What is this project deliberately not?10
Open questions
What do you still need to learn or decide?11