If you are as much as a complexity theory geek as I am becoming, you might appreciate this map by Brian Castellani that links to the founders of the various branches of complexity science. The map is described as “s a macroscopic, transdisciplinary introduction to the complexity sciences spanning 1940-2015. ” It is a fantastic resource because each of the founders of a branch of this science are represented by links to archives of their work. You could read for hours. Days even.
A couple of years ago I wrote a post that was critical of the way in which the Representative for Children in Youth in British Columbia drove practice changes among social workers. In short the reason had to do with apply too much order (rules and checklists) in a complex space (social work practice). At a certain point, when you are trying to prevent deaths that have occurred in the past, you end up outlawing all but the deaths that will surprise you in the future. We look at reviews of child deaths as if they were expected and predictable and create highly ordered accountability mechanisms to prevent them from happening again. The problem with this, as anyone knows who works with complexity, is that you create a break between good social work practice which is sensitive to nuance and context, and rigorous accountability standards. While no one is arguing that social workers should not be accountable, what is required is the ability for social workers to develop and rely on their practice, because no amount of rules will prevent children from dying in novel ways, but good social work practice does have an effect. In fact, checklists over practice almost ensure children will die in increasingly novel ways because as social work becomes constrained simply to what is on the checklist, social workers narrow their gaze too much and are unable to detect the weak signals in a situation that would otherwise anticipate a problem before it happens. This is the dilemma between anticipatory and predictive awareness and getting it wrong is costly.
It’s a brutal example, but I do believe it points to the the consequences of accountability models that assume that all outcomes are predictable and negative effects can be prevented with best practices even when its proven that they can’t be. (the confusion in that link is perfectly illustrative, by the way. “Child deaths are preventable” on the one hand and “we lack the most basic information about why children die” on the other.) That can be true in ordered systems but not in complex ones. This particular problem has a major implication for philanthropic organizations that are seeking to have “impact.” In many cases, the impact is a pre-defined outcome of a process taken largely in a narrowly defined strategic context. Real life is messy but logic models are sweetly and seductively clean.
Messiness is important and working in messy ways is a critical skill of philanthropic workers, donors and directors. In this recent article Martin Morse Wooster argues for a loosening of constraints on philanthropic work and although he doesn’t provide a solid theoretical basis for his assertions, but good theory on the limits of managing and measuring impact backs him up.
Many front line philanthropic workers – grants administrators, programs staff and consultants – know this approach but they are often constrained by donors, Boards and executives who demand simple outcomes, simple metrics and clear impact. I’m increasingly interested in putting together specific trainings and learnings for boards and donors that will increase their literacy of messiness in support of making smart changes and supporting good in a way that is much more aligned with how community actually works.
One such offering is currently open for enrolment. We are gathering in June in Glasgow and will be repeating the workshop in October in Vancouver. If you’d like it in your neck of the woods, let me know.
For a long time I have known that the idea that culture change can be managed is a myth. A culture is emergent and is the result of millions of interactions, behaviours, artifacts and stories that people build up over time. It is unpredictable and results in surprise. The idea that a “culture change initiative” can be rolled out from the top of an organization is not only a myth, it’s a hidden form of colonization. And worse, the idea that people need to be changed in the way the boss determines if we are to become the kind of place that we all aspire too is cruel and violent.
So what to do when an organization says that its culture needs change? Until I had stumbled over David Snowden’s work, I had few practical tools, principles and practices for doing this work. Since working with the theory that Dave has assembled and translating it into praxis, I have come up with a number o
Here are a few key notes for working with people who ask me to help them with that.
Principles
- Culture is an emergent set of patterns that are formed from the interactions between people. These patterns cannot be reverse engineered. Once they exist you need to change the interactions between people if you want to change the patterns.
- Culture includes stories but it is not a story. This is important because simply changing the story of the organization will not change the culture. Instead you need to create ways for people to interact differently and see what comes of it.
- Cultural evolution is not predictable and cannot be led to a pre-determined character. You can aspire all you want to a particular future culture but it is impossible to script or predict that evolution.
Practices
- Start by getting clear about the actual work. In my experience people use the term “culture change” as a proxy for the real work that needs to be done: improving employee relations, becoming more risk tolerant, shifting leadership styles…whatever it is, it’s best to start with getting clear what is ACTUALLY going on before assuming that the problem is the “culture.”
- Look at what actually is. Studying the way things are is important, because that helps you to identify what you are actually doing. It seems simple, but it’s important to do it in a way that doesn’t bring a pre-existing framework to the work. You have to look at the patterns from the work that you already do, not from how it illuminates a pre-existing model.
- Work with emergence to understand patterns together. Using tools such as anecdote circles, organizations can discover the patterns that are present in the current environment. Anecdote circles generate small data fragements that describe actual actions and activities. Taken together and worked through, patterns become clear, like the process of generating a Sierpinsky triangle. Out of large data sets, hidden patterns appear.
- Identify those patterns and discuss ways to address them with safe to fail experiments. Run a session to create several ideas that are coherent with the patterns, design multiple small experiments to try to shift the patterns. Institute rigorous monitoring and learning and allow for experiments to fail.
- Support new ideas with appropriate resources. If you really want to change the interactions between people you need to resource these changes with time, money and attention. The enemy of focused innovation is time. Even allowing employees to work on something a half day a week could be enough to create and implement new things. Butif they have to do it on top of the full workload they have, nothing will get done.
- Learn as you go. Developmental evaluation is they way to go with new forms of emergent practice. To be strategic about how change is happening, it’s important to design and build in evaluation at the outset.
These are just notes and practices, but are becoming standard operating procedures in my world when working with groups and organizations who are trying to address that elusive idea of “culture change.”
Last weekend I took a ramble across Bowen Island, where I live, with a friend and colleague, Annemarie Travers. Annemarie and I have been teaching the Leadership 2020 program for a number of years now and we both love walking: she on the long pilgrimages of the Camino and Shikoku and me in the mountains of southern British Columbia. We are also both interested in managing in complexity.
My friends over at the Social Labs Revolution website have been fielding questions about the prototyping phase of labwork and today published a nice compilation of prototyping resources. It’s worth a visit. It got me thinking this morning about some of the tools I use for planning these days.