This is a draft of a potential Signpost article, and should not be interpreted as a finished piece. Its content is subject to review by the editorial team and ultimately by JPxG, the editor in chief. Please do not link to this draft as it is unfinished and the URL will change upon publication. If you would like to contribute and are familiar with the requirements of a Signpost article, feel free to be bold in making improvements! · next-next issue draft
| |||||
The rules of Wikipedia clearly state that the platform is not a battleground. The policy expresses this plainly, almost optimistically, as if reminding us of our better selves: we are here to work together, not to argue. However, anyone who has been editing the encyclopedia for a while knows that conflict is an unavoidable part of the process. Edits are challenged, sources are debated, and phrasing is negotiated. On the surface, these are just routine editorial processes, but they can feel surprisingly personal to those involved. Many of us do not separate our writing from our identity as much as we believe. When someone changes our words, it can feel like an attack on our judgment, expertise, or understanding: this is where tension starts emerging.
People take up editing certain articles because they care about a topic, a field, a detail in history, or a cultural moment—something they want to help document and explain. However, enthusiasm can easily turn into attachment. When we care about something, we want it to be accurately represented, or at least in a way that feels right to us. So, when another editor disagrees, criticism can feel threatening rather than welcoming. The disagreement itself isn't the problem; it's actually crucial for improving articles. The real issue is how quickly disagreement can shift from a discussion about content to a heated competition over who is right.
This dynamic explains a lot of Wikipedia's internal issues. Once editors focus on proving they are right, instead of working together for further accuracy, the project's purpose is lost. Discussions shift away from content and become about positions; reverts turn into symbols, and talk pages transform into arenas. The quality of the article—something we all claim to care about—becomes secondary to the desire not to back down. This is where conflict does real harm: not just to relationships on the platform, but to the product we are supposed to build together.
The consequences are significant. New editors, including experts who could enhance the encyclopedia, often leave over just one negative encounter. They perceive intensity as hostility, or gatekeeping, or a sign that their contributions are not welcome. Meanwhile, long-time editors can become weary, defensive, or hardened due to repeated arguments. Communication becomes sharper, patience shorter, and collaboration more strained. A few tough interactions contribute to a culture that quietly pushes people away. Once this culture sets in, reversing it becomes much harder than stopping it from forming in the first place.
If we genuinely believe that Wikipedia is not a battleground, then the answer is not to avoid disagreement, but to change the way we handle it. We can explain reverts, instead of just making them. We can ask for reasoning, instead of jumping to conclusions. We can take a moment before responding to a pointed message. We can strive, at the very least, to read each other with understanding. These are simple habits, almost trivial on their own, but culture is built from habits that are repeated often enough to become the norm (for better or for worse).
Wikipedia succeeds because it relies on collaboration. But collaboration only works when everyone feels respected, heard, and treated as partners, instead of opponents. If we want an encyclopedia that reflects the best of collective knowledge, we must resist the urge to turn every disagreement into a contest. We have to remember, especially in moments of frustration, that, nine-and-a-half times out of ten, the person on the other end did not come here to fight either.
Discuss this story