A small elevator speech I shared on the OSLIST yesterday:
Self organization works by a combination of attractors and boundaries. Attractors are things that draw components of a system towards themselves (gravity wells, a pile of money left on the ground, an invitation). Boundaries (or constraints) are barriers that constrain the elements in a system (an atmosphere, the edges of an island, the number of syllables in a haiku)
Working together, attractors and boundaries define order where otherwise there is chaos. We can be intentional about some of these, but not all of them. Within complex systems, attractors and constraints create the conditions to enable emergence. What emerges isn’t always desirable and is never predictable, but it has the property of being new and different from any of the individual elements within the system.
Self-organization is where we get new, previously unknown things from.
I was working with a couple of clients recently who were trying to design powerful questions for invitations to their strategic conversations. Both organizations are dealing with complex situations and specifically with complex changes that were overtaking their ability to respond. Here are some of the questions that cam up:
- How can we be more effective in accomplishing our purpose?
- How can we create more engagement to address our outcomes?
- What can we do to innovate regardless of our structure?
- Help us create new ideas for executive alignment around our plan to address the change we are now seeing?
Can you see what is wrong with these questions, especially as they relate to addressing complexity?
The answer is that each of these questions contains a proposed solution to the problem, buried as assumptions in the question itself. In these questions the answers to addressing complexity are assumed to be: sticking to purpose, creating more engagement, innovating except structurally, aligning executives around our plan. In other contexts these may well be powerful questions: they are questions which invite execution once strategic decisions have been taken. But in addressing complex questions, they narrow the focus too much and embed assumptions that some may actually think are the cause of their problems in the first place
The problem is that my clients were stuck arguing over the questions themselves because they couldn’t agree on solutions. As a result they found themselves going around and around in circles.
The right question for all four of these situations is something like “What is going on?” or “How can we address the changes that are happening to us?”
You need to back up to ask that question first, before arriving at any preferred solutions. It is very important in discerning and making sense of your context that you are able to let go of your natural inclination to want to DO something, in favour of first understanding what we have in front of us. Seeing the situation correctly goes a long way to be able to make good strategic choices about what to do next. From there, planning, aligning, purpose and structure might be useful responses, but you don’t know that until you’ve made sense of where you are.
Tim Merry‘s work on collaborative advantage:
My friend and colleague Tim Merry is sharing some of his most recent thinking on project design and development here in Columbus at the Art of Hosting Beyond the Basics retreat we are doing. This is a really useful and interesting introduction to his approach:
Amanda Fenton provides a very useful reference that helps underscore the reasons why core teams are important. It turns out that having 10%of a population deeply committed to an idea will significantly contribute to that idea being widely adopted by the other 90%.
I don’t know about the veracity of this claim in every context but it does point to the need to abandon the idea that everyone needs to be on board to make things happen. For steel real years I have been interested in helping groups create a topography of engagement whereby a core the holds a central circle of shared purpose and shared work and concentric circles are organized around this work. The team percent rule helps me to think about the mechanics if how invitation can spread and how container building scales.
Makes me think for example that if you engaged in transforming a large traditional conference to something radically participatory you need at least ten peer met of the participants to be committed to that new form. For a conference of 600 that means reaching 60 people. This means a core team of 10 needs to each find five other people to really commit to the idea. From there invitation can go broader and less deep. But without those 60 on the next ring out you run the risk of having 10 committed individuals trying to convince hundreds to take a leap.
I think there is probably nothing new under the sun. Engagement work has been tried, refined and improved all over the world in the last couple of decades that I wonder if there is anything new we can learn? It does seem to fall into “authentic engagement” and “engagement washing” – if I can coin a couple of phrases. But I haven’t seen radically new thinking or practice for a while.
What we are getting instead is some terrific collections of tools, handbooks and harvests of processes. This .pdf of a Handbook for Civic Engagement prepared for a community process in the United States is an excellent example of the kind of harvesting that is useful. It sums up lessons learned from engagement process, proceeds from practice to inform theory and provides some useful invitations for practice and application. This is an artifact which has emerged out of the space of engagement “praxis” – the gap between theory and practice. I’m interested in tis inquiry at the moment, and stumbling across things like this in my quest to understand what is useful in harvesting from initiatives that sustain the capacity and learning begun in real engagement.
“Engagement washing” initiatives don’t usually leave these kinds of documents in the places where the engagement took place. It should be a hall mark of good practice that process learnings are shared and tools are developed as well as results documented.