Design Doc | Discovery | Exploration | Go to market
Ensure each project begins with a kickoff meeting, wherein stakeholders and cross-functional team leads come together to synchronize the various users, issues, schedules, and anticipated outcomes.
Define who will be working on this project and what will they be doing.
| Name | Responsibility |
|---|---|
| Project name + Work ticket link | Due date |
|---|---|
| Name | Current state | Desired state |
|---|---|---|
Review the current state as well as competitors’ current states to inform the future state. Keep track Artifacts in the Exploration --> Artifacts table below.
Identify and survey end users, business stakeholders, and subject matter experts to get their problems which will be refined into needs. Use the tables below or this version in google sheets to track and prioritize them.
Scope your users' needs/problems like this to find the root instead of solving symptoms of a deeper problem.
| User | Time/date | Verbatim | Encoded needs like 1, 2, & 3 |
|---|---|---|---|
| ${mainNeed1} | ${mainNeed2} |
|---|---|
| Subneed 1.1 | Subneed 2.1 |
| Individual need 1.1.1 | Individual need 2.1.1 |
| Individual need 1.1.2 | Individual need 2.1.2 |
| Subneed 1.2 | Subneed 2.2 |
| Individual need 1.2.1 | Individual need 2.2.1 |
In which way might we enable ${user} to solve ${mainNeed1} & ${mainNeed2}, to ${userGoal} & ${businessGoal}?
Next is exploration