Difference between revisions of "Solution Development"
(→Discovery) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
==[[Insight]]== | ==[[Insight]]== | ||
| − | 1. ''Mission Insight'' - [Aspirer]]s define why the [[mission]] is important and what is [[mission]] success | + | 1. ''Mission Insight'' - [[Aspirer]](s) define why the [[mission]] is important and what is [[mission]] success |
* [[Aspirer Development]] - Why is this [[mission]] important to the [[aspirer]]? What is [[mission]] success (Aspirer Requirements)? What [[aspirer]] and [[beneficiary]] [[Problem/Unmet Need|problem/unmet need(s)]] must be addressed to achieve the [[mission]]? What is the source or cause of each the [[Problem/Unmet Need|problem/unmet need(s)]]? <br> | * [[Aspirer Development]] - Why is this [[mission]] important to the [[aspirer]]? What is [[mission]] success (Aspirer Requirements)? What [[aspirer]] and [[beneficiary]] [[Problem/Unmet Need|problem/unmet need(s)]] must be addressed to achieve the [[mission]]? What is the source or cause of each the [[Problem/Unmet Need|problem/unmet need(s)]]? <br> | ||
2. ''Solution Insight'' - [[Aspirer]] and [[beneficiary]] insight into addressing [[Problem/Unmet Need|problem/unmet need(s)]] - ''Market Research''<br> | 2. ''Solution Insight'' - [[Aspirer]] and [[beneficiary]] insight into addressing [[Problem/Unmet Need|problem/unmet need(s)]] - ''Market Research''<br> | ||
| Line 66: | Line 66: | ||
==[[Iteration|Iterate]]== | ==[[Iteration|Iterate]]== | ||
Repeat steps 16 - 18 often | Repeat steps 16 - 18 often | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 15:06, 13 November 2016
Solution Development is the process of designing, creating, producing and securing adoption of the solution to ensure the mission is achieved and problem/unmet need(s) are addressed in the enablement of an eDream.
Contents
Insight
1. Mission Insight - Aspirer(s) define why the mission is important and what is mission success
- Aspirer Development - Why is this mission important to the aspirer? What is mission success (Aspirer Requirements)? What aspirer and beneficiary problem/unmet need(s) must be addressed to achieve the mission? What is the source or cause of each the problem/unmet need(s)?
2. Solution Insight - Aspirer and beneficiary insight into addressing problem/unmet need(s) - Market Research
- Aspirer Development - will addressing the problem/unmet need(s) achieve the mission?
- Beneficiary Development - do they believe they have problem/unmet need(s)? If so, how are they addressing it now?
5. Enablement Insight - determine what it would take to get the solution created, produced and adopted
- Decision Maker Development - what Decision Makers need to approve solution creation, acceptance or funding
- Contributor Development - what contributions will be required by Contributors to make it happen
- Knowledge Development - what Knowledge will be needed to make it happen
- Funding Development - what Funding will be needed to make it happen
- Personal Development - what Personal Needs will need to be addressed to make it happen
Discovery
3. Solution Design Requirements - define requirements for each eDream element to ensure mission is achieved and problem/unmet need(s) are addressed - Solution Requirements
- Aspirer Development - Aspirers requirements to accept that the solution achieves the mission and addresses the problem/unmet need
- Beneficiary Development - Beneficiary requirements to accept and adopt the solution to address their problem/unmet needs
- Operational Development - operational requirements to produce the solution
- Communications Development - communications requirements communicate the solution
6. Solution Enablement Requirements - determine the enablement approach and requirements (the How?) to get the solution created, produced and adopted
- Decision Maker Development - the approach and Decision Maker requirements to secure approval
- Contributor Development - the approach and Contributor requirements to secure contributions
- Knowledge Development - the approach and Knowledge requirements to secure it
- Funding Development - the approach and Funding requirements to secure it
- Personal Development - the approach and Personal Needs requirements to secure it
- Operational Development - the approach and Operational requirements to ensure enablement of the solution
- Communications Development - the approach and Communication requirements to ensure enablement of the solution
8. Solution Design Validation - insight into whether the solution design will achieve acceptance and likely adoption - Market Research
- Aspirer Development - will the solution design achieve aspirer acceptance that it address the problem/unmet need(s) achieve the mission?
- Beneficiary Development - will they believe the solution design addresses their problem/unmet need(s)? If so, would they adopt the solution?
- Decision Maker Development - will the solution design achieve Decision Maker approval of the solution creation, acceptance or funding
11. Solution Experience - people experience solution to determine the value and likelihood of adoption - Market Research
- Aspirer Development - experience solution to determine if it will address the problem/unmet need(s) achieve the mission?
- Beneficiary Development - experience solution to determine the value of it addressing the problem/unmet need(s)? How it looks, feels, ease of use, ease to try, ease to see value, ease to adopt, time to achieve return-on-investment. Will they adopt the solution?
- Decision Maker Development - experience solution to determine the value from solution acceptance
16. Solution Adoption Validation - understand why or why not people are adopting the solution and what they want improved - Market Research
- Beneficiary Development - have they adopted the solution? If yes, what do they want improved? If no, what would it take to get them to adopt?
- Decision Maker Development - have they accepted the solution? If yes, what do they want improved? If no, what would it take to get them to accept it?
Planning
4. Solution Design - the solution approach, solution elements and detailed design that addresses the Solution Design Requirements
7. Solution Enablement - the solution enablement approach and enablement elements to address the Solution Enablement Requirements
9. Solution Design and Solution Enablement Update - update to address the discovery from the Solution Design Validation
12. Solution Design and Solution Enablement Update - update to address the insight from the Solution Experience
17. Solution Design and Solution Enablement Update - update to address the insight from the Solution Adoption Validation
Execute
10. Solution Creation - actions to create the solution
- Operational Development - operational actions to produce the solution
- Communications Development - communications actions communicate the solution
Either the entire solution or a minimally viable solution (MVS) is created. A MVS is a solution that is less than complete, yet is enough complete for the beneficiaries to fully experience the solution before completing the entire solution.
13. Solution Creation Update - create the revised solution based on new solution design resulting from Solution Design Experience
- Repeat steps 11, 12 and 13 until it provides the value Beneficiaries and Decision Makers want
14. Solution Production - actions to scale the initial and ongoing production of the solution
- Operational Development - operational actions to ensure efficiency, effectiveness, scale and low cost production of the solution
15. Solution Awareness - actions to create awareness of the solution
- Communications Development - communications actions to ensure awareness for full-scale solution adoption
18. Solution Improvement - actions to improve the solution, operational and communications to ensure full-scale solution adoption
Iterate
Repeat steps 16 - 18 often
