Beyond Icebreakers: Improv and Agile for Feedback and Continuous Improvement

Working without complete certainty

When I enter an improv scene, I do not know exactly where it will go.

That does not mean I enter without skills, experience or intention. It means accepting that the scene will also be shaped by my scene partners, by new information and by whatever emerges in the moment.

I recognise the same condition in my work with agile teams. We may have a product vision, a plan and a set of priorities, but we cannot know everything in advance. Customer needs change. Technical constraints appear. Assumptions turn out to be wrong.

The Agile Manifesto values responding to change over following a plan. Its principles also encourage frequent delivery, collaboration, self organising teams and regular reflection followed by adjustment.

In both worlds, I have learned to treat a plan as a useful starting point, not as a promise that reality is obliged to respect.

The question I return to is: what is happening now, and what does it invite us to do next?

Learning instead of looking right

I have felt the pressure to appear competent in both environments.

On stage, when I become too concerned with looking clever, I stop listening. Instead of contributing to the scene, I start protecting my own performance. I have seen the same instinct in project work when we hide uncertainty, defend an unsuccessful decision or continue with a weak solution because changing it might look like an admission of failure.

Patti Stiles explores this distinction in her essay “Focus: Self or Process”. She describes how focusing on personal success can separate an improviser from the group. Focusing on the process makes the player more aware, flexible and ready to support whatever the work needs.

Rereading that essay reminded me why this is one of the strongest connections between improv and agile. If my objective is to prove that I was right, feedback feels threatening. If my objective is to improve what we are creating together, feedback becomes useful information.

I find that this small change of focus transforms the conversation.

• What did we notice?
• What helped the work move forward?
• Where did we lose information or connection?
• What could we try in the next iteration?

Feedback without judgement does not mean avoiding honesty

I have been in rooms where people say they want an open feedback culture, but that phrase can describe two very different experiences.

In one room, we are respectful and honest. We discuss what worked, what did not work and what we want to try differently.

In another, we remain pleasant but avoid anything uncomfortable. Everyone sounds supportive, while the important observations stay outside the meeting. The official retrospective is positive. The real retrospective happens later, between two people in the corridor.

I do not experience the second room as psychologically safe. To me, it feels like politeness mixed with uncertainty.

In “A Matter of Opinion”, Patti Stiles argues that a supportive improvisation culture still needs honest discussion. Mistakes create opportunities to learn, but those opportunities disappear when every observation that is not positive is treated as an attack.

Her distinction between an opinion and a judgement gives language to something I have experienced many times. An opinion offers a perspective we can examine together. A judgement presents that perspective as an unquestionable fact.

In a retrospective, I would rather hear “I did not hear about the change until the testing phase, and that left us with two days to adapt” than “There was no communication”. I would rather hear “When the concern was raised, we moved to the next topic without discussing it” than “You never listen”. The first version gives us something specific to investigate. The second judges a person or the entire team.

When I ask for a non judgemental environment, I am not asking people to avoid disagreement. I want us to disagree without reducing anyone to the problem we are discussing.

Feedback should help the next attempt

What I value in feedback is whether it can influence the next attempt.

When I returned to “Post Show Notes”, I was struck again by Patti’s description of notes as information for learning and improvement. She warns against notes that serve the status or ego of the person giving them, because those notes create fear rather than curiosity.

I have seen the same danger in organisations. A retrospective can become a performance of authority: the most senior person explains what went wrong, someone creates a list of actions for everyone else, and the meeting produces a document without making the team better at noticing or adapting.

The approach I find more useful is to treat feedback as a shared enquiry:

• Describe what you observed.
• Explain the effect it had on the work.
• Stay curious about other perspectives.
• Choose one change that the team can actually test.
• Observe what happens in the next cycle.

Without another attempt, feedback remains an opinion about the past. With another attempt, it becomes part of the learning process.

The environment comes before the method

From both improv and transformation work, I have learned that the environment comes before the method.

I can schedule a daily meeting, but that alone will not make a team agile. I can repeat “Yes, and” in a workshop, but that alone will not make a group collaborative. What matters is whether the surrounding environment allows the practice to become real.

• Can people admit that they do not understand something?
• Can someone question an established approach without being labelled difficult?
• Can the team examine a failed experiment without searching for a person to blame?
• Can a junior participant influence the direction of the work?
• Can people change their minds when new information appears?

If the answer is no, more ceremonies and more games will not solve the underlying problem.

Make the system visible through play

This is why I use improvisation in my work. It makes these dynamics visible. During a simple exercise, I can see how quickly we stop listening when we try to control the result. We can feel what happens when an offer is ignored, when a mistake is supported or when another person changes the direction of the work.

For me, the exercise creates a small version of the system. The reflection afterwards is where I help the group connect that direct experience to everyday work.

Process is not the opposite of results

I am not arguing that outcomes are unimportant. In my professional work, organisations need results, products need to work and customers need value. On stage, an improvised performance still needs to engage an audience.

What I can influence more directly is the process: how carefully I listen, how quickly we test assumptions, how openly we share information and how intelligently we respond to what we discover.

I do not believe a healthy process guarantees the perfect result. I do believe it makes useful results more likely and makes us more capable when reality changes.

This is what improv and agile have most deeply in common for me. They replace the impossible demand to know everything in advance with a more practical discipline: pay attention, contribute, learn, adjust and continue.

For me, that is much more than an icebreaker. It is a way of working.