A team is told to use “Yes, And” in a brainstorming session. People smile, avoid criticism for ten minutes and then return to the same decision patterns as before. The phrase was present. The practice was not.
The common misunderstanding
In improvisation, “yes” does not mean that a character approves of everything. It means the performer accepts the reality that has already been created. If my scene partner says we are on a delayed train, I cannot improve the scene by insisting we are in a submarine because I prefer my own idea.
In organisational life, accepting reality is equally different from approving it. A deadline moved. A customer is unhappy. A dependency exists. A colleague has raised a concern. Saying “yes” to the existence of that information is the beginning of a useful response—not the end of critical thinking.
The “and” is a commitment to contribute. It asks: given what is now true or offered, what can I add that helps us move?
Acceptance is not agreement. It is the refusal to waste energy arguing with what is already present.
Blocking often hides in professional language
Teams rarely say “no” as directly as improvisers do in a beginner scene. Blocking can sound more sophisticated: “We tried that already,” “That will never pass governance,” “The architecture does not support it,” or “Let us come back to this when we have more data.”
Any of those statements may contain a legitimate constraint. The blocking pattern appears when the constraint ends the shared thinking instead of shaping it.
A more generative response preserves the constraint and adds movement: “The current architecture cannot support that volume. Could we test the customer need with a smaller segment while we assess the platform change?” The response has not become less rigorous. It has become more useful.
Four workplace versions of the practice
Teams do not need to repeat the words “yes, and” in every meeting. The principle can show up in more natural language:
- Acknowledge and extend: “I see the risk you are naming. I would add one dependency we should test.”
- Constraint and option: “We cannot use that route under the current policy. We could achieve the same outcome this other way.”
- Difference and connection: “I see the priority differently. We agree that the customer impact has to be visible in the decision.”
- Question and contribution: “What would need to be true for this to work? I can help validate the billing impact.”
When not to use it
Applied improvisation should not be used to suppress disagreement, override boundaries or pressure people into supporting a decision. A clear no is necessary when something is unsafe, unethical, outside authority or simply not a good choice.
The practice is most valuable before the decision closes: while the group is trying to understand, generate or build. It improves the quality of the material available for judgement. It does not remove judgement.
Max Grillo is an applied improvisation facilitator. He manages and hosts Rice Cookie Improv, is co-founder of Monday Flow Improv and is a member of the Applied Improvisation Network. He combines workshop practice with more than 25 years of experience in technology and transformation.
More about Max