This is an old revision of this page, as edited by 71.230.253.48 (talk) at 03:47, 18 October 2006 (minor spelling fix: "consesnus" -> "consensus"). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 03:47, 18 October 2006 by 71.230.253.48 (talk) (minor spelling fix: "consesnus" -> "consensus")(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff) | This page documents an English Misplaced Pages ]. Editors should generally follow it, though exceptions may apply. Substantive edits to this page should reflect consensus. When in doubt, discuss first on this guideline's talk page. |
]
| Misplaced Pages guidelines | |||
|---|---|---|---|
| Behavioral | |||
|
|||
| Content | |||
| Editing | |||
|
|||
| Style | |||
| Deletion | |||
| Project content | |||
| Other | |||
| Search | |||
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.
Instruction creep on Misplaced Pages
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.
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
Source
This page was inspired by the meta-wiki concept: m:instruction creep.