Difference between revisions of "Solution Development"
(→Planning) |
|||
| Line 34: | Line 34: | ||
==[[Planning]]== | ==[[Planning]]== | ||
4. ''Solution Design'' - the [[solution]] approach, [[design]] and [[Solution Elements|elements]] that addresses the ''Solution Design Requirements'' <br> | 4. ''Solution Design'' - the [[solution]] approach, [[design]] and [[Solution Elements|elements]] that addresses the ''Solution Design Requirements'' <br> | ||
| + | 7. ''Solution Design'' - update [[solution]] approach, [[design]] and [[Solution Elements|elements]] to also address the ''Solution Enablement Requirements'' <br> | ||
| + | 9. ''Solution Design'' - update [[solution]] approach, [[design]] and [[Solution Elements|elements]] to also address the insight from the ''Solution Design Validation'' <br>==[[Planning]]== | ||
| + | |||
| + | ==[[Execute]]== | ||
| + | 10. ''Solution Creation'' - the [[solution]] approach, [[design]] and [[Solution Elements|elements]] that addresses the ''Solution Design Requirements'' <br> | ||
7. ''Solution Design'' - update [[solution]] approach, [[design]] and [[Solution Elements|elements]] to also address the ''Solution Enablement Requirements'' <br> | 7. ''Solution Design'' - update [[solution]] approach, [[design]] and [[Solution Elements|elements]] to also address the ''Solution Enablement Requirements'' <br> | ||
9. ''Solution Design'' - update [[solution]] approach, [[design]] and [[Solution Elements|elements]] to also address the insight from the ''Solution Design Validation'' <br> | 9. ''Solution Design'' - update [[solution]] approach, [[design]] and [[Solution Elements|elements]] to also address the insight from the ''Solution Design Validation'' <br> | ||
| + | |||
| + | |||
==[[Solution Requirements]]== | ==[[Solution Requirements]]== | ||
Revision as of 14:58, 9 January 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. Aspirers determine mission and problem/unmet need(s) to be addressed
2. Solution Insight - Aspirer and beneficiary insight into addressing problem/unmet need(s) - Market Research
- Aspirer Development - will addressing 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
8. Solution Design Validation - insight into whether the solution design will achieve acceptence 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
Discovery
3. Solution Design Requirements - define requirements that 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
Planning
4. Solution Design - the solution approach, design and elements that addresses the Solution Design Requirements
7. Solution Design - update solution approach, design and elements to also address the Solution Enablement Requirements
9. Solution Design - update solution approach, design and elements to also address the insight from the Solution Design Validation
==Planning==
Execute
10. Solution Creation - the solution approach, design and elements that addresses the Solution Design Requirements
7. Solution Design - update solution approach, design and elements to also address the Solution Enablement Requirements
9. Solution Design - update solution approach, design and elements to also address the insight from the Solution Design Validation
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
