Development Process

From WikiDreams
Revision as of 09:52, 11 June 2016 by Admin (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

The is the process of understanding (insight and discovery), and executin 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.

Insight

1. Mission Insight - Aspirer(s) define why the mission is important and what is mission success

2. Solution Insight - Aspirer and beneficiary insight into addressing problem/unmet need(s) - Market Research

5. Enablement Insight - determine what it would take to get the solution created, produced and adopted

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

6. Solution Enablement Requirements - determine the enablement approach and requirements (the How?) to get the solution created, produced and adopted

8. Solution Design Validation - insight into whether the solution design will achieve acceptance and likely adoption - Market Research

11. Solution Experience - people experience solution to determine the value and likelihood of adoption - Market Research

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

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

14. Solution Production - actions to scale the initial and ongoing production of the solution

15. Solution Awareness - actions to create awareness of the solution

18. Solution Improvement - actions to improve the solution, operational and communications to ensure full-scale solution adoption

Iterate

Repeat steps 16 - 18 often

Solution Requirements

Incumbant Comparisons

Solution Design

Solution Design is development of the solution to present to the beneficiary(ies) and the Decision Maker(s) to get feedback prior to building or creating the solution.

Solution Build/Create

Solution Build/Creation is the solution developed based on the detailed blueprint of the solution design.

Solution Pilot/Test

Solution Pilot/Test is developing solution built or created by putting it into the hands of the beneficiary(ies) or others to get feedback on the effectiveness of the solution.

Solution Adoption/Benefit

Solution Pilot/Test is the development of the adoption of the solution and ensuring benefits are received by the beneficiary(ies) and Decision Maker(s).

Solution Tracks

To be included in eDream Maps

Creative Content

Design

Innovation

Knowledge

Product/Services