Sue Gardner is the executive director of the Wikimedia Foundation, the non-profit, non-commercial organization that operates nearly 300 online projects. Originally from Canada, she worked with the Canadian Broadcasting Corporation in production, journalism and documentaries.
In 2007, she took up consulting for the Foundation on operations and governance and within a year was in the top job. Her tenure has seen a precipitous increase in the staffing at the San Francisco office, which now employs some 100 people, up from 65 just six months ago, and a budget well in excess of $20M a year. In October 2009, Gardner was named by the Huffington Post as one of ten “media game changers of the year” for the impact on new media of her work for Wikimedia.
The Signpost interviewed Gardner on her fourth anniversary as executive director. In person, the boss of one of the world's most powerful websites is all charm and professionalism. Much of the interview concerned the issues she raised in a landmark address in November to the board of Wikimedia UK,[1] in which she said the slide showing a graph of declining editor retention (below) is what the Foundation calls “the holy-shit slide". This is a huge, "really really bad" problem, she told Wikimedia UK, and is worst on the English and German Wikipedias.
A prominent issue on the English Wikipedia is whether attempts to achieve high quality in articles – and perceptions that this is entangled with unfriendly treatment of newbies by the community – are associated with low rates of attracting and retaining new editors. Although Gardner believes that high quality and attracting new editors are both critical goals, her view is that quality has not been the problem, although she didn't define exactly what article quality is. What we didn’t know in 2007, she said, was that “quality was doing fine, whereas participation was in serious trouble. The English Wikipedia was at the tail end of a significant drop in the retention of new editors: people were giving up the editing process more quickly than ever before.
There aren't enough people to do the work ... people are stressed and they're burned out ... you still have lots of [older editors] doing scut-work ... So where are the new generations of people, relieving them of the need to do all this scut-work? — Sue Gardner, UK address
Participation matters because it drives quality. People come and go naturally, and that means we need to continually bring in and successfully orient new people. If we don’t, the community will shrink over time and quality will suffer. That’s why participation is our top priority right now.
At the core of Gardner's philosophy, then, is an intrinsic connection between editor retention and what she calls openness. But The Signpost wanted to know more about where article quality fits into this model – specifically whether the three factors are sometimes at odds with each other and whether a purely one-way causality is involved. Deletions and reversions might be distasteful to new editors, but how can we, for instance, maintain strict standards about biographies of living people (BLP) without reverting problematic edits and deleting inappropriate articles? Gardner rejected the premise:
I don’t believe that quality and openness are inherently opposed to each other. Openness is what enables and motivates people to show up in the first place. It also means we’ll get some bad faith contributors and some who don’t have the basic competence to contribute well. But that’s a reasonable price to pay for the overall effectiveness of an open system, and it doesn’t invalidate the basic premise of Wikipedia: that openness will lead to quality.
What do you say, we asked, to editors whose focus has been on improving quality and who may have taken your comments and the recent focus of Foundation initiatives as an indication that their contributions aren't valued, or even that they are part of the problem?
If you believe there’s an inherent tension between quality and openness, then yes, you might believe that when I advocate for openness, I’m speaking against quality; but I don’t believe that. Quality improvement work – like page patrolling, the FAC, developing content partnerships, and staging competitions like Wiki loves monuments – makes Wikipedia better and more valuable for readers. Where we run into problems is when we do things that repel or frustrate good-faith new editors. But I’m not sure there’s a fixed relationship between activities designed to improve quality and activities that hurt new editor retention, so I don’t think editors who focus on quality improvement should feel attacked or unappreciated when openness is being emphasized.
... we’re not falling off a cliff; but we are having serious difficulty retaining good faith new editors, and that will cause our community to dwindle if we don’t fix the problem.
Does the Foundation have any solutions to enable the editing community to address the cultural issues that might be driving editors away – beyond the WMF's technical initiatives such as an easier editing interface and means of empowering kitten distribution, and external initiatives such as outreach and institutional partnerships?" For Gardner, "The editor retention problem is our shared problem. ... it's easiest for the Foundation to help when there's a technical or tools aspect to the problem. But when the issue is purely editorial or cultural, it’s harder for us to play a role." She singled out two areas: the first is behavioral problems, and the second the sheer quantity of policy and instructional text ("simplifying it would help everyone").
We queried her take on this second area, pointing out that all publishers that aim to present high-quality information find they need complex rules, whether explicit or via accepted standards of writing and scholarship. Could she give specific examples of areas where we could simplify policy without sacrificing standards?
Yes, the premise of this question is absolutely correct. The analogy I often use is the newsroom. Anybody who’s curious and reasonably intelligent can be a good journalist, but you do need some orientation and guidance. Just like a newsroom couldn’t invite in 100 random people off the street and expect them to make an immediate high-quality contribution, neither can Wikipedia expect that.
So if we say that becoming an editor should be easy, really, that's a little delusional. And it’s exactly why people need easy instructional text and videos. The resources used by Wikipedia Ambassadors aren’t ideal in every respect, but they’re increasingly road-tested and optimized for the real-world instruction of new contributors. They're pretty good. In general, to the extent that we’re showing instructions as part of the user interface, we need to make them concise, and emphasize the must-read items instead of trying to cover every edge case.
I don't have specific examples of where policy should be simplified, but I do think it would be helpful for us to visibly embrace "be bold" again, as well as "break all rules." People get embarrassed when they make mistakes, and some of our policies seem almost impossibly intricate. So, I think one helpful thing we could do is to tell people that making mistakes is normal and okay.
We need to be able to experiment, to do stuff. We’re going to consult when when we think it’s helpful and necessary, … but we need to do tiny bits of experimentation ...
At this point, Gardner stepped back to take a big-picture view of how the community and the WMF should interface, saying that the Foundation isn't the expert in either the behavioural or the cultural aspects:
The community understands them better than we do, and will probably have better ideas about how to solve them. ... The Foundation will lead on technical initiatives such as the visual editor, and I think the editing community should lead on others. There are other initiatives where we’re partnering with the editing community – for example, the Foundation built the feedback dashboard to make new editors’ experiences visible to experienced editors, and to give experienced editors an easy mechanism for coaching the new people. We’ve started working with editors to create new page triage, a tool that will make page patrolling easier, and will offer options that support and encourage new editors as well as repelling vandalism and other bad edits.
While staking the Foundation's claim to the more technical side of the equation, Gardner doesn't shrink from providing advice on how we can fix the cultural problem.
If you look at new editors’ talk pages, they can be pretty depressing – they’re often an uninterrupted stream of warnings and criticisms. Experienced editors put those warnings there because they want to make Wikipedia better: their intent is good. But the overall effect, we know, is that the new editors get discouraged. They feel like they’re making mistakes, that they’re getting in trouble, people don’t want their help. And so they leave, and who can blame them? We can mitigate some of that by toning down the intimidation factor of the warnings: making them simpler and friendlier. We can also help by adding some praise and thanks into the mix. When the Foundation surveys current editors, they tell us one of the things they enjoy most about editing Wikipedia is when someone they respect tells them they’re doing a good job. Praise and thanks are powerful.
What, then, does Sue Gardner believe are our significant social challenges? She puts these questions in response:
How do we counter systemic bias when it comes to defining reliable sources and notability – that is, in a context where decisions are made by consensus, and in which many types of people are underrepresented, how do we ensure systemic bias doesn’t weaken and harm the quality of the decisions we collectively make? How can we better distinguish in the patrolling process between good faith new-user mistakes, and bad faith edits? What are the three most essential pieces of advice that every new editor should be given, and how do we make them front and centre, early in their experience with us? In general, how can we best equip new editors to edit well, as quickly and enjoyably as possible?
[Around the time of the Siegenthaler and Essjay controversies] Jimmy went to Wikimedia and said "quality … we need to do better", [and through the distortions of the ripple-effect in the projects] there was this moral panic created around quality … what Jimmy said gave a whole lot of people the license to be jerks. ... Folks are playing Wikipedia like it's a video game and their job is to kill vandals ... every now and again a nun or a tourist wanders in front of the AK-47 and gets murdered ...
Many people have complained that Wikipedia patrollers and administrators have become insular and taken on a bunker mentality, driving new contributors away. Do you agree, and if so, how can this attitude be combated without alienating the current core contributors?
I wouldn’t characterize it as bunker mentality at all. It’s just a system that’s currently optimized for combating bad edits, while being insufficiently concerned with the well-being of new editors who are, in good faith, trying to help the projects. That’s understandable, because it’s a lot easier to optimize for one thing (no bad edit should survive for very long) than for many things (good edits should be preserved and built upon, new editors should be welcomed and coached, etc.). So I don’t think it’s an attitudinal problem, but more an issue of focusing energy now on re-balancing to ensure our processes for patrolling edits, deleting content, etc. are also designed to be encouraging and supportive of new people.
If the presumably less important issue of controversial content merits outside study by consultants, why isn't the Foundation putting resources into having social scientists diagnose the problems of editor retention and offer suggestions to the community to reform its internal culture? Why aren't there Foundation usability experts recommending overhauls of dense and daunting policy and procedural pages and not just of technical aspects such as the interface?
As I said, we do want to work with community members to figure out how to reduce policy and instructional cruft: probably the first step in doing that, though, would be a convening of interested editors. The community department has been talking about doing that. I think it would be very difficult for most social scientists to help us with a highly specific problem like new editor retention, because it's a deep community issue, and not many social scientists understand very much about how Wikipedia works.
Having said that, Gardner pointed out that the Foundation tries to persuade social scientists who do understand Wikipedia to study it, and has done "lots of informal consultation on participation-related issues" with them.
We put it to Gardner that much of the supporting research she cited to the Wikimedia UK board was informal, small-scale or not entirely rigorous (such as the study based on a dubious assumption that any editor who was not a sockpuppet, vandal or spammer was editing in "good faith" – ignoring self-promoters and POV-pushers). Now that we know editor decline is a very serious problem, is a comprehensive and rigorous research initiative being planned to analyze the phenomenon?
No. The Foundation isn’t a research organization, and programs like the Summer of research aren’t intended to conduct comprehensive, authoritative studies, but to produce actionable insights that guide and support our work. That’s why we tend to focus on small, fast, tightly defined research projects that will answer simple questions, such as "Which warning templates deter new editors the least?" and "Which help avenues are most used by new editors?"
How can a culture that has a heavy status quo bias be changed? How can the community be persuaded to become less risk-averse?
My hope is that the community will become less risk-averse as the Foundation makes successful, useful interventions. I believe the Vector usability improvements are generally seen as successful, although they of course haven't gone far enough yet. Wikilove is a small feature, but it’s been adopted by 13 Wikipedia language-versions, plus Commons. The article feedback tool is on the English Wikipedia and is currently being used in seven other projects. The new-editor feedback dashboard is live on the English and Dutch Wikipedias. New warning templates are being tested on the English and Portuguese Wikipedias. And the first opt-in user-facing prototype of the visual editor will be available within a few weeks. My hope is all this will create a virtuous circle: support for openness will begin to increase openness, which will begin to increase new editor retention, which will begin to relieve the workload of experienced editors, which will enable everyone to relax a little and allow for more experimentation and playfulness.
Regaining our sense of openness will be hard work: it flies in the face of some of our strongest and least healthy instincts as human beings. People find it difficult to assume good faith and to devolve power. We naturally put up walls and our brains fall into us-versus-them patterns. That’s normal. But we need to resist it. The Wikimedia projects are a triumph of human achievement, and they’re built on a belief that human beings are generally well-intentioned and want to help. We need to remember that and to behave consistently with it.
Wikimedia Incubator has released its 2011 end-of-year report, its first ever. The Incubator hosts test versions of new Wikimedia candidates before they are moved to their own subdomain, and the page details the project's yearly activities:
As we begin a new year, the WikiProject Report continues its tradition of revisiting the projects we featured in the Signpost last year. We highlighted 48 projects and published three special issues in 2011, setting a record of 51 WikiProject Reports in one year. The only thing that could stop our four Report writers was a combined earthquake, tsunami, and nuclear meltdown in Japan which postponed our 14 March interview with WikiProject Japan. Our 2012 New Year's resolution is to fill all 52 weeks of the year with insightful interviews, news, and specials featuring Wikipedia's diverse community of WikiProjects.
This past year was dominated by academic and scientific pursuits. WikiProject Schools showed us how school rivalry, an administration's puffery, and outright vandalism by the student body can make articles about primary and secondary schools a contentious place to dedicate one's time. WikiProject Academic Journals suggested that simply finding something to write can be a major hurdle when covering notable academic journals. The assortment of academic and scientific topics covered in 2011 include mathematics, computer science, elements, physics, the solar system, philosophy, feminism, economics, medicine, and the taxonomic pursuits of WikiProject Tree of Life.
We also traveled the world in 2011. In addition to the aforementioned WikiProject Japan, the report visited Russia, New Zealand, Croatia, and revisited WikiProject India in time for their 2011 WikiConference. We also featured the politics of Australia and visited a few locations in the United States, including the country's umbrella project, the connected people of the District of Columbia, and the busy folks covering the state of Oregon.
The United Kingdom saw a considerable amount of coverage in 2011. Geographic-specific projects ranged from the county of Somerset to the transit system in London to the web of railways and waterways connecting Britain. Nearly all of the sports covered in the Report originated in the UK, from cricket to rugby union to tennis.
In terms of history, the project caught up with projects covering the World's Oldest People and the historic structures in the United States included in the National Register of Historic Places. We also paid our yearly visit to the folks at WikiProject Military History, who shared their journalistic skills when asked about the monthly newsletter, the Bugle.
In addition to the UK's transportation systems mentioned above, the Report interviewed other transportation-related projects covering aircraft, spaceflight, automobiles, and Formula One racing.
We saw a variety of arts and entertainment projects. Music was represented by WikiProject Classical Music and WikiProject Albums. Meanwhile, WikiProject Animation and WikiProject Comics showed us the artistic side of Wikipedia. In contrast to our heavy coverage of literature in 2010, the only literary project covered in 2011 focused on the Warriors series. For a fun change of pace, we played a few rounds with WikiProject Board and Table Games. Hunters and collectors shared WikiProject Firearms with us.
In 2011, we interviewed six specialty projects that work behind the scenes on Wikipedia. Our interview with WikiProject Spam was our most viewed article ever. The WikiProject Council is the "WikiProject WikiProject" helping new projects get off the ground and providing organization to the massive WikiProject community. WikiProject Wikify has been improving Wikipedia through its backlog elimination drives. WikiProject Disambiguation helps readers find what they're looking for by making sure disambiguation pages and hatnotes point to the right places. WikiProject Articles for Creation enables anonymous editors to contribute new articles through a review process. WikiProject Wikipedia-Books focuses on collecting worthwhile articles and printing them for offline use.
In addition to our yearly recap, the Report published special editions offering tips on reviving WikiProjects and listing some excellent examples of WikiProject iconography. We hope to provide more special reports this year and can use your feedback to determine what gets covered. If there is a project you would like to see interviewed or a WikiProject-related topic you'd like to see explored in depth, just drop us a line at the Signpost's WikiProject Desk.
Next week, we'll jazz things up. Until then, improvise with the material in the archive.
Reader comments
Over the past year, 1,053 pieces of featured content were promoted. The most active of the featured content programs was featured article candidates, which promoted an average of 30 articles a month. This was followed by featured picture candidates (25 a month). Coming in third was featured list candidates (20 a month). Featured sound candidates, although the most active in April, died in mid-August; as such, it promoted an average of 11 sounds a month. Featured topic and featured portal candidates were a bit sluggish, each promoting fewer than 20 items over the year.
Despite this fairly large increase in the total amount of featured content, systemic bias continues, specifically a focus on the anglosphere. At featured article candidates, common topics include male political figures, ships, television episodes, and songs, generally from the US, Britain, and Australia. Featured list candidates has been dominated by discographies and sports rosters, also predominantly from the US and Britain. Featured picture candidates has seen many animal species, works of art by European and American artists, and similar subjects. Although there are some exceptions, the systemic bias pervades every featured content process. For comparison, numerous non-anglosphere topics, even on important figures such as Prime Ministers, remain stubs.
Aside from the promotion of featured content, another key development this year was the creation of today's featured list, where featured lists are shown on the main page, currently once a week on Mondays. The proposal was implemented 13 June after a formal proposal in early June. Several years in the making, this new section of the main page has shown 29 featured lists thus far, starting with List of signs and symptoms of diving disorders.
What does the future hold? Will the number of successful nominations continue to increase, or will other projects join featured sounds? Will systemic bias continue to run rampant? Will featured topics, portals, and sounds ever reach the main page? Will Jenna Jameson? Only time will tell.
| Articles | Lists | Sounds | Topics | Portals | Pictures | Total | |
| January | 42 | 16 | 4 | 2 | 0 | 32 | 96 |
| February | 29 | 28 | 15 | 1 | 2 | 25 | 100 |
| March | 33 | 21 | 24 | 0 | 0 | 40 | 118 |
| April | 31 | 17 | 54 | 1 | 1 | 29 | 133 |
| May | 37 | 21 | 24 | 1 | 0 | 18 | 101 |
| June | 31 | 21 | 7 | 1 | 1 | 20 | 81 |
| July | 36 | 29 | 6 | 2 | 1 | 23 | 97 |
| August | 32 | 19 | 2 | 1 | 1 | 31 | 86 |
| September | 22 | 22 | 0 | 2 | 0 | 29 | 75 |
| October | 25 | 23 | 0 | 4 | 2 | 14 | 68 |
| November | 13 | 13 | 0 | 1 | 0 | 13 | 40 |
| December | 24 | 13 | 0 | 1 | 0 | 20 | 58 |
| Total | 355 | 243 | 136 | 17 | 8 | 294 | 1053 |
And now, the Signpost is proud to present the last new featured content of 2011.
.jpg)
No featured articles were promoted this week.
Three featured lists were promoted this week.
Six featured pictures were promoted this week.
The Arbitration Committee opened one new case this week, bringing the number of open cases to a total of four. As a result of the recent election, four new arbitrators took their seats for the first time.
On January 1, 2012, four new editors began their terms as members of the Arbitration Committee. The new arbitrators are Courcelles (Audit Subcommittee), Hersfold (former arbitrator and a former clerk), AGK (former Chair of the Mediation Committee), and SilkTork, all of whom were elected to serve for two-year terms. New members who did not already have oversight and checkuser permissions were granted such permissions on the start of their terms. Four sitting arbitrators were returned at the election: Risker, Roger Davies, and Kirill Lokshin were elected for two-year terms; Jclemens will serve for a one-year term.
With the entry of new arbitrators, assignments to internal sub-committees have been shifted.
The three arbitrator members of the Audit Subcommittee (AUSC) will be incoming member AGK, and current arbitrators David Fuchs and Jclemens. With the promotion of community representatives Courcelles and AGK of the AUSC into the full ArbCom, the only at-large community member of the subcommittee is Keegan. Arbitrator PhilKnight said that the committee is discussing the two empty seats on AUSC and a "formal announcement will follow shortly". The AUSC deals with scrutiny and review of oversight and checkuser functions.
The Ban Appeals Subcommittee (BASC) will consist of Elen of the Roads, PhilKnight, and new arbitrator Hersfold.
The committee opened this case after a record number of statements were posted. The case concerns the actions of several administrators and users revolving around a perceived instance of incivility by Malleus Fatuorum and several consequent blocks and unblocks. Several arbitrators recused themselves before the start of the evidence phase.
With a draft target of January 12 to complete both evidence and workshop phases, decision drafters Risker and Hersfold have to contend with at least 23 submissions. So far, this is a total of about 140 diffs and a great deal of analysis to comb through.
The case involves accusations of "disruptive editing" in debates over the retention and usage of images of Muhammad. The evidence target has been set for January 11 by drafter AGK. 14 editors have since posted evidence submissions, which have included concerns about specific users involved in the debates.
Drafter AGK also posted questions to involved parties regarding issues such as image use and the inclusion of secondary sources.
The evidence and workshop phases are now coming to a close. A proposed decision is due by January 16 and will be drafted by Roger Davies, Jclemens, and Elen of the Roads. The case involves the appeal of a ban on TimidGuy imposed by Jimmy Wales on alleged POV and conflict-of-interest issues.
Several arbitrators posted proposed principles, findings of fact, and analysis of evidence in the case workshop. Several proposed principles deal with the process of imposing a ban and the illegitimacy of "secret bans" (which is a disputed element of the case).
Now in its ninth week, the case is in a late stage of the workshopping and drafting of a final decision. Discussion by arbitrators has centered on proposals by several committee members. No date for a final decision has been posted.
