I've been a cooperative process consultant since 1987. Early in my career it became apparent to me that in the community context you need to be able to work with both thoughts and emotions. Neither alone is sufficient to create and sustain healthy group dynamics.
Ever since that insight I've been wrestling with how best to integrate these two essential ingredients into a plenary cake mix that will reliably produce something both palatable and nutritious. Let me describe the progression:
1. Stonewalling
While there remain a lot of intentional communities who are not resolved about the need to work explicitly with energy, I'm happy to report that their number is dwindling. Mainly because the rational-only approach simply doesn't work. It polarizes half the group and leads to brittle decisions. I think the only thing that sustains this antediluvian idea is paralysis about how to work effectively with energy. It calls for a level of personal awareness and a communication skill set that are typically not screened for in membership, and the way forward can be bumpy.
In fairness to groups in this muddle, the skills needed to work effectively with thoughts are completely different from the skills needed to work effectively with energy, and it can be a challenge finding or developing people who are ambidextrous.
2. Separate But Equal
More subtle is what I style the Plessy v Ferguson approach where the group offers both business meetings (for the product oriented) and heart circles (for the relationship oriented)—thereby officially acknowledging the need for energy work. While there is a tendency to style these two separate offerings as equally valuable (whence my reference to the 1896 Supreme Court ruling), in fact, they rarely are treated that way, and the integration of the two is left largely to the imagination. (The people needing exposure to the energetic information often don't attend those sessions, and the product of the heart circles does not inform the business meetings. Stalemate.)
Just as the 1954 Brown v The Board of Education Supreme Court ruling exposed the fallacy of Plessy v Ferguson, I'm here to tell you the money is in figuring out how to integrate these two precious elements into all plenaries, where the one complements the other.
3. An Issue's Journey
That inspired me to develop the concept of An Issue's Journey, a sequence that could serve as a blueprint for productively working through a generic issue from start to finish. This was my initial attempt, back in the late '90s:
Step 1: Presentation of the Issue (What are we talking about? What are trying to accomplish on this topic?)
Step 2: Questions (Did everyone understand the Presentation? Let's make sure everyone is on the same bus.)
Step 3: Discussion (What does a good response to this issue need to taken into account?)
Step 4: Proposal Generating (What responses best balance the factors identified in the previous step?)
Step 5: Decision (Are we satisfied that what we've come up with is good enough?)
Step 6: Implementation (Who will do what, by when, and with what budget?)
While this articulation did a decent job of explaining why you should never start with proposals, it didn't get at the energy/ideation dichotomy very well. Gradually it occurred to me that there needed to be an explicit invitation to welcome strong energy if that was in the room (it isn't always, but when it is there needed to be a place to open it up and hold it). My thought (circa 2014) was to include it in Step 3, suggesting that if anyone wanted an opportunity to make a full-throated pitch for why a factor mattered to them, they would be given 1-2 minutes on the soap box to do so.
This didn't quite answer the need, so I kept tinkering… which lead a new-improved model that I trotted out a couple years later.
4. An Issue's Journey 2.0
Step 1: Presentation of the Issue (What are we talking about? What are trying to accomplish on this topic?)
Step 2: Questions (Did everyone understand the Presentation? Let's make sure everyone is on the same bus.)
Step 2a: Clearing the Air (Are there unresolved tensions in relation to this issue? If so, let's deal with them here.)
Step 3: Identifying Factors (What does a good response to this issue need to taken into account? What common values do we need to keep in mind? This is an expansive phase, casting the net.)
Step 4: Proposal Generating (What responses best balance the factors identified in the previous step? This is a contractive phase—advocacy is over; now we're looking for bridging.)
Step 5: Decision (Are we satisfied that what we've come up with is good enough?)
Step 6: Implementation (Who will do what, by when, and with what budget?)
I added 2a (instead of renumbering 1-7) because this step isn't always needed—though if it is, then it needs to happen early. The three key steps in this sequence are 2a, 3, and 4. Each requires a different container and quality of participation, and they need to be undertaken in this order.
This was closer to what I wanted, but I found the level of engagement in Clearing the Air to be uneven. Some spoke from the heart while others treated it as a platform for analysis or simply as a way to insert an early pitch for their preferred solution and it was clunky to manage, which brought me to my latest incarnation, that I test drove this past summer…
Step 1: Presentation of the Issue (What are we talking about? What are trying to accomplish on this topic?)
Step 2: Questions (Did everyone understand the Presentation? Let's make sure everyone is on the same bus.)
Step 3: Laying Out the Field (Is there anything you want the group to know about how this issue touches you? We are looking for statements from the heart. Everyone gets one chance at the mic. We are not looking for dialog, judgments, or proposed solutions at this stage. If unresolved tensions surface, we'll deal with them as we go.)
Step 4: Identifying Factors (What does a good response to this issue need to taken into account? What common values are in play?)
Step 5: Proposal Generating (What responses best balance the factors identified in the previous step?)
Step 6: Decision (Are we satisfied that what we've come up with is good enough?)
Step 7: Implementation (Who will do what, by when, and with what budget?)
My early experiments with this reconfiguration have been encouraging. The sharing manifested in Laying Out the Field has included strong feelings and also tenderness that has previously not been widely disclosed, and has helped to establish a nuanced understanding of what matters to people before we get into problem solving. To be fair, people still try to sneak in ideas about solutions, which I have to gently yet firmly set aside, but there's a learning curve with any new process and I try to breathe through it.
While it may not be heaven, I reckon I'm getting closer all the time.