ParticipationSystems: Difference between revisions
m (→🌅 Vision: updated wording with Strategic Plan) |
m (→😠 Identified Pain Points: Moved from Pain Points to Principles for Participation) |
||
| Line 16: | Line 16: | ||
# Our software tools continue to evolve in ways that encourage (responsible) openness and match our aspiration for being a great participatory organization | # Our software tools continue to evolve in ways that encourage (responsible) openness and match our aspiration for being a great participatory organization | ||
== | == Principles for Participation == | ||
* Volunteers have access to the right data, at the right time, through the right tools | |||
** Not all volunteers need access to all data (e.g. based on data sensitivity, NDA-status, etc.), but they do need to be able to seamlessly access what they need to execute Mozilla’s mission | |||
* Great ideas come from everywhere | |||
** Foster creation and collaboration, whether it originates from paid staff or from our amazing community of volunteers | |||
* Decrease inertia while protecting Mozilla’s brand | |||
** Low barrier for entry to get started as a volunteer and use progressively higher bars for representing Mozilla’s brand | |||
* Appropriate cost & security controls | |||
* By default, paid staff and volunteers should use the same platforms and tools | |||
== 🚩 Organizational Change Strategy == | == 🚩 Organizational Change Strategy == | ||
Revision as of 14:20, 26 September 2016
Overview
The purpose of the Participation Systems initiative is to force multiply Mozilla’s capacity to deliver our ambitious mission by aligning software and IT systems that enable staff, volunteers, and allied communities to work together in radically participatory ways.
🌍 Background
While our leadership is unified in wanting Mozilla to be truly open to volunteer participation, our current organizational “operating system” makes it difficult to work strategically across employee-volunteer-community boundaries. The legacy systems we use are messy and complicated encouraging collaborative workflows that lack engagement and creating barriers to volunteer participation. We have walls that need to be taken down, and new systems that need to be built.
🌅 Vision
By 2020, Mozillians and participants find it easy to access, understand and collaborate on Mozilla’s projects, allowing them to be effective and feel good about contributing to the mission.
- Mozilla is a great participatory organization, welcoming to staff, volunteers, and allied community alike
- Programs see the value participation brings to their efforts, and are able to build it into their processes and workflows
- Mozilla is knowable and understandable leading people to see where and how they can make high value contributions
- Our software tools continue to evolve in ways that encourage (responsible) openness and match our aspiration for being a great participatory organization
Principles for Participation
- Volunteers have access to the right data, at the right time, through the right tools
- Not all volunteers need access to all data (e.g. based on data sensitivity, NDA-status, etc.), but they do need to be able to seamlessly access what they need to execute Mozilla’s mission
- Great ideas come from everywhere
- Foster creation and collaboration, whether it originates from paid staff or from our amazing community of volunteers
- Decrease inertia while protecting Mozilla’s brand
- Low barrier for entry to get started as a volunteer and use progressively higher bars for representing Mozilla’s brand
- Appropriate cost & security controls
- By default, paid staff and volunteers should use the same platforms and tools
🚩 Organizational Change Strategy
- Generate Momentum/Create Demand
- Close collaboration with groups that want to work together.
- When: In progress w/ IT, MoFo, Participation, CD, identifying other key parties.
- Scale to “new” areas
- Build on infrastructure to facilitate new pan-Mozilla projects that leverage participation.
- When: by EOY, ongoing
- Replace legacy systems
- Identifying legacy systems for participation and migrating them.
- When: TBD
✅ Program Goals
- Enable Mozilla identity (non-LDAP)
- Design and implement volunteer management systems
- Evolve collaboration and communication systems
- Evolve participation infrastructure
Execution
👥 Who is the team?
As of SEPT 2016
| Responsible | Accountable | Support | Consulted | Informed |
|---|---|---|---|---|
| Henrik Mitsch | George Roter
Josh Howard |
Product/Program Management | Simon Wex
TBD |
Katharina Borchert - CIO |
Phase 1 (until mid-AUG 2016)
| Responsible | Accountable | Support | Consulted | Informed |
|---|---|---|---|---|
| George Roter | David Ascher | Product/Program Management | Simon Wex | Katharina Borchert - CIO |
| Engineering - Participation | ||||
| Engineering IT
Team to TBC |
🙌🏼 How to get involved
The Participation Systems initiative is a run by a cross-organization team working on discrete, finite-duration projects. Each project has its own goals and composition of engaged stakeholders. For more information on how to get involved, click on the wiki page for each project below.
For general questions and up to date information, join us via our #participationsystems (Mibbit) IRC channel and our Participation Systems category on Discourse.
🚀 Current Projects
Volunteer Management Systems
Reps Portal
Community Analytics
Discourse 💬 Evolution
Participation Infrastructure
Subproject: Community website migration