Webmaker/2013plans: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 81: Line 81:
* Call with new management team
* Call with new management team


''Nov 23''
'''Nov 23'''
* 1st review of straw man budget
* 1st review of straw man budget


===Nov 28-29===
'''Nov 28-29'''
* Management team work sprint (Toronto)
* Management team work sprint (Toronto)


===Nov 30===
'''Nov 30'''
* Roadmaps for each goal
* Roadmaps for each goal
* Key hire job descriptions written up
* Key hire job descriptions written up
* 2nd review of budget
* 2nd review of budget


===Dec 5===
'''Dec 5'''
* Lock strategy deck and budget
* Lock strategy deck and budget


===Dec 10===
'''Dec 10'''
* Ship strategy deck and budget to board
* Ship strategy deck and budget to board


===Dec 12===
'''Dec 12'''
* Board meeting
* Board meeting

Revision as of 16:45, 19 November 2012

Context


Vision: Build a generation of webmakers
Long term goal: Move tens of millions of people from using the web to making the web.

Overarching goal for 2013

[write this]

Top level goals

Product: in 2013 we want Mozilla Webmaker to be:

1. A popular way to make and remix web content
2. Levels up your web skills every time you make something
3. Powered by a global community of makers and mentors

Ops: in order for this vision of Webmaker to succeed we need to:

4. Create a culture of excellence (process + outcomes)
5. Tee up solid long term funding and resource base
6. Establish a regular flow of new product ideas

Product goals plus concrete objectives

objectives = short term things we will do to pursue a goal, last less than a year

1. A popular way to make and remix web content


Metric: # of makers

1.1 Visitors turned into makers (more than two visits post sign up)
1.2 Personal gallery + social media let you share and showcase what you made
1.3 Steady flow of starter projects based on popular internet topics and themes
1.4 Webmaker.org becomes a way for finding and celebrating best 'makes'
1.5 Simple way to pull your existing content in from mobile and social networks

2. Levels up web skills every time you make something


Metric: # of badges issued

2.1 Full set of Webmaker badges covering all the skills we care about
2.2 Playlists, 
badge pathways and user dashboards making learning easier
Tools and projects to learn javascript added to Webmaker.org
Partners build our tools and badges into their sites, includes skills we don't teach
L10N added as way to bring learninig and content to more people

3. Powered by a global community of makers and mentors


Metric: # of mentors

3.1 Makers turned into mentors (organize 2+ events or volunteer online)
3.2 Grassroots instructor community established, 
like a year round summer code party
3.3 Tools and support to help community make great content and learning projects
3.4 Tools that make it easy to find local 
teachers / events / clubs online
3.5 More + better mentor how to guides: step by step guides for local organizing

Ops goals plus concrete objectives

objectives = short term things we will do to pursue a goal, last less than a year

4. Create web sites and events that invite web makers into all we're doing


4.1 Build simple online hub for all Mozilla web maker activities
4.2 Roll out online platform for Hive learners and members
4.3 Build Popcorn and MoJo event models to drive learning and engagement
4.4 Run an awesome 2012 Mozilla Festival, build around learning and software
4.5 Establish baseline participation and engagement metrics and track/report

5. Tell the Mozilla story well, inspire people to get involved


5.1 Tell one Mozilla story; build brand architecture, core narrative, and brand book
5.2 Deploy strong 'non-profit' elements throughout all Mozilla channels
5.3 Raise the communications bar; simple messaging, integrated comms, regular blogs/video
5.4 Build awareness of Mozilla as web-maker/learning org with public, media, and Mozillians

Planning Schedule

Nov 21

  • Call with new management team

Nov 23

  • 1st review of straw man budget

Nov 28-29

  • Management team work sprint (Toronto)

Nov 30

  • Roadmaps for each goal
  • Key hire job descriptions written up
  • 2nd review of budget

Dec 5

  • Lock strategy deck and budget

Dec 10

  • Ship strategy deck and budget to board

Dec 12

  • Board meeting