WikipediaProduct Thinking6 min readWhy the edit button is still there
An open door, a revert, and a rule about sources doing the work.
- The surface
- Reading an article, clicking edit, the citation needed tag, the talk page, and the revision history.
- What the user wants
- I noticed something wrong or missing and I want to fix it without joining anything.
Edit sits on every page
An edit control appears on articles and on individual sections, and editing is possible without an account on most pages.
Lowest possible barrier to contribution
Most people who could improve a page will never sign up to do it, so requiring an account loses the majority of potential fixes. Section-level editing also shrinks the perceived task from rewriting an article to fixing a paragraph. The scope of the ask determines who says yes.
Citation needed
Unsupported claims are tagged inline with a visible marker rather than deleted outright.
Naming the gap instead of closing it
A tag is simultaneously a warning to the reader and a precise, small task for a contributor. It converts a vague sense that an article is weak into a specific job someone can do in five minutes. Deleting the claim would have lost the information and the invitation.
Verifiability, not truth
The core content rule asks whether a claim is supported by a reliable published source, not whether editors believe it is true.
Making disputes resolvable
Arguments about truth between strangers do not terminate. Reframing the question as whether a source exists gives every dispute a checkable answer and moves the authority outside the argument. This single rule is why the project scales past the point where people agree.
Reverting is cheaper than vandalising
Full revision history is public and any version can be restored in one action, with tools and bots that surface suspicious edits.
Asymmetric repair cost
An open system survives not by preventing bad edits but by making them trivial to undo. When repair costs less than damage, defenders win on effort alone. The history also means nothing is ever lost, which lowers the risk of letting anyone edit in the first place.
The talk page
Every article has a separate discussion page where disagreements are argued out, kept off the article itself.
Separating the artifact from the argument
If disputes lived in the article, readers would see the fight instead of the content. A parallel space lets conflict happen without degrading the product. It also creates a record of why the article says what it says, which stops the same argument recurring forever.
No reward mechanics
There are no points, streaks or public leaderboards on contribution, and editor recognition lives in community processes rather than in the reading interface.
Protecting intrinsic motivation
Adding extrinsic rewards to work people do out of interest can crowd out the original motivation and shift behaviour toward whatever is scored. Wikipedia's contributors are there because the subject matters to them. The restraint is a deliberate design choice and an unusual one.
Why the door can stay unlocked
What not to copy
- The editing experience for a newcomer is still hostile: markup, policy shorthand and the real possibility of having a first edit reverted by a bot within a minute.
- The editor base is demographically narrow, and coverage reflects that, with well documented gaps in biographies of women and in non-English topics.
- Verifiability inherits the biases of what got published, so subjects that established sources ignored stay under-covered no matter how many editors care.
- Entrenched editors accumulate procedural power, and policy fluency becomes a way to win arguments regardless of the substance.
The takeaway
In an open system, make repair cheaper than damage and give every dispute a checkable question, then you can leave the door unlocked.
Finished the teardown? Bank it and the day counts toward your run.
Where the principles come from
- Governing the Commons, Elinor Ostrom
- Here Comes Everybody, Clay Shirky
- Drive (intrinsic motivation and crowding out), Daniel Pink
- The Cathedral and the Bazaar, Eric S. Raymond
Written from public behaviour of the product, not from inside it. Interfaces change often, so treat the flow described here as of the time of writing and check the live product before quoting it.