 | This is anessay. It contains the advice or opinions of one or more Wikipedia contributors. This page is not an encyclopedia article, nor is it one ofWikipedia's policies or guidelines, as it has not beenthoroughly vetted by the community. Some essays represent widespread norms; others only represent minority viewpoints. |
 | This page in a nutshell: When there are process issues with a discussion, those need to be resolved before the underlying question is debated. |
Wikipedia hasmany established rules to help guide discussions towards more productive outcomes. However, in reality editors regularly start discussions that violate these rules, sometimes out of ignorance and sometimes because they are seeking to gain an advantage. This can take many forms, fromnon-neutral RfCs todiscussion forks toattempts to close discussions by involved parties.
When these things happen, it creates process questions that can disrupt the discussion and, if left to fester, ultimatelyundermine confidence in the result. The longer the problems go unaddressed, the messier the situation becomes and the harder it is to resolve. It is therefore important that such problems be nipped in the bud as soon as they are spotted.
Unfortunately, this often does not happen. Voicing your opinion on a hot topic is satisfying, whereas trying to wrangle a discussion into compliance can be thankless, and it's often inadvisable to try to do both. But for Wikipedia to function smoothly, the project needs editors who come across a discussion and see a process violation topick up the mop in that moment and set things straight. Likewise, when someone comes in and raises a process-related point, editors engaged in the discussion need to temporarily set down their pitchforks and give space for the point to be resolved before resuming the debate.
Wikipedia has few technical means to enforce discussion rules, so it ultimately falls on human editors to keep everything in line. When process is settled first, discussions work better.