I’ve previously shared an introduction to Liberating Structures, the methods that filled the “facilitation gap” in my own continuous improvement practice. These 4 Liberating Structures have been most important to my continuous improvement practice.

During planning

• Ecocycle Planning—an initial conversation that can help an uncertain or newly formed team figure out what to work on. Starting with a portfolio-level listing of major systems or responsibilities, people locate each of those in its overall lifecycle. The resulting ‘ecocycle’ is a big picture of things that need fixing, things that could be skillfully closed down, and things that need to be nurtured into further growth. There’s your schedule of continuous improvement projects.

During an improvement activity

• TRIZ—a scavenger hunt for existing system behaviors that produce bad outcomes. Purposefully designing a broken system is fun. Then, insight comes when people look for similarities between the bad system they’ve imagined and the way things get done today. TRIZ lets groups see how their collective work is both interrelated and necessary—and where there is room for creative destruction.
• 25/10 Crowdsourcing—a machine for generating bravery, starting with the question: “If you were ten times bolder, what big idea would you recommend?” The activity ends with a tantalizing presentation of the weirdest ideas that were elevated or supported by the whole group. There will be a few ideas you can go do right away, ‘ten times bolder’ premise be damned.

Afterwards

• What/So What/Now What—a group closing reflection and commitment. Can scale up or down, but this is the smallest possible closing that helps people make sense of what happened and to decide what’s next.

Look, they’re all good

There are dozens of Liberating Structures. Even if you are familiar with some of them, others will be new. I encourage you to seek them out. For example, I only started using Ecocycle Planning in the last year or so, but it has already gotten me out of a couple real pickles.

“Five conventional structures guide the way we organize routine interactions and how groups work together: presentations, managed discussions, open discussions, status reports and brainstorm sessions. Liberating Structures add 33 more options to the big five conventional approaches.”

So much of continuous improvement comes down to gathering a small group of people together (ideally with snacks) and opening a space so that everybody can decide what to do next.

The Lean books and teachers I learned from taught me what needed to happen—the observations, diagrams, analysis, ideas, and plans—but couldn’t convey how to get all this to occur within groups of people who were happy, unhappy, skeptical, annoyed, burned-out, eager, curious, tired, distracted, in pain, lost in thought, worried, hungry, or optimistic.

Facilitation is its own separate skill.

Like the other so-called “soft skills,” it is hard as hell.

But eventually, Liberating Structures gave me the methods I needed.

No new thing under the sun

Each Liberating Structure is a recipe for a small, generative group interaction. Flip through the collection and you’ll find short definitions and plenty of examples, along with detailed, insightful facilitation guides.

As you explore, many of the formats and activities might seem familiar—and for good reason. Very little of this work is original, which is why nearly all of it is useful. For example, the What, So What, Now What? Liberating Structure is one particular expression of a device you might have seen in academic or business writing (as Chris Argyris’ ladder of inference) or in community development (my teachers at the Institute of Cultural Affairs call it ORID, an unlovely contraction of “objective, reflective, interpretive, and decisional”). The point of this particular Liberating Structure isn’t to be innovative, but instead to give just enough structure to help a group to listen and reflect on its shared experience. And it, like all the others, is offered with attribution and links to further reading to satisfy the eggheads.

Most of the Liberating Structures are small, with time commitments beginning at around 15 minutes. As you practice them, you may find yourself planning events by chaining a sequence of Liberating Structures together. There’s even a Liberating Structure for having group plan its own event—what my friend Dan calls choreography, but the Liberating Structure is called Design Storyboards.

And Liberating Structures are a great boost to continuous improvement efforts because they loosen up hierarchies and create new ways for people to learn from one another. This is an important part of Lean, and it’ll happen eventually—but some carefully deployed Liberating Structures can help things along. Some of the structures, like Ecocycle Planning, fit directly into the portfolio planning and management systems that sustain continuous improvement over time.

Getting started

The stuff is available online and is free to use. Read up on the Liberating Structures web site, starting with the LS Menu.

I recommend the excellent, free LiSA app for your phone or iPad. (LiSA also runs on recent Macs.) LiSA is great for quick reference, as well as for working out an agenda using a chain of Liberating Structures.

Beyond that, the very best way to learn Liberating Structures is to watch, do, and teach. (It’s also the best way to learn anything.) For this purpose, my friend Alyssa recommends this monthly international, online meetup.

Big changes, small changes

It’s only fair to let the Liberating Structures folks have the last word. Because what they want is what I want, too:

“We want everyone to learn to foster big changes by inviting people to make small structural changes in how they work together.”

Identify project risks using this fun, thought-provoking 15-minute method to capture wisdom from the people who know best—those who will do the work and those who will be affected by it.

It’s the venerable project premortem.

I recommend this method if you’re leading a project in your own organization. And if you’re a consultant, like me, it can be a significant information-seeking behavior at the beginning of a project.

The underlying capability is prospective hindsight. Here’s a definition from Gary Klein, in his HBR piece from 2007 on premortems:

Prospective hindsight—imagining that an event has already occurred—increases the ability to correctly identify reasons for future outcomes by 30%. We have used prospective hindsight to devise a method called a premortem, which helps project teams identify risks at the outset.

The premortem is not a new idea—this 2007 article popularized the technique. However, I keep using it because each time I do, I learn things that are valuable to know at the beginning of a new project—and particularly with a new client.

The power of the premortem is this:

1. People will just tell you things if you ask them nicely.
2. And if you ask using prospective hindsight, they will come up with surprising answers, sometimes even mentioning their organization’s ‘undiscussables.’

A few things I’ve learned from premortems

• That the current effort was the second attempt, and therefore doomed to failure for the same reasons the first effort failed.
• That the current effort was the third attempt, etc.
• The existence of a specific policy making the intended change impossible, and that policy-makers were not involved in designing or selecting the project.
• That the ongoing budget to support this work had already been allocated to a particular technology, program, or team.
• That people don’t trust or believe their leadership, or the project’s sponsors, or one another.
• Various discoveries about an organizational problems in communication and clumsiness in making changes.

These were all things worth learning quickly—as in, cheap and early—so that possibilities remained for adjustment or better awareness of the environment.

Here’s how it’s done: running your premortem

1. Before the meeting, write a simple scenario. Something like: “It is December and our project has failed spectacularly. As the first snow falls, we gather together and ask—what happened? Why did this fail?” Be precise about the future date: maybe 2 months after the presumed project completion; link the date to some major event or local seasonality.
2. Schedule 15 minutes in a project kick-off meeting to run the premortem.
3. At the start of the premortem, state the scenario and ask the question.
4. Allow 1-3 minutes for individual reflection.
5. Offer an anonymous feedback form and invite participants to provide their responses. Clearly state how you will use these, for example, that individual responses remain anonymous, but you will share themes and takeaways with the group and with project sponsors.
6. After the individual reflection time is complete, open up for a brief discussion across whatever participation modes are available. Acknowledge and thank people for their responses. Do not attempt to problem-solve or diagnose right now, but make it clear you’ll be doing so later. If project sponsors, execs, etc. attend, you will have to coach them on this behavior in advance, the message being: we’re listening now, we’ll problem-solve afterwards.
7. Close with sincere thanks and by telling people where and when you’ll share takeaways from the premortem—ideally with planned remediations for each.

An encouragement

The project premortem concept may seem a little weird. It is.

But it’s a great way to show up and listen. The simple act of listening to people and adjusting based on what you hear is wonderful.

And, almost as a side effect, the things people mention might be the things that doom the project to failure—or the things that, adjusted and kept in mind, might make it a great success.