In his blog post “Reinventing Mozilla on Campus” George Roter delves into the potential of Mozilla on Campus and the way in which we’ve only just scraped the surface of this potential.
This year, the Participation Team has a key hypothesis as part of our strategy: That we can supercharge participation with a reinvented campus program.
Below we’re laying out the full process we will follow for reinventing Mozilla’s presence on campus and articulating clearly the opportunities you have to be involved. If you haven’t yet, I recommend you start by reading George’s post and then dive into the information below!
Who Is Involved:
For this project we’re using the [RAPID](https://en.wikipedia.org/wiki/Responsibility_assignment_matrix#RAPID) responsibility matrix to clarify the roles and responsibilities of those involved in the decision making process.Recommend - Lucy Harris, Christos Bacharakis
The Recommended role involves 80 percent of the work in a decision. They will gather relevant input and propose multiple options so that the decision maker’s choices are as clear, simple and timely as possible.
Agree - Mark Surman, Chris Lawrence, Rosana Ardilla, Mitchell Baker, Katharina Borchert
The Agree role represents a formal approval of all options and recommendations.
Perform - Christos Bacharakis, Lucy Harris, 270 Strategies
The Perform role defines who is accountable for executing or implementing the decision once it is made.
Input -Primary: FSA E-Board & RALs, Mozilla Clubs, Reps Committee, Policy & Advocacy, Marketing & Branding
Secondary: Local Coaches, All FSAs, All Reps, SUMO, L10N, Tech Speakers, MDN, Mozilla Science, Mozilla Leadership Network.
The Input role provides relevant information and facts so that the Recommender and Decider can assess all the relevant facts to make the right decision. However, the ‘I’ role is strictly advisory. Recommenders should consider all input, but they don’t have to reflect every point of view in the final recommendation.
Decide - George Roter
The Decide role is for the single person who ultimately is accountable for making the final decision, committing the group to action and ensuring the decision gets implemented.
The Mozilla on Campus Process
Phase 1: Listening (May 16-27)
In the listening phase Christos and Lucy will be requesting interviews with all of the primary Input groups with the goal of gathering information on two specific topics:
- Data about the strengths and weaknesses of existing campus programs.
- Understanding about what Input groups see as the opportunity on Campus for Mozilla and their communities.
If you are a member of one of the input groups, look out for an interview request from Christos or Lucy shortly.
May 27th - Based on the results of these interviews we will be identifying and pull out some of the big meaty “tensions” or questions, and sharing them on Discourse in order to get broad input. Examples of the kind of “tensions” we anticipate hosting discussions around are: whether our campus presence should be multi-purpose vs. specialized, highly-connected vs. individual, highly selective vs. highly open, etc.
Phase 2: Synthesize Data & Identify Options (May 30-June 10)
In this stage the *Recommend* and *Perform* groups will synthesize all of the input we’ve received, and put together some options for what the future of Mozilla on Campus could look like. We will then share these options with the *Agreers* for feedback which we will use to hone and refine the options.Phase 3: Final Input (June 13 - 24th)
At this point the refined options will be shared back to the entire *Input* group for comments and feedback. We will be conducting some of this Input stage in person with those who are in London.Phase 4: Finalize Decision and Disseminate (June 24 - mid-July)
Based on the final input, the options that remain will be further revised and refined and final versions will be brought to the *Decider* by early July. George Roter will make and announce a final decision by mid-July.Once the decision is officially made and announced the Perform group will begin the process for implementing the new plan. Our goal is to have an early version of the Mozilla on Campus program ready to launch near the start of the 2016-2017 school year.
This is our planned schedule but obviously the timeline is likely to shift slightly. We’ll keep you updated about any changes.
Hopefully in this process you can already see the opportunities for you to provide input, share your ideas, and shape the future. We will do our best to send reminders and prompts whenever there is an opportunity for input, but we also need those of you who care about this issue to keep an eye on discourse and to take the time to respond, question, and share. Even if it’s just to say you’re excited, uncertain, or don’t understand.
We hope you’ll start now by sharing your questions, thoughts, and feedback about this post on Discourse here.
We can’t wait to reinvent the future of Mozilla on Campus with you!
Lucy & the Campus Campaign Team
