Difference between revisions of "Development Process"

Revision as of 10:27, 11 June 2016

The process of understanding (insight and discovery), planning, executing and iterating the enablement of the eDream.

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? How does the aspirer define mission success? What are the aspirer problem/unmet need(s) that must be addressed to achieve the mission? What is the source or cause of each the problem/unmet need(s)?
  

2. eDream 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 - Who are the beneficiaries (list)? What are the beneficiary problem/unmet need(s) that must be addressed to achieve the mission? What is the source or cause of each the problem/unmet need(s)? Does the beneficiary(ies) believe they have problem/unmet need(s)? If so, how are they addressing it now?
  
• Solution Development - What is the solution approach to address the needs of the aspirer(s) and beneficiary(ies)? What are the solution elements?
  
• Communications Development - What is the communication approach to the beneficiary(ies)? What are the communication elements?
  
• Operational Development - What is the operational approach? What are the operational elements?
  

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. eDream Design Requirements - define requirements for each eDream element to ensure the mission is achieved and problem/unmet need(s) are addressed

• 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
  
• Solution Development - overall solution design and solution requirements
  
• Operational Development - operational requirements for initial and ongoing (if necessary) production of the solution
  
• Communications Development - communications requirements for initial and ongoing (if necessary) communication of the solution
  

6. 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. eDream 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

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