Wikipedia:Avoid instruction creep

From Wikipedia, the free encyclopedia

This page is considered a guideline on Wikipedia. It is generally accepted among editors and is considered a standard that all users should follow. However, it is not set in stone and should be treated with common sense and the occasional exception. When editing this page, please ensure that your revision reflects consensus. When in doubt, discuss first on the talk page.

Shortcut: WP:CREEP

The status of this policy or guideline is disputed. Please see the relevant discussion on the talk page.

Wikipedia Guidelines
Content
Autobiography Don't copy sources Disambiguation Hoaxes Patent nonsense
Classification
Subpages Cats, lists, boxes Lists Categories
Editing
Be Bold Build the web Edit summary Article size
Discussion
Talk page guidelines Sign on talk pages Build consensus
Behavior
Etiquette Profanity Don't disrupt Wikipedia to illustrate a point Don't bite the newcomers User page
Style
Manual of style See also policies

Instruction creep occurs when instructions increase in size over time until they are unmanageable. It is an insidious disease, originating from ignorance of the KISS principle and resulting in overly complex procedures that are often misunderstood, followed with great irritation or ignored.

The fundamental fallacy of instruction creep is thinking that people read instructions. What's more, many new rules arise with the deliberate intent to control others via fiat without an adequate attempt for consensus or collaboration. This tends to antagonize others even when it appears to the instigator that he's acting with proper intent.

Instruction creep is common in complex organizations where rules and guidelines are created by changing groups of people over extended periods of time.

[edit] Instruction creep on Wikipedia

Instruction creep begins when a well-meaning user thinks "This page would be better if everyone was supposed to do this" and adds more requirements.

Procedures are popular to suggest but unpopular to follow, due to the effort to find, read, learn and actually follow the complex procedures.

Page instructions should be pruned regularly. Gratuitous requirements should be removed as soon as they are added. All new policies should be regarded as instruction creep until firmly proven otherwise.

[edit] See also

Creeping featurism — when a computer program ends up doing more and more.
Functionality creep — when a physical document or procedure ends up serving unexpected or unplanned purposes.
Red tape
Bureaucracy
Iron law of oligarchy - on inevitable instruction creep