| Page Properties | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Table of Contents |
|---|
📔 Process and Documentation
Be sure to check the communications process and start the internal communications template.
Hypothesis
E.g. By doing this we intend to [XYZ]. If we get this right we expect to see [IMPACT]. It is OK for the outcome to be a ‘learning’.
...
Must be quantitative and timebound e.g. Increase X from Y to Z by [DATE]. Also be sure that these are directly attributable to the work within control of Product (or state where this might not be the case). For example, a new feature without promotion might not be discovered and adopted).
Goal / Outcome | Metric |
|---|---|
📈 Market, Competition and Opportunity Analysis
...
What would need to be true for this to be successful…
The risks to consider include:
Desirability - will they want it
Usability - can we make it simple enough to understand and use
Feasibility - can we build it
Viability - it fits with our business model
Low Risk | High Risk | |
|---|---|---|
Low Knowledge Little data available |
| Anything in here needs testing…
|
High Knowledge |
|
|
\uD83D\uDDD2 Requirements
A high level overview…
Requirement Headline | Details | Importance | ||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
|
|
\uD83C\uDFA8 Solution Discovery
We are going to build a feature that achieves [ABC] by doing [XYZ].
Include links to:
Designs
User testing and results
Flow diagrams
Tech solution (architecture design and other assets)
Open Questions
Question | Answer |
|---|---|
Out of Scope
Explicitly state what is not covered by this work (where it might reasonably be assumed it would be covered).
...