This is an explanatory essay about the procedural policy regarding policies and guidelines.
|This page in a nutshell: When editing guidance, keep in mind the risk of increasingly detailed instructions resulting in bloated pages that new editors find intimidating and experienced editors ignore.|
Avoid instruction creep to keep Wikipedia policy and guideline pages easy to understand. The longer, more detailed, and more complicated you make the instructions, the less likely anyone is to read or follow whatever you write.
Nobody reads the directions from beginning to end. And increasing numbers of directions result, over time, in decreasing chances that any particular rule will be read at all, much less understood and followed. Spread out over many pages, excessive direction causes guidance to become less coherent and increasingly drift from actual community consensus. Further, having too many rules may drive away editors. To avoid these outcomes, keep Wikipedia space pages broad in scope, not covering every minute aspect of their subject matter.
Keeping policies and guidelines to the point is the most effective way of preserving transparency. Substantive additions to policy should generally be rejected unless:
- There is a real problem that needs solving, not just a hypothetical or perceived problem.
- The proposal, if implemented, is likely to make a real, positive difference.
- All implied requirements have a clear consensus.
Ensure that additions are placed in a logical context, and do not obscure the meaning of the surrounding text.
It is usually better for a policy or guideline to be too lax than too strict. Content not clearly prohibited by any policy is still subject to editor discretion. Consensus-building on article talk pages can be undermined by an over-strict policy, as an editor who wants to follow it literally can claim that the issue is already decided.
If you just think that you have good advice for Wikipedians, consider adding it to an essay.
Since things often "creep in" without scrutiny, even longstanding instructions should be subject to review. The amount of time an instruction has been present does not strengthen consensus behind it, though one should be wary whenever removing a longstanding part of policy.
If an instruction does not make sense or does not seem to describe community consensus, check the page history to see when it was added and how it may have changed over time. Then check the talk page and talk archive, to see whether there was any related discussion.
If you decide to change the instructions, either explain your change on the talk page or boldly make your changes, giving your rationale in the edit summary. If you meet with disagreement, discuss the matter further. Those who oppose complete removal may still be willing to compromise on changes.
Linking to this pageEdit
Additional instruction can be helpful when it succinctly states community consensus regarding a significant point, but it is harmful when the point is trivial, redundant, or unclear.
If someone cited this page to explain their view, they mean that they think the rule is at least unnecessary and unimportant, if not downright harmful by creating a lot of burdensome bureaucracy or a rule that will be ignored because it prevents editors from writing good articles. It's rare that what Wikipedia really needs is yet another rule.
If you cite this page to support your opposition to "creepy" rules, remember that some editors really need to have this concept spelled out for them. They're usually dealing with a problem that seems significant to them, and they believe that writing down a rule somewhere will somehow solve their problem, even though 99.9% of editors will never even read the rule they're proposing, much less follow it. So don't say "Oppose per CREEP"; instead, say "Oppose the creation of this unnecessary and complicated rule for a very uncommon situation that could just as easily be solved by editors using their best judgment to apply the relevant existing rules as explained at WP:CRYPTIC" – or whatever the facts of the case at hand are.
Policies, essays, and guidelines
- Wikipedia:Asshole John rule
- Wikipedia:Avoid writing redundant essays
- Wikipedia:Don't stuff beans up your nose
- Wikipedia:Notability (mailboxes) (humor)
- Wikipedia:Overlink crisis
- Wikipedia:Practical process
- Wikipedia:Requests for process
- Wikipedia:The rules are principles
- Wikipedia:Silence does not imply consent when drafting new policies
- Wikipedia:Too much detail
Essays encouraging redundancy
- Criticism of Wikipedia#Excessive rule-making
- Feature creep
- Instruction creep
- Iron law of oligarchy
- Parkinson's law
- Red tape
- Scope creep
- Template:Simple help page (edit notice)