Participation Experiments: Planning Framework

Mar 3, 2015 - working document

This document is complementary with the Participation experiment tracking and assessment spreadsheet.

Purpose of this document

Articulate a planning framework for describing Participation experiments in Q1 and Q2 across Mozilla. The hypothesis is that:

  1. “Plans are useless, but planning is indispensable.” Eisenhower. By having a planning framework, we will capture our thinking in a way that will allow us to audit it against the results and inevitable changes that will happen during implementation. This will increase the fidelity and pace of our learning, providing more value to the overall Participation strategy and direction.
  2. Having an initial idea for this framework will serve as a jumping-off point for teams to customize it for their own needs, while resulting in some common elements that will allow aggregation of lessons.

Experiment Index

Click on an experiment title to learn more.

  1. How might we reimagine Mozilla.org as a hub for driving participation and relationships with our mission?
  2. How might we create a sub-structure in the Mozilla Reps program and volunteer communities (working name "Impact Teams") that provides value to functional teams while giving a development path for volunteers?
  3. How might we gain deeper insights about region-specific Firefox desktop user needs and attrition causes through hyper-local user research?
  4. How might we enable Product Management to more quickly process their backlog of feature specs for Firefox Android in a way that still maintains excellent quality?
  5. How might we enable Mozilla to promote open web privacy by hosting and administering many more Mozilla-sponsored Tor nodes through the help of a Security IT community?
  6. How might we amplify the voice of our advocates and show the world the problems with today's Web through a coordinated, local, and grassroots kind of way?
  7. How might we build and sustain a strong community of creative designers to amplify and de-centralize Mozilla's creative process and put more ownership in the hands of volunteers?
  8. How might we give more exposure to our regional communities , and empower them to improve their online and offline structure and presence, to enable them to tell their story and grow?
  9. How might we increase the number of Firefox downloads and installs coming from community-run web properties?
  10. How might we promote community health by providing a dynamic snapshot of various statistics to enable community managers and others to be better informed and build programs and initiatives when armed with better information?
  11. How might we promote a better online presence of our local communities while consolidating and optimising infrastructure that runs this?
  12. How might we collect all the feedback that Developer Evangelists collect from developers at events in a streamlined, structured way that immediately benefits our engineering teams
  13. How might we involve our volunteers much more in the design, planning and execution of Fx OS launch activities that lead to sustained community growth around Fx OS
  14. How might we substantially increase the amount of hyper local content created for Marketplace that builds on our experiments of 2014?
  15. How might we help our PR team capture relevant local media coverage and give the team a heads up for industry/developer events that might be critical for Mozilla staff to attend?
  16. How might we empower many more Mozillians to effectively evangelize our technologies and values locally?
  17. How might we help the Marketplace team to find apps and mobile optimize websited in local markets in order to curate a great marketplace experience for users?
  18. How might we build local clubs that serve as participation hubs spanning accross the different areas of Mozilla like Webmaker, MDN, and developer relations and connect us to the local non-profit and tech scenes?
  19. How might we build a volunteer QA team that would challenge a company like Apple for their maniacal attention to detail?
  20. How might we evolve our student ambassador's program into full fledged chapters that are a massive source of activity, creativity and talent for Mozilla and the open web?
  21. How might we create optimization challenges (algorithms, speed, etc), maybe even with cash prizes, for our various product or IT teams?
  22. How might we create an series of open source academies around the world that are as intense and high quality as the App Academy?
  23. How might we deepen the understanding of our organization's strategy among thousands of Mozillians?
  24. How might we increase the leadership, team building and strategy capabilities of our key volunteer participants, at scale, with a low resource input?
  25. How might we get community and volunteers into the workflow of functional teams on a timeframe that allows them to be effective participants?
  26. How might we develop an integrated vision and strategy for regional communities and ReMo?
  27. How might we incorporate country-level strategy and brand considerations into product/campaign design, testing and rollout plans?
  28. How might we develop a common vision and framework for Mozilla's fellowship programs (that potentially connects to a common vision for Mozilla's leaders)?
  29. How might we get another 500-1,000 people through the progression to being high-quality regular code contributors?
  30. How might we dramatically re-imagine l10n, modernizing translation to use proven methods from other organizations, and getting our people to add value to localization in other ways?
  31. How might we build a low-cost innovation labs program that drives massive participation?
  32. How might we win a single large country with at least one product (over 50% market share) by having a whole of Mozilla/whole of mission approach and broad participant involvement?
  33. How might we evolve the Reps program structure to be effective in taking on the responsibilities of leadership that is increasingly expected of them?
  34. How might we engage Mozilla alumni to provide us with market/technology intelligence and be an influential voice for Mozilla in the world?
  35. How might we have a common onboarding for Mozilla staff and core volunteer participants?
  36. How might we create an internal Mozilla community economy that allows participants to exchange or offer goods or services of value (potentially in exchange for their contribution to Mozilla's impact)?
  37. How might we identify and steward potential core contributors from the re-launching word-of-mouth platform?
  38. How might we have a platform that brings continuity in how we manage relationships with volunteers, supporters, advocates and others who have a relationship with Mozilla?
  39. How might we create an internship program that invests in a next generation of Mozilla's leaders?
  40. Not actually developing talent for other areas right now. Nothing in between volunteers and a staff member in areas like community management, education, etc. How would we enable that?
  41. How might we develop agile and easily deployable technological solutions (infrastructure) to support quick and measurable deployment of other experiments
  42. How can we provide local physical spaces (aka "Participation Hubs") for contributors to meet, share and hack in a financially sustainable way?


Planning Framework

1) Experiment/idea in a “How might we” single question

[Starts with “How might we” and gets to the heart of what this experiment is designing for.

e.g. How might we have volunteers collect timely, quality local market data for the FxOS team in a sustainable and scalable way?]

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

[Articulates the context that a particular team is facing and how this experiment addresses that. Also speaks to how this benefits/addresses participation more generally.]

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

[Getting into rough details of what the scope and dimensions of a solution could look like. Who is going to volunteer/participate and why (volunteer user stories). Tells a story about success, both in the short term of what we would high-five in a few months, and also in the longer-term for Participation at Mozilla. If there’s a story of scale or broader implications, it makes that clear too.]

4) Where the idea came from and who is implicated

[Team that initiated the idea, team that will own it, teams that will be involved in the implementation.]

5) Options for implementation (rapid prototypes of solutions)

[Some quick different ideas for how this could look. A very rough sketch of the design -- components and options for those, key strategic questions, etc.]

6) Hypotheses and how we test them

[Hypotheses that are guiding this experiment, in particular related to topics that are relevant for our Participation strategy. This might be for our approach to Participation or the structure/function of the team.

Examples:

Hypothesis: 

Having local market pulse teams is a light touch, yet engaging and motivating for regional community members.

How to test:

Measure the number of hours of staff time/volunteer leader time/volunteer implementer time. Survey volunteers to gauge their level of motivation. Gather data on engagement level (time, frequency) of volunteers.

Hypothesis: 

Local market pulse teams provide useful, actionable information to sales teams.

How to test:

Observe/ask how data is being used. Ask sales teams to determine how much they would pay for equivalent research.

Hypothesis:

Participation staff team can provide value in the setup phase (strategy, mobilizing initial volunteers, etc), but then can wind down its role as the functional team supports ongoing activity.

How to test:

Track time spent. Determine value added A/B testing of continued involvement or ending involvement in particular communities.

]


Experiments:

How might we reimagine Mozilla.org as a hub for driving participation and relationships with our mission?

1) Experiment/idea in a “How might we” single question

How might we reimagine Mozilla.org as a hub for driving participation and relationships with our mission?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Mozilla.org is a place that has a lot of traffic. Right now we’re trying to drive Firefox downloads. What if we reimagine it as a hub for building a relationship between Mozilla’s mission and people who could be aligned with Mozilla’s mission, whether or not they are Firefox users.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


How might we create a sub-structure in the Mozilla Reps program and volunteer communities (working name "Impact Teams") that provides value to functional teams while giving a development path for volunteers?

1) Experiment/idea in a “How might we” single question

How might we create a sub-structure in the Mozilla Reps program and volunteer communities (working name "Impact Teams") that provides value to functional teams while giving a development path for volunteers?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Sustained participation in functional areas

Common structure + bridge to functional areas

Learning opportunities and path for development for volunteers -- learning, leading

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

Option A:

Option B: (Ensure this is connected to staff)

6) Hypotheses and how we test them

  1. A clear, common pathway for leadership will attract volunteers and allow a deliberate investment in people at each stage of the process
  2. Getting volunteers to work closely with functional teams is an investment that gives value to both volunteers and staff/teams


1) Experiment/idea in a “How might we” single question

How might we gain deeper insights about region-specific Firefox desktop user needs and attrition causes through hyper-local user research?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Fx user research team is 2 people

Lack the resources to get real, human feedback

“What do you like about Firefox?”, “Why did you switch to Chrome?”

Firefox user team now is able to have the right information to make good decisions with the product

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


How might we enable Product Management to more quickly process their backlog of feature specs for Firefox Android in a way that still maintains excellent quality?

1) Experiment/idea in a “How might we” single question

How might we enable Product Management to more quickly process their backlog of feature specs for Firefox Android in a way that still maintains excellent quality?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

They don’t have time to spec out product ideas -- doesn’t make it into the roadmap

Volunteers develop product plans -- build skills on doing product management

The Product Management team for Firefox Mobile is having a backlog of features and other things that they want to develop plans/specs for. The experiment would be to test whether it's possible to hand out a defined and scoped feature and have one or more volunteers help flesh it out to a proper plan.


This never gets in the roadmap because they don’t ever get to specs that are well articulated.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

Who would volunteer: students of product management wanting real-world experience? People generally interested in a topic and eager to learn?

Success would mean that the product management team would actually get high quality product specs hashed out with the help from volunteer community AND that volunteers participating would get real-world experience that they could put on their resumes - in addition to knowing that they have been part of shaping a flagship product in the market.

4) Where the idea came from and who is implicated

Had a conversation with Karen, and they have features that don’t have specs and so it gets deprioritized.

5) Options for implementation (rapid prototypes of solutions)

Could do this as a challenge/competition.

Could structure this as something like an internship/program we could recruit people to: Would need to do some training of how to write product specs. Have some structure on how they would contribute.

Options:

  1. competition type. get more than one team/person to spec something out and pick the best one.
  2. program where we build a product management contributor program with an education component up front. mentorship. leveled-up contributors. longer-term investment. well-defined scope and timeline to get people to be product managers.
  1. self-serve, ad hoc to build a community of product managers over an extended period of time

Building a relationship/partnership with a University program for recruiting participants to this. (Loop in Dietrich to this conversation -- fertile testing ground for this)

On universities: Chose one in Asia, africa, south america.

6) Hypotheses and how we test them

  1. There are enough concrete projects/features that existing product managers will have the time to build out .
  1. Strong list of ideas, now and in the future.
  1. We can have volunteers contribute substantially to an important part of core product management, at a high quality.
  1. Product managers on staff rate the specs as high enough quality to build against
  1. Spec’d out features of this sort would have a product impact.
  1. These features get on the roadmap and ultimately into the product.
  1. We can build a community of product managers who extend the product management team.


How might we enable Mozilla to promote open web privacy by hosting and administering many more Mozilla-sponsored Tor nodes through the help of a Security IT community?

1) Experiment/idea in a “How might we” single question

How might we enable Mozilla to promote open web privacy by hosting and administering many more Mozilla-sponsored Tor nodes through the help of a Security IT community?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Clearly points to the Mozilla mission - put these nodes in the cloud, volunteers administer

One person might be able to do 10 of these nodes

Mozilla IT security team would develop education/curriculum

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

Find one or two volunteers to administer these Tor nodes.

Highly aligned to Mozilla’s mission. Incentive for community -- getting security/IT admin training. Might be simple to incentivize people to get connected with this.

Not really a tonne of work for our team.

What is the ownership and governance structure on this?

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

This is the only example of us working together with an organization that is outside of Mozilla. We can learn something about participation vis-a-vis working with others.

6) Hypotheses and how we test them

  1. There are people who are interested in administering these Tor nodes/being volunteer sys admins.
  1. We are able to build an educational on-ramp to these
  2. Number of people we have doing this
  1. Volunteer sys admins will be able to allow us to scale the number of Tor nodes that we host.
  1. Set goals for uptime/bandwidth/available flags to use on the node that allow us to gauge the success of the volunteer sys admins


1) Experiment/idea in a “How might we” single question

How might we amplify the voice of our advocates and show the world the problems with today's Web through a coordinated, local, and grassroots kind of way?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Firefox Marketing's biggest problem today is that the problem statement isn't really articulated and known by people, so they don't see why Firefox might be the solution. What if we could find a way to amplify the voices of all passionate advocates that are out there so that they could spread awareness of the problems of the web in a way that teed the marketing team up for success? Give people the talking points and tools they'd need to spread the message in their own voice through local newspapers, seminars, blogs, medium.com, etc.

Problem statement of the web isn’t known to people

Fx marketing team is struggling with this -- helping people know why open web standards are important

Amplify our volunteers to amplify their voice (Eric Petitt calls it MozVoice), tell their own story in a powerful way - local newspapers, business networks, giving presentations at

Is it only about the messaging? More about structure and dedicated resources from the Marketing team.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

The people who would volunteer for this are the passionate advocates around the world who joined Mozilla already or haven't because they haven't realized that they can make a difference. What they share in common is a general understanding of why the open web matters, but perhaps they are still struggling to articulate this Why even to their friends and colleagues still. The solution might be a set of really solid talking/writing points that they could use to develop and amplify their own voice. Part of the solution could even be a web site/portal where many of the personal stories are shared - similar to The Web We Want.

This could scale globally and locally to the point where we had passionate spokespeople in every city, finding a way to get into their local newspapers and other channels to make the open web and the importance of it mainstream!

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them

1) Experiment/idea in a “How might we” single question

How might we build and sustain a strong community of creative designers to amplify and de-centralize Mozilla's creative process and put more ownership in the hands of volunteers?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Reimagining the Creative Collective. More people participate in making of the creative assets for Mozilla.

Mary Ellen is a champion for this

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


How might we give more exposure to our regional communities , and empower them to improve their online and offline structure and presence, to enable them to tell their story and grow? The tool to power this would be Community Tiles.

1) Experiment/idea in a “How might we” single question

How might we give more exposure to our regional communities , and empower them to improve their online and offline structure and presence, to enable them to tell their story and grow? The tool to power this would be Community Tiles.

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Already kicked this off -- community tiles on the launch/new tab page

Partnering with 3 communities to give local communities the tile to own/customize

Feedback into their community, design, needs, etc

https://docs.google.com/a/mozilla.com/document/d/1TZF5m2dNvvsdSS-crU9zRelFdxbKlgbYkF9XUte17tA/edit?usp=sharing

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

Up to the community to figure out the biggest problem for them - enable the community to figure out what they need in order to best leverage their tile. Opportunity for building a coaching function here.

Feel this is a communication channel. No real functional integration.

This is less about the tile, and more about how we can coach and support the community to utilize this space really effectively.

4) Where the idea came from and who is implicated

Content Services team: https://wiki.mozilla.org/Tiles/Community_Involvement

Patrick Finch is currently advocating, he also presented on this at FOSDEM.

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them

  1. Involving community participation increases awareness of Tiles and enables local communities to best leverage their own tile.
  1. Evidence/reports from communities indicating that this is providing real value to them
  1. We can successfully, and manageable, coach/level up volunteers and communities to use the community tile strategically.
  1. First set of communities up and running with successful strategy and ready to educate other communities on best practices and thought framework

1) Experiment/idea in a “How might we” single question

How might we increase the number of Firefox downloads and installs coming from community-run web properties?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Chris More on the Firefox growth team … have been optimizing this on main Mozilla properties

The community sites have a download button, but they haven’t been optimized

Promotes downloads -- A/B testing, tracking, etc -- community members can learn about this (tech, marketing, segmenting)

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


How might we promote community health by providing a dynamic snapshot of various statistics to enable community managers and others to be better informed and build programs and initiatives when armed with better information?

1) Experiment/idea in a “How might we” single question

How might we promote community health by providing a dynamic snapshot of various statistics to enable community managers and others to be better informed and build programs and initiatives when armed with better information?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Dashboard, snapshot of country and region

Reps, Mozillians, number of events

Over time would allow for trends, analysis, etc

Would help us to focus our efforts

Audiences: Community managers, rest of org, communities themselves

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

MVP

It would be visible on Mozillians.org -- click on a country and the information appears on that page.

Decision-making: Having this in place would allow those teams to understand what’s going on, answer questions they already have.

Regional community builders:

Start to see correlations in Reps/functional teams/etc -- would give a more granular view on what’s working and what’s not, and some guesses as to why

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

First step - prototype: one country profile. Pick out one country to start with.

Building out some user stories on how various people would use this, would allow us to know what to build and why.

6) Hypotheses and how we test them

  1. Functional teams would find country-level information useful and actionable
  1. People are using this and it’s changing their decisions
  1. Community builders would find this information useful and actionable
  1. CDT, Reps, and regional community leaders are using this to make decisions
  2. CDT, Reps, and regional community leaders are using this to set goals/ambitions
  1. Building this upfront will allow us to not spend one-off time
  1. Amount of time we take on one-off requests


1) Experiment/idea in a “How might we” single question

How might we promote a better online presence of our local communities while consolidating and optimising infrastructure that runs this?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Right now we host various community sites on various platforms - pay for space on various servers around the world

Consolidate

WordPress multi-site

Bring down costs

Stronger security

Evaluate the quality of the sites, helps community to have great web presence

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


1) Experiment/idea in a “How might we” single question

How might we collect all the feedback that Developer Evangelists collect from developers at events in a streamlined, structured way that immediately benefits our engineering teams

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Developer evangelists travelling all over the world -- ideas on how to do things differently, etc

We’re not very good at channeling the info in that raw form. The idea is to give this data back to developers. Equip dev evangelists with the tools they need to record and channel the info back to our platform/engineering teams so the dev feedback isn’t lost.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

Something super-simple:

Figuring out how to prep the engineering teams to receive this information from the evangelists so

they are prepared to make their feedback a priority?

Have a really quick web-app/tool to submit this information

4) Where the idea came from and who is implicated

Dietrich Ayala. Tech Evangelism team? Also Engineering and Platform teams would be impacted by the output.

5) Options for implementation (rapid prototypes of solutions)

Could be a template or way to summarize the feedback in a way that makes sense for Engineering teams. Could be a list of bugs, or some other form as agreed by stakeholders.

Create some way for this is highly open/visible, have moderation, rating (from community/from developers)

6) Hypotheses and how we test them

  1. Convinced having worked with our engineering teams is that raw feedback could be acted upon.
  1. Way to test: # of bugs submitted as a result of an event? Could be tagged with a specific keyword to indicate that it came from feedback at a Tech Evangelism event. Would also allow us to track this effectively. e.g. https://ffdevtools.uservoice.com/forums/246087-firefox-developer-tools-ideas
  1. If we remind evangelists that this is valuable, then they will collect this information and send it back
  1. How many evangelists actually file reports back
  1. If we make it easy to collect/submit information, people will submit regular and quality information
  1. How many evangelists actually file reports back
  2. How much of this information is rated high quality by developers - how many bugs are fixed
  1. We can reinforce the value of this feedback, and this will strengthen the developer community
  1. Way to test: reduced # of repeated (negative) feedback as a result of actually fixing these issues?
  1. We will uncover local disparities that will be insightful for teams
  1. Run process on 2 events, similar in nature, but in different parts of the world.


1) Experiment/idea in a “How might we” single question

How might we involve our volunteers much more in the design, planning and execution of Fx OS launch activities that lead to sustained community growth around Fx OS

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

General feelkng on FxOS marketing team that we have a top down approach to marketing FxOS. We’re not invlving volunteers in the design process.

Have campaigns and messaging that is more relevant locally

John Bernard - way to approach FxOS launches in Africa

Sustained community growth + momentum around this - years after the launch of our products

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

John Bernard, FxOS marketing team.

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


1) Experiment/idea in a “How might we” single question

How might we substantially increase the amount of hyper local content created for Marketplace that builds on our experiments of 2014?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Find innovative ways to encourage and motivate developers to build hyper-local content (e.g. when your local baker will ship loaves of bread … this is particularly important where William lives in Paris!)

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


How might we help our PR team capture relevant local media coverage and give the team a heads up for industry/developer events that might be critical for Mozilla staff to attend?

1) Experiment/idea in a “How might we” single question

How might we help our PR team capture relevant local media coverage and give the team a heads up for industry/developer events that might be critical for Mozilla staff to attend?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Way to capture what local media is saying + knowing what events locally that are happening that we should be part of or know about.

PR team isn’t really on top of this - they have a limited budget where they don’t have agencies

Triage what’s really relevant, what’s not

Engaging volunteers to be stronger at PR

Gap currently between local PR teams and volunteers on the ground. We are not able to catch all things happening around the world as they relate to Mozilla.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

  1. It could be investing in key individuals in the community and growing a team of PR expertise, coupled with education and growing skills for how to run PR locally.
  2. It could also be a low-touch way to submit feedback to PR that involves anyone. More of a news ticker feed for paid staff PR team to make sure they don’t miss anything important. Anyone could submit news and events that are happening that Mozilla should be aware of.
  1. Start with a low touch tool to submit news segmented by region. See if that gives PR team better insights (hypothesis 1)
  2. Identify people who stand out in the community as particularly skilled with informing PR team.
  3. Invest in skills to further develop these individuals (training, education, etc) and enjoy even better insights and activities in those regions.

6) Hypotheses and how we test them

  1. There are local insights/news that are not getting to the PR team today that this experiment would enable and that are actionable
  1. Much better local insights
  2. PR team acts on this
  1. By getting local teams to think about PR more we’ll level up their skills and PR activities
  1. Number of volunteers who are active in PR
  2. Increase in articles and quality around the world


1) Experiment/idea in a “How might we” single question

How might we empower many more Mozillians to effectively evangelize our technologies and values locally?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Better equip our community evangelists.

Content and skills.

e.g. speaker training

Havi + Dietrich

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


1) Experiment/idea in a “How might we” single question

How might we help the Marketplace team to find apps and mobile optimize websited in local markets in order to curate a great marketplace experience for users?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

e.me partnership ending.

Marketplace team would like to provide a great experience for users by having a curator/editorial team -- volunteers would own the content curation for that market

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


1) Experiment/idea in a “How might we” single question

How might we build local clubs that serve as participation hubs spanning across the different areas of Mozilla like Webmaker, MDN, and developer relations and connect us to the local non-profit and tech scenes?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Have stronger organization, sustained local/city-level effort - Webmaker, MDN team, Mary Ellen

Mozilla clubs -- all of these things converge

Evangelising the mission, clubs at local level - Mozilla in its whole at a local level

Integrate with the local tech scene.

Connect with Mozilla Spaces

Start piloting this in Bangalore next quarter

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


1) Experiment/idea in a “How might we” single question

How might we build a volunteer QA team that would challenge a company like Apple for their maniacal attention to detail?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Astonished by how “not good” the QA team is at Mozilla compared to his experience at Apple. Gotta be these folks out there excited about finding bugs, categorizing them and be really detail oriented. How do we find them, bring them together, and have them provide the QA function that dramatically increases quality.

World class QA team is the concept.

We’ve had some individuals before, but have not systematized

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

Johnath

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


1) Experiment/idea in a “How might we” single question

How might we evolve our student ambassador's program into full fledged chapters that are a massive source of activity, creativity and talent for Mozilla and the open web?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Similar to Rosana’s concept, except doing it at the uni level. How do we bring student’s massive talent in an organized way?

Students have the most available and flexible time.

Use for more than marketing.

Could be quick and easy to tes.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


How might we create optimization challenges (algorithms, speed, etc), maybe even with cash prizes, for our various product or IT teams?

1) Experiment/idea in a “How might we” single question

How might we create optimization challenges (algorithms, speed, etc), maybe even with cash prizes, for our various product or IT teams?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

We have lots of server optimization challenges that we never get to, no time. How do we put them out as things that are grand challenge types that people can just hack away on until they find a solution. Could get tons of problems like this framed by engineering teams with well-described solutions. Outside of Bugzilla environment and more in a crowd source context.

You deal with discrete code on the side, sandboxed.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

Can we get teams to sandbox and identify challenges/tasks that we could put into a list?

With measurable results. Important part of making this discretized.

Doing research of how these types of competitions work (NASA has been doing these things in the past, there’s a cultural change implied in this that we can learn from other companies).  We’re late to the party of how to work like this.

Select 1, 2 or 3. Work with engineering teams, set them up in parallel, throw them out in the universe and.

Different types of bounties?

Criteria is that tasks/challenges are discrete in nature and clearly defined and scoped.

Possible related projects at Mozilla:

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

How would this be presented/posted? Don’t know - some list somewhere. Important to make sure the right people see it. We could just look at best practices from e.g. Nasa.

Create a simple web page with a list. Fire out communication in all of our channels to get the word out. And then give it a month of time to expect to see results. Longer term, could be an engaging web site like Phone bloks: https://community.phonebloks.com/challenge 

  1. Start with a discrete challenge, simple web page and get communication out to all channels.
  2. Learn from first challenge, eval results.
  3. Iterate
  4. Build out more substantial-ish website listing similarly discrete challenges
  5. Learn from these challenges, eval, iterate
  6. Consider scaling this out to open ended challenges in addition

6) Hypotheses and how we test them

  1. Which types of challenges (clearly scoped, discrete with defined results vs open ended and subjective) lead to successful competitions? We want to start with discrete projects.
  2. A crowd-sourced solution leads to bigger impact that engineering teams are happy with - solves a problem that we couldn’t do ourselves.


How might we create an series of open source academies around the world that are as intense and high quality as the App Academy?

1) Experiment/idea in a “How might we” single question

How might we create an series of open source academies around the world that are as intense and high quality as the App Academy?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Can we create the same kind of intense environment for FxOS marketplace by having innovation dollars that people can access, or develop partnerships with other FLOSS companies that can draw from this academy.

Build it all over the world - Lagos, Bangalore, Dhaka.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


1) Experiment/idea in a “How might we” single question

How might we deepen the understanding of our organization's strategy among thousands of Mozillians?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Could we take plans and translate them and give them the entrepreneurial flare so it makes sense to people. Enable volunteers to build their strategic skills. Product: volunteers understanding strategy in more depth.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

Dave Slater

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


1) Experiment/idea in a “How might we” single question

How might we increase the leadership, team building and strategy capabilities of our key volunteer participants, at scale, with a low resource input?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

How do we level up our volunteers to be leaders in a way that creates value? Unclear how this looks like, but meta conversation seen throughout conversations that suggest this could unlock a lot of value to the org.

Is accountability built into it? Think so.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


How might we get community and volunteers into the workflow of functional teams on a timeframe that allows them to be effective participants?

1) Experiment/idea in a “How might we” single question

How might we get community and volunteers into the workflow of functional teams on a timeframe that allows them to be effective participants?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Came from broad reactions on the Spring campaign. Volunteers feel they are brought in very late, no opportunity to shape campaigns. How can we enable volunteers to get involved earlier? What are the workflows that enables volunteers to give input really early? Mindset shift.

Mindset shift + mechanical process.

If volunteers were involved earlier, they would have a much more meaningful way to participate. They would be able to socialize things with their teams, mobilize people on the ground, etc. They’re typically brought in at step 5 in a project plan, when it’s almost/almost ready to roll out.

 

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

  1. Identify a short list of projects that have the characteristics of 1) haven’t launched yet and 2) in the domain of getting value from communities. Choose 1-2 of them.
  2. Rather than running an experiment, observe how this is already happening today and the experiment is basically a selling to senior managers about the value of doing things in this fashion.

The scope seems to be Marketing, where programs are often planned out in “secret” and where volunteers are involved very late in the game and are generally seen as soldiers rather than strategic partners.

6) Hypotheses and how we test them

  1. If you bring volunteers in at an early phase and a way that makes them part of the core team, the risk of something leaking will go down to essentially zero because they feel a shared sense of ownership.


1) Experiment/idea in a “How might we” single question

How might we develop an integrated vision and strategy for regional communities and ReMo?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Develop a common unified vision for both Reps and regional communities. They’re probably separate due to historical reasons.

Moz Hispano seems to be doing something like this already.

Resistance from integration comes from community itself partially. Not easy to deal with it, no “clean slate”. Backstories that would have to be tackled.

Pierros: Missed opportunities today because we don’t have this integration in place. Break down messages between Reps and regional communities. If we broke this gap, we would more easily get messages across and run projects and experiments much faster.  

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


1) Experiment/idea in a “How might we” single question

How might we incorporate country-level strategy and brand considerations into product/campaign design, testing and rollout plans?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Some of this came from Firefox marketing, other things from FxOS marketing. Spring campaign is a great example: great message for the US, not so good for the rest of the world. How do we play around with having local drivers for how we plan and design campaigns.

We currently have no input from communities in e.g. Indonesia, Kenya, etc on how a particular campaign would fly in their region. Idea would be to enable that input to happen.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


1) Experiment/idea in a “How might we” single question

How might we develop a common vision and framework for Mozilla's fellowship programs (that potentially connects to a common vision for Mozilla's leaders)?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Currently we currently have 5 fellowship programs, Mdn, Open News, Advocacy, Open Science, and 1 more. There’s a bunch going on, but they’re not learning from one another.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


How might we get another 500-1,000 people through the progression to being high-quality regular code contributors?

1) Experiment/idea in a “How might we” single question

How might we get another 500-1,000 people through the progression to being high-quality regular code contributors?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

From talking with people, the order of magnitude that we’d need to massively accelerate our work would be 500-1000. That would also be within capacity to manage. How do we get there?

500-1000 is the sweet spot - clear number based on feedback.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


How might we dramatically re-imagine l10n, modernizing translation to use proven methods from other organizations, and getting our people to add value to localization in other ways?

1) Experiment/idea in a “How might we” single question

How might we dramatically re-imagine l10n, modernizing translation to use proven methods from other organizations, and getting our people to add value to localization in other ways?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

l10n ten years ago was a compelling advantage. Today it’s not. Easier ways of delivering l10n that we’re not doing. How could we convince people to try something more like editorial, cultural translations, understanding markets, how language shows up. Taking the volunteer community we have and shift them to a higher value effort.

Making it a competitive advantage for us, again.

The lower value efforts could be crowd sourced or paid.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


How might we build a low-cost innovation labs program that drives massive participation?

1) Experiment/idea in a “How might we” single question

How might we build a low-cost innovation labs program that drives massive participation?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Reboot on Labs and/or WebFWD. How much desire is there in the org is unknown, but it comes across as something we could try. Moz Hispano has their own lab. Hook regional labs into Product teams.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


How might we win a single large country with at least one product (over 50% market share) by having a whole of Mozilla/whole of mission approach and broad participant involvement?

1) Experiment/idea in a “How might we” single question

How might we win a single large country with at least one product (over 50% market share) by having a whole of Mozilla/whole of mission approach and broad participant involvement?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

How do we manifest our mission within a full push in a particular country where everything is pushing at the same time. Marketing, webmaker, l10n, support, developers, all of these things pushing in a market in a coordinated way.

Shortlist: US, Germany, Bangladesh, Indonesia, Philippines, South Africa.

Forces all teams to work together.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


How might we evolve the Reps program structure to be effective in taking on the responsibilities of leadership that is increasingly expected of them?

1) Experiment/idea in a “How might we” single question

How might we evolve the Reps program structure to be effective in taking on the responsibilities of leadership that is increasingly expected of them?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Combo of leadership skill development, having Reps starting to understand their roles differently. Testing new forms of agendas when they work together. Moving from budget to strategic conversations. Experimenting with how they see their roles from a governance perspective.

More a series of hypothesis - paths of innovation.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


1) Experiment/idea in a “How might we” single question

How might we engage Mozilla alumni to provide us with market/technology intelligence and be an influential voice for Mozilla in the world?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Ex-employees who are out there in the world and still care about Mozilla. Have their own closed Facebook group, talk about Mozilla, yet don’t provide much value back to Mozilla. How do we get their ideas back into Mozilla and get them to be influencers of Mozilla in their domain?

Related: alumni for the Reps program already exists.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

Mitchell, Mary, Chris

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


1) Experiment/idea in a “How might we” single question

How might we have a common onboarding for Mozilla staff and core volunteer participants?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Moz staff onboarding needs to be re-evaluated.  We’re not creating Mozillians among staff when they’re moving in. There’s very little in what roles they have as volunteers, little education about how we’re different, how we work with communities.

Build some common elements and messaging into the onboarding to make the first couple of months rich and wonderful that translates into the mindsets we want for Mozillians as a whole.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

Chris, Slater, Emma

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


1) Experiment/idea in a “How might we” single question

How might we create an internal Mozilla community economy that allows participants to exchange or offer goods or services of value (potentially in exchange for their contribution to Mozilla's impact)?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Super blue sky right now.

We have a trust economy already - what else can we do to strengthen that?

e.g. AirBNB credits.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


1) Experiment/idea in a “How might we” single question

How might we identify and steward potential core contributors from the re-launching word-of-mouth platform?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

How do we steer the people from the WOM program to start to become core contributors. Provide opportunity to choose, based on early analysis of who might be likely to make that switch. Tap them on their shoulders so that they contribute. Do it in an automated way.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


How might we have a platform that brings continuity in how we manage relationships with volunteers, supporters, advocates and others who have a relationship with Mozilla?

1) Experiment/idea in a “How might we” single question

How might we have a platform that brings continuity in how we manage relationships with volunteers, supporters, advocates and others who have a relationship with Mozilla?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Pierros, Sean Rich, and others already digging in. Some coordination. Experiment to do a holistic design on how to manage in a seamless way. Testing it out, and modeling.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


1) Experiment/idea in a “How might we” single question

How might we create an internship program that invests in a next generation of Mozilla's leaders?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Most are for coding and marketing right now.

Not actually developing talent for other areas right now. Nothing in between volunteers and a staff member in areas like community management, education, etc. How would we enable that?

Building international internship program is part of this idea as well.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


How might we create an internship program that invests in a next generation of Mozilla's leaders?

1) Experiment/idea in a “How might we” single question

How might we create an internship program that invests in a next generation of Mozilla's leaders?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

Most are for coding and marketing right now.

Not actually developing talent for other areas right now. Nothing in between volunteers and a staff member in areas like community management, education, etc. How would we enable that?

Building international internship program is part of this idea as well.

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them


How might we develop agile and easily deployable technological solutions (infrastructure) to support quick and measurable deployment of other experiments

1) Experiment/idea in a “How might we” single question

How might we develop agile and easily deployable technological solutions (infrastructure) to support quick and measurable deployment of other experiments

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)        

In a nutshell, this experiment is three things:

  1. Expanding Community IT by expanding its focus as a DevOps team for some resources we’ve put on AWS
  2. Test the value of freeing up dev time by offloading DevOps work to volunteers.
  3. (Aspirational) Use the outcome of this experiment as a demonstration of the potential value of investing in community from an MoCo IT team perspective. Get IT team along in the conviction tunnel.

Single domain

Wildcards

Able to deploy experiments really quickly

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

How Community IT should be involved, be able to tap into this flexible infrastructure. Getting some educational initiatives in place for community IT. Community IT would be co-drivers of this.

Combination of many different types of deployment, different solutions.

PR team requests to find a creative way to gather relevant media content locally and send it back to the PR team. This is an example of a tool that we could more quickly develop with this existing infrastructure instead of reinventing the wheel.

What’s the articulated value proposition of having this be our own tool as opposed to just hacking together google docs or whatever it takes to get something ready quickly? Gives us a chance to deploy really fit-for-use tools that reach MVP status really quickly, rather than have lower quality experiences.

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

6) Hypotheses and how we test them

  1. We will be able to have a quicker turn-around time in order to deploy an experiment. We can eliminate most of the 1/3rd of the time for deployment.
  1. How much time are we spending on deployment?
  1. Common metrics infrastructure will allow us to measure experiments and evaluate these moving forward.
  2. This will reduce friction in trying tech-based experiments.
  3. Tools like this give a better experience that whipped together google docs-like solutions
  1. Not sure how to test this.
  1. Creating an environment like this will bring maintenance costs, consolidate infrastructure.


How can we provide local physical spaces (aka "Participation Hubs") for contributors to meet, share and hack in a financially sustainable way?

1) Experiment/idea in a “How might we” single question

How can we provide local physical spaces (aka "Participation Hubs") for contributors to meet, share and hack in a financially sustainable way?

2) What the experiment is all about (specific and general problem/opportunity, general idea, etc)

There’s a need for physical spaces where volunteers can meet and work together locally around the world. Last year we started to experiment around this, identified a few communities where we wanted to test the

Currently have 3 spaces run by community: Taipei, Manila, and [didn’t hear]. Results in these 3 spaces have been better achievements, larger community.

Problem is lack of resources?

3) What a solution might look like, a descriptive definition of success (along with impact to mission) and how this might scale or be a breakthrough for Participation at Mozilla

This goes beyond just enabling Mozillians to work together. It can turn into a more general gathering of people who support the open web. A place for more than just our contributors.

Potential business model that generate revenue and be financially sustainable.

Similar idea in Berlin: we wanted to build a Lab.

4) Where the idea came from and who is implicated

5) Options for implementation (rapid prototypes of solutions)

  1. New community spaces
  2. Existing office spaces
  3. Triggering entrepreneurial startup for promoters of the open web

6) Hypotheses and how we test them

  1. If we provide physical spaces to community then we will empower them to do more, do better and recruit more contributors
  1. More contributors in that region
  1. There is a space that is not filled by the Hubs/Hacker Space/Accelerator that Mozilla can help to fill