Get Started. It's Free
or sign up with your email address
Rocket clouds
RP by Mind Map: RP

1. Product

1.1. Product: Solutions Management

1.1.1. Internal Solutions Management Portal aka "Walled Garden" Store for re-use Deconstruct for re-mixing Choose to publish to the public portal

1.1.2. Branded Solutions Management Storefront Manage public challenges Publish solutions in branded platform Publish to public portal

1.1.3. Product: Public Portal

1.2. Product Development

1.2.1. "Prime the pump" Taxonomy Identify repositories of data IBM to analyze the data in those repositories Map analysis to topics? Solutions Definition AI input Manual input Building blocks Can building blocks be created by AI? Can building blocks be created by "the crowd"? What is the incentive to create building blocks? Doe we need extrinsic incentives for building block creation? What is the relationship between building blocks and the taxonomy?

1.2.2. The First MVP Customers EcoTrust Blue Solutions Oxfam Mercy Corps Smaller "Solutions Management" or "Walled Garden users" User Stories Solutions management Challenge Management Solutions re-mixing Public Portal

1.3. Incentives and Currencies

1.3.1. Time Banking Foundations provide $time as part of grants Earn $time Input solutions Create Building blocks Curate content Comment / Feedback - Expertise Spend $time Learn about solutions and Building Blocks from creators and re-users Get formal consulting buy RP services

1.3.2. RFP Platform Publish RFP in context of Problems Solutions Building blocks Take applications that input / re-mix Solutions Building blocks

1.3.3. Grant requirements to "publish" solutions

1.3.4. Grant requirements to

1.4. Services

1.4.1. Training / Events Slam Workshop

1.4.2. Challenge Management Internal Multi-org / Community Public

2. Ecosystem

2.1. Orgs defined by co-creation

2.1.1. Wikipedia

2.1.2. Minecraft

2.1.3. MeetUp

2.2. Similar Efforts

2.2.1. Idealist Team

2.2.2. Imperative

2.2.3. Skibb

2.2.4. Solvermine

2.2.5. Goodnet

2.2.6. List of problem solving platforms

2.2.7. Wikipedia Crowdsourcing projects

2.2.8. Social Citizens / Case Foundation

2.2.9. Other

2.3. Articles etc

2.3.1. HBR: Community Powered Problem Solving

2.3.2. Deloitte: Next Generation of Problem Solving

2.4. Other interesting Orgs

2.4.1. FSG Collective Impact Common Agenda: All participants have a shared vision for change including a common understanding of the problem and a joint approach to solving it through agreed upon actions Shared Measurement: Collecting data and measuring results consistently across all participants ensures efforts remain aligned and participants hold each other accountable Mutually Reinforcing Activities: Participant activities must be differentiated while still being coordinated through a mutually reinforcing plan of action Continuous Communication: Consistent and open communication is needed across the many players to build trust, assure mutual objectives, and appreciate common motivation Backbone Organization: Creating and managing collective impact requires a separate organization(s) with staff and a specific set of skills to serve as the backbone for the entire initiative and coordinate participating organizations and agencies Shared Value

2.4.2. Creative Commons

2.4.3. LinkedIn

2.4.4. IDEO Amplify

2.4.5. Guidestar

2.4.6. Fluxx

2.4.7. Neighborworks Success Measures

2.4.8. Corporates Cisco eBay

3. Customers

3.1. Behavior Change

3.1.1. Store publicly

3.1.2. Re-Use

3.1.3. Deconstruct

3.1.4. Re-Mix

3.2. Customer Pain

3.2.1. Internal Solutions Management

3.2.2. Improvement of solutions through "peer review" or "external confirmation" like behavior

3.2.3. re-use of solutions by others

3.2.4. PR from External publication of solutions

3.3. Descriptions

3.3.1. Customer 1: Large and/or established orgs with many existing solutions and a pain point around managing those solutions Willing to invest in "platform" Blue Solutions Oxfam Mercy Corps User willing to buy a basic "solutions management" product Grameen Foundation Island Institute

3.3.2. Customer 2: Small(er) less established orgs needing to draw on external resources to adopt successful solutions Likely free users of "Public Portal"

3.3.3. Customer 3: Primarily characterized as a data repository. Generally an intermediary like Guidestar, the foundation center, ...

3.3.4. Customer 4: Foundations who do not behave like customer 1 but are valuable as data repositories or channel partners / lead gen Rockefeller Foundation

4. Theory of Change

4.1. We need communities that are better able to respond to stress and a world that is reducing the likelihood of our communities being under stress.

4.2. We are making some progress toward these goals but the progress is not happening quickly enough.

4.3. We believe we can accelerate the pace of change by more effectively managing the process for creating that change; specifically, by improving the process of managing solutions.

4.4. We believe that there are great processes for creating specific solutions that respond to specific problems; however, there do not exist great tools to take those solutions and 1) share them for re-use and peer review, 2) deconstruct them for re-use and re-mixing of the components.

5. What now?

5.1. Business Model Canvas