180:
258:
77:
325:
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.
147:
324:
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
355:
265:
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.
387:
198:, 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
397:
305:
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.
313:
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
155:
When editing guidance, keep in mind the risk that increasingly detailed instructions will result in bloated pages that new editors find intimidating and experienced editors ignore.
171:
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.
240:
539:
350:
345:
544:
534:
413:
382:
218:
252:
168:
97:
89:
361:
194:
from beginning to end. And increasing numbers of directions result, over time, in decreasing chances that any particular rule will be
377:
239:. Do not make substantive additions to a policy or guideline unless the addition solves a real and significant problem, not just a
321:
because it prevents editors from writing good articles. It's rare that what
Knowledge (XXG) really needs is yet another rule.
418:
372:
340:
203:
85:
318:
392:
367:
38:
490:
226:
243:. Before publishing your edit, review the text for potential unintended consequences and re-write as appropriate.
222:
467:
430:
96:
This page provides additional information about concepts in the page(s) it supplements. This page is not one of
221:. It is usually better for a policy or guideline to be too lax than too strict. Detailed policies can lead to
274:
101:
356:
Knowledge (XXG):If MOS doesn't need a rule on something, then it needs to not have a rule on that thing
288:
179:
111:
314:
270:
64:
60:
277:
the matter further. Those who oppose complete removal may still be willing to consider changes.
230:
229:
process. If you just think that you have good advice for
Wikipedians, consider adding it to an
440:
163:
273:
make your changes, giving your rationale in the edit summary. If you meet with disagreement,
261:
An issue perhaps better left to editor discretion (though the handwash is a thoughtful touch)
195:
519:
445:
199:
17:
528:
435:
257:
455:
206:
pages broad in scope, not covering every minute aspect of their subject matter.
269:
If you feel that a change is needed, either make your case on the talk page or
495:
450:
388:
Knowledge (XXG):Silence does not imply consent when drafting new policies
253:
Knowledge (XXG):Policies and guidelines § Conflicts between advice pages
256:
184:
141:
71:
398:
Address problems without creating new specialized rules
296:
126:
119:
42:
487:
Calcification in rule-making drives away new editors.
59:"WP:CREEP" redirects here. For creep in articles, see
431:
Criticism of
Knowledge (XXG) § Excessive rule-making
90:
procedural policy regarding policies and guidelines
491:"Study: Knowledge (XXG) is driving away newcomers"
351:Knowledge (XXG):Don't stuff beans up your nose
346:Knowledge (XXG):Avoid writing redundant essays
8:
187:vines, instructions can grow much too fast.
26:
414:Knowledge (XXG):Abundance and redundancy
383:Knowledge (XXG):The rules are principles
178:
98:Knowledge (XXG)'s policies or guidelines
32:This is an accepted version of this page
540:Knowledge (XXG) essays about competence
480:
28:
362:Knowledge (XXG):Notability (mailboxes)
7:
378:Knowledge (XXG):Requests for process
545:Knowledge (XXG) essays about style
535:Knowledge (XXG) supplemental pages
419:Knowledge (XXG):Redundancy is good
102:thoroughly vetted by the community
57:
373:Knowledge (XXG):Practical process
341:Knowledge (XXG):Asshole John rule
489:Vergano, Dan (January 3, 2013).
335:Essays against instruction creep
202:. To avoid these outcomes, keep
145:
75:
393:Knowledge (XXG):Too much detail
368:Knowledge (XXG):Overlink crisis
217:. Keep policies and guidelines
520:Instruction creep at Meta-Wiki
281:Not every instruction is creep
63:. For creep of templates, see
1:
192:Nobody reads the directions
561:
286:
250:
109:
58:
468:Template:Simple help page
18:Knowledge (XXG):RULECRUFT
425:Knowledge (XXG) articles
167:to keep Knowledge (XXG)
153:This page in a nutshell:
39:latest accepted revision
262:
188:
260:
251:Further information:
204:Knowledge (XXG) space
182:
309:Linking to this page
169:policy and guideline
100:as it has not been
29:Page version status
263:
241:hypothetical issue
227:consensus-building
200:drive away editors
189:
35:
441:Instruction creep
164:instruction creep
159:
158:
139:Explanatory essay
137:
136:
86:explanatory essay
16:(Redirected from
552:
508:
507:
505:
503:
485:
299:
225:, impairing the
149:
148:
142:
129:
122:
79:
78:
72:
21:
560:
559:
555:
554:
553:
551:
550:
549:
525:
524:
516:
511:
501:
499:
488:
486:
482:
478:
473:
446:Parkinson's law
331:
319:will be ignored
317:or a rule that
311:
303:
302:
295:
291:
283:
255:
249:
212:
177:
146:
140:
133:
132:
125:
118:
114:
106:
105:
76:
68:
55:
54:
53:
52:
51:
50:
34:
22:
15:
12:
11:
5:
558:
556:
548:
547:
542:
537:
527:
526:
523:
522:
515:
514:External links
512:
510:
509:
479:
477:
474:
472:
471:
459:
458:
453:
448:
443:
438:
433:
422:
421:
416:
407:
401:
400:
395:
390:
385:
380:
375:
370:
365:
359:
353:
348:
343:
332:
330:
327:
310:
307:
301:
300:
292:
287:
282:
279:
248:
245:
211:
208:
176:
173:
157:
156:
150:
138:
135:
134:
131:
130:
123:
115:
110:
107:
95:
94:
82:
80:
56:
47:30 August 2024
36:
30:
27:
25:
24:
23:
14:
13:
10:
9:
6:
4:
3:
2:
557:
546:
543:
541:
538:
536:
533:
532:
530:
521:
518:
517:
513:
498:
497:
492:
484:
481:
475:
470:(edit notice)
469:
466:
465:
464:
463:
457:
454:
452:
449:
447:
444:
442:
439:
437:
436:Feature creep
434:
432:
429:
428:
427:
426:
420:
417:
415:
412:
411:
410:
409:
405:
399:
396:
394:
391:
389:
386:
384:
381:
379:
376:
374:
371:
369:
366:
363:
360:
358:(WP:MOSBLOAT)
357:
354:
352:
349:
347:
344:
342:
339:
338:
337:
336:
328:
326:
322:
320:
316:
308:
306:
298:
294:
293:
290:
285:
280:
278:
276:
272:
267:
259:
254:
246:
244:
242:
238:
234:
232:
228:
224:
223:wikilawyering
220:
216:
209:
207:
205:
201:
197:
193:
186:
181:
174:
172:
170:
166:
165:
154:
151:
144:
143:
128:
124:
121:
117:
116:
113:
108:
103:
99:
92:
91:
87:
81:
74:
73:
70:
66:
62:
48:
44:
40:
33:
19:
500:. Retrieved
494:
483:
461:
460:
424:
423:
403:
402:
334:
333:
323:
312:
304:
284:
268:
264:
236:
235:
219:to the point
214:
213:
191:
190:
162:
160:
152:
83:
69:
46:
37:This is the
31:
456:Scope creep
406:encouraging
315:bureaucracy
297:WP:NOTCREEP
196:read at all
84:This is an
529:Categories
476:References
408:redundancy
215:Principles
210:Prevention
88:about the
496:USA Today
462:Templates
112:Shortcuts
65:WP:TCREEP
61:WP:ACREEP
502:June 17,
451:Red tape
329:See also
289:Shortcut
127:WP:KUDZU
120:WP:CREEP
43:reviewed
404:Essays
364:(humor)
275:discuss
237:Editing
175:Problem
271:boldly
247:Fixing
161:Avoid
231:essay
185:kudzu
183:Like
504:2021
45:on
531::
493:.
233:.
93:.
41:,
506:.
104:.
67:.
49:.
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
