You know the scene didn't work. You can feel it. But when someone asks "what happened?" all you can say is "I don't know, it just... died." That feeling — knowing something failed without being able to name it — is the vocabulary gap that keeps intermediate improvisers stuck.
Here's the vocabulary.
Every scene failure falls into one of three collapse modes: latency, fracture, or decay.
Latency means the responses came too slow or landed on the wrong beat. Someone retreated into their head — internal computation — and by the time they resurfaced, the scene had moved on. The rhythm broke. The energy dropped. Both players felt the lag but couldn't name it. Latency is the collapse mode of the overthinker.
Fracture means the two players ended up in different scenes. One thought they were having a serious conversation; the other thought they were doing a bit. The signals diverged somewhere — an offer was missed or misread — and the shared reality split. Neither player can figure out why it feels off because they can't see the scene from outside.
Decay means the scene went thin. Details stopped mattering. Earlier threads were dropped. Nothing accumulated. The scene didn't break or lag — it just faded. This is what happens when no one deepens, when offers are made but not built upon.
Now zoom in. Within those modes, specific antipatterns are usually at work:
Performing cleverness — you're crafting a joke instead of responding to your partner. The audience gets a punchline but the scene gets nothing. This is the intermediate trap: you're skilled enough to be funny and it's killing your scenes.
Hesitation — the gap between impulse and action. You had the response but you second-guessed it. The moment passed. In an irreversible system, hesitation has weight — the scene registers the absence.
Bulldozing — you're driving your agenda regardless of what your partner offers. You're in the scene but not in the same scene. You're generating but not receiving.
Steering — subtler than bulldozing. You're accepting your partner's offers on the surface but redirecting everything toward where you want the scene to go. You look collaborative but you're not.
Overcomplication — you added a fourth element when two would have served. You introduced a new character when the relationship needed deepening. You invented plot when the game needed heightening. The scene got heavy and stopped moving.
Judgment — you're evaluating the scene while you're in it. "This isn't working." "My partner's choices are weird." "I should have said something different." The evaluation circuit fires and the creation circuit shuts down. You can't build and audit simultaneously.
To use this vocabulary: after a scene, ask yourself three questions. (1) Which collapse mode was it — latency, fracture, or decay? (2) Which antipattern was operating — was I computing, performing cleverness, hesitating, bulldozing, steering, overcomplicating, or judging? (3) What would the opposite behavior have looked like?
That third question turns diagnosis into practice. The vocabulary isn't just for naming what went wrong — it's for seeing what to try next.