Building an Academy

March 31, 2015 § 16 Comments

Last December in Portland, I said that Mozilla needs a more ambitious stance on how we teach the web. My argument: the web is at an open vs. closed crossroads, and helping people build know-how and agency is key if we want to take the open path. I began talking about Mozilla needing to do something in ‘learning’ in ways that can have  the scale and impact of Firefox if we want this to happen.

Mozilla Academy

The question is: what does this look like? We’ve begun talking about developing a common approach and brand for all our learning efforts: something like Mozilla University or Mozilla Academy. And we have a Mozilla Learning plan in place this year to advance our work on Webmaker products, Mozilla Clubs (aka Maker Party all year round), and other key building blocks. But we still don’t have a crisp and concrete vision for what all this might add up to. The idea of a global university or academy begins to get us there.

My task this quarter is to take a first cut at this vision — a consolidated approach  for Mozilla’s efforts in learning. My plan is to start a set of conversations that get people involved in this process. The first step is to start to document the things we already know. That’s what this post is.

What’s the opportunity?

First off, why are we even having this conversation? Here’s what we said in the Mozilla Learning three-year plan:

Within 10 years there will be five billion citizens of the web. Mozilla wants all of these people to know what the web can do. What’s possible. We want them to have the agency, tools and know-how they need to unlock the full power of the web. We want them to use the web to make their lives better. We want them to be full citizens of the web.

We wrote this paragraph right before Portland. I’d be interested to hear what people think about it a few months on?

What do we want to build?

The thing is even if we agree that we want everyone to know what the web can do, we may not yet agree on how we get there. My first cut at what we need to build is this:

By 2017, we want to build a Mozilla Academy: a global classroom and lab for the citizens of the web. Part community, part academy, people come to Mozilla to unlock the power of the web for themselves, their organizations and the world.

This language is more opinionated than what’s in the Mozilla Learning plan: it states we want a global classroom and lab. And it suggests a name.

Andrew Sliwinski has pointed out to me that this presupposes we want to engage primarily with people who want to learn. And, that we might move toward our goals in other ways, including using our product and marketing to help people ‘just figure the right things out’ as they use the web. I’d like to see us debate these two paths (and others) as we try to define what it is we need to build. By the way, we also need to debate the name — Mozilla Academy? Mozilla University? Something else?

What do we want people to know?

We’re fairly solid on this part: we want people to know that the web is a platform that belongs to all of us and that we can all use to do nearly anything.

We’ve spent three years developing Mozilla’s web literacy map to describe exactly what we mean by this. It breaks down ‘what we want people know’ into three broad categories:

  • Exploring the web safely and effectively
  • Building things on the web that matter to you and others
  • Participating on the web as a critical, collaborative human

Helping people gain this know-how is partly about practical skills: understanding enough of the technology and mechanics of the web so they can do what they want to do (see below). But it is also about helping people understand that the web is based on a set of values — like sharing information and human expression — that are worth fighting for.

How do we think people learn these things?

Over the last few years, Mozilla and our broader network  of partners have been working on what we might call ‘open source learning’ (my term) or ‘creative learning’ (Mitch Resnick’s term, which is probably better :)). The first principles of this approach include::

  • Learn by making things
  • Make real shit that matters
  • Do it with other people (or at least with others nearby)

There is another element though that should be manifested in our approach to learning, which is something like ‘care about good’ or even ‘care about excellence’ — the idea that people have a sense of what to aspire to and feedback loops that help them know if they are getting there. This is important both for motivation and for actually having the impact on ‘what people know’ that we’re aiming for.

My strong feeling is that this approach needs to be at the heart of all Mozilla’s learning work. It is key to what makes us different than most people who want to teach about the web — and will be key to success in terms of impact and scale. Michelle Thorne did a good post on how we embrace these principles today at Mozilla. We still need to have a conversation about how we apply this approach to everything we do as part of our broader learning effort.

How much do we want people  to know?

Ever since we started talking about learning five years ago, people have asked: are you saying that everyone on the planet should be a web developer? The answer is clearly ‘no’. Different people need — and want — to understand the web at different levels. I think of it like this:

  • Literacy: use the web and create basic things
  • Skill: know how that gets you a better job / makes your life better
  • Craft: expert knowledge that you hone over a lifetime

There is also a piece that includes  ‘leadership’ — a commitment and skill level that has you teaching, helping, guiding or inspiring others. This is a fuzzier piece, but very important and something we will explore more deeply as we develop a Mozilla Academy.

We want a way to engage with people at all of these levels. The good news is that we have the seeds of an approach for each. SmartOn is an experiment by our engagement teams to provide mass scale web literacy in product and using marketing. Mozilla Clubs, Maker Party and our Webmaker Apps offer deeper web literacy and basic skills. MDN and others are think about teaching web developer skills and craft. Our fellowships do the same, although use a lab method rather than teaching. What we need now is a common approach and brand like Mozilla Academy that connects all of these activities and speaks to a variety of audiences.

What do we have?

It’s really worth making this point again: we already have much of what we need to build an ambitious learning offering. Some of the things we have or are building include:

We also have an increasingly good reputation among people who care about and  fund learning, education and empowerment programs. Partners like MacArthur Foundation, UNESCO, the National Writing Project and governments in a bunch of countries. Many of these organizations want to work with us to build — and be a part of — a more ambitious approach teaching people about the web.

What other things are we thinking about?

In addition to the things we have in hand, people across our community are also talking about a whole range of ideas that could fit into something like a Mozilla Academy. Things I’ve heard people talking about include:

  • Basic web literacy for mass market (SmartOn)
  • Web literacy marketing campaigns with operators
  • Making and learning tools in Firefox (MakerFox)
  • MDN developer conference
  • Curriculum combining MDN + Firefox Dev Edition
  • Developer education program based on Seneca model
  • A network of Mozilla alumni who mentor and coach
  • Ways to help people get jobs based on what they’ve learned
  • Ways to help people make money based on what they’ve learned
  • Ways for people to make money teaching and mentoring with Mozilla
  • People teaching in Mozilla spaces on a regular basis
  • Advanced leadership training for our community
  • Full set of badges and credentials

Almost all of these ideas are at a nascent stage. And many of them are extensions or versions of the things we’re already doing, but with an open source learning angle. Nonetheless, the very fact that these conversations are actively happening makes me believe that we have the creativity and ambition we need to build something like a Mozilla Academy.

Who is going to do all this?

There is a set of questions that starts with ‘who is the Mozilla Academy?’ Is it all people who are flag waving, t-shirt donning Mozillians? Or is it a broader group of people loosely connected under the Mozilla banner but doing their own thing?

If you look at the current collection of people working with Mozilla on learning, it’s both. Last year, we had nearly 10,000 contributors working with us on some aspect of this ‘classroom and lab’ concept. Some of these people are Mozilla Reps, Firefox Student Ambassadors and others heavily identified as Mozillians. Others are teachers, librarians, parents, journalists, scientists, activists and others who are inspired by what we’re doing and want to work alongside us. It’s a big tent.

My sense is that this is the same sort of mix we need if we want to grow: we will want a core set of dedicated Mozilla people and a broader set of people working with us in a common way for a common cause. We’ll need a way to connect (and count) all these people: our tools, skills framework and credentials might help. But we don’t need them all to act or do things in exactly the same way. In fact, diversity is likely key to growing the level of scale and impact we want.

Snapping it all together

As I said at the top of this post, we need to boil all this down and snap it into a crisp vision for what Mozilla — and others — will build in the coming years.

My (emerging) plan is to start this with a series of blog posts and online conversations that delve deeper into the topics above. I’m hoping that it won’t just be me blogging — this will work best if others can also riff on what they think are the key questions and opportunities. We did this process as we were defining Webmaker, and it worked well. You can see my summary of that process here.

In addition, I’m going to convene a number of informal roundtables with people who might want to participate and help us build Mozilla Academy. Some of these will happen opportunistically at events like eLearning Africa in Addis and the Open Education Global conference in Banff that are happening over the next couple of months. Others will happen in Mozilla Spaces or in the offices of partner orgs. I’ll write up a facilitation script so other people can organize their own conversations, as well. This will work best if there is a lot of conversation going on.

In addition to blogging, I plan to report out on progress at the Mozilla All-Hands work week in Whistler this June. By then, my hope is that we have a crisp vision that people can debate and get involved in building out. From there, I expect we can start figuring out how to build some of the pieces we’ll need to pull this whole idea together in 2016. If all goes well, we can use MozFest 2015 as a bit of a barn raising to prototype and share out some of these pieces.

Process-wise, we’ll use the Mozilla Learning wiki to track all this. If you write something or are doing an event, post it there. And, if you post in response to my posts, please put a link to the original post so I see the ping back. Twittering #mozacademy is also a good thing to do, at least until we get a different  name.

Join me in building Mozilla Academy. It’s going to be fun. And important.

§ 16 Responses to Building an Academy

  • Greg Slepak says:

    I think it’s great that you point out the cross-roads that the web is at. We all see “the web” being turned into apps that end up in walled gardens (React Native is this).

    What sort of curriculum do you have in mind?

    I’d like to put in a vote for teaching people about:

    1. New emerging technologies (new ways of doing the web). The web has problems. Big ones. Fundamental ones. We can’t build upon a crumbling foundation, we have to first rebuild a solid foundation, and then build things on top of it, as er… Obama would put it.

    What sorts of problems does the web have? I’ll list off a few:

    – It’s not secure. Even if we managed to force HTTPS on everyone, it still wouldn’t be very secure. Getting people to use HTTPS is a big enough challenge on its own.

    – It has amnesia. We can’t seriously expect one non-profit to fix this problem (as great as they are, the Internet Archive is not up to the task of really solving this, and even if they were, they are a single point of failure. The web should have fundamental answers to this.).

    – It’s complicated. This is the #1 reason you are seeing things going from open => closed. I mean, look at this blog of yours. You’re relying on another company to host it for you because it’s easier than running your own. Are you spending the time learning how to run your own blog? No. If you can’t be bothered with that, how can you expect / ask others to do it? We need to make it _simple_ for people to create content on a _simple_ open, decentralized, distributed platform. The web we have today is not that.

    2. Curriculum #2 should be taking the tech from #1 and re-inventing the web. Today’s web is not going to take you to open. It will take you to closed systems, where people are dependent on a small number of companies to do things for them.

    • Greg says:

      @Greg In terms of issue 2 and 3 I think we are addressing these issues of the open web in the curriculum. We made a concerted effort to encourage open web advocacy and self publishing in Version 1.5 of the map.

      The first set of curriculum encouraged folks to publish to the Open Web

      I see no issue with folks publishing on their own site. It might make sense for webmakers to start on hosted solutions and transition to open tools. FYI this post is also cross posted to the webmaker blog and the is syndicated on the planet webmaker RSS feed.

      Your comment reflects how we need to have different levels of learning and leadership in the Academy. I can’t address your first issue personally or with those I teach. We are learning, “What is a url?”

  • Dror says:

    Unrelated question: why does all of your links refer to Google queries?

  • zafar^ says:

    Mark, this is super interesting because we (authors of Teaching is Out, Learning is IN) wanted your inputs in the perspectives section of the book. However, we realized that the situation in India requires addressing a very specific set of problems. Anything that brings about a greater access and transparency is welcome and it hardly matters what we call it. I am all for Mozilla Academy!

  • […] the next six months, I need to write up an initial design for Mozilla Academy (or whatever we call it). The idea: create a global classroom and lab for the citizens of the web, […]

  • […] work with the metrics around #teachtheweb looking for insights into Marc Surman’s call for a Mozilla Academy by the year […]

  • Open Fluency says:

    […] Web Literacy Map again. Specifically the “Leadership” component of what we do at Mozilla. In his post, Mark called this piece fuzzy, but I think it will become clearer as we define what […]

  • […] initiatives here in Victoria for a few years, and have been watching with interest as Mozilla increases their informal learning activities around web literacy.  The thing that  connected a lot of dots with how Mozilla works (at least in […]

  • Sven Ehmann says:

    This sounds like a great, ambitious and important project indeed.
    I would be happy to somehow contribute.

    For now I would like to share a few experiences gained over organizing Junior Lab, a one week hardware and software camp for 80 girls and boys between 8 and 14, which took place around eastern 2015 in Berlin/Germany. This video gives an impression (despite the german language)

    I initiated Junior Lab because my daughter had a great idea about a smart traffic light. I knew we could have prototyped it, but i didn’t know how to do it. I felt this was unfair, searched for but couldn’t find any offer that spoke to her and then build the story of Junior Lab, which deliberately started from within the kids daily life and interests – and not from a school-like curriculum. Junior Lab was about Music, Fashion, Superheros in the first place and then about Arduinos, 3D printing, coding, stitching circuits and so on. We used a very open, friendly visual language to tell this story (thanks to photographer Jan von Holleben) and it seems this helped us to reach a) kids and parents who otherwise weren’t that interested in technology b) girls and boys alike c) partners who saw the relevance and were comfortable with our not too technical approach.

    There are many other projects with a similar mindset (kidshackday, hackidemia, coder dojo, etc.) and i feel what unites all of us, is the understanding that it has to be fun and relevant to the participants before any other agenda. Its not about what we want to teach them, it about what they want to learn from us.

    I was overwhelmed by the positive response we got. In the first place by the commitment of the participants over 5 days. They asked us when the breaks would be over, they wanted 3D printers for the birthdays afterwards, some parents asked me for the next sessions as their kids decided that now they wanted to learn coding or soldering. After this (and after visiting Mozfest in London for the first time last year) I strongly believe that learning needs such enthusiastic real-life experiences as starting points, as well as great stories to connect to existing interests.

    I also see a great potential in using objects and the whole IoT idea as a starting point. here is why: my music lessons in school where always about notes and never about playing an instrument. if the teacher had given me drums sticks or a guitar for half an hour I would have been ready to learn those notes, but without it remained too abstract. i somehow feel it might be similar with coding. Learning to code without knowing and understanding what the result would be and do, might not be interesting enough…

    Looking forward at Junior Lab we are now discussing how to continue and grow this idea with a variety of people and potentially partners who expressed their interest – some in Berlin or other places in Germany, some in other parts of the world. If I could wish for a future Junior Lab it would be about an open and democratic culture of learning, rather than about specific courses. It would allow us to build a network of people with ideas, idealism and experiences to teach and mentor around hardware, software and ideas. I would like to scale it from one day workshops to ongoing courses, both online and in real world events, so that participants could continue according to their interest, time available and pace. I would like to see a (or several) location(s) with such ongoing offers as well a couple of containers traveling the world – and not just major cities in well developed countries. I would dream of kids developing their own ideas – which naturally grow very soon – in small teams. girls and boys from different parts of the world connected online, who then meet and present their results to other kids. Beyond that I would also like to follow some suggestion we received to also run a senior lab and even better bring kids, their parents and grand parents together to learn together and from one another…

    (I would like to mention, that Junior Lab was organized together with FabLab Berlin and supported by a number of partners such as start coding, ottobock, the BMW foundation, to name a few.)

  • You ask what the Academy would look like. Here is a suggestion for one piece of it, that seems important and achievable > A Mozilla Developer Institute that trains the next generation of technology inventors.

    It’s also something that the MIT Media Lab (where I work) might be interested to help with. Curious to hear what you and your team think.

  • […] to run their own projects in a way that engages the community and builds skills. This builds on a core belief part of our pedagogy here at Mozilla, that the most transformative moments often come from working on things that matter, building them […]

  • […] With even more ambition and dreaming though, I see something like this as a way to create a ‘Participation Standard’ – which can be something Mozilla designs for adoption across open source projects everywhere.   Last year I spent a lot of time working with a number of other open projects, trying to solve for a lot of these same issues – imagine ‘cross project’ learning pathways.  Perhaps this is something Mark can consider in thinking for the ‘Building a Mozilla Academy‘. […]

  • […] consultation was primarily used as a medium to obtain feedback from the Shuttleworth fellows on the Mozilla “Academy” vision, that envelopes the products and programs of the Mozilla Learning plan. Mark conducted two […]

  • […] Academy’ although that’s likely to change. As a way to get the process rolling, I wrote a long post in March outlining what we might include in that strategy. Since then, I’ve been putting together a team to dig into the strategy work […]

  • […] been talking about ‘leadership development’ since early on in the Mozilla Learning (aka Academy) planning process. Basically, the idea is to get more people to teach and advocate for […]

What’s this?

You are currently reading Building an Academy at commonspace.


%d bloggers like this: