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} |
Quickly identify the right problem and solve it with the right people in a Lightning Design Jam. At the end of the design jam using an Impact / Effort ranking system is very helpful. Here is another ranking system should you need one a bit more in-depth: Concept Selection Matrix
Drawings, surveys, flow charts, prototypes. UI, code repos, and more.
| Date | Creator | Artifact |
|---|---|---|
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