Liberating Structures is a toolkit of more than 40 facilitation formats designed to make sure everyone involved can contribute their ideas. For testers, formats such as Troika Consulting help sharpen the understanding of requirements, and TRIZ helps uncover risks and possible failure scenarios. Good starting points are liberatingstructures.com, liberatingstructures.de, and local user groups.
Key Takeaways
- Liberating Structures counter the HiPPO effect: when the highest-paid person in the room speaks first, everyone nods along and valuable ideas from the team get lost.
- In Troika Consulting, the person asking for help literally turns around so the other two can discuss the problem without nonverbal interruptions, which forces structured listening.
- Risk-based testing often fails in practice because Excel risk lists disappear on a network drive, while test-related risks such as unstable test environments never make it onto them.
- Liberating Structures only work when there is a concrete problem behind them. Trying out methods for their own sake is as pointless as retrospectives whose results nobody follows up on.
What Liberating Structures Are
Liberating Structures are a toolkit of facilitation formats built to bring everyone in the room into the discussion. They start from a simple assumption: every person in the room has good ideas. What usually keeps those ideas from surfacing is the typical meeting culture, not a lack of substance.
Traditional facilitation relies on one person standing at the front and calling on people. Liberating Structures push that idea further. Instead of leaving the steering to a facilitator, they give the group a structure that makes participation unavoidable. Hence the name: structure that frees people up.
Everyone knows the workshop pattern these methods get around. Half the group sits there and says nothing. When the manager speaks, every head turns toward them. There is a name for it, the HiPPO effect: highest paid person’s opinion. Everyone nods, the boss must be right. Liberating Structures are meant to get teams out of exactly that trap.
Christian Kram uses these methods in his daily work at a self-organized company without traditional bosses. When nobody makes the final call based on hierarchy, the group needs a communication framework that gets it to a decision. It saves the 45 minutes of talking around the actual question.
1-2-4-All: From One Person to the Whole Group
1-2-4-All is one of the core structures and a good place to start, because the name already describes how it works. Everyone first thinks alone for one minute. Then pairs exchange ideas for two minutes. Two pairs join into a group of four, and at the end the whole group comes together.
The strength lies in this step-by-step build-up. Nobody can sit it out, because everyone has to put their own thought into words at the start. No one gets through without contributing.
Something else happens when the thoughts come together that doesn’t happen in individual work. New ideas appear when two old ones meet. In the pairs and foursomes, solutions come up that nobody had thought of alone. Christian Kram uses the format when a new topic is introduced, for example to collect expectations for new office space.
Troika Consulting: Sharpening Test Cases by Listening
Troika Consulting gathers structured feedback on a problem of your own, and the key is enforced silence. Three people form a group. One brings a question, the other two give advice, and the person who asked has to stay quiet for part of the time.
The sequence is tightly timed. First, the person asking presents the problem in about a minute, for example: “How should I read user story XY?” or “What else do we need to watch out for?” The other two then ask clarifying questions. After that, the person asking turns around and listens while the two discuss the problem behind their back and sketch out solutions. Only once that timebox is over can they respond.
For testers, the format is a way to get a firmer grip on the test basis and to question requirements before writing test cases. Instead of drafting test cases alone, you get input early and check your understanding against two other minds. After a quarter of an hour, you have a first round of useful feedback.
Turning around is more than a symbolic gesture. It takes the nonverbal side out of play. The two advisors can’t see whether you frown, and you can’t jump in right away. Many people find it hard to listen, especially when it is their own topic. That is exactly what the method trains.
TRIZ: Uncovering Risks without Excel Wallpaper
TRIZ uncovers risks by having the group deliberately exaggerate and play out the worst case. The guiding question is: what could go really, badly wrong? Exaggeration is explicitly encouraged.
One of the principles behind Liberating Structures is to break up existing structures and make progress by failing forward. TRIZ does that in a playful way. In one team, the provocative question about a volcanic eruption led a participant to a real issue: the data center sat right on the Rhine, and there had been problems there before.
After the exaggeration comes a sober reality check. Which of these bad scenarios have we actually run into? That produces the first major risk factors and a rough direction for planning.
This touches a sore spot in many test strategies. Risk-based testing gets promoted a lot, but teams often lack a practical way into it. A risk analysis ends up as Excel wallpaper on a shared drive that hardly anyone opens. It lists the grand, galaxy-sized risks. The mundane local ones are missing: an unstable test environment, a tight testing window. A dedicated risk manager doesn’t think about those.
“The person wearing the shoe knows best where it pinches. The people who are affected afterwards usually know best where the real risks are.”
(Christian Kram)
Impromptu Networking: Building a Shared Understanding of Quality
Impromptu Networking quickly brings different perspectives on a question to light by discussing the same question in changing pairs. Everyone first thinks briefly about a topic, for example: “What does quality mean to me?” or “What do we need to do to test this user story properly?”
Then come short timeboxes of two to four minutes in which two people talk. After each round, partners switch, again and again. That way you collect the views of several colleagues one after another.
The difference from a round-robin is easy to feel. When people talk one after another around a circle, you tune out by the fourth or fifth person at the latest. In a one-on-one conversation, you communicate differently and stay involved. Christian Kram likes to use the format with groups whose members don’t know each other yet, for example to ask why everyone is there in the first place.
It fits the expectation in agile teams today that quality is not just the testers’ job. Developers, product owners, and UX designers all shape quality together. A shared understanding at the start is the foundation for that.
Methods Need a Problem, Not a Purpose of Their Own
Liberating Structures only work when they solve a concrete problem. Using a method because it looks new and trendy gets you nowhere. As soon as a team notices that a real question is being answered, the skepticism fades quickly.
Reservations are normal, especially in larger organizations with long-serving staff. “Now we’re sitting in a circle? What does he want from us?” Christian Kram runs these formats anyway, even at C-level, because Liberating Structures are something you experience rather than something you explain. People who have taken part once are often convinced.
The key is a concrete goal in the room: What should our test strategy look like? What obstacles do we expect in the next test phase? Then everyone sees right away that results come out of it. That is true beyond these methods. Doing exploratory testing just so you can post about it afterward is equally pointless.
Many people know the same trap from retrospectives. They get held dutifully, the results end up as a spreadsheet on a drive or a note in a drawer, and nothing happens. Next time, people rightly ask what the point is. Ideally, a structure ends with an idea or a direction that somebody then follows up on. Without that follow-through, any method stays without consequence.
How the Methods Combine into a Sequence
Individual structures can be chained into a sequence called a string. Different methods serve different purposes, and that is exactly what makes combining them work.
Some structures bring things into the open. Others help you question something. Still others help set a strategy or derive actions. A typical string moves from uncovering to questioning to concrete actions.
This rough grouping helps when choosing. The overview below sorts the methods mentioned here by purpose.
| Method | Purpose | Typical Use in Testing |
|---|---|---|
| 1-2-4-All | Collect and condense ideas | Introduce new topics, clarify expectations |
| Troika Consulting | Get feedback on your own problem | Understand the test basis, prepare test cases |
| TRIZ | Uncover risks | Identify risk factors for test planning |
| Impromptu Networking | Align perspectives | Build a shared understanding of quality |
Where to Learn and Practice Liberating Structures
The easiest way in is through the websites and local user groups. There is liberatingstructures.com, and for German speakers liberatingstructures.de. Together they now describe more than 40 structures, each with instructions.
A useful feature on the German site is a selection tool that asks what problem you want to solve and suggests matching structures. If websites feel too old-fashioned, there is also a Liberating Structures app for Android and iOS, and the Android version is said to be decent.
The strongest recommendation goes to user groups and meetups. They exist in Hamburg, Frankfurt, and East Westphalia, among other places, plus groups such as The Liberators, who run workshops regularly. There you can try the methods without having to deliver a result in a work setting. That is how the enthusiasm starts for many people: go along one evening, join in, and walk out hooked.
Frequently Asked Questions
Why do the opinions of just a few people often prevail in meetings?
It’s usually the meeting culture that’s to blame, not a lack of substance within the team. As soon as a manager expresses an opinion, everyone turns to look at them and nods in agreement. This is known as the HiPPO effect: “highest paid person’s opinion.” Half the group sits there silently. Liberating Structures, on the other hand, provide the group with a framework that forces participation.
What’s the benefit of working on a topic first alone, then in pairs, and then in groups of four?
This step-by-step process prevents people from sitting it out: Anyone who spends a minute at the beginning formulating their own thoughts alone can’t get away without contributing. When the ideas are brought together, something emerges that individual work alone cannot produce. Two old ideas become one new one, and in the pairs and groups of four, solutions emerge that no one had thought of on their own before.
How can a tester verify their understanding of requirements before writing test cases?
By presenting their problem to two colleagues and then deliberately remaining silent. This is how Troika Consulting works: The person asking the question presents it in about a minute; the other two ask clarifying questions; then the first person turns away and listens while the others discuss the matter behind their back. In a quarter of an hour, there’s useful feedback on the test basis.
Why does risk-based testing so often fail in practice?
Because teams lack a practical way into it. The risk analysis ends up as an Excel spreadsheet on a shared drive, where hardly anyone ever looks at it. It lists the big, global risks. The mundane, local risks are missing: an unstable test environment, a tight testing window. A dedicated risk manager doesn’t think about those. Those who wear the shoes know best where they pinch.
How does a team identify risks that aren’t on any official list?
One approach is deliberate exaggeration. TRIZ asks what could really go wrong and has the group run through the worst-case scenario. In one team, the provocative question about a volcanic eruption led to a real concern: the data center was located right on the Rhine, and there had already been problems there. This is followed by a comparison to see which scenarios have actually occurred before.
How do you align understanding of quality in a mixed team?
Impromptu Networking is well-suited for this: The same question, such as one about each person’s understanding of quality, is discussed in time boxes of two to four minutes in rotating pairs. Unlike in a round-robin discussion, where people tend to tune out by the fourth person at the latest, everyone stays engaged. In an agile environment, developers, product owners, and UX designers collaborate on quality anyway.
How do you combine multiple facilitation formats into a meaningful process?
You string them together into a “string,” a sequence of multiple structures. The combination works because the formats serve different purposes: some bring things to light, others help raise questions, and still others lead to a strategy or specific actions. A typical string progresses from uncovering issues, through questioning, to concrete actions. This framework makes the selection process easier.
What helps counter skepticism when a team rejects unfamiliar formats?
A specific goal on the table, such as the question of the future test strategy or obstacles in the next testing phase. As soon as a team realizes that a genuine question is being answered, skepticism quickly dissipates. Explaining doesn’t help much, but experiencing it does. Consistency is also important: If a structure ends without an idea or direction that someone follows up on, it remains inconsequential, like an unprocessed retrospective.
