| Revision as of 14:28, 7 August 2006 editCedrus-Libani (talk | contribs)5,757 edits it's not a guideline it's an essay← Previous edit | Revision as of 10:39, 9 September 2006 edit undoRadiant! (talk | contribs)36,918 edits It is a longstanding guideline to avoid ins.creep, as a corollary to policy WP:NOT a bureaucracyNext edit → | ||
| Line 1: | Line 1: | ||
| {{ |
{{guideline|]}} | ||
| {{Guideline list}} | {{Guideline list}} | ||
Revision as of 10:39, 9 September 2006
 | 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 bureaucracies also arise with the deliberate intent, as 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.
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
Source
This page was inspired by the meta-wiki concept: m:instruction creep.