This MedLibrary.org supplementary page on Wikipedia:CREEP is provided directly from the open source Wikipedia as a service to our readers. Please see the note below on authorship of this content, as well as the Wikipedia usage guidelines. To search for other content from our encyclopedia supplement, please use the form below:
Related Sponsors
 |
While this essay is not a policy or guideline itself, it is intended to supplement Wikipedia is not a bureaucracy. Please update the page as needed, or discuss it on the talk page. |
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 bureaucracies also arise with the deliberate intent to be alternatives to regulations; this is almost always noticed by the other side, and tends to antagonize. It tends to antagonize 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.
Contents |
Instruction creep on Wikipedia
Instruction creep begins when a well-meaning user thinks "This page would be better if everyone were 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.
Avoiding instruction creep
For proposed new instructions, instruction creep can be avoided if all of the following hold:
- There is a good indication of an actual problem (as opposed to a hypothetical or a perceived problem)
- The proposed instructions truly solve this problem (as opposed to treating symptoms or making symbolic gestures)
- The instructions have little or no undesirable side effects (such as false positives, overcomplexity, or unnecessary prohibitions)
See also
- Wikipedia:Practical process
- Wikipedia:Requests for process
- Bureaucracy
- 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.
- Iron law of oligarchy
- Parkinson's law
- Red tape
- Wikipedia:If it ain't broke, don't fix it
Source
This page was inspired by the meta-wiki concept: m:instruction creep.
Wikipedia content modification information:
- This page was last modified on 8 July 2008, at 23:21.
Wikipedia Authorship and Review
Wikipedia content provided here is not reviewed directly by MedLibrary.org. Wikipedia content is authored by an open community of volunteers and is not produced by or in any way affiliated with MedLibrary.org.
Wikipedia Usage Guidelines
This article is licensed under the GNU Free Documentation License. It uses material from the Wikipedia article on "Wikipedia:CREEP".
The URL for this specific entry is:
All Wikipedia text is available under the terms of the GNU Free Documentation License. (See Copyrights for details). Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc.