SUMO now helping an additional 7.3 million visitors

About 3 weeks ago we made the switch to a new information architecture and new design. The goal was to improve the browsability of the site and help people find the articles that they were looking for. 3 Weeks later we can now take a look at our key performance indicators to determine whether the whole project was worth the effort


Since this project was primarily concerned with the KB, we can focus on the helpfulness rating in this channel. Also, we know from our exit surveys that about 80% of our visitors use the KB. The KB helpfulness rating is based on the survey that accompanies each article in each language. We ask the question “Was this article helpful?”, which can be answered with yes or no. Of course this metric is not perfect, articles that describe features have higher ratings than articles explaining how to fix a problem, English articles are generally higher rated than localized articles, despite having the same content, and the rating is also influenced by the path people took to get to the page. However, in this case we are not interested in the absolute ratings, we are particularly interested in the change since we moved to the new iA and design.

So, what happened?

We knew from previous tests that making the change would be beneficial for that segment of our users who would rather browse than search for their article. People rate an article down, when it’s not the one that they were looking for. We know as much from our article surveys, and assuming we did our homework we should help more people find the right article. That being the case we expected the helpfulness of articles to rise, but it was hard to tell by how much it would rise. Considering that we have over 500,000 visitors per day and 80% use the KB, even a change by one percentage point would help an additional 1.46 million visitors per year. Without further ado, here are the results:

The results are phenomenal, we raised the helpfulness by 10 percent on average. That’s an increase by 5 percentage points and means an additional 7.3 million visitors per year stating that they found a SUMO article helpful. This is across all languages and across all incoming channels. It means that in 7.3 million cases where people might have decided to drop Firefox or be miserable because they couldn’t get Firefox to do what they wanted, they will now leave SUMO satisfied with their browser.

It’s hard to overstate the significance of this, and we are extremely happy with the results. The improvements to the site were the result of month of hard work by many people on the SUMO team, from SUMOdev, our creative team, and UX designers. We knew we were able to offer our users a better service, and the work has finally paid off. Continually thinking about how to serve our users better is what’s driving this team, and we will take these results as motivation to work even harder on improving our services.

Today, I’m very proud of what this team made possible, and I’d like to extend my thanks to each and everyone involved in the process: You made these results possible!

The All New SUMO

Today we are going to make one of the biggest changes yet to SUMO, the Mozilla Support site, and this blog post is about what changes we are making. The changes will effect you the most as a user, but there are a number of changes for contributors as well.

First, a little history, what’s the SUMO team been up to this year?

For the last 9 month the SUMO team has been working on a new way to let users access our site content. Until recently the only way to reach most of our articles was by search, or by following links in articles. This is how wikis traditionally work. Of course that way of accessing content only works for a part of our visitors, some people want to search and some people want to browse to the solution, drilling down with ever finer topics to reduce the number of article that are related to the issue.

To come up with a new information architecture that would let people drill down like that, we first researched the mental model of our site users, how they think about issues and in what categories they would look for them. Based on that we created a small number of base categories and assigned our articles to those categories.

The next step was figuring out how to make this information architecture visible. We started to lay out a number of alternatives on paper and tested with real people in a lab. This paper prototyping gave us a way to test a number of ways to lay out the information very quickly. After a number of iterations we settled on the final designs and workflows.

Now we had everything to start adapting our site, but since this would be a big redesign, and we’d soon switch to the new unified One Mozilla design anyway, the decision was made to use this opportunity to rebuild the site based on the new theme, and that’s why the changes today not only affect the KB, but every part of our site.

So, what is changing? What does it look like?

The main change is, that we now support several products from one start page and all articles can be accessed by browsing. Let’s start with the start page:

We have the main topics on top, they allow you to start browsing by selecting your issue first, and then the product you have issue with.

One step below you can see the hot topics. Those are actually articles, things that came up recently and affect a large number of people. By providing them upfront we save a large number of people  the hassle of searching or browsing for their solution.

Below that we have the product picker, this is a way to navigate our content by choosing the product first and then narrowing down the topics.

No matter what way you select, topic first or product first, you’ll end up narrowing down the number of articles to a scanable few and proceed to read one of the articles.

The important thing for localizers to note is: all of this is automated, there is no need anymore to create navigation pages and all the confusion that brought with it.

So, how did the article view change? On the surface not much has changed, but because we keep track of topics, we can now offer you a way to move to related topics, which is particularly interesting for people landing on articles from external searches:

Much, much more has changed, but this is the gist for the KB part of the site.

So, what has changed for forum contributors?

While the new iA did not touch the support forum per se, we took the redesign as an opportunity to improve a number of factors in the listing of questions for our contributors.

The new design is more friendly and clean, but at the same time gives more information about the thread content at the same time. This is especially helpful when contributors scan the thread listing page deciding which thread to pick next.

We already started rolling the design out to our contributor base over the last week and will start rolling it out to 1% of the general audience today. If everything goes to plan we’ll make it available to the general audience on Monday. If you want to try it out now, just register an account, and if you have any feedback, please use the comment section below.

The new information architecture will open up our content to a whole new group of users and make it much more accessible, while our new design is more coherent, taking into account all of the features we added since our first release while also being consistent with the Mozilla sites in general. All of this makes us very excited and hopeful that we’ll get that much closer to our number one goal: Happy users!

Verbatim contributors no longer need a committers agreement

The new Verbatim registration
The new Verbatim registration

Verbatim is probably one of the least known and at the same time one of the biggest L10n tools at Mozilla. If you see localized text on one of the sites or Mozilla campaigns, chances are it was localized with Verbatim. Hundreds of localizers are registered for the various sites and languages that are managed by Verbatim.

Registration was always open at Verbatim, but to commit any localized text, you had to file a bug, print out the committers  agreement, sign it and send it back by fax or traditional mail. That’s quite a barrier, if all you want is just to help localize a mozilla campaign. Some time ago we made that easier by allowing contributors to take a picture of the contributor agreement and email the signature. But still, the agreement had to be processed by someone at Mozilla and only after closing the bug we’d be able to assign you commit rights.

Last week we went one step further and removed the necessity for the contributor agreement altogether. Now we ask you to accept our license agreement upon registration, and locale leaders can request commit access for any registered user. This will reduce the overhead for contributors and Mozilla staff significantly, and it will hopefully lead to more contributions in 2012 and happier localizers overall. Of course we are not done yet, you can see our immediate plans for Verbatim on the Verbatim planning page. One of the next steps now is to allow the management of contributors by locale leaders instead of the Verbatim admins.

Another feature we added last week is acknowledgment of contributors on Verbatim. We now have a page linked from the Verbatim footer that shows each languages with its supported projects and the contributors to each project. The next step for this is to allow individual sites to credit their localizers directly on the sites. And hopefully we can crosslink the names to Mozillians sometime soon, to make it even easier for new contributors to get in touch with our established localizers.

Implementing bureaucratic overhead is usually rather simple, but reducing it is an order of magnitude harder. Especially as organizations grow and people change, it sometimes becomes unclear why a process was put in place and sometimes the process stays even as the world changes and the need for it goes away. That makes it all the more important for each and every one in an organization to constantly re-evaluate existing processes to simplify them and to eliminate the ones that are no longer needed.

In the case of Verbatim registrations several teams at Mozilla helped to lower the bureaucratic overhead needed to contribute as a localizer. I’d like to thank Seth Bindernagel who agreed to start the discussion about that with me, and Gerv, who drove the change to allow camera-pictures as contributor agreements last year; Chris Hofmann and the L10n team, who helped to drive the main discussion on Verbatim and localizer tools forward, the legal team for reviewing our processes and giving us the green light; Mike Morgan and Laura Thompson for assigning the necessary web developer resources to make those changes happen, Peter Bengtsson for the fantastic implementation and finally Stas Malolepszy for his continued support throughout the whole process.

How to support 400 million users with 4 people

Last weeks FOSDEM was my 7th FOSDEM in a row and my first as part of the SUMO team. And since it’s my favorite tech conference, I wanted to share some of my experiences at Mozilla with my fellow FOSDEM visitors.

We have around 400 million Firefox users by now, that means that offering traditional support to them is completely impossible, especially since the support team has only 5 employees. But we still want happy users, and the only way that works is when users help other users. So, after evaluating the situation, we spent most of last year designing the best possible tools for our community. Because we are facing the same challenges most free software projects will face, I wanted to share our assessment and our solutions with the broader free software community, and since I needed a catchy title, it’s called “How to support 400 Million users with 4 employees.”

Instead of boring you with the slides, that don’t makes any sense on their own, I tried a little experiment. I recorded the whole presentation with my voice on it and exported it as a video. It’s a bit rough around the edges, but hopefully still useful. Let me know if you have any questions or comments.

Mozilla in Skopje

Last weekend we had a fantastic event in Skopje that brought together almost the whole Balkan in Macedonia. Together with David Tenser we were there to learn more about our community and present SUMO and our big rewrite. Later we had the chance to talk to the bigger audience about the role of support within Mozilla and what it means to support 400 million users. Mapping names to faces after chatting online for some time is always nice and there was plenty of chance for that as well.

I like to think that the Balkans event was as fun as it was productive. For us it’s important to reach as many people in their native language as possible, especially with support and that’s a goal we share with our localizers. We already had locale leaders for half of the languages spoken in the Balkan region, big thanks to Aleksandar, Edo, Milos and smo; and we added 3 more with Bulgarian, Greek and Mazedonian, another big thanks to Emil, Martin, Pierros, Contanton and Gorjan. This event was a first in that the locale communities set goals for themselves to track their progress. There we didn’t but here I pledge that I’ll try everything I can to help the locale communities to bring support to people in their native language. And hopefully we will have localized support for the top 20 articles in every language spoken in the Balkans by the end of the year 🙂

And a huge thanks to William and especially Gorjan (who is 17!), for making the Balkans meeting such an amazing event!

Patricia was so kind to translate this into Belorussian. How cool is that?! Check it out here:
Belorussian by PC

Are Americans different from Germans?

So, are Americans different from Germans? Or from dutch, or from Brazilians? Okay, they probably are to some point, but the question for the SUMO team is: do Americans have the same questions about Firefox as Germans or Spanish or any other language group? Currently we do assume that, but we didn’t actually back that up with data. The process of doing so is quite tedious, but we have 300 articles in our knowledge base and if it turns out that the top 20 articles in Spanish are different from the top 20 articles in English our localizers can make much better decisions about which article to localize or work on next. Ideally we would send out weekly rankings to our localizers and we will hopefully be able do so with Kitsune, the new KB project, in the meantime however we are working on making sense of the data we have and we will share that with localizers soon.

If you are a localizer and want to know about the popularity of an article, just ask in our contributor forums, I’ll try to come up with an answer quickly.

My first day, after 7 years

Hello Mozilla community,

today is my first day as the SUMO community manager. I actually do plan to put that on my business card “SUMO community manager”. I guess it will lead to a lot of interesting questions 😉 And that will give me an excuse to tell people about the extraordinary privilege that I have doing just my job.

I have been with Mozilla for more than seven years now. I started as a localizer for Firefox (then m/b or Phoenix) and lead the German Firefox community ever since. A few month ago I applied for the position of the “Support community manager” at Mozilla. After all, managing a support community is what I’ve been doing for several years as a hobby.

I mean that’s the dream of most people, right? Getting payed for something you would do even if nobody happened to pay you. Turning your
hobby into your job. But it’s more than that. Now I don’t have to feel bad for putting so much time into it and I get to extend the scope of my
work, which is just awesome.

While leading the German community I had a lot of time to gain experience in building communities and working with them. I’ll still be
part of the German community, but now I hope to use that experience to work much more closely with the international community on global support issues at Mozilla. Coming from a local community I know the pain points of those communities and my hope is that as part of the SUMO-Team I’ll be able to guide the way to a much more localization- and community-aware SUMO.

So, all in all, I couldn’t have asked for a better situation to be in, I’m grateful everything worked out so perfectly and I’m excited to get
started. Oh, and I have one more blog post about why I think I have one of the best jobs in the world.


Eines der wichtigsten Features von Firefox sind Erweiterungen. Eines der größten Schwächen von Firefox sind Erweiterungen. Ich hab ein gutes dutzend davon installiert und benutze sie regelmäßig, aber bei jedem Update auf eine neue Version gehe ich erst sicher, dass meine Erweiterungen auch mit der neuen Version kompatibel sind. Dafür muss der Entwickler einer Erweiterung seine Erweiterung mit der neuen Firefox-Version testen und dann auf die Kompatibilität der Erweiterung bekannt geben. Bei über 6000 verfügbaren Erweiterungen gibt es immer Entwickler, die gerade im Stress sind oder auf Weltreise oder einfach nicht mehr interessiert.


Mozilla hat aber eine riese Userbasis für Betatests, da liegt es also nahe, diese auch für Addon-Betatests zu gewinnen. Genau dafür ist der Add-on Compatibility Reporter gedacht. Wer den installiert, kann alle Erweiterungen installieren, auch die, die als nicht kompatibel markiert sind, und kann dann an Mozilla melden, ob das Add-on auch in der neuen Firefox-Version noch funktioniert. Diese Daten stehen dann den Entwicklern zur Verfügung und Mozilla kann direkt einzelne Entwickler anschreiben, wenn die Add-ons nicht kompatibel zu sein scheinen. Wer daran teilnehmen möchte, kann die Erweiterung hier herunterladen.


Schon seit einiger Zeit habe ich, wie auch Robert für Seamonkey und Alexander für Thunderbird, Werbung auf der Firefox-Website geschaltet, um Ausgaben für Server etc. nicht aus eigener Tasche zahlen zu müssen. Zunächst mit der Google-Version von Firefox, dann mit der Ebay-Version. Leider reichen die Einnahmen daraus nicht mehr, um den Server zu betreiben, deswegen habe ich heute zusätzlich die Yahoo-Edition aufgenommen. Da Yahoo aber kein öffentliches Programm dafür hat, bin ich eine Vereinbarung mit Tobias Selb von eingegangen, der offizieller Parter von Yahoo für diese Edition ist. Ich hoffe, dass ich dabei nichts übersehen habe, aber wenn es einen guten Grund gibt, der dagegen spricht, bitte eine E-Mail an mich.

Nightlies jetzt auch auf Deutsch verfügbar

Seit einiger Zeit schon können Firefox-Nightlies auch auf Deutsch heruntergeladen werden und es werden auch Updates für diese Nightlies automatisch zur Verfügung gestellt. Bisher wäre das häufig nicht praktikabel gewesen, weil jeder neue Englische String die deutsche Ausgabe unbrauchbar gemacht hätte, aber inzwischen gibt es Skripte, die fehlende deutsche Strings durch entsprechende Englische ersetzen, bis ich dazu komme, diese neuen Strings zu lokalisieren. Es wäre schön, wenn sich einige hier dazu entschließen könnten, diese deutschen Nighlies zu verwenden, damit wir Fehler schon im frühen Stadium finden und beseitigen können.

Die Nightlies  für Firefox 3.6 befinden sich unter:

Windows Installer

Die Nightlies für Firefox-Trunk: