Theory about decision-making only sticks once you watch it survive a real argument. This walkthrough is invented, but it follows exactly how rough consensus untangles a genuinely contentious decision. Use it as a model for how to handle the next heated thread in your own community without it turning into a brawl.
The proposal
A contributor proposes a change to a default setting in the Malairte wallet, arguing it would make the experience smoother for beginners. Within hours the thread has forty replies. Some love it. Some hate it. A few are arguing about something only tangentially related. To a newcomer it looks like chaos with no way out. To someone who understands rough consensus, it is just the messy beginning of a normal process.
Separating noise from objection
A moderator steps in, not to pick a side, but to sort the thread. They distinguish three things: genuine enthusiasm (helpful but not decisive), vague dislike ("I just do not like it", which stalls nothing), and serious technical objections. Only the last category actually matters. After sorting, two real objections remain: the change might confuse existing users who rely on the old default, and it might interact badly with one type of hardware.
Working the objections, not the votes
Here is the crucial move. Nobody counts hands. Instead the discussion turns entirely to those two objections. Can the change be made without confusing existing users? Someone suggests applying the new default only to fresh installs. The hardware concern prompts a contributor to test the affected setup and report back. The conversation has shifted from "who is winning" to "what would need to change for this to be safe."
Reaching rough consensus
Within a week, both objections have been addressed. The new default applies only to fresh installs, and testing confirmed the hardware concern was unfounded. The people who raised the serious objections say they are now satisfied. A handful of quiet "fine with me" replies follow. Nobody with a sound technical reason is still strongly opposed. That, precisely, is rough consensus, and the change moves forward.
Why the loud minority did not derail it
Some people in the thread never liked the idea and still do not. Under a majority vote they might have blocked it or been steamrolled, breeding resentment either way. Under rough consensus their vague dislike carried no weight, because it pointed to no problem anyone could fix, while the one newcomer with a real, specific hardware concern got taken completely seriously. Merit beat volume.
The lesson for moderators
The whole outcome turned on one calm question, asked repeatedly: "What specifically would need to change for you to be okay with this?" That question is the practical heart of rough consensus. Train your community to ask it, and even your most contentious decisions resolve into progress instead of factions.