Posted 7 years ago on Feb. 13, 2013, 6:16 p.m. EST by OccupyWallSt

Tags: consensus

Consensus process (the idea that a group must strictly adhere to a protocol where all decisions are unanimous) is the absolute worst idea that has ever been introduced to the activist community.

Consensus process is the tyranny of the individual. It is the most anti-social of all processes because it allows any one person to assert irrational authority over an entire group of people and block any sort of decision making. It has nothing do with anarchism (even the IWW doesn't use consensus!) because it was invented by Quakers for religious reasons. It's stood in the way of progress, destroyed social movements, destroyed groups, destroyed communities, and relegated radicals to the fringes of American politics since the 70's when it was first popularized.

Consensus process is in many ways an attempt to formalize the act of resistance, which I suspect is what makes it so popular in activist communities. Let's compare this to democracy, a system which was invented to formalize dissent. With democracy, you could fight and disagree without resorting to violence. Feathers could be ruffled, progress could be made, and life moved on according to plan. Resistance on the other hand is when you're so angry at something, that you're willing to go on a crusade and use all available means to stop that thing from happening Resistance knows no rules. It is something that should never happen, yet is the responsibility of any socially conscious individual. It's a wild beast which cannot be tamed. Now ask yourself what happens when you get a bunch of people in one room, people whose nature inclines them towards resistance, and then give them the power to resist with a simple hand gesture and a requirement that all others be subservient to their demand. You do the math.

To give an example, the first time I saw a block used at Occupy was at one of the first general assemblies in August 2011. There were about a hundred people that day and in the middle of the meeting a proposal was made to join Verizon workers on the picket line as a gesture of solidarity in the hope that they might also support us in return. People loved the idea and there was quite a bit of positive energy until one woman in the crowd, busy tweeting on her phone, casually raised her hand and said, "I block that". The moderator, quite flabbergasted asked why she blocked and she explained that showing solidarity with workers would alienate the phantasm of our right-wing supporters. Discussion then abruptly ended and the meeting went on. The truth was irrelevant, popular opinion didn't matter, and solidarity—the most important of all leftist values—was thrown to the wind based on the whims of just one individual. Occupy had to find a new way to do outreach.

But as bad as that sounded, it was actually one of the most graceful instances I've seen of a block being used. This is because the proposal was actually dropped as though it never happened. Things don't always go so smoothly. Blocks have a tendency to bring out the worst in people. The thing they don't tell you about consensus, is that it only works if you're willing to exclude others from it. When faced with a block, it's common for people to use psychological manipulation, threats, invent process to deny that person a vote, or even pressure them to leave the group entirely. Oftentimes when such people don't get their way, they'll leave the group themselves. Consensus invites the most awful type of conflict because there can be no agreeing to disagree. But at the same time consensus also quells the more constructive forms of dissent because most considerate and rational people aren't masochistic enough to welcome the hatred and backlash inherent in blocking a proposal.

Consensus process can also be hacked. This is because it leaves too much to interpretation, doesn't actually specify procedure, and doesn't make sense! Take for instance kicking someone out of your group. Do you need consensus to kick them out? Or do you need consensus to keep them on board? Oftentimes such things aren't clear, so the system becomes ripe for manipulation and exploitation. If you ever want to be evil and push a proposal through a consensus body, just make a compelling argument that you need consensus to not pass your proposal (rather than the other way around). If that doesn't work, try writing your proposal with the opposite language and blocking it yourself. If people call you out on your shenanigans, just accuse them of being authoritarians who refuse to follow process and demand that they either step down or reach consensus on creating a rule to forbid what you’re doing. Then block that proposal too. If they tell you that you’re not allowed to block then you can always complain that true consensus cannot be reached until there’s a quorum of every single group member present.

Grassroots activist groups also follow the spirit of consensus regardless of what process they use. This is because participation in occupy assemblies, working groups, and affinity groups is entirely voluntary. Generally speaking, these groups do not control any land or resources upon which their members depend, therefore making it nearly impossible to practice any real coercion. When freedom of association exists in the truest sense of the words, the act of participation in and of itself can be considered itself a form of a consent, even if decision-making power rests in the hands of the majority or an individual leader.

Consensus should be reserved to teams (small groups where people work well together and trust one another) as de facto rather than official process. Many of us operate by implicit consensus without even realizing it. It’s a natural human behavior to not want to piss off and ignore other members of your team. But when the occasional irresolvable conflict arises, a majority vote isn’t the end of the world. It’s called democracy. If those conflicts happen too often, then perhaps it’s time to reconsider why you’re working with such people.

When it comes to deliberative process for larger groups that can’t be considered teams, start off with what's been known to work and has stood the test of time, like Robert's Rules of Order. It’s not the ideal system to prevent all forms of hierarchy, but it’s at least been proven to work in organizing democratic assemblies that are capable of functioning. Why must we reinvent the wheel? The only clear explanation is that it’s fun to fetishize process rather than accomplishing work. There are actually people who've devoted much of their careers as activists to unnecessarily reinventing process, and for years they've been using entire activist communities as guinea pigs in their experiments. Why must we allow ourselves to be pawns in someone else's game? Our goal should be fighting power and injustice, and we should settle for no less than the best tools for the job.

But we also shouldn't have to follow Robert's Rules by the book all the time. Oftentimes people will forgo formal process entirely until it's needed. It's also perfectly reasonable to borrow good ideas from other processes. One such example is the "progressive stack" which Occupy has used from its very first general assembly meeting. This means when you have a meeting and ten people want to speak at once, one person will be assigned to "take stack" by writing down the names of whoever has their hand raised. The person taking stack will then prioritize speaking order in favor of people belonging to groups whose voices have traditionally been marginalized. Examples of such groups include women, people of color, and the lgbtq community. This is great news if you're a queer trans woman of color, but not such great news for straight white middle class cis men whose voices have far too often dominated discussion. Another great tool for facilitating collective thought is the temperature check, where everyone in the room twinkles their fingersto express how favorably they feel about the topic of deliberation. But in reality, that’s just a more fabulous variation of Robert’s Rules where the chair will try to gauge support for a proposal during deliberation by asking everyone in the room to say aye / nay or give a show of hands.

The only significant experimentation we should be doing with process at this time is trying to find ways to use modern technology to make democracy more democratic. For the first time in the history of civilization, we are able to scale up conversations to span the entire globe. A deliberative assembly no longer must be limited to the number of people capable of fitting in a single room. Why are we not taking advantage of this? Several attempts have been made to develop such systems, but most of the existing solutions are either shoddy, hard to use, or focus on anonymous voting rather than deliberation. These systems also do not make an effort to define the procedural conventions to govern the aspects of software use which cannot be digitized. Engineers, please start teaming up with process experts to accomplish this.

To learn more about the follies of consensus, read the essays "Blocking Progress" by Howard Ryan and "Fetishizing Process" by Mark Lance.

This article is part of the series To Consense or Not-to-Consense. To read a response to this article, see On Consensus.