OS: General Assembly Process Principles and Practice
http://processandfacilitation.wordpress.com/
[Dear OR, Here is a group of suggestions about GA facilitation for folks to read through. We're posting it per OR GA's recent request for more info. Also to encourage everyone to take a turn very soon in any/all of the roles needed to run our meetings, and live into the vital principle of shared facilitation in a horizontal leaderless egalitarian movement. This is an example posted FYI and not engraved in granite. Just some "how to" pointers from OS. Questions and comments about any of these docs are most welcome. Contact any of us on the facilitation working group: Ryan Acuff, Mike Millow, Ben Dean-Kawamura, Louise Wu, et al. any time -L.Wu].
After the General Assembly voted on Friday 7 Oct.2011 to delegate the organization of the facilitation process to the Process and Facilitation group (a group whose suggestions are, as said in principle #1, subject to the vote of the general assembly), we have been working on several documents through email, and in person to write down both the ideas behind the process and to reflect the actual process that is happening in the General Assembly. This document is one attempt to gather the “best practices” we have seen and thought of, and the process we are striving to enact. We want the process and our work to be seen and understood by all those who are interested, and the process to be beneficial to all who attend the general assemblies. These are not binding notes, nor are they written on a whim. We take these seriously and believe them to be a solid foundation for training and facilitating General Assemblies.
OS: General Assembly Process Principles and Practice
The Process Principles
The structure, process, and facilitation of the general assembly are based on seven basic principles. These principles reflect the basic reasons we are here: for everyone in the 99% to speak and make decisions that affect the whole. These principles can be changed at the will and vote of the general assembly. We will read these the beginning of every general assembly.
1. All decisions that affect the collective are made by general assembly. No decisions that affect or represent the whole are made by working groups. Working groups focus proposals to bring to general assembly, and they coordinate the work.
2. Yelling really loud does not put you on stack. Come to the front and get on stack if you have a proposal or an announcement. Never repeat what some else already said.
3. Assembly time is precious. Think three times before you speak. Does this really help the assembly make a better decision?
4. Nothing is more precious than the thoughts of the quiet. Nothing is more precious than the words of the silenced. Speak up! Please! Especially when it’s really hard!
5. Facilitators make space and move the process. Facilitators never present content or represent someone else’s thoughts. The assembly is responsible for keeping the facilitators in line.
6. Use the People’s Microphone. It makes us choose our words, and makes us listen.
7. The assembly is responsible for signing to the facilitators. If the assembly doesn’t sign, the facilitator doesn’t have anything to facilitate!
8. No one else can speak for you. That’s why we need you here!
The general assembly facilitates these principles by communicating with hand signals to the facilitators. There are also seven hand signals
1. Twinkle—“I like this, I support what this person is saying” “I agree”
2. Anti-twinkle—“I don’t like this” “I disagree”
3. Direct Response—“I have a correction of fact or a clarifying question.” Do not use this to state a different idea or arguing about values.PFWG suggests eliminating the “direct response” option as it allows people to jump stack and is therefore easily misused to express an opinion. It is also difficult to identify the difference between a “clarifying point” or “correction” and the expression of an opposing value, ideology, or idea.
4. Ears—“I cannot hear what is being said”
5. Wrap it up—“This is taking too much time” “I get your point, please finish”
6. Process point—“Process is not being followed” “Off topic”
7. Block—“I believe the vote we have just taken is against the basic, foundational principles of why we’re here.”
It is the role of the facilitators to see these signs from the general assembly and call on them.
There are four facilitator roles: Process mover, Stacker, Agenda worker, Timekeeper—it may be useful to have more people working in a single meeting to give people a rest and to keep the flow going.
Agenda worker: Reads Agenda, maintains approved agenda, keeps stack/line of people to speak to general assembly, checks with proposal makers that they are making a clear, concise, actionable proposal and not an announcement; coordinates time guidelines with Timekeeper, tells stacker/process mover what is next
Time keeper—coordinates with Agenda worker to suggest times for each agenda item, signals speaker to wrap up when they are reaching the time limit for report backs, proposals, announcements, works with Stacker to determine when to close stack, reads the weather and the interest in the general assembly to moderate length of general assembly, keeps time for blocking concerns.
Stacker—[“Stack” is the list of people who are called. The General Assembly has chosen to use ‘progressive stack’ see definition below] takes progressive stack during discussions, coordinates with Process mover to determine how many people to call on and when to cut stack, coordinates with Agenda keeper to keep progressive stack for working group, proposals, and announcements (to be organized both by progressive stack, urgency, and timeliness in coming to the podium or getting on the agenda).
Process mover— reads the assembly for hand signals, uses progressive stacking principles to call on points of process and direct responses, does ‘temperature checks’; reads the interest of the assembly for moving to a vote, for continuing discussion; works with agenda to include morale/personal statements throughout agenda (e.g. “shake a hand make a friend” or lead a chant, or encourage three deep breaths. May ask another person from the GA to lead this). The most important phrase for the process mover is “I see.” When the process mover sees any hand signals, names what is seen and acts on it.
▪ Process point: the Process mover says “I see a process point” and uses progressive stack to call on it.
▪ Direct response: PM says “I see a direct response. Is this a correction or a clarifying question?” then calls on it.
▪ Wrap it up: PM says “I see signals to wrap it up. Please conclude your statement”
▪ Twinkles: PM says “I see approval. We will [discuss/vote]
ALL FACILITATORS: count for votes on blocks; be prepared to clarify process; repeat founding principles;
Progressive stack: “Stack” is the term we are using for the list of people who want to speak. To get on “stack” raise your hand so the “stacker” can see you. We use progressive stack to help people whose voices have been silenced or ignored in history and society to be heard. This means that if you appear to be a white, ablebodied man, you will likely not be called on first, or second, or third, even if you were the first to raise your hand. If you are not white, female, disabled, elderly, you will be given priority in the stack. People who have not spoken before in the general assembly (to the memory of the stacker) will have higher priority than those who have spoken before. Progressive stack is used for both discussion and points of process/direct response. This is difficult, subject to the historical and ideological framework of the stacker. It also relies on visible markers of being part of an historically oppressed group. There are invisible disabilities, transpeople who pass, sexual orientations that do not show, race and class that is not visible or noticed by the stacker. Because of the highly subjective decisions facilitators make, it is crucial that these roles are rotated amongst people of different classes, races, sexual orientations, genders, age, physical ability, education, experience.
Rotation Suggestion
We suggest a rotation of “watch one, do one, teach one” to incorporate new facilitators. After “watching one” by participating in the general assembly, new facilitators can step into one of the roles. After being process mover once, you are an experienced facilitator! and we encourage you to do one of the other roles, such as stacker, where you will be able to assist a new facilitator read the assembly as you gather stack. No one should be process mover two assemblies in a row. No one should be stacker to assemblies in a row. No two people should switch these roles back and forth between themselves. No one should spend more than two assemblies in a row in one of the prominently visible facilitator roles of Process mover or Stacker.
FLOW OF EVENTS
Process & Facilitation Working Group gets the agenda from the information table. Organizes it. Suggested order:
1. Agenda—read, amend, approve.
2. Working group report backs/announcements
3. Proposals
4. Announcements
5. Personal statements/morale (sometimes this is facilitated with progressive stack, sometimes only partially, sometimes not at all; some statements/morale can be included earlier too)
15 minutes before the assembly begins, hand signals are explained.
The General Assembly begins with someone reading the 7 principles of process. Then the facilitators and their roles should be introduced. This should include an explanation from the stacker of how progressive stack works.
Work through Agenda.
HOW PROPOSALS WORK
The agenda keeper organizes the proposal makers and directs the next in line to the podium.
The proposer makes the proposal.
If there are direct response signals, Process mover uses progressive stack to ask the signaler “Is this a correction or a clarifying question?” If yes, the direct response is heard. Process Mover and Stacker should watch for Process points while listening. If a process point is shown or the direct response is not a correction or a clarification, the facilitator interrupts to use progressive stack to call on the process point or interrupts. After direct responses to the proposal are made, the proposer may reply with a clarification. This section is in the process of being revised; the PFWG is suggesting that we begin with the question from the process mover “Are there any clarifying questions?”
Then the Process mover checks with the assembly: “Respond with twinkles/antitwinkles: would you like to discuss this proposal.” Reports “I see mostly approval for discussion. We will take stack for discussion” or “I see anti-twinkles. We will move to a vote unless there are serious, potentially blocking concerns. Are there any serious blocking concerns?” Stacker also watches to see if there are many people indicating desire to speak. Then we go to stack.
Stacker makes eye contact or otherwise indicates when a hand has been seen. Takes note of who wants to speak, selects order of who will be called, and tells process mover who to call on.
Process mover, Stacker, and Time keeper continue to watch for process points, direct responses, and “wrap it up.”
After several points have been heard, if people are repeating ideas, Process mover should check to see if the assembly would like to move to a vote. “Respond with twinkles/anti-twinkles: Would you like to move to a vote?” Report using “I see” language.
Process mover asks for all in favor of the proposal to vote, then for all against, and then for blocks.
If there is a clear majority that all facilitators agree on, the vote is called. Process mover says “I see [approval/disproval]. The proposal [passes/does not pass] If there is not a clear majority or the facilitators disagree on whether the majority approves or disapproves the proposal, Process mover says “We do not see a clear majority. Proposal does not pass. Would you like to continue discussing this” and follows the signals from the assembly.
If there is a block. The facilitator says to the blocker “You have two minutes to explain why this is against the basic principles of why we’re here.”
If there is more than 1 blocker, those blocking should meet for 5 minutes to discuss their blocks and determine if they have different reasons for blocking. There will then be two minutes for blocking concerns to be heard. This is not per person blocking, but for all concerns—this is to ensure that all blocking concerns are heard by the General Assembly and to also ensure that the assembly not be held up by many blocks
Time keeper keeps time.
Facilitator says: “In the light of these concerns, we will retake the vote on the proposal. To uphold the proposal we must have 4/5ths approve.” Proposal is restated. Vote is taken. Hands are counted by ALL FACILITATORS.
Next proposal is brought.
When proposals are finished, we move on with the agenda.
▪ Written Monday.10 Oct 2011
▪ Updated Frid. 14 Oct 2011: added notes on eliminating “direct response”; clarified notes on blocking procedure
(I would like to include a PDF or .doc of this document, but I don’t know how. When I find out, I will upload a file)
Posted in Uncategorized | Leave a comment
Some resources.
Posted on October 14, 2011
Here are some links to some great resources to look at. We’ve taken many of our ideas from them, and encourage you to do the same!
Una Spenser’s “Primer on Consensus and the General Assembly”:
http://www.dailykos.com/story/2011/10/08/1022710/–occupywallstreet:-a-primer-on-consensus-and-the-General-Assembly
“The Occupation Cookbook” from Zagreb, Croatia’s University Occupation
——-
http://processandfacilitation.wordpress.com/2011/10/14/process-principles/
Process Principles
Posted on October 14, 2011
Process Principles (10/13 draft)
All decisions that effect the whole are made by general assembly. That way, groups can’t take over, or misrepresent. (clarification of the wording of this point, 10/14):
All decisions that effect the whole are made by the general assembly. Individuals and groups may speak for themselves and represent themselves. The General Assembly speaks for the Occupy Seattle movement, and its collective decisions.
Groups are for doing work and bringing proposals. If you have an idea, start a group! Don’t ask the assembly, just find some friends and do it!
Yelling really loud doesn’t put you on stack. Raise your hand. If you have a proposal or announcement, come to the front and get on the agenda. Never repeat what someone else already said.
Assembly time is precious. You can’t speak every time. Think three times before you speak. Does this really help the assembly make a better decision?
Nothing is more precious than the thoughts of the quiet. Nothing is more precious than the words of the silenced. Speak up! Please! Especially when it’s really hard!
Use the people’s microphone. It makes us choose our words. It makes us listen.
Facilitators make space and move the process. Facilitators never present content or represent another’s idea. The assembly is responsible for keeping facilitators in check.
The assembly is responsible for signing [demonstrate hand signs as you speak] to the facilitators. If the assembly doesn’t sign, the facilitator doesn’t have anything to facilitate!
No one else can speak for you. That’s why we need you here!
———–
http://processandfacilitation.wordpress.com/2011/10/14/hand-signals/
Hand Signals
Posted on October 14, 2011
Twinkle (wiggle fingers up) – I like it. I agree. (Alternative: Raise the roof.)
Anti-twinkle (wiggle fingers down) – I don’t like it. I disagree. (Alternative: Lower the roof.)
Wagon wheels (index fingers point past each other and spin) – Move it on. Wrap it up. True, but we’ve heard this before and my socks are wet.
Point of Process (index fingers together, thumbs together) – Speaker is talking at the wrong part of the meeting. Off topic. Abuse of process.
Block (forearms crossed over head) – This proposal that just passed is against the foundational principles of why we’re here. Speaker then has two minutes to explain their block; if multiple blocks, they have a few minutes to find a spokesperson to present all of their points in two minutes. Assembly then “re-votes” (technically, votes to uphold or overturn the block; but to avoid confusion, we restate the original proposal with for & against) and must obtain a 4/5 supermajority (i.e. four “pro” for each “against”) to overturn the block.
Ears (flat palms shooting out from ears) – I can’t hear you. Speak up. Too quiet.
Optional Signs
Facilitators have stopped recognizing these in the General Assembly for now, but they might be useful in Groups. WARNING: It can be VERY difficult to judge when these signs are being used well and when they’re being abused. Even if this is clear, it can be VERY difficult to discourage misuse.
Clarifying Question (Cusp one hand into a “C”.) – Jumps stack to top. Must be a question addressed to proposal bringer (or whoever brought the statement being addressed.)
Point of Information (index finger up) – Jumps stack. I have a fact you don’t know. (What’s a fact? What’s the line between information and opinion? Notoriously difficult to call and discourage misuse.)
Direct Response (rocking pistols) – Don’t get us started. It always seems like a good idea at the beginning – don’t put me on stack, it’s about what that person just said. But we found it almost always ends up meaning, “I really want to talk right now.”
###
Requested to be posted by: Louise Wu
Leave Your Response