Explaining Webmaker crisply
September 25, 2012 § 9 Comments
We’ve been honing our description of Webmaker recently. Partly, this is so we can explain Webmaker to the world. But it’s mostly aimed to clarifying what we’re building and who we’re building it for as we move into the next phase of development.
At a recent meeting in Toronto, Erin Knight led a set of discussions on this topic. I came out of these discussions with four big takeaways:
1. Webmaker is a peer to Firefox and FirefoxOS.
Mozilla has big priorities right now: the web on the desktop; the web in the mobile environment; and web literacy. We need to start positioning Webmaker in this context, showing how Mozilla’s three big bets / priorities all tie back the same mission.
Also, we need to make the link between the value of a phone you can re-program because it’s made from the web (FirefoxOS) and the value of knowing how the web works (Webmaker). Getting web phones into the hands of millions of skilled and creative people is the key to a next wave of innovation on the web.
2. We should describe Webmaker by simply explaining what you can make.
We need to describe Webmaker more simply and concretely. We’ve been able to say ‘Mozilla wants to create a generation of people who know how the web works and can reprogram it.’ But describing what we’re building to make this happen has been difficult. We took a shot at fixing this in Toronto:
Mozilla Webmaker: a quick way to make, remix or tweak a webpage or video while learning how the web works.
While this isn’t quite right yet, it opens up an important new direction: we should be explaining what you can make with Mozilla Webmaker. This creates a more tangible picture in people’s minds and helps them understand how they can engage. I’m hoping others can come up with better wording than what we have above, but based on the general approach of saying what you can make.
3. Our audience is people with something to share.
Up to now, we’ve been a bit fuzzy about who we’re targeting with Mozilla Webmaker. In Toronto, we narrowed in on ‘people how have a maker attitude and something to share’ as a core audience.
There are two pieces to this. The first is is about an approach to life: one that involves tinkering, remixing and iteration. The second is about having made something that you are proud and excited about, something that you want to share or show to other people: a picture you took; a video you made; a game you’ve modified; a big idea you’ve dreamed up. We build the needs and desires of this audience into our design process as we work on the next phase of Mozilla Webmaker.
4. Educators are also a key audience.
During the last thee months, almost 700 people organized Mozilla Webmaker Summer Code Party events. Whether they gathered 100 people or simply brought a few friends around a kitchen table, these people have played a critical role in getting Mozilla Webmaker off the ground. And they have done so because they care about inspiring and educating others about the creative potential of the web.
Personally, I hadn’t really thought about this group as one of our key audiences before. But clearly they are. These are the first people to ‘get’ what we’re trying to do with Webmaker and to feed back in to help improve it. Like the early adopters who first installed Firefox on other people’s computers, these grassroots educators and evangelists could be the core of our global community. Over the next couple of months, we need to figure out ways to more actively help them and bring them into what we’re building.
These four insights aren’t particularly radical. They fit with where we’ve been going with Mozilla Webmaker for the past year. However, I do think they make it easier to explain what we’re doing. They also offer increased clarity on what we need to be building and who we need to be building it for over the next six months. Erin is going to do her own post on this aspect of the Toronto discussions, looking at how we practically pull all the pieces of Webmaker into a more cohesive offering.