It’s good to have Dave Snowden back from his treks in the Himalayas. He’s been a big influence on my thinking and practice over the past few years and his near daily blog posts are always rich, irreverent and practical. He is in the process of creating an important body of theory and practice that is useful even if the language and the concepts are sometimes a lot of work to grasp. The payoff from wrestling with his ideas is rich.
Today he’s discussing “dispositionality” which simply means that making change in a system is much easier when you have a sense of what the system is pre-disposed to do (and what it is NOT pre-disposed to do…)
Back in the summer Caitlin and I led a learning lab for the board and staff members of various community foundations from around British Columbia. The five principles that Dave articulated today were very much embedded in our work and they are becoming very much the basis for any change and planning work I do. Here’s how we made it work, pen and paper style.
1. Map the current state of the system, including its dominant flows, eddy points and whirlpools.
We began with a World Cafe design based on small stories of change. It is always good to ask people about actual decisions or stories that they remember to ground their experience in discovery. If you run a cafe on “What are the big sources of change in our sector?” you get a data set that is divorced from reality, meaning that it is subject to being gamed by the participants. I can just insert the things I want to see in there. But if I am asked to tell a story about a particular decision I had to made, the data set is richer and we have a good chance to see emerging patterns.
And so our Cafe ran like that: “Tell a story of a time when you knew things needed to change?”
Each person told a story and the other three at the table listened and wrote down what they heard was the impetus for change, with one data point on a post-it note. We did several rounds of story telling. At the end of the round, we asked people to give the post-its to the story teller, and we gave the story tellers time to rank each post it note on a scale of 1-3. A one meant that the impetus for change was just known to me (a weak signal), two meant that a few other people know about this impetus, and a three meant that this change trigger was known by everybody.
We then had the group cluster all the post-its to find major categories, and we sorted post it notes within the categories to produce a map that was rendered by our graphic recorder, Corrina Keeling. You can see that above.
2. Identify the energy gradient associated with existing dominant patterns and what adjacent possible states to any undesirable pattern present themselves.
The resulting map shows the major areas for change making, specific “acupuncture points” and the “energy gradients associated with the dominant patterns.” Practically what this means is that items marked in yellow were very weak signals and could be candidates for a change initiative that would appear out of left field for the dominant system. Not a bad thing to do, but it requires a lot of resources and political capital to initiate. The red items were things that EVERYBODY was talking about, which meant that the space for innovation was quite closed down. There are a lot of experts, large consulting firms, influential funding pots and politically committed people tackling change at this level because it is perceived to be an influential place to play. As a result it is generally a zone that is not failure tolerant and so these items are not good candidates for a probe or prototyping approach.
But the orange items were in a kind of Goldilocks zone: there are a few people who know that you can make change here, so you have allies, but the field is not cluttered with competing experts trying to assert their ideological solutions.
The whole map allows you to make choices.
3. Engage in safe-to-fail experiments in parallel either to change the energy gradient or to nudge (or shift) a dominant pattern to a more desirable state ideally through action rather than platitude.
This is of course the best approach to making change within complex systems. We took time to develop prototypes that were intended to tell us something about the system. A bonus would be that we might might create ideas that would turn into interesting new initiatives, but the primary function of running prototypes is to probe the system to tell us something about what is possible. Making tentative conclusions from action inspires people to try more, on a path that is a little more blazed. Just creating platitudes such as “Let’s build networks for knowledge transfer” doesn’t do enough to help change makers poke around and try things that are likely to work.
Each participant in the group created one or two prototypes which they rolled out, seeking to make a bit of change and learn about what helped or hindered change making in a relatively conservative sector of civil society.
4. Monitor the impact in real time and take multiple small actions to reinforce the good and disrupt the bad.
We kept the group together over a few months, having them check in over webinars to share the progress on their prototypes. We deliberately created a space where things were allowed to fail or radically change and we harvested learning all the way along. Where things were working, prototypes evolved in that direction, and we had a little funding to help accelerate them. By simply starting, participants discovered oblique strategies and in some cases entirely new ways to address their basic desire for changing some element of their environment. Without engaging in a deliberate yet loosely held action-based project, it is very difficult to see the opportunities that lie in the blind spots.
This learning was summarized in a report, but the bigger harvest was the capacity that each participant built to take steps to sense, design and implement change initiatives with a better informed complexity approach.
5. At all costs avoid any announcement of a change initiative or idealistic outcome based targets
I think this goes without saying. Change making in the complex space is essentially learning on overdrive. When we are truly stuck and yet we have a sense that “this might just work” we need good support to explore that instinct. Being deliberate about it helps. But announcing that “this is what we are doing and here are the targets we have to meet” will collapse people’s inherent creativity down to narrowing the focus of their work on achieve the pre-determined outcomes. That is a perfect strategy for destroying the capacity to engage with complexity, and it can result in a myopic approach to change that guarantees “black swan events” and other nasty surprises.
Just finished out first day of work with Navajo Area Health Promotion practitioners and 30 community wellness workers, Elders and healers from across the Navajo Nation. We are blending an Art of Hosting workshop with content and process from some recent research in neuroscience, epigenetics, and adverse childhood experiences and with wellness and leadership models from our Navajo colleagues with whom we have a ten year relationship.
One of the pieces of work we are doing is supporting these folks in launching or accelerating some community based projects using the social networks they have in place here. This will involve us spending time in Open Space tomorrow and on Friday running a ProAction Cafe in which 6-8 projects will be able to to be developed. As a way of grounding these projects in patterns that are useful for this context we spent this afternoon generating a Navajo pattern language for resiliency. We did this with a two round World Cafe in which we asked for stories of supporting resiliency and stories of leadership challenges. This is a kind both/and appreciative inquiry. At the conclusion of the Cafe, I asked people to reflect on one teaching or piece of advice that would be useful based on the discussions. I invited them to write a word or a phrase on one side of an index card and write some explication on the back.
The attached collection of 27 or so patterns include both expected patterns such as “Presence” and “Listening.” They also include some Navajo principles like “Ádáhodí?zin” meaning ‘Letting our children go, to learn and discover who they are.”
On Friday we will use these principles to help design projects. I’ll hand a few out to each project proponent and ask them to take a few minutes to brainstorm how to incorporate these pieces of ground tested advice in their project design.
Today a client emailed me with a small anxiety about setting up a meeting room in a circle. The work we will do together is about rethinking relationships in a social movement and the concern was that it was already unfamiliar enough territory to work with. Setting up the room in a circle might cause people to “lose their minds.” I get this anxiety, because that is indeed the nature of doing a new thing. But I replied with this email, because I’m also trying to support leadership with my client who is doing a brave thing in her calling:
This morning we began our Harvesting and Collective Sensemaking online course. Rowan Simonsen, Amy Lenzo and I were really excited to be able to share our first little insights with people, and especially this new mnemonic that we created to capture five key principles of harvesting practice: PLUME. We are excited to introduce this into the world.
Just about to leave Montreal this morning for Toronto and north to Thornbury, Ontario to visit family. I was here for the conference of the Canadian Evaluation Society, where I participated on a panel on innovative dialogue methods (and yes I noted the irony in my remarks) and later led a World Cafe where I presented some of the sense-making processes I’ve been working on. I was here on the recommendation of Junita Brown who has been in some good conversations with evaluators around the use of the World Cafe for evaluation purposes. Originally Amy Lenzo and I were scheduled to host a cafe here that was much more ambitious: a plenary cafe with the participants to explore the learning field of the conference. Through various machinations that was cut back to a panel presentation and a very small world cafe at the end of the day with 16 people. The conference was one of those highly scripted and tightly controlled affairs that I hardly ever go to.
The session before us was a case competition where student teams were responding to a mock RFP from Canada World Youth to evaluate an Aboriginal Youth leadership Program. Not a single team had an Aboriginal person on it, and every single presentation was basically the same: full of fundamental flaws about what constitutes success (“Did the youth return to their communities”) or what constitutes a cultural lens (“We are using a medicine wheel to understand various parts of the program). One group of fresh faced non-Aboriginal students even had the temerity to suggest that they were applying a decolonizing strategy. Their major exposure to indigenous communities was through a single book on decolonizing methodology and some internet searches about medicine wheels. It was shocking actually, because these were the students that made the finals of this competition. They looked like fresh versions of the kinds of evaluation firms that show up in First Nations certain they know what’s going on.
To make matters worse, the case competition organizer had a time mix up with the conference planner meaning that our panel started 30 minutes late which gave me very little time to present. As I as doing a a cafe directly afterwards I ceded most of my time to my panel colleagues Christine Loignon, Karoline Truchon who did a very interesting presentation on their use of PhotoVoice. It was clear to me at the conference that the practitioners among us had a better grasp of complexity theory, power and non-linear sense-making than any of the professional evaluators I met.
I presented most of the work that I have been documenting here over the last few months, and later led a small group through a cafe where we engaged in the creation of a sensemaking framework and used a pen and paper signification framework.
By far the better experience for me was hanging out with friends and colleagues. On the first night I arrived I had dinner and drinks with my friends from Percolab: Paul Messer, Samatha Slade and Elizabeth Hunt. We ate fish and chips, drank beer and whisky and caught up. On Sunday I met Jon Husband for lunch on the grass at McGill with his delightful godson and then joined the Percolab folks for a visit to the new co-operative ECTO co-working space on Mount Royal in the Plateau, followed by a barbeque with family and friends.
And Last night, after my presentations a great evening with Juan Carlos Londono and Lisa Gravel. We had dinner at Lola Rosa and spent hours going over the new French translation of the GroupWorks Pattern Language Deck. This was a brilliant time. I learned a bunch of new French words and most fun of all we discussed deeper etymology, nuance and the limitations and benefits of our respective languages in trying to convey some of the more esoteric practices of hosting groups. The new deck has some beautiful reframing and some names for patterns that need some work. But it’s exciting to see this translation and I always love diving into the language.
I really do like Montreal a lot and in the past number of years come to love it more as I have lost my inhibition about speaking French. the more French I speak, the more French I learn and the more the heart of the city opens up. Many English Canadians have the idea that Montreal is a cold hearted city to English speakers, but I find that isn’t true at all. Just offer what you can in French and people open up. And if you’re lucky enough to sit down with lovers of words like the friends I have, your learning explodes.
Off for a couple of days to visit family and then home to Bowen Island for a series of small local facilitation gigs, all of which will tell me something deeper about my home place.