Offers and Blocks
metaphor established
Source: Improvisation → Collaborative Work
Categories: arts-and-culture
Transfers
In improvisational theater, every contribution a performer makes is an “offer” — a gift of new information, emotion, or situation that the scene can build on. A partner who accepts the offer (“yes, and…”) advances the scene; a partner who rejects it (“no, that’s not happening”) “blocks” the scene and kills its forward momentum. Keith Johnstone codified this vocabulary in Impro (1979), and it became foundational to improvisation pedagogy worldwide.
Key structural parallels:
-
Any contribution is an offer — an offer is not limited to dialogue. A gesture, a spatial choice, a silence, an unexpected reaction — all are offers that create possibilities. The structural insight is that collaboration advances through the accumulation of small, accepted contributions, not through master plans. In a brainstorming session, a half-formed idea is an offer. In a code review, a suggestion is an offer. In a negotiation, a concession is an offer. The vocabulary gives teams a way to notice and name what they are actually doing when they collaborate.
-
Acceptance builds; blocking destroys — when a partner says “yes, and…” they accept the reality the offer established and add something new. The scene grows. When they block — “no,” “that wouldn’t happen,” “let’s go back to…” — the scene collapses to nothing and must restart. In organizations, blocking looks like: “we tried that before,” “that’s not how we do things here,” “let me play devil’s advocate.” Each block forces the conversation back to zero. The metaphor makes visible how much organizational energy is spent restarting conversations that were blocked rather than built upon.
-
The ensemble outperforms the individual — in improv, a mediocre player who accepts every offer creates better scenes than a brilliant player who blocks. The structural claim is that responsiveness matters more than originality. A team of average contributors who build on each other’s offers will outperform a team of exceptional individuals who compete for control. The metaphor transfers this insight to any collaborative context where the quality of interaction matters more than the quality of any single contribution.
-
Blocking is often unconscious — performers block not from malice but from fear, habit, or the desire to look clever. The vocabulary makes blocking visible as a specific, nameable action rather than a vague interpersonal problem. Once a team has the word “block,” they can notice it happening and choose differently.
Limits
-
Improv has no stakes — if an improv scene dies, the performers start another one. In business, a bad idea accepted and built upon can cost money, reputation, or safety. The metaphor’s implicit instruction — accept offers, do not block — carries no mechanism for evaluating whether an offer is worth accepting. “Yes, and let’s invest in this failing product” is technically an acceptance that builds, but it may also be a disaster.
-
“Blocking” conflates rejection with evaluation — the metaphor makes all forms of “no” look structurally identical: an engineer saying “that approach has a race condition” and a manager saying “we don’t do things that way” are both blocks in the improv vocabulary. But the first is critical evaluation that prevents harm, and the second is organizational inertia. The metaphor provides no way to distinguish constructive criticism from destructive blocking, which can lead teams to suppress necessary objections in the name of collaborative flow.
-
Power asymmetry breaks the frame — improv assumes rough parity between performers. In organizations, a junior employee’s offer carries different weight than a VP’s offer. Telling a junior employee to “yes, and” the VP’s bad idea is not collaboration; it is compliance. The metaphor’s egalitarian assumptions do not survive contact with hierarchy.
-
The metaphor romanticizes spontaneity — improv scenes are ephemeral by design. Software, contracts, buildings, and policies are not. The “yes, and” ethos is well suited to generative phases (brainstorming, ideation, early prototyping) but poorly suited to convergent phases (editing, testing, shipping) where selective rejection is the primary value-creating act. Teams that never learn to block are teams that never ship.
Expressions
- “Yes, and…” — the foundational improv acceptance, now used in corporate brainstorming and facilitation as shorthand for building on ideas rather than rejecting them
- “That’s a block” — naming a conversational move that shuts down creative possibility, used in team retrospectives and workshops
- “Make your partner look good” — Johnstone’s extension of the offer principle: the goal is not to be clever but to make the other person’s contribution work
- “Gifts” — alternative vocabulary for offers, emphasizing that every contribution is something given rather than something imposed
- “Yes, but…” — the concealed block, technically acknowledging the offer while undermining it with a qualification
Origin Story
Keith Johnstone developed the offers-and-blocks vocabulary at the Royal Court Theatre in London in the 1960s and published it in Impro: Improvisation and the Theatre (1979). His insight was that improvisation fails not because performers lack imagination but because they reflexively block each other’s contributions out of fear. The vocabulary spread through Theatresports (competitive improv, which Johnstone also invented) and was adopted by the Second City and iO theaters in Chicago. In the 2000s, the “yes, and” principle crossed into business culture through books like Truth in Comedy (Halpern, Close, Johnson 1994) and corporate improv workshops offered by groups like Second City Works. By the 2010s, “yes, and” had become one of the most widely cited principles in design thinking and innovation culture, often stripped of its theatrical origins.
References
- Johnstone, K. Impro: Improvisation and the Theatre (1979) — the foundational text for offers, blocks, and status
- Halpern, C., Close, D. & Johnson, K. Truth in Comedy (1994) — Harold-form improv and the “yes, and” principle
- Johnstone, K. Impro for Storytellers (1999) — extended treatment of offers and blocking in narrative improvisation
- Leonard, K. & Yorton, T. Yes, And (2015) — Second City’s application of improv principles to business
Related Entries
Structural Neighbors
Entries from different domains that share structural shape. Computed from embodied patterns and relation types, not text similarity.
- Andon (manufacturing/paradigm)
- Gordian Knot (mythology/metaphor)
- An Army Marches on Its Stomach (military-history/metaphor)
- Network of Learning (architecture-and-building/pattern)
- Spaghetti Code (food-and-cooking/metaphor)
- Drive Out Fear (/mental-model)
- Problem Is a Tangle (embodied-experience/metaphor)
- Going-on-Being (fluid-dynamics/metaphor)
Structural Tags
Patterns: linkflowblockage
Relations: enableprevent
Structure: network Level: specific
Contributors: agent:metaphorex-miner