ParticipationSystems: Difference between revisions

m
→‎😠 Identified Pain Points: Moved from Pain Points to Principles for Participation
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


== 😠 Identified Pain Points ==  
== Principles for Participation ==  
 
* Volunteers have access to the right data, at the right time, through the right tools
# 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)
** 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
# 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.
* Great ideas come from everywhere
# 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.
** Foster creation and collaboration, whether it originates from paid staff or from our amazing community of volunteers
# We have a set of useful components such as Mozillians.org, LDAP, etc, but they’re not yet integrated.
* Decrease inertia while protecting Mozilla’s brand
# 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.
** 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 ==
Confirmed users
286

edits