Drumbeat/website/contentstrategy/ideas

Drumbeat IDEAS

Ideas Overview

Mozilla Drumbeat will engage with leaders and social entrepreneurs to 1) surface nascent IDEAS or challenges, 2) bring the Drumbeat community to bear on articulating, reviewing and providing feedback on these ideas and challenges, and 3) attract resources to make the best ideas reality.

We're looking for things we can do or build to shape the open Internet of the future. Given the main interests and core competencies of the Drumbeat community, the ideas and proposals should probably lend themselves to "design thinking."

Ideas Criteria

Each idea has to:

• Be associated with one or more of the ten broad themes for making the Internet better.
• Must have “open Internet DNA” and values. Relate to “open, participatory, transparent, distributed control,” etc.
• Probably should involve "design thinking." (let's flesh this out further?)
• Should be sufficiently ambitious and forward-thinking. e.g., "How do I make my 'Kill IE6 campaign' succeed?" is probably not the right fit.

Questions:

• Is there a public interest / business model criteria? e.g., RouteBricks may meet our other criteria, but is funded by Intel. Does that disqualify it?

Plugging the best ideas into the Mozilla Design Challenge methodology

• Mozilla can plug the best ideas into its “design challenge” methodology: going out to schools, letting students enter a competition, and getting mentoring and training online about topics that help them execute solutions.

Workflow

1) Clearly communicate the Drumbeat Ideas vision, specific ask and criteria. Probably including a value proposition that helps answer "what's in for them?"

2) Gather suggested ideas / problems into the funnel Probably with a LOW barrier to entry -- gather as many ideas as possible, and make it easy to submit through multiple channels. Not everyone will fully fill out an entire web form. Some idea suggestions will come (as they are already) as comments on a blog post, one-sentence tweets, etc. We need to be flexible with intake.

3) Curate, edit and flesh out ideas & problems that meet the criteria I'm suggesting this as a general Drumbeat approach -- combine a low barrier to entry WITH a high level of curation. Not to be elitist -- but to keep ideas on track for Phase One and make it easier for people to submit.

4) Surface and showcase nascent ideas or challenges / problems On the Drumbeat web site and other channels. Use images, crisp copy and emphasize the human element (overlapping with PEOPLE where appropriate) to make the ideas inspiring.

5) Bring community to bear Engage the community to articulate & review the idea or problem. Make it easy for them to contribute to the ideas in small or big ways, and easily vote the idea up or down.

6) Attract resources for the worthiest ideas / problems

Either by:

• Turning them into a full fledged Mozilla design challenge
• Connecting them with volunteers / problem solvers within the Mozilla community
• Attracting third party money or support?
  • By simply raising the profile of the idea or problem, is there the prospect of some third party stepping in to help?
• Other...

• [Let's flesh out this last part so that we can more clearly articulate the value proposition and help the sexiness and viral spread of the ask.]

Three different kinds of "IDEA?"

The are three different types of potential ideas that may flow into the Drumbeat IDEAS stream. (These are useful primarily just for our own internal planning purposes -- they don't necessarily need to be presented this way to users.)

1) “Unbaked” New ideas with little or no existing support. Probably still at the conceptual or problem statement or “wouldn’t it be nice if” stage. Could be as simple as a one-paragraph blog post or pencil sketch.

e.g., “Wouldn’t it be great if there was a way for bloggers to route around censorship in places like Iran or China by using a cache tool on their browser?”

2) “Half baked” An idea that real stakeholders are already playing with, working on, or developing in some way -- but that could benefit from an open innovation process and Mozilla community brainpower.

e.g., “We’re working on developing icons that make it easier for consumers to make smarter decisions about privacy terms of service. BUT, we could use some help figuring out how they should work and what they should look like.”

3) “Fully baked” Good, interesting ideas that are already mostly fleshed out or completed. They don’t necessarily need design help -- maybe they just need money or other kinds of support.

e.g., “We just built our own village phone company in Mozambique using an ordinarily router and sim card. But now we could use some money and volunteers to spread to other communities.”

User Stories

e.g., Prof who has idea to... but has no way to build it e.g., Citizen journalist with a business model idea but now way to test it out e.g., Icon designers, but need ten different designers to take a shot at it

Questions for Discussion

The Drumbeat IDEAS life-cycle may end up looking something like:

1) Problem / idea statement: _________________

2) Solution statement: _________________

3) Solution design: _________________

4) Solution: _________________

Questions

Does Drumbeat's "Ideas" mechanism end after the "solution design" step? How far can we realistically take those?

For "fully baked" ideas, do we lose the purity of the "design thinking" approach if we simply focus on spreading or scaling? Or risk making the brand too loose or broadly focused? "This cool project is done -- now how do we scale and spread it?" Is that an acceptable problem statement for Drumbeat?

• Will the same methodology and workflow work for all three types of ideas? Should we tailor the response and workflow based on different idea types?
• How do we ensure we’re not diluting what Mozilla Labs are already doing with their own design challenges?
• How do we decide which ideas will be turned into fully formed design challenges?
• How many design challenges can Mozilla realistically support?

• How does “Ideas” relate to authorship and the “fame and fortune” aspect of getting to the event? e.g., does the PROPOSER or author of the idea receive the credit? Or the design challenge winner?
  • Could be BOTH. The Drumbeat narrative could be about connecting people with design challenges or problems they’re trying to solve (like a community technology center organizer in Romania saying: “We could do our work a lot better if we had a solution like ‘x.’” And then connecting that challenge with a developer in Prague or San Francisco who has the answer. Then BOTH of them come to the event together -- providing a uniquely “Drumbeat-ish” narrative of bringing two people together, connecting problems with solutions.