Design Doc | Discovery | Exploration | Go to market
Keep the refined problem statement in mind when exploring solutions:
In which way might we enable ${user} to solve ${mainNeed1} & ${mainNeed2}, to ${userGoal} & ${businessGoal}?
Get help with a hypothesis framework.
| If | then | due to |
|---|---|---|
| ${hypothVariable} | ${predictedResult} | ${hypothRationale} |
Drawings, surveys, flow charts, prototypes. UI, code repos, and more.
| Date | Creator | Artifact |
|---|---|---|
For when multiple ideas to solve the problem statement are needed. Use the table below or this google sheet.
| Person | Concept |
|---|---|
| Grouped concepts |
|---|
For ranking solutions against the right problems. Use the table below or this google sheet.
| Needs | Grouped concept 1 | Grouped concept 2 |
|---|---|---|
| Need 1.1 (main or sub or indv) | ||
| Need 1.2 | ||
| Need 2.1 (main or sub or indv) | ||
| Need 2.2 | ||
| Cost (difficulty) | ||
| Wow factor | ||
| Elegance & beauty | ||
| Scalability | ||
| Totals |
Use the following questions to understand what you need to learn from your user test.
General
What business challenges are being addressed?
What questions are being answered?
What needs to be understood from this study?
Users
Who might be using this part of the product, experience, service, app, site, etc?
Goals
What specific questions need answers?
How will the insights be used from this study?
| Version | KPI 1 | KPI 2 |
|---|---|---|
Next is go-to-market