ParticipationSystems: Difference between revisions
m (ββπ₯ Who is the team?: Updates to represent current realities.) |
m (ββπ
Vision: updated wording with Strategic Plan) |
||
| Line 9: | Line 9: | ||
== π
Vision == | == π
Vision == | ||
# Mozilla is a | 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. | ||
# 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 | # Mozilla is a great participatory organization, welcoming to staff, volunteers, and allied community alike | ||
# Our software tools continue to evolve in ways that encourage (responsible) openness and match our aspiration for being a | # 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 | |||
== π Identified Pain Points == Β | == π Identified Pain Points == Β | ||
Revision as of 14:17, 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
π Identified Pain Points
- Protected resources within frequently used information and collaboration systems are not accessible to NDAβed volunteers (specifically, google documents/slides/etc and some of the content that is currently in Mana)
- We lack an identity system for volunteers that would unlock access and collaborative capacities. This is complex given the broader need for an identity strategy for staff that is happening in parallel.
- It is difficult for volunteers to manage their contributions and touch-points with Mozilla, or even find/understand opportunities for participation that exist due to inconsistent systems and processes that donβt relate or speak to one another.
- We have a set of useful components such as Mozillians.org, LDAP, etc, but theyβre not yet integrated.
- We lack understanding of volunteer involvement in different areas (advocacy, coding, SuMo, innovation), and are unable to manage our relationship with volunteers and help them be effective because of fragmented tools and limited systems.
π© 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