Wikipedia:Status quo stonewalling



Status quo stonewalling is opposition to a proposed change without (a) stating a substantive rationale based in policy, guidelines and conventions or (b) participating in good-faith discussion.

Such stonewalling is typified by an insistence on keeping a current version instead of adopting a proposed change – or reverting to the version prior to a disputed change (the status quo) – avoiding substantive discussion of the issues related to the change while engaging in behavior that is typical of disputes. Such behavior creates the appearance of a real substantive dispute about the change when none (or little) exists.

When a substantive objection to a change exists, stonewalling is not required. So stonewalling is typically used when those opposed to the change don't actually have a substantive objection to the proposed change, or when they know whatever argument they have can be easily refuted, or is contrary to consensus.

Editors seeking to defend a status quo situation should refrain from employing the stonewalling tactics listed here, and instead follow the advice at How to avoid status quo stonewalling.

What is status quo stonewalling?
Status quo stonewalling is disruptive behavior that is characterized by the use of tactics which obstruct, delay, prolong, or distract discussion from reaching consensus, usually when those opposing a proposal have few if any substantive arguments with which to support their position, and often when it appears that consensus supports, or is close to supporting, the change. While it's very difficult for one editor acting alone to succeed with stonewalling, if only two or three are involved, who don't even have to be coordinating their efforts, their ability to successfully build and maintain a stonewall retaining the status quo can be distressingly effective. With a few more editors it becomes even easier.

True consensus in a given situation is ideally measured and determined by the strength of the arguments presented, but often formal or informal polling is used as a substitute to determine consensus. So if enough people express objection to a change, that can be easily interpreted to be evidence of a lack of consensus in favor of the change. While that's probably usually an accurate assessment, if those opposed don't actually have substantive arguments supporting their objection, but those in favor of the objection do, there can actually be consensus in favor of the change when it appears that there isn't. Status quo stonewalling is about taking advantage of such a situation in order to prevent a change.

Can stonewalling be done in good faith?
The capacity of the human mind to engage in denial and rationalization can be impressive. As such, someone engaged in what may even seem like blatant stonewalling might not be fully aware of it. In fact, it's almost certain that the stonewaller feels justified in doing what they are doing for one reason or another. So, challenging as it might be, it's probably best to assume good faith and help them find a way to stop stonewalling without them losing face.

Reverting with "discuss first" without discussing
Stonewalling editors may revert with an edit summary such as "discuss first", "no consensus", or "more discussion is needed,". In other words, BRD the D. For a strategy to deal with this behavior, see How to respond to a “no consensus” edit summary.

Refusing to continue to discuss
An editor may have a good reason for disengaging from discussion, for example, WP:DEADHORSE, WP:PERENNIAL, and WP:FILIBUSTER. Then again, an editor may disengage because they are lazy, unwilling to compromise, or unable to concede. Disengaging editors should alert the other editor and provide their rationale. If you get ghosted, consider the "does not reply" strategies suggested at How to respond to a "no consensus" edit summary.

Before reacting to another editor refusing to further discuss, recall that Wikipedia is not about winning and consider whether the issue is important enough to deserve more of your time. If you believe it is then seek a third opinion.

Imposing a moratorium on proposals for change
Wikipedia normally allows any editor to propose changes on any subject at any time. A moratorium, which limits discussion of a particular proposal, runs counter to that and must never be applied hastily or without good reason. To limit the frequency of a debate that has become demonstrably repetitious and unproductive is a common reason to impose a moratorium (see the perennial proposals list), but sometimes a moratorium may be applied – or participants in a discussion may to apply one – when the subject has not yet reached that threshold. Doing so is inappropriate and is almost certainly stonewalling.

It is impossible to know whether a given situation is going to be resolved with further discussion, no matter how repetitious discussion about it up to a certain point has been. For this reason, and because discussion is essentially harmless and the normal way we develop consensus on WP, some believe moratoriums on proposals or discussion should never be applied, and are always forms of stonewalling.

“Change the guideline first”
When a proposal contradicts a guideline but provides a reason to do so, simply opposing due to the guideline contradiction is status quo stonewalling

While it may seem reasonable to require an RfC to change the guideline before other changes are made, often the only way to gain consensus for a guideline change is to establish precedent showing consensus for contradicting the existing guideline at least in some particular cases

Simply rejecting contra-guideline proposals because they contradict the guideline can create a Catch-22 situation biased towards preserving the status quo: the change can’t be made because it contradicts the guideline, and the guideline can’t be changed because there is no precedent establishing consensus contrary to the guideline.

Opposition to a proposal that contradicts a guideline should not be based simply on the guideline contradiction; it should address why the reason provided is not good enough, if that’s truly the case.

Reverting or opposing on procedural grounds
When someone does not like a change but has no substantive reason to revert or oppose, sometimes they will justify their action on procedural reasons. Possible reasons given are:

Defending a revert because it's related to an ongoing dispute
A variation of avoiding substantive discussion because of is involved is reverting a policy or guideline edit solely on the grounds that the edit favors the person who made the edit in some ongoing dispute.

The evaluation and discussion of the edit should be regarding whether there is consensus support or opposition to the edit, and/or whether there is good reason to support or oppose the edit, and what those reasons are. Justifying the revert solely on the grounds that it favors the editor in an ongoing dispute and avoiding any substantive discussion about the edit independent of that dispute is simply a lame excuse to retain the status quo.

Defending a revert because the related text is mentioned in an open case
If an issue related to the text that is the subject of change and revert is being discussed in an Arbcom or other case, that is sometimes used as a basis to "restore" the "original" wording until the case is resolved, which might take weeks or even months. But any objection to a change should be accompanied with a substantive explanation explaining why the change is believed to be against consensus or contrary to policy, guidelines, conventions or accepted practice.

A !vote of "no change needed"
In a poll, someone opposing might !vote Oppose with a non-substantive justification like "no need for change", or "current title is fine", etc. If no good reasons have been given for the proposed change, then say so. If some reasons have been given, then address them.

Arguing the status quo "does no harm"
Status quo stonewallers may say the status quo "does no harm" or is "okay." While this is often true, it says nothing about the proposed change. Compare WP:OWNBEHAVIOR: "An editor reverts a change simply because the editor finds it 'unnecessary' without claiming that the change is detrimental."

A variant of this assertion is that the proposed change is "unhelpful" or "not a material improvement." Evidently, the objecting editor only favors the original version because it is the status quo. That is not a valid reason to oppose a change that another editor believes is a materially helpful improvement.

Use of this argument in requested moves discussions is particularly laughable because no titles ever do any harm. In other words, the logical extension of the "no harm" argument is that no title should ever be moved, since no title ever does any harm. For example, there would be no harm in having any article at the title, This is an unreasonable title. As long as the reasonable title remained a redirect to the article, everyone would be able to find the article, and link to it, and there would be no harm. But if someone (presumably a vandal) did move an article there, the fact that it remaining there caused no harm would not be a good argument to leave it there! Defending the status quo with "it does no harm" is never a strong argument, and can suggest status quo stonewalling.

Opposing a proposal based only on asserting that it's not supported by consensus
Consensus regarding a proposal is determined by evaluating the arguments made by all those participating. It's putting the cart before the horse to simply argue that consensus opposes the proposal.

Claiming consensus supports the status quo when it doesn't
When a good faith discussion about a proposal results in "no consensus" (rather than "consensus opposes change"), the status quo is usually favored (WP:NOCONSENSUS). Once this occurs it's common though incorrect to later argue that consensus the status quo.

Avoiding substantive discussion because of who is involved
Instead of explaining why the proposed change is opposed in substantive terms, those opposed instead complain about those who support the move, or their behavior (comments which, even if justified, don't belong on article and policy/guideline talk pages, but, rather, on user talk or dispute resolution pages).

Moving the goal posts
Bring me a rock.

Ignoring good faith questions
As part of the normal process to develop consensus, there will typically be some discussion, until it gets to a question or issue on which the argument of the status quo stonewallers fails. At this point they drop the discussion to avoid answering. Or they claim the question has already been answered, without indicating where (with a link or quote) it was answered.

Some time later a discussion picks up again, which also ends at a similar point. A talk page with numerous discussions about a change, each stalled at a similar point like this, is a tell-tale sign of status quo stonewalling.

Accusing change proponents of disruptive, tendentious, or TLDR editing
In multiple stalled discussions, proponents of the change are likely to make patient and good faith repeated attempts to discuss the substantive points at issue. Trying different approaches, some posts might get long and repetitive. So another diverting/delaying tactic used at such a point is for the stonewallers to accuse the frustrated proponents of change of too much editing, either in the form of tendentious editing, or battleground mentality, or making TLDR or WP:DE/WP:IDHT posts. The stonewallers' argument is usually something along these lines: Any apparent consensus in favor of the change is invalid because of the tendentiousness of the change proponents' editing, which has caused proponents of the status quo to no longer participate. As the TLDR essay notes, As a label, [TLDR] is sometimes used as a tactic to thwart the kinds of discussion which are essential in collaborative editing. So is TE.

Allegations of disruptive editing by users who have a record of disagreeing with the accused editor should be given close scrutiny before being accepted, as they may be an abuse of process.

Filibustering
Filibustering is the practice of making long meandering comments that may appear to be serious and substantive, but don't really say anything substantive, and the purpose of which is to delay or avoid some kind of decision or process.

For example, the comments might go on and on about hypothetical cases that are practically unlikely to occur. Another form is to bring up supposed issues in great detail, even though they were raised and addressed before. They could also involve straw man arguments, or red herrings which are likely to not be immediately recognized as such by the uninitiated. In addition to creating delay, a purpose of filibustering can be to wear others out, so that they leave, and thus no longer contribute in support of the change, helping to create the appearance that there is no consensus supporting the change.

Starting a new diverting discussion when existing discussion is favoring change
If it appears that an ongoing discussion is leaning towards favoring change, a common tactic is to distract by starting a new section/discussion. Like throwing a red herring to hunting dogs, this move is based on the hope that editors who contributed to the first discussion will be too busy or put-off by all the wikidrama to also contribute to the new discussion, thus weakening consensus in favor of the change in the new discussion. The excuse given for having a new discussion might be an alleged need for "more" or "broader" discussion, but anything plausible sounding is likely to be tried.

Suggest a third option without actually proposing one
This tactic involves suggesting that neither the status quo nor the proposed change is satisfactory, and so a third option needs to be discussed, without ever proposing an actual third option. If an actual third option is proposed, this delay tactic will not work, since an actual third option can be discussed, and consensus about it likely established one way or the other, which either results in a change, or going back to considering the first proposed change, so the delay would be very temporary. Much more effective stonewalling is to argue endlessly that a third option is needed, without ever coming up with one.

Edit war lockdown
With two or three editors opposing the change, they have enough people to revert good faith efforts to effect the change in question in a manner that puts no one at risk for a 3RR violation, but creates an edit war situation that motivates an admin to lockdown the page, probably at the status quo version. Such an effort does not have to be coordinated, but can occur naturally as long as a few stonewalling opposers are watching the page in question. This tactic is especially effective on policy pages where admins seem to be less tolerant of multiple reverts, and more apt to restore the status quo version once they get involved.

Finding excuses to ignore discussion results
There is no end to the excuses those opposing a change may use to argue the result of a discussion favoring the change should be dismissed. After all, any excuse to dismiss the result favoring change will serve their position for retaining the status quo, so the motivation for rationalization in favor of dismissal is strong.

For example, one discussion might be moving in favor of the change, so a stonewaller starts a second diverting discussion, then a change supporter summarizes the results of the first discussion in the second discussion, which moves on to favor the change as well, so the stonewallers claim the second discussion they started is invalid because it was biased by bringing in the results of the first discussion, thus successfully stonewalling two change-favoring discussions, and retaining the status quo against consensus.

Manipulating an admin into helping
Because many admins are predisposed to favor the status quo whenever there is a dispute, after creating sufficient smoke and noise with some of the tactics listed above, stonewallers can often be successful in convincing an admin that a legitimate dispute exists, and there is no consensus in favor of the change, when the dispute is actually non-substantive, and the apparent lack of consensus is actually the result of successful sandbagging. Duped in this manner, the admin is then likely to restore the status quo version (if necessary), and possibly even lock the page if any evidence of an edit war can be demonstrated. This tactic is particularly effective because it causes an admin who sees themself as being uninvolved to get involved in a manner that favors one side (the status quo stonewallers) over the others. Once so engaged, such an admin can prove to be useful to the stonewallers repeatedly.

Arguing a policy or guideline needs to change first when opposing a proposal that is based on ignoring that policy/guideline per IAR
This occurs when a proposal is made based on ignoring a policy/guideline per WP:IAR because the propriety and consensus support of that rule is being questioned, and those supporting the status quo ignore the reasons for invoking IAR, and simply declare that unless the rule itself is changed, it must be followed.

The fallacy in this argument is that our rules largely reflect practice, and practice must usually change before a change to the rules is warranted. That means that for a change to a rule that accurately reflects practice to occur, that rule must, at least initially, be ignored, to at least question the issue of whether that rule still has consensus support. This is why substantive contributions in such cases must at least address the reasons being given for ignoring or changing the rule in question. Simply declaring that the rule must be followed unless it is changed, without addressing, much less refuting, the arguments made to ignore the rule, is simply a form of WP:JDLI evasion in such cases.

How to avoid status quo stonewalling
The chief characteristic of legitimate status quo defending is substantive discussion regarding the change and how it compares to the status quo situation:
 * 1) If the status quo cannot be defended with strong arguments based in policy, guidelines, consensus and actual practice, don't try to defend it. If the new contribution is also inadequate in your opinion, then research and refine it rather than reverting.  The ideal collaborative edit cycle is WP:Bold-refine.
 * 2) Honor the D in BRD.
 * 3) *If you revert a change, provide a clear substantive explanation of your objection to the change in the edit summary or, if additional space is necessary, on the talk page.
 * 4) *Don't close your mind to the possibility of a compromise, or even changing your mind entirely.
 * 5) *Answer good faith substantive questions about your position favoring the status quo over the proposed change. If the questions seem repetitive to you, don't just say so, take a few minutes to find where they were already asked and answered, and provide a link to it.
 * 6) *If a discussion starts to move away from supporting the status quo, don't use diversionary tactics to try to prevent that from happening. Instead, engage editors in discussion, try to understand why they hold the opinions they hold, and try to persuade them about why the status quo is better (if they don't persuade you to favor the change, or a compromise).
 * 7) Keeping in mind that polling does not replace consensus-building, support the use of polling to determine whether there is substantial support for either the change or the status quo, even if the polling results in an outcome with which you disagree.
 * 8) If the same change seems to be repeatedly proposed, create a FAQ explaining the reasons supporting the status quo, and the reasons for opposing the frequently proposed change (e.g., The Sega Genesis naming dispute).

Discount or dismiss non-substantive !votes in discussion evaluations
If closing admins would discount if not dismiss entirely !votes lacking substantive justification in polls that they are closing, and be clear that they are doing so, then people would be discouraged from simply !voting against a proposal, without explaining why.

Refactor non-substantive diversionary comments in discussions
Comments that are non-substantive, especially if diversionary (attempt to divert discussion from substantive points about the proposed change in question), can be refactored, like with the Hide template. However, it's probably more effective and less combative to ask an uninvolved admin to make an edit like that rather than doing it as an editor involved in the dispute.

Advocate for the reverting of unexplained reverts
Reverts of good faith edits without adequate explanation should not be tolerated, and the most effective way to accomplish this is by reverting such reverts as soon as possible. In other words, WP:Obvert. If people are not willing to explain and defend their reverts of good faith edits, they should not be reverting, and the only way to discourage them is by undoing their reverts.

Since it's currently not accepted behavior on WP and likely to be seen as edit warring, it's probably best to advocate for it for now where appropriate, rather than actually revert such reverts.