The Pun Battle: A Yes-And Game That Builds Team Flow
This improv "yes-and" exercise is a fast chain game where players make themed puns, and each pun must build on the previous person's word or idea. Building on the last contribution forces close listening; adding instead of blocking models the "yes-and" reflex; and the shared laughter bonds the team — all in a few low-stakes minutes.
Two of the most useful team habits are almost impossible to teach by instruction. "Listen closely" and "build on each other's ideas instead of shooting them down" sound obvious on a poster and vanish the moment a real meeting heats up. The pun battle smuggles both habits in through the side door. It's silly on purpose — and the silliness is what lets people drop their guard long enough to actually practice the skills.
Why "yes-and" is hard to learn any other way
In real discussions, our default reflex is "yes-but." Someone offers an idea and we immediately spot the flaw, the risk, the reason it won't work. That instinct has its place, but it kills momentum and makes people stop offering. "Yes-and" — accepting what's there and adding to it — is the engine of good collaboration, and you can't install it with a lecture. You install it with reps. A pun chain is reps disguised as a game: to play at all, you have to accept the last word and add yours, which is "yes-and" in miniature.
How do I run a pun battle?
You need a group and zero materials. Five to ten minutes is plenty.
- Pick a theme. Food, the ocean, office life, your product — anything with lots of associated words. A rich theme keeps the chain going.
- Go around making puns. One person makes a pun on the theme. The next person makes another — but it has to build on the previous person's word or idea, not start from scratch.
- Build, don't block. The single rule: each pun connects to the last one. You're riffing off what you just heard, which means you have to actually hear it. No rejecting someone's pun — you accept it and add.
- Keep the chain alive as long as you can, then stop on a laugh. When the groans peak or the chain finally breaks, call it. There's no winner to crown — the point was the flow, not the score.
A worked example
A team takes "the ocean" as the theme. Someone opens: "I'm feeling a bit shore of myself today." The next builds on shore: "Don't worry, we'll wave that off." The third catches wave: "Yeah, just go with the flow." Then: "I'm current-ly out of ideas" — and the chain keeps rolling. Notice what's happening underneath the puns: each person had to listen hard enough to catch the exact word to spring from, and nobody could win by rejecting the previous line. By the time the chain collapses in laughter, the team has just done two minutes of pure listen-and-build — the same muscle they'll need in the next real brainstorm.
When the pun battle is most useful
It's a great opener before any creative or collaborative session — it warms up listening and "yes-and" right when you're about to need them. It's also a quick mood-reset for a tense or tired team, because shared laughter does real bonding work. It's not the move for a sombre or high-pressure moment, and word-play games can land unevenly across languages and cultures, so adapt the theme to your group. The goal is participation and flow, never clever-pun supremacy.
The takeaway
You can't lecture a team into listening closely and building on each other — but you can play a game where doing both is the only way to keep going. The pun battle is that game: pick a theme, build each pun on the last, and let the laughter do the bonding. Two silly minutes now buys you a sharper, more generous conversation later.
This is one of Funstorming's 100 quests — bite-sized soft skills methods you actually put into practice, not just read about. Try it, then bring your result (or your sticking point) to the Funstorming community of practice (CoP), FunHub | Your Soft Skills Playground.
#funstorming #softskills