Experience is essential in a complex system. It can also make a team reject an idea before the idea is fully heard because someone remembers a similar attempt, a previous architecture or a constraint that existed three years ago.

The sentence that closes the room

We tried that already may be completely true. It can still close the wrong conversation. The previous attempt may have used different technology, served another customer group or failed for a reason that no longer exists.

Inside a specialist team, history becomes shorthand. Everyone knows the old story, so nobody explains it. An outsider hears the conclusion but not the assumptions underneath it.

That gap can be useful. The outsider is not there to prove the experts wrong. They are there to ask what the team has stopped asking itself.

Fresh eyes add value when they help experts inspect an old conclusion, not when they pretend expertise is unnecessary.

Useful ignorance needs a structure

In Getting to Yes And, Bob Kulhan with Chuck Crisafulli describes a silo exercise on print pages 164 to 166. A team working on a real challenge is joined by one or two people from another department who do not know the history. The group first generates ideas without rejecting them, then evaluates them with curiosity about the thinking behind each suggestion.

The sequence matters. If evaluation begins immediately, the established team can explain why every outside idea is impossible. If generation never moves into judgement, the result is an interesting list with no responsibility.

The value appears between those phases. The team asks what the outsider noticed, which assumption created the suggestion and whether part of an old solution could work in a new context.

I see this at functional boundaries

Billing, finance, customer service and technology can look at the same issue and see different systems. A billing expert may focus on rating and invoicing. Finance may see cash flow and control. Customer service may see explanation and trust.

None of those perspectives is complete by itself. The outside participant often asks a basic question that reveals a hidden handover or a word that two functions use differently.

I would use this practice for a problem that is real enough to matter but not so political that an outsider is entering an ambush. The host team must genuinely want another perspective.

Protect both expertise and curiosity

The outside participant should contribute to the top of their intelligence, not perform confidence about a domain they do not know. Questions, analogies and observations are valid contributions.

The specialist team should explain constraints during the evaluation phase without using history as a weapon. Instead of that cannot work, try naming the condition that would need to change.

The final decision remains with the people responsible for the work. Opening the thinking does not remove accountability. It improves the material available for judgement.

Browse all improv exercises for listening, creativity, collaboration and leadership

Sources used

About the author

Max Grillo is an applied improvisation facilitator. He has participated in more than 700 improv workshops and accumulated more than 10,000 hours of improv practice. He co-manages and co-hosts Rice Cookie Improv, is cofounder of Monday Flow Improv and is a member of the Applied Improvisation Network. He has facilitated improv in Munich since 2017 and brings more than 25 years of experience in technology and transformation.

More about Max