Spent an hour in conversation with a friend in the US last night discussing the role of dialogue in connecting communities together. My friend has extensive experience working with immigrant, refugee communities and in working with inner city agencies. He’s been personally affected by Trump’s travel edict as his family members are directly targetted by the current travel ban. He’s a man I respect very much.
We were talking about ways to connect and understand the “other side.” After our conversation I stumbled over this podcast on the “deep story” of what is motivating Trump supporters, and probably both Brexit supporters and other Europeans struggling with how the world is changing and how they perceive their privileges coming apart. We talked about how there is always a thin slice of people that will never sit down with “the other.” We also spoke about the many main street Republicans who feel abandoned by their party and have done since the Tea Party took it over. It comes down to the fact that arguments on economics and policy cannot overrule the emotional aspects of identity, especially when people feel those identities are under assualt through no fault of their own.
In her new book, Strangers in Their Own Land, sociologist Arlie Hochschild tackles this paradox. She says that while people might vote against their economic needs, they’re actually voting to serve their emotional needs
The image of standing in line to get your rewards and watch people stream past you is compelling. It’s one thing to deconstruct this image with data and facts, but first it’s important to understand it and how people deeply FEEL it.
Deep story is fascinating to me. Here in my home community of Bowen Island, we experience tensions from time to time over our deep story. We all have ideas about what we think this place is and who we think we are. To some extent that story is an illusion born in our world views and our desires. In a place like Bowen Island, where most of us moved here from somewhere else, our own deep story includes the deep motivation that brought us here.
And deeper beneath the personal deep story we bring is the emergent and slowly changing story of the island’s identity. Over the last couple of years, as a member of our local Economic Development Committee, I have worked with friends and colleagues to understand our deep story. Once you can see it, it reveals the deep yes’ and deep no’s that make things happen or hold things back. People are often surprised by things that go on in our little community, but understanding the deep story helps to explain where these things come from.
When you understand the deep story, you can find deep places to connect together and important places of engagement and curiosity. Dialogue gets more interesting as we set out to learn about each other, what we care about, what we assume is true, and what is essential to our identity. Strategy that does not take the power of identity into consideration creates implementation plans that will inevitably endure oblique assaults on its efficacy. Understanding the deep story and identity of a place or a person is essential to resilience, collaboration and peacemaking across difference. A healthy community can hold different stories in all their complexity, even when those stories conflict with each other. An unhealthy community pits one story against another, and cynical leaders do the same.
We have a choice as citizens. This podcast helps us become resourceful in making that choice.
When I was up in Whitehorse last week I got to spend time with folks from the Public Service Commission discussing a project that would see us looking at discriminations in the workplace from a complexity angle. Using Cynefin and SenseMaker(tm), we hope to understand the ways in which the landscape of discrimination shifts and changes over time so that the PSC can make wiser decisions about the kinds of initiatives it sculpts. One of the problems with diversity initiatives in the public service (in any large public organization really) is the feeling that they need to be broad based and rolled out to everyone. This usually results in a single initiative that spreads across the whole organization, but except for a little awareness raising, does little to address specific instances of discrimination. Everything from awareness raising “cultural competency training” to zero tolerance accountability measures have limited effect because a) discriminatory behaviour is highly context and situation dependant and b) the public service has a permeable boundary to the outside world, meaning ideas, behaviours and people move between the two contexts all the time. The larger your organization, the more like the real world you have to be.
At any rate, I took a bit of time to do a mini-Cynefin teaching to explain how strategy works in the complex domain. and my friend Pawa Haiyupis and I added two Ps to my concentric circles of intervention in a complex system. So to review:
- Patterns: Study the patterns in a complex setting using narrative capture and sense-making. This can be done with the SenseMaker(tm) software, and it can also be done with dialogic interventions. The key thing is to let the people themselves tag their stories or at the very least have a group of people reviewing data and finding patterns together. For example, you might notice a correlation between stressful times in an organization and an increase in feelings of discriminatory behaviour
- Probe: Once you have identified some patterns, you can make some hypotheses about what might work and it’s time to develop some safe to fail probes. These aren’t meant to be successful: they are meant to tell you whether or not the patterns you are sensing have developmental potential. Failure is entirely welcome. What if we offered stress reduction activities during high stress times to help release pent up feelings? We want to be okay with te possibility that that might not work.
- Prototype: If a probe shows some promise, you might develop a prototype to develop a concept. Prototypes are designed to have tolerance for failure, in that failure helps you to iterate and improve the concept. The goal is to develop something that is working.
- Pilot: A pilot project is usually a limited time proof of concept. Roll it out over a year and see what you learn. In Pilot projects you can begin to use some summative evaluation methods to see what has changed over time. Because of their intensive resource commitment, pilot projects are hardly ever allowed to fail, making them very poor ways of learning and innovating, but very good ways to see how stable we need to make an approach.
- Project/Program/Policy: Whatever the highest level and most stable form of an initiative is, you will get to there if your pilot shows promise, and the results are clear. Work at this level will last over time, but needs regular monitoring so that an organization knows when it’s time to tinker and when it’s time to change it.
Cynefin practitioners will recognize that what I’m writing about here is the flow between the complicated and the complex domains, (captured by Dave Snowden’s Blue dynamic in this post.) My intention is to give this some language and context in service organizations, where design thinking has replaced the (in some ways more useful) intuitive planning and innovation used in non-profits and the public service.
Since October, when I first starting sketching out these ideas, I’ve learned a few things which might be helpful as you move through these circles.
- Dialogue is helpful at every scale. When you are working in a complex system, dialogue ensures that you are getting dissent, contrary views and outlying ideas into the process. Complex problems cannot be addressed well with a top-down roll out of a change initiative or highly controlled implementations of a single person’s brilliant idea. If at any point people are working on any stage of this alone, you are in danger territory and you need another pair of eyes on it at the very least.
- Evaluation is your friend and your enemy. At every stage you need to be making meaning and evaluating what is going on, but it is critically important to use the right evaluation tools. Developmental evaluation tools – with their emphasis on collective sense making, rapid feedback loops and visible organizational and personal learning – are critical in any complexity project, and they are essential in the first three stages of this process. As you move to more and more stable projects, you can use more traditional summative evaluation methods, but you must always be careful not to manage to towards targets. Such an error results in data like “We had a 62% participation rate in our diversity training” which tells you nothing about how you changed things, but can shift the project focus to trying to acheive a 75% participation rate next cycle. This is an especially pervasive metric in engagement processes. And so you must…
- Monitor, monitor, monitor. Intervening in a complex system always means acting without the certainty that what you are doing is helpful. You need data and you need it on a short term and regular basis. This can be accomplished by formal and informal ongoing conversations and story captures about what is happening in the system (are we hearing more stories like the ones we want?) or through a SenseMaker(tm) monitoring project that allows employees to end their data with a little data capture.
- These practices are nested, not linear. An always to remember that this is not a five step process to intervening in a complex system. In a large organization, you can expect all of these things to be going on all the time. Building the capacity for that is a kind of holy grail and would constitute a 21st century version of the Learning Organization in my books.
I remember when I worked in the federal government, one of my roles was acting as part of an internal facilitation team. This team was put together by a director in who had an interest in organizational development. This was back in the late 1990s and we didn’t really have in house OD units which was a blessing. Instead we had this team of people that were interested in systems thinking, development and facilitation and we were made available by our bosses to do work within the organization. I cut a lot of my hosting teeth in that context.
I remember that we once led a little informal experiment. We were finding that much of what we heard when we ran sessions in the organization was platitudes of a kind of aspired set of values and stories. But when you went on the road with people, especially senior people, you’d get the real stories. This is where anyone wanting to go into management was going to get their real mentorship training. My job involved a lot of travel so I heard a lot of these stories.
We called these “tie off” stories, because when senior managers travelled in the public service at that time, they used to take their ties off and just wear an open collar shirt and a blazer. (This seems to have become a mark of high status these days, but back then it was a kind of relaxing of protocol) When the tie came off the stories flowed. And travelling around remote British Columbia communities pre-World Wide Web and smartphone, means you get a lot of time kicking back in hotel bars and airports and avalanche detours. With no Netflix to watch, no mobiles to check and no email to get through, there was nothing left but storytelling. (By the way, I rarely learned anything deeply personal about people in these settings. Personal stories were strictly available only when your senior manager was completely casual. I learned early on that the uniforms of business are like the gels used in the theatre lighting to change the colour of the stage light: suits and jeans and ties filtered the person. People were always “authentic” but their uniforms constrained and shaped what was coming through.)
A small group of us resolved to spend a year listening to these stories and comparing them to stuff we heard in formal planning processes and at the end of a year we basically concluded that there were two different organizations: one that was a performance for the bean counters and the accountability police, all tidied up into reports, memos and budgets and the other which was a mess of story, rumour, gossip, cobbled together work-arounds, covered up failures and surprising results. When citizens wonder why government seems to be such a mess of bureaucratic boondoggle, saying one thing and doing another, they are noticing an actual phenomenon. Part of the reason for this phenomenon is that the second set of characteristics and stories is how things actually get done, but the first set is the story the public (and the Minister) wants to hear.
You cannot have innovative change without a mess. And very few organizations, especially it seems in the public sector, allow for mess making to happen. Whatever we learn, it has to be packaged up into something neat and simple, and preferably replicable. It bothers me to this day that citizens demand one without the other. I think citizens need to be a bit more grateful about the way public servants get things done in spite of the overwhelming demand to simplify processes and guarantee results in what is a massively complex job.
I was back at St. Aidan’s United Church in Victoria yesterday, hosting another conversation in their continued evolution into their next shape. Last December we worked together to explore four possible scenarios that were being proposed for the congregation. In the past few months they have been working on implementing one of these scenarios – the one which featured a plan to develop a Spiritual Learning Centre. Yesterday was a short strategic conversation called to explore the shape of what that Centre could be and how it will change life at the church.
A couple of good blog posts in my feed this morning that provoked some thinking. These quotes reminded me how much evaluation and planning is directed towards goals, targets and patterns that cause us to look for data that supports what we want to see rather than learning what the data is telling us about what’s really going on. These helped me to reflect on a conversation I had with a client yesterday, where we designed a process for dealing with this.