Consensus With Straw Polls: A Process For Meetings

Todd Davies
June 2016

Notes: The following is a process description I wrote for a multiracial activist group on which I served, and which was adopted on a trial basis as its official process document. It is based on consensus methods I have learned over the years in various groups. This document addresses primarily the formal aspects of consensus, and does not include guidelines for facilitators and others who fill process roles. See below (after the process description) for recommended additional readings.

Process Description: Consensus With Straw Polls

Consensus comes in different varieties. Some practitioners view tests of consensus as a substitute for voting, and they do not believe that votes or anything that looks like them should be included in a consensus process. But the version of consensus we have agreed to includes voting as part of a larger process, that culminates in a test for consensus. In this version, we typically call votes "straw polls" or "temperature checks", to clarify that these do not constitute the decision of the group, but are preliminary to it. Straw polls are not binding on the group.


The process below is intended to make meetings go more smoothly, and not to make meetings unduly difficult to conduct. It is useful and sometimes necessary for all members to be more or less familiar with the elements of an agreed-on process. But optional elements and shortcuts may be taken when group members agree this is appropriate in a given context. The use of consensus terminology can be skipped when someone's intent is clear from context. But members may request clarification based on elements of the agreed process, or invoke a point of process (see below).


Consensus includes elements that are intended to help resolve conflicts in the group. The conflicts best resolved by consensus are not necessarily personal or behavioral conflicts, but rather are differences of opinion about courses of action. For example, some in the group think we should do X, and others think we should not do X. We can call these "simpler conflicts". Personal or behavioral conflicts are also addressed by elements of a consensus process, as well as by guidelines agreed to by the group. But personal and behavioral conflicts sometimes stem from a lack of agreed-on process for resolving simpler conflicts, so that under an agreed-on consensus process, some of those personal/behavioral conflicts may go away or be less likely.


Following an agreed-on process can help clarify where group members are with respect to a question or possible course of action. In groups that lack a defined process, members may agree or disagree with each other without some group members knowing exactly what others think, or with members not being on the same page about whether the group has agreed, or on what has been decided. Conflicts can sometimes arise, either during a meeting or later, when some or all group members are unclear about each other's views, whether an agreement has been reached, and if so what it is. A lack of process for clarifying this puts a heavier burden on the group's memory and/or on its note taker for remembering what the group has decided in the past. Expressed or unexpressed conflicts over this can sometimes escalate or otherwise keep the group from operating effectively.


Elements of consensus, which can be called on or invoked by group members at different times, depending on the facilitator and general practice of the group, include the following:


process: the set of practices that group members agree to in advance, supplemented by the practices of a facilitator and the group itself; these latter practices determine the details of how the process works in a particular meeting or context


process roles:


proposal: a course of action the group could take, which requires everyone's agreement; adopted when the group reaches consensus (see below on "test for consensus")


discussion phase: period after proposal is made, prior to a test for consensus


stack: the order of speaking for group members during the discussion phase, which may be governed in different ways: raising hands, going around, talking pieces, free-for-all, etc., depending on the group or facilitator


contributions that can override the stack (with gestures to signal for attention or for recognition from the facilitator):


contributions (on proposals) subject to the stack - any category may be expressed at any time during the discussion phase by a member during their turn; gestures may be made by members who are not on the stack; some gestures have ambiguous meanings, which the group can clarify by agreement:


straw poll (alternative terms - "temperature check" or “nonbinding vote"): a poll to let all members know where the group stands on a proposal; this may precede a test for consensus during the discussion phase on a proposal, but is not mandatory; it does not end the discussion phase unless the group has otherwise agreed to do this


test for consensus: the final step required for approving a proposal; only applied to one proposal, which should be the only proposal under discussion when the test for consensus is made

Additional recommended readings: