Competence is required

From Meta, a Wikimedia project coordination wiki
(English) This is an essay. It expresses the opinions and ideas of some Wikimedians but may not have wide support. This is not policy on Meta, but it may be a policy or guideline on other Wikimedia projects. Feel free to update this page as needed, or use the discussion page to propose major changes.

Wikimedia is a big place, with many editors, all with their own opinions on how to do things. It seems surprising that we are able to work together functionally, but somehow this is what usually happens.

One of the fundamental principles that facilitates this is assume good faith. It is good advice, reminding us that, when we disagree, everyone involved is (usually) trying to do what they think is best. Sure, we get people who intentionally damage Wikimedia projects as well, but they're usually quite easy to deal with. They can be blocked from editing, as needed, with little fuss and generally no controversy.

Where we often see big controversies, though, is with editors who are unintentionally and often unknowingly disruptive while trying to help. This is where we sometimes see an unintended side effect of our (generally quite useful) notion of assuming good faith. Many editors have focused so much on this tenet that they have come to believe that good faith is all that is required to be a useful contributor. Sadly, this is not the case at all. Competence is required as well. A mess created in a sincere effort to help is still a mess.

Clearly, every editor is incompetent when doing some types of edits in certain subject areas, so it is important to know or discover your limitations.

Compared to good faith[edit]

Assuming that people are trying to help seems trivial—but if someone is unable to help or is sometimes helpful but at other times disruptive, their edits may cause a net loss to the project. The proverbial bull in a china shop might have good intentions, but he's clearly bad for business. We always must value the project as a whole more than we value the contributions of any individual editor.

So, the next time someone posts on a noticeboard saying "Editor Example is causing problems—here are the diffs to demonstrate this", or "Disruptive editor Example is asking for an unblock", think twice before just "Assuming good faith". The person making the complaint is probably already assuming good faith, and they're concerned about a lack of competence, not a lack of good faith. Both competence and good faith are required to edit usefully. If an editor has already demonstrated incompetence that causes disruption, no amount of good faith can fix the problem resulting from the editor's lack of competence.

Some common types[edit]

Most of us were pretty incompetent at editing Wikimedia projects when we started. We might not have understood wikicode, we might not have signed our posts, or we may not have fully appreciated exactly which sources are reliable. The great thing about this situation is that it's easily fixable. Help the newbies understand what we do here, and soon they'll be making themselves useful. Do not bite the newcomers.
The best good will is for naught if a basic understanding of the facts, their mainstream interpretation, and their cultural context are lacking.
Some people just can't function well in this particular collaborative environment. We can't change these projects to suit them, so if they're unable to change themselves, they'll need to be shown the door politely but firmly.
Some behavioral issues and personality traits may be correlated with the inability to collaborate civilly in an environment in which such collaboration is essential. The community assesses editors solely on the basis of their actions within the project. Blocking an editor who has demonstrated that they are unable to participate in the project is not discrimination on the basis of disability (if one exists), even if that disability contributes to their failure to participate.
Immature and/or childish/young
Some editors are too immature to participate in Wikimedia projects. This can include most children, some teens, and few adults. Editors that are too immature and demonstrate childish behavior, including silly hoax pages, long pointless redirects, or overly disruptive editing, will be asked to leave and come back when they are much older. These editors should be cut some slack when they return, and either show that they are here to improve the project, or be blocked for a much longer period of time, possibly indefinitely.
Some editors hold personal opinions so strongly that they cannot edit neutrally and collaboratively with other editors. If this continues to be disruptive and a user is unable to step away from topics where they have strong biases, a topic ban is generally appropriate. Try this first before going for a site ban, because some people can make valuable contributions in places other than their pet topic. It is often very difficult to see one's own biased editing, though it is easy to see that of others.
Language difficulty
If someone's native language is not that of the project they are contributing, consider trying to encourage them to edit a project in their own language (or a global project). Those projects need help from editors too.
There is also the problem of editors whose command of a language is sufficient for colloquial use, and who can make themselves understood on talk pages and in other informal circumstances, but who do not write sufficiently well in that language that their contributions to articles are acceptable. These editors could also be encouraged to edit the project of their native language or other languages they are more conversant with, and to limit their contributions on articles to edits that do not require writing in any languages they do not know or to work with native speakers to improve their contributions.
Editing beyond one's means
Some people aren't able to grasp the subtleties of how a project works. They may still be able to do some easy jobs, but they'll probably run into trouble if they try biting off too much. Encourage them to keep to the simple things, or suggest a break if they're getting frustrated about their edits getting reverted or getting into contentious interactions with other editors.
Lack of technical expertise
Insufficient technical knowledge is not usually a problem, unless when adding, deleting, or changing technical content. Not everyone needs the same skill set—and as long as people operate only where they're capable, differences in skill sets are not a problem.
Some people get so upset over a past dispute that they look at everything through a lens of "So-and-so is a bad editor and is out to get me." Taken to extremes, this easily becomes quite disruptive. An enforced parole of "don't interact with this other editor" may be something to try in these cases.
Non-incremental changes
Some enthusiastic new editors combine multiple diverse article changes into one large edit or rapid series of edits. If reverted, at the talk page they start talking about everything at once, which renders methodical progress impossible. Try asking these editors to present their desired changes, their reasoning, and their reliable sources for just one paragraph at a time, or for just one paragraph per subsection heading. Those editors who are capable of collaboration—a necessary skill to edit any Wikimedia project—will understand and appreciate the advice. Those who continue to talk about everything at once probably lack the required ability to collaborate.

What "Competence is required" does not mean[edit]

  • It does not mean "come down hard like a ton of bricks on someone as soon as they make a mistake." Wikimedia wikis have a learning curve. We should cut editors (particularly new ones) some slack, and help them understand how to edit competently. Mistakes are an inevitable part of the wiki process.
  • It does not mean perfection is required. Articles can be improved in small steps, rather than being made perfect in one fell swoop. Small improvements are our bread and butter.
  • It does not mean we should ignore people and not try to help improve their competence.
  • It does not mean we should label people as incompetent. For example, we do not say "You are incompetent because you don't know anything about the subject of this article."
  • It does not mean that civility does not apply when talking to incompetent people. Rude and uncivil comments may discourage the motivation of the targeted editor, raising their psychological barrier against recognizing their own mistakes or seeking to improve their skills.
  • Finally, it does not mean we will give any good-faith editor an infinite number of opportunities to make themselves useful. If, after an appropriate amount of time and coaching, someone still isn't competent, don't make a heroic effort to defend them. Cut them loose, and focus your mentoring efforts on a better candidate.

Local and global competence[edit]

Most everyone has a specific circle of competence, an area or project in which they possess the knowledge and expertise to contribute effectively. At the same time, each person necessarily has areas which fall outside of that circle. Therefore, having a local lack of competence may not equate to a person being globally incompetent in a way that would prevent them from contributing to the project at all. Often, the best editors are not necessarily experts in everything, but rather are adept at recognizing areas where they do and do not have the required expertise, and focusing on those where they may be the most productive. Concentrating on local competence, rather than global incompetence, may help to identify ways in which problematic editors can become productive ones, by focusing on individual strengths rather than individual weaknesses.

The bottom line[edit]

There can be a fine line between mischief and incompetence. It doesn't help to spend too much time trying to figure out the reason for the disruption, because many trolls do their trolling by feigning incompetence. It is difficult to distinguish between fake or real incompetence, but disruption is disruption and needs to be prevented. Give editors a few chances, and some good advice, certainly—but if these things don't lead to reasonably competent editing within a reasonable time frame, it's best to wash your hands of the situation. Wikimedia projects, for better or worse, are just not the best fit for everybody.

This essay...[edit]

... is often criticized for being uncivil. The most sensible defense to such criticism is that the primary purpose of this essay is not to present it to competence-lacking editors to let them know they are incompetent. After all, as argued here, they are either incapable of recognizing their own incompetence (see Dunning–Kruger effect) or are incapable of changing their behavior. Rather, the purpose of this essay is to inform discussion amongst other editors of how to deal with issues arising from incompetence. So, if this essay seems to apply to an editor, it is usually not appropriate to tell them so.