Wikipedia:Avoid instruction creep

"WP:CREEP" redirects here. For creep in articles, see WP:ACREEP. For creep of templates, see WP:TCREEP.

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.

Problem

Like kudzu vines, instructions can grow much too fast.

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.

Prevention

Principles. Keep policies and guidelines to the point. It is usually better for a policy or guideline to be too lax than too strict. Detailed policies can lead to wikilawyering, impairing the consensus-building process. If you just think that you have good advice for Wikipedians, consider adding it to an essay.

Editing. Do not make substantive additions to a policy or guideline unless the addition solves a real and significant problem, not just a hypothetical issue. Before publishing your edit, review the text for potential unintended consequences and re-write as appropriate.

Fixing

Further information: Wikipedia:Policies and guidelines § Conflicts between advice pages

An issue perhaps better left to editor discretion (though the handwash is a thoughtful touch)

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 a policy.

If you feel that a change is needed, either make your case 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 consider changes.

Not every instruction is creep

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.

Linking to this page

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 are 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 would 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.

See also

Essays against instruction creep

• Wikipedia:Asshole John rule
• Wikipedia:Avoid writing redundant essays
• Wikipedia:Don't stuff beans up your nose
• Wikipedia:If MOS doesn't need a rule on something, then it needs to not have a rule on that thing (WP:MOSBLOAT)
• 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
• Address problems without creating new specialized rules

Essays encouraging redundancy

• Wikipedia:Abundance and redundancy
• Wikipedia:Redundancy is good

Wikipedia articles

• Criticism of Wikipedia § Excessive rule-making
• Feature creep
• Instruction creep
• Parkinson's law
• Red tape
• Scope creep

Templates

• Template:Simple help page (edit notice)

External links

• Instruction creep at Meta-Wiki