How to Totally Ruin a Rollout: What TRIZ Taught Us About Hidden Risks

Sometimes the fastest way to understand what good looks like is to ask a deliberately uncomfortable question: How could we totally ruin this? That was the question I used during a retrospective with my team before an important rollout.

Instead of starting with the usual “What went wrong?” or “What should we improve?”, I wanted us to look at the situation from a completely different angle. So we used TRIZ - also known in Liberating Structures as Creative Destruction.

Its purpose is not simply to imagine failure. It is to identify the activities and behaviours that prevent us from achieving what we really want - and deliberately stop them to make space for something better. And that is exactly what happened.

Start with the nightmare scenario

The first question was simple: How to totally ruin the rollout? The team started listing everything that could make the rollout fail. Some ideas were realistic. Some were exaggerated. Some were funny. That was exactly the point.

TRIZ works well because it introduces a kind of serious play. Once people are invited to design a disaster on purpose, they stop trying to give the “right” answer. They become more creative. They say things they might otherwise avoid saying. And suddenly risks, behaviours, and assumptions that had been sitting quietly in the background become visible.

Instead of asking people directly: “What are we doing wrong?” we asked: “What would we have to do if we really wanted this rollout to become a mess?” That shift changed the energy in the room.

The most important question came next

The first part was fun. The second part was much more interesting: Which of these do we already do?

That is where TRIZ becomes more than an exercise in imagination. The team had already created a list of behaviours, conditions and decisions that could damage the rollout. Now we had to look at that list honestly and ask: Are any of these already happening? Not necessarily in an extreme form. Not because anyone wants the rollout to fail. But perhaps in smaller, everyday ways.

This is the moment when the abstract worst-case scenario starts becoming useful. The conversation is no longer about “what might theoretically go wrong”. It becomes about patterns we can actually recognise. And this is the real value of Creative Destruction: not simply identifying risks, but making counterproductive behaviours visible.

Why this works

Direct questions about problems can make people defensive. If I ask: “What are we doing badly?” - the question already contains judgement. People may start explaining, defending, or looking for someone responsible.

TRIZ creates distance. At first, we are talking about an imaginary disaster. That makes it easier to explore uncomfortable ideas. Only later do we bring the conversation back to reality. And by then, the team has already named the patterns themselves. That matters.

As a facilitator, I do not need to arrive with a diagnosis. The structure helps the team discover it.

From hidden patterns to concrete action

The third question on our board was: What will we stop or change? This was important because I did not want the retrospective to end with an impressive collection of risks and no action.

We looked at the patterns we had identified and asked:

• Which of these can we influence?

• Which behaviours should we stop?

• What needs to change before the rollout?

• What would create more space for a better outcome?

• Where should we start?

The result was not a theoretical risk register.

We left with concrete takeaways. Some risks were less serious than they had first appeared. Some became much more visible. And some were connected to behaviours or ways of working that the team could actually change. That distinction matters.

Not every possible problem deserves the same amount of attention. The useful question is not only “What could go wrong?” but also: What are we already doing that makes the wrong outcome more likely?

What changed in the conversation

The biggest difference was not the list of risks. It was the quality of the conversation. Instead of discussing problems only after they happened, we were able to talk about them before they became incidents.

Instead of asking who was responsible, we looked at the conditions and behaviours that could make failure more likely. Instead of trying to predict everything, we focused on what we could stop, change, or influence.

The team also seemed more comfortable discussing difficult scenarios because we approached them indirectly first. Paradoxically, imagining failure created more safety for talking about reality. That is one of the reasons I find TRIZ so useful. It combines humour, exaggeration, and reflection in a way that can make a difficult conversation easier to enter.

TRIZ is not really about negativity

At first glance, TRIZ can sound pessimistic. Why would a team deliberately focus on the worst possible outcome? Because the purpose is not to stay in the worst-case scenario. The purpose is to expose what gets in the way.

Creative Destruction is about deliberately identifying counterproductive activities and behaviours, then stopping them so that better ideas and practices have room to emerge. When we exaggerate failure, patterns become easier to see. We can ask:

• What would make this fail?

• Are we already contributing to any of those conditions?

• What should we stop doing?

• What should we change?

• What do we need to protect or strengthen instead?

That turns negative imagination into practical learning.

A simple version you can try

You do not need a complicated setup. For a rollout, change initiative, project, or difficult team situation, try three questions:

1. How could we completely ruin this?

Invite exaggeration. Let people be creative. Do not correct or evaluate ideas too quickly.

2. Which of these things are we already doing?

This is the critical step. Look for similarities, even if reality is less extreme. This is where the team starts recognising counterproductive patterns.

3. What will we stop or change?

Choose a small number of actions the team can actually influence. Do not try to solve everything. The goal is not to create a perfect plan. The goal is to stop what gets in the way and create enough space for better behaviour to emerge.

What I learned as a facilitator

This retrospective reminded me of something I see repeatedly in teamwork: The quality of the answer often depends on the quality of the question. If I ask a predictable question, I will often get predictable answers. If I ask, “What went wrong?” I may hear the same issues the team has already discussed several times. But if I change the perspective, people notice different things.

TRIZ permitted the team to think differently. And my role was not to tell them what the risks were. It was to create a structure in which they could see the patterns themselves.

That is the kind of facilitation I find most valuable. Not bringing a ready-made answer. Creating the conditions for a better conversation.

Sometimes the opposite question gets us closer to the truth

We often try to improve things by asking directly what success should look like. That is useful. But sometimes the opposite question reveals more.

What would make this fail?

What would we have to do to create the worst possible outcome?

Which of those patterns are already present?

What should we stop doing to make room for something better?

Once we see that, the way forward often becomes much clearer. It is not magic. It is Creative Destruction: making counterproductive patterns visible, stopping what gets in the way, and creating space for something better. And sometimes that is exactly what a team needs.