Confirmed users
354
edits
Learning/Strategy: Difference between revisions
Jump to navigation
Jump to search
→FAQ
Benmoskowitz (talk | contribs) (Fleshed out Q/A) |
Benmoskowitz (talk | contribs) (→FAQ) |
||
| Line 36: | Line 36: | ||
== FAQ == | == FAQ == | ||
'''What *is* 'Mozilla Academy'?''' | '''Q: What *is* 'Mozilla Academy'?''' | ||
That's what we're trying to figure out. At the very least, Mozilla Academy will be a clearly packaged and branded harmonization of Mozilla's learning and leadership programs. People will be able to clearly understand what we're doing and which parts are for them. | That's what we're trying to figure out. At the very least, Mozilla Academy will be a clearly packaged and branded harmonization of Mozilla's learning and leadership programs. People will be able to clearly understand what we're doing and which parts are for them. | ||
'''Are you set on the 'Mozilla Academy' name?''' | '''Q: Are you set on the 'Mozilla Academy' name?''' | ||
It's pretty unlikely that we will use that name. Many people hate it. However, we needed a moniker to use during the strategy process. For better or for worse, that's the one we chose. | It's pretty unlikely that we will use that name. Many people hate it. However, we needed a moniker to use during the strategy process. For better or for worse, that's the one we chose. | ||
'''Who is 'Mozilla Academy' for?''' | '''Q: Who is 'Mozilla Academy' for?''' | ||
* Over the past few weeks, we've started to look at who we're trying to serve with our existing programs (blog post on this soon). Using the 'scale vs depth' graph in the Mozilla Learning plan as a framework, we see roughly three main audiences: | * Over the past few weeks, we've started to look at who we're trying to serve with our existing programs (blog post on this soon). Using the 'scale vs depth' graph in the Mozilla Learning plan as a framework, we see roughly three main audiences: | ||
| Line 56: | Line 56: | ||
* A big part of the strategy process is getting clear on these audiences. From there we can start to ask questions like: who can Mozilla best serve?; where can we have the most impact?; can people in one group serve or support people in another? Once we have the answers to these questions we can decide where to place our biggest bets (we need to do this!). And, we can start raising more money to support our ambitious plans. | * A big part of the strategy process is getting clear on these audiences. From there we can start to ask questions like: who can Mozilla best serve?; where can we have the most impact?; can people in one group serve or support people in another? Once we have the answers to these questions we can decide where to place our biggest bets (we need to do this!). And, we can start raising more money to support our ambitious plans. | ||
'''What is a ‘strategy’ useful for?''' | '''Q: What is a ‘strategy’ useful for?''' | ||
* We want to accomplish a few things as a result of this process. A. A way to clearly communicate the ‘what and why’ of Mozilla's learning and leadership efforts. B. A framework for designing new programs, adjusting program designs and fundraising for program growth. C. Common approaches and platforms we can use across programs. These things are important if we want Mozilla to stay in learning and leadership for the long haul, which we do. | * We want to accomplish a few things as a result of this process. A. A way to clearly communicate the ‘what and why’ of Mozilla's learning and leadership efforts. B. A framework for designing new programs, adjusting program designs and fundraising for program growth. C. Common approaches and platforms we can use across programs. These things are important if we want Mozilla to stay in learning and leadership for the long haul, which we do. | ||
'''What do you mean by 'common approaches'? ''' | '''Q: What do you mean by 'common approaches'? ''' | ||
* There are a number of places where we do similar work in different ways. For example, Mozilla Clubs, Hive, Mozilla Developer Network, Open News and Mozilla Science Lab are all working on curriculum but do not yet have a shared curriculum model or repository. Similarly, Mozilla runs four fellowship programs but does not have a shared definition of a 'Mozilla Fellow'. Common approaches could help here. | * There are a number of places where we do similar work in different ways. For example, Mozilla Clubs, Hive, Mozilla Developer Network, Open News and Mozilla Science Lab are all working on curriculum but do not yet have a shared curriculum model or repository. Similarly, Mozilla runs four fellowship programs but does not have a shared definition of a 'Mozilla Fellow'. Common approaches could help here. | ||
'''Are you developing a new program for Mozilla?''' | '''Q: Are you developing a new program for Mozilla?''' | ||
* That’s not our goal. We like most of the work we're doing now. As outlined in the 2015 Mozilla Learning Plan, our aim is to keep building on the strongest elements of our work and then connect these elements where it makes sense. We may modify, add or cut program elements in the future, but that’s not our main focus. | * That’s not our goal. We like most of the work we're doing now. As outlined in the 2015 Mozilla Learning Plan, our aim is to keep building on the strongest elements of our work and then connect these elements where it makes sense. We may modify, add or cut program elements in the future, but that’s not our main focus. | ||
'''What's the timing for all of this?''' | '''Q: What's the timing for all of this?''' | ||
* We will have a basic alignment framework around 'purpose, process and poetry' by the end of June. We'll work with the at the Mozilla all hands in Whistler. We will develop specific program designs, engage in a broad conversation and run experiments. By October, we will have an updated version of the Mozilla Learning plan, which will lay out our work for 2016+. | * We will have a basic alignment framework around 'purpose, process and poetry' by the end of June. We'll work with the at the Mozilla all hands in Whistler. We will develop specific program designs, engage in a broad conversation and run experiments. By October, we will have an updated version of the Mozilla Learning plan, which will lay out our work for 2016+. | ||
| Line 89: | Line 89: | ||
* We eliminate confusion about what we advocate vs. what we deliver | * We eliminate confusion about what we advocate vs. what we deliver | ||
* Then finally — brand simplification | * Then finally — brand simplification | ||
'''Q: How can I get involved?''' | '''Q: How can I get involved?''' | ||