Hmmm…maybe I should have let the group do this…
When I popped off to London last week to take a deep dive into Cognitive Edge’s work with complexity, one of the questions I held was about working with evaluation in the complex domain.
The context for this question stems from a couple of realities. First, evaluation of social programs, social innovation and other interventions in the human services is a huge industry and it holds great sway. And it is dominated by a world view of linear rationalism that says that we can learn something by determining whether or not you achieved the goals that you set out to achieve. Second, evaluation is an incredibly privileged part of many projects and initiatives and itself becomes a strange attractor for project planning and funding approval. In order for funders to show others that their funding is making a difference, they need a “merit and worth” evaluation of their funds. The only way to do that is to gauge progress against expected results. And no non-profit in its right mind will say “we failed to achieve the goals we set out to address” even though everyone knows that “creating safe communities” for example is an aspiration out of the control of any social institution and is subject to global economic trends as much as it is subject to discrete interventions undertaken by specific projects. The fact that folks working in human services are working in a complex domain means that we can all engage in a conspiracy of false causality in order to keep the money flowing (an observation Van Jones inspired in me a while ago.) Lots of folks are making change, because they know intuitively how to do this, but they way we learn about that change is so tied to an inappropriate knowledge system, that I’m not convinced we have much of an idea what works and what doesn’t. And I’m not talking about articulating “best practices.”
The evaluation methods that are used are great in the complicated domain, where causes and effects are easy to determine and where understanding critical pathways to solutions can have a positive influence on process. in other words, where you have replicable results, linear, summative evaluation works great. Where you have a system that is complex, where there are many dynamics working at many different scales to produce the problems you are facing, an entirely different way of knowing is needed. As Dave Snowden says, there is an intimate connection between ontology, epistemology and phenomenology. In plain terms, the kind of system we are in is connected to the ways of knowing about it and the ways of interpreting that knowledge.
I’m going to make this overly simplistic: If you are working with a machine, or a mechanistic process, that unfolds along a linear trajectory, than mechanistic knowledge (problems solving) and interpretive stratgies are fantastic. For complex systems, we need knowledge that is produced FROM the system and interpreted within the system. Evaluation that is done by people “outside” of the system and that reports finding filtered through “expert” or “disinterested” lenses is not useful for a system to understand itself.
Going into the Cynefin course I was interested to learn about how developmental evaluation fit into the complex domain. What I learned was the term “disintermediated sensemaking” which is actually the radical shift I was looking for. Here is an example of what it looks like in leadership practice.
Most evaluation uses processes employing a specialized evaluator undertaking the work. The problem with this is that it places a person between the data and experience and the use of the knowledge. And it also increases the time between an experience and the meaning making of that experience, which can be a fatal lag with strategy in emergent systems. The answer to this problem is to let people in the system have direct experience of the data, and make sense of it themselves.
There are many many ways to do this, depending on what you are doing. For example:
- When clustering ideas, have the group do it. When only a few people come forward, let them start and then break them up and let others continue. Avoid premature convergence.
- When people are creating data, let them tag what it means, for example, in the decision making process we used last weekend, participants tagged their thoughts with numbers, and tagged their numbers with thoughts, which meant that they ordered their own data.
- Produce knowledge at a scale you can do something about. A system needs to be able to produce knowledge at a scale that is usable, and only the system can determine this scale. I see many strategic plans for organizations that state things like “In order to create safe communities for children we must create a system of safe and nurturing foster homes.” The job of creating safe foster homes falls into the scope of the plan, but tying that to any bigger dynamics gets us into the problem of trying to focus our work on making an impact we have no ability to influence.
- Be really clear about the data you want people to produce and have a strategy for how they will make sense of it. World Cafe processes for example, often produce scads of data on table cloths at the centre of the table, but there is often so little context for this information that it is hard to make use of. My practice these days is to invite people to use the table cloths as scratch pads, and to collect important data on post it notes or forms that the group can work with. AND to do that in a way that allows people to be tagging and coding the data themselves, so that we don’t have to have someone else figure out what they meant.
- Have leaders and teams pour over the raw data and the signification frameworks that people have used and translate it into strategy.
These just begin to scratch the surface of this inquiry in practice. Over the next little while I’m going to be giving this approach a lot of thought and try it out in practice as often as I can, and where the context warrants it.
If you would like to try an exercise to see why this matters try this. the next time you are facilitating a brainstorm session, have the group record dozens of insights on post its and place them randomly on a wall. Take a break and look over the post its. Without touching the post its, start categorizing them and record your categorization scheme. Then invite the group to have a go at it. Make sure everyone gets a chance to participate. Compare your two categorization schemes and discuss the differences. Discuss what might happen if the group were to follow the strategy implicit in your scheme vs. the strategy implicit in their scheme.
This afternoon I’m coming home after a morning running a short process for a church in Victoria, BC. The brief was pretty straightforward: help us decide between four possible scenarios about our future. Lucky for me, it gave me an instant application for some of the stuff I was learning in London last week.
The scenarios themselves were designed through a series of meetings with people over a number of months and were intended to capture the church’s profile for its future, as a way of advertising themselves for new staff. What was smart about this exercise was the fact that the scenarios were left in very draft form so there was no way they could be confused for a “vision” of the future. It is quite common in the church world for people to engage in “visioning exercises” to deal with the complex problems that they face, but such visions are doomed evermore to failure as the bigger organization is beginning to enter into a period of massive transformation and churches are suffering from all kinds of influences over which they have no control.
Visioning therefore is not as useful as selecting a lens through which the organization can make some decisions.
Each scenario contained some possible activities and challenges that the church would be facing, and the committee overseeing the work was charged with refining these down to a report that would, to use my own terms, be a collection of heuristics for the way the organization would act as it addressed future challenges.
Our process was very informed by some thinking I have been doing with Dave Snowden’s “Simple rules for dealing with complexity.” Notably principles about avoiding premature convergence, distributing cognition and disrupting pattern entrainment. Furthermore, the follow up work will be informed by the heuristic of “disintermediation” meaning that the team working on the project will all be working with the raw data. There is no consultants report here. The meaning making is still very much located with the participants.
So here was our process.
- At small tables of four, participants were given 5 minutes to read over the scenarios silently.
- We then entered a period of three 15 minute small group conversations on the topic of “what do you think about these scenarios?” Cafe style, each conversation happened with three different groups of people. I was surprised how much introduction was going on as people met new folks. The question was deliberately chosen not to be too deep or powerful because with a simple question, the participants will provide their own depth and power. When you have a powerful need, you don’t need to contrive anything more powerful than what people are already up for.
- Following the cafe conversations, a round of silent reflection in which people were given the following direction. “Express your preference for each of the scenarios on a scale of 1-7. Seven means “Let’s do it” and one means “No Way.” For each scenario write your preference on your post it and write a short sentence about the one concrete thing that would make your vote one point higher.” So there is lots in this little exercise. First it’s a way of registering all of the objections to the scenarios without personalizing them. Secondly it gets at concrete things that the team can do to improve scenarios and third it harvest preferences and not simple yes/no decisions which are not appropriate for this kind of work.
- At each table someone gathered all the posts its of the same colour and by colour folks came to the front and placed them on the scale. Doing it this way meant that no one was sure whose preference was going where and it also meant that people couldn’t revise their post its once they saw how the preferences were being expressed.
The whole thing took about 75 minutes.
The result of this sense making was the chart you see above. Two hundred pieces of finely grained information ordered by the people themselves. The project team now has at least three things they can do with this material.
- They can recreate the scale, as each post it is colour and preference coded. That way they have a rough idea of the scenario with the greatest support, and they can show anyone who wants to see metrics where we stand on the proposals.
- They can cluster post its for each scenario according to “work that will make it better” which means they don’t have to pay attention to the scale. The scale is completely subjective, but each of these post-its contains one piece of concrete information to make the scenario better, so in some ways the numbers don’t really matter. They can cluster these ideas by each scenario AND they can re-cluster them by each topic to give an idea of overall issues that are happening within the organization.
- If we wanted to go a step further, we could use these post it notes to do a number of Cognitive Edge exercises including a Cynefin contextualization (which would tell us which things were Obvious, Complicated and Complex (and maybe Chaotic) and we could also do some archetype extraction which might be very useful indeed for constructing the final report, which would stand as an invitation to thier new personal and an invitation to the congregation.
I had the great pleasure of coaching a team of folks last night who were running their first World Cafe. I’ve been working with this crew for a while – a core team looking at the future of the Victoria Presbytery of the United Church of Canada – and this was the first time they’ve stepped up to run their own conversational process as part of our work. Last night it was a Cafe to sense the future of what the Presbytery could be and do. And they did great.
One of the advantages of coaching is that one gets to reflect on the little bits and pieces of practice that make things work. Last night a number of them came up, so I thought I’d share them here.
Give instructions one at a time. Don’t give a long list of instructions. At the beginning of the Cafe let people know how the time will flow, but when it comes time to invite people to do certain things (move between tables, change questions, reflect, summarize…whatever) just give one instruction at a time. It is important that people know WHY we are doing a thing, but not important that they have the whole flow. And especially if your instruction involves them moving, then don’t give any more instructions until they have stopped.
Invite people to mark the paper early. The paper in the middle of the table is for all to use. “Typical” facilitated sessions imprint people with the pattern that someone will take notes while everyone else talks. It’s important that before the conversation begins, you invite people to pick up a marker, write something and draw something on the paper in front of them. That way, before the conversation begins, folks know that the paper is for everyone to use, there is no top or bottom, and images and words are equally welcome.
Have one more marker and one fewer post it note than people. If you have tables of four, give them five markers. This means that people can trade colours without prying a marker from someone’s hand. And if you are summarizing key findings, have three post-its for a table of four, to encourage people to pick three things together rather than just having everyone put their best thought down. World Cafe is about tapping and making visible collective intelligence. You lose that if you just have individual thoughts.
Build in silence. At the conclusion of a round, have a minute or two of silence. It calms the room down, allows people to reflect and integrate what they are hearing and makes it easier to give directions. This is especially important if you are wanting people to raise their level of awareness from what is important personally to what patterns are emerging. It requires a shift in awareness to see that.
Collect post its before having a summary conversation. Last night we used post its at the conclusion of the third round to capture the patterns that people were hearing consistently in all three rounds. Collecting the post-its before we had a summary conversation meant that people couldn’t “report out” and instead we hosted a “conversation with the whole” whereby we roved around asking people what stood out for them. What emerged was indeed a conversation and not a boring reporting out of things that everyone knew anyway.
Avoid the temptation to use a different question for each round. This is important. Having a different question for all three rounds creates three shallow conversations and inhibits pattern finding. It can also leave people feeling like they are being led down a garden path and it doesn’t leave a lot of space for emergent conversation. For all Cafe beginners, I always suggest they do their first Cafe with a single question for all three rounds. This gives you a clear picture of how the process can work to surface COLLECTIVE intelligence.
Keep the question simple and broad and make sure you can answer it on your own. Trust the group. They want to have a conversation, not guess at answers that you are trying to get them to. Last night our question was simple; given a context in which the structures of the Church are becoming increasingly unsustainable and in which congregations still need to be connected on a local level “What should Presbytery be and what should it do?” That was it. Three rich rounds on that, with lots of great insight and some amazingly courageous admissions (“Time to finally admit that this structure is dead.” etc.)
Invitation matters. Even though the 50 people we had out last night are used to being together every few months, the core team mworked on their invitation for a month. They held the purpose of the event close (discovering what the new shape and function of the Presbytery could be) and they shared the question with participants, even before we had decided on what the final question was. The team made sure people RSVP’d on the invitation which helped us to know the logistics of food and space, and also gave a chance for the conversation to begin as folks started sharing what they were thinking right away. This primed the conversation and meant that people were really ready for the work. Ninety minutes was not enough.
Know what you will do with the harvest and tell people. People learned in the invitation what our plans were for the harvest. This even was about helping the core team design some experiments over the next year for new ways that the Presbytery could meet and be useful to the two dozen United Church congregations on southern Vancouver Island. We summarized the patterns that people found (above photo) and began right away writing a report. But the bigger piece of work will be engaging in design over the next couple of months to create new and interesting gatherings in line with what the Presbytery members actually want.
Caitlin Frost, Tim Merry, Tuesday Ryan-Hart and I have been loving offering our Art of Hosting Beyond the Basics workshop over the past nine months.
We’re really pleased to announce that we are coming to Minnesota May 6-8, Staffordshire UK July 8-10 and Ontario this fall. And we’re really happy with the video invitation.
If you have been working with participatory methods and are curious about extending these tools and forms of leadership to systemic challenges, please consider joining us!
in this video, Organizational practices applied by Tim Merry he talks about an organization that adopts basic practices to restore humanity to its structures. Predicated on the idea that the quality of results are directly dependant on the quality of relationship in the organization, he describes using circle practice as a simply way to activate relational capacities in a team.
The link between relationship and results is well established. It is the basis of relational theory and is a core assumption underlying a whole world of organizational development thinking and practice, including the Art of Hosting.
Good relationships are fundamental but not completely exclusive to getting great results. It is also important that people in the organization are skilled for the work they are doing and that there is a clarity about what we are trying to achieve. Skills include the technical skills needed to do the job as well as adaptive skills needed to be able to respond to changing conditions. Clarity includes personal and collective clarity of purpose.
i find that many organizations excel in a technical skills focus and spend a lot of time on clarifying organizational purpose through strategic plans and the operational plans that are meant to connect everyone in an organization to the central purpose.
And what passes for good management is this technical axis of organizational life. It is privileged by using terms like “hard skills” and when push comes to shove the “softer side” of organizational life is often sacrificed in favour of strict accountability to the plan.
Restoring relational skills is often the first step to stabilizing a team that has lost its way. I have worked with highly skilled team – for example in university professional faculties – where there is no shortage of extremely talented individuals and an audacious but achievable drive to be the best of their kind in their market. But very often highly skilled and committed people get into tough disputes with one another as egos clash and personal purposes become more important tha organizational ones. Over time toxic environments can appear that, when combined with the unskillful use of power and authority, can create pain and trauma in organizations. Almost everyone I know has a story of this. It is absolutely rife in organizational life as we seek to balance self-fulfillment with collective strategic direction.
What Tim points to, and what we cover in the Art of Hosting, including in our offering on Beyond the Basics, is that a restorative approach to human relationships can steady the ship. This means taking time away from strictly strategic objectives in order to attend to relationships. And it is not simply a thing that happens in offsite meetings to deal with organizational conflict. It is about instituting practices – such as week-starting and week-ending circles – to discuss strategic objectives, and to do so in a way that honours and deals with the struggles that naturally occur as we try to do things we’ve never done before.
A weekly practice of PeerSpirit Circle for example becomes a strategic leverage point for better organizational life and more humane working environments. It doesn’t replace technical skills or organizational goals, but it ties those things to personal aspirations and provides a rich ground for creativity, adaptability, cohesion and sustainability