Tag Archives: mozilla

How do we do better product testing in Q2?

We’ve been trying to figure this out for Webmaker. Here’s a proposal:

  • 1) Start small. Figure out our product testing strategy *for Q2.* (Instead of “everything we need to do to get better at testing.” Which feels too overwhelming.) What are the most important things to test and learn this quarter?
    • Proposal: start with the key Engagement Ladder stuff. We’ve said those calls to action are the most important — let’s make sure they’re clear and feel good for users, and identify where they’re bailing or getting stuck. For example:
      • Sign up. Create an account.
      • Create an event.
      • Make a teaching kit.
      • Issue a mentor badge.
    • Why start here? Because we’ve said these pathways are the *most* important. In terms of reaching our 10k contributors goal. We should do usability testing to see where users are getting stuck here, and ship incremental improvements to address those.
  • 2) Focus on testing with lead users. People teaching the web. These users are signing up for Webmaker training, and will be using and offering feedback on Webmaker stuff over the next several weeks. This is a prime opportunity. What do we want to feed in there? https://wiki.mozilla.org/Webmaker/Testing
  • 3) Unstick usertesting.com. aka:

Let’s make it easy for people to test whatever the hell they want, all the time.

  • It doesn’t seem like we’re really making full use of usertesting.com as an asset.¬† Let’s figure out why. (e.g., not sure of process / don’t have log-in / don’t have time / need training / ?) How do we make it easy and permissionless for our devs and designers to play there?
    • For example: when Aali wants to test right-to-left in Popcorn, why can’t he just go ahead and do it? How do we make running a test on usertesting.com as easy and standard as writing a blog post?
  • 4) Optimize the process for sharing out the findings. Understanding what we’re learning from this testing. And then feeding it back into the product. That’s always the hard part. I think we win there by doing usability testing on the small number of things mentioned in (1), rather than “let’s test everything.”
  • 5) Update the Webmaker get involved page. This is where we’re sending folks now. Review and optimize.

What’s missing / wrong? Please comment here.

5 easy ways to support Mozilla

Mozilla Love

What’s the best way to support Mozilla right now?

5 simple suggestions:

  1. Tweet some love using #mozlove or #standwithmozilla
  2. Use the “MozLove” avatar. You can download it here: http://mzl.la/mozlove
  3. Download Firefox. Or encourage others to switch http://www.mozilla.org/firefox
  4. Make a donation. Mozilla is a non-profit community dedicated to protecting the open web. http://mozilla.org/donate
  5. Get more involved with Mozilla’s non-profit mission. http://www.mozilla.org/contribute

Open when it matters: please help Mozilla

Best tweet I saw yesterday

Mozilla needs your love and help right now. More than just a debate about our CEO, this threatens to divide us in other ways if we let it. We need dialogue, and to bring open hearts and minds around the two crucial issues here — both of which are meaty and substantive and vitally important to Mozilla:

  • (1) We don’t need to agree on everything — or force ideological consensus — in order to work with others. That’s a vital part of Mozilla’s open culture and mission. A lot of people have fought for this principle. It’s at the heart of what makes open source vibrant, diverse and practical. And it’s a fragile thing worth protecting.
  • (2) But there are limits to that openness — and those limits center around basic rights. The world has changed. For many (including me), marriage equality is now a rights issue — and no longer just a speech or “personal opinion” issue. So when colleagues frame this purely as a matter of personal opinion, they signal to others that they don’t understand or haven’t considered this difference. That’s why simply doubling down on “freedom of speech” or personal opinion arguments will not work as a way to work past this. The situation requires more.

This is hard. It deserves to be treated that way. Many of us feel very strongly about either or both of these issues — and so it requires nuanced, Mozilla-style reasoning that weighs both sides to find a solution.

That’s why I’m so proud of thoughtful, emotionally complex posts from colleagues working this through in the open. Like this, or this. And disappointed by stories like this one.

If you believe in (2), as I do, I think we’re served by demonstrating patience and compassion here. The difference between marriage equality as a right versus a matter of political or personal opinion is nuanced, historically recent, and culturally complex for a global community like Mozilla’s. And it’s on us to demonstrate that we understand and show respect for (1) as well, and not skip it over casually. For a lot of people, it’s at the heart of the Mozilla project.

Our ability to work this through — together in the open, with open hearts and minds — is even more important than any decision about our CEO. It will determine our strength once all this is done.