A working session aimed at removing one recurring waste of time per quarter — a meeting, a report nobody reads, an approval step that approves everything. It is not a game, and teams who say they hate team building usually like it, because it ends with something genuinely gone.
What it is good for
- WellbeingGiving the team a genuine break rather than another meeting with a theme.
- Problem solvingStructuring an ambiguous problem under a time limit.
- Trust & safetyLowering the cost of admitting a mistake or asking for help.
- CollaborationWorking a shared problem where no one person holds all the information.
What you need
- Sticky notes or a shared board
- Access to the team's calendars and recurring processes
The run sheet
Silent list (10 min)
Everyone writes every recurring thing that costs them time and produces little: meetings, reports, forms, rituals, approvals. One per note. No names attached to anything.
Cluster and count the hours (15 min)
Group them, then estimate the hours per month each cluster consumes across the whole team. Rough numbers are fine; the magnitude is what matters, and the magnitude is usually startling.
Vote on the biggest, most removable (10 min)
Two dots each: one for 'costs the most', one for 'easiest to remove'. The thing with both is where you start.
Design the removal (20 min)
Not 'we should reduce it'. Who stops doing what, from when, and who needs to be told. If the thing serves someone outside the room, who talks to them and by when.
Kill one thing before you leave (5 min)
Cancel the meeting series in the room. Send the message. Delete the recurring task. A session that ends with an intention produces nothing; one that ends with a deleted calendar entry gets you invited back.
Facilitator notes
- Anonymity in the silent list matters, because the biggest time sink is often something a person in the room created.
- If the obvious answer is a meeting a senior person runs, the senior person has to be the one to cancel it. Otherwise nobody will name it next quarter.
- Run it quarterly. The second time is easier because the team has seen that something actually went.
Debrief questions
Ask these immediately afterwards, not next week. Fifteen minutes of these is what turns the activity into something the team refers back to — see the debrief guide.
- What did we delete today, and who needs to hear about it?
- What did the room not dare to put on the board?
- What do we check in three months to know whether this worked?
Variations
Calendar edition
Start from the team's actual recurring calendar entries rather than memory. Blunter and usually faster to a result.
Cross-team edition
Two teams who create work for each other run it together. Uncomfortable, and by far the highest-yield version.
Access and inclusion
Silent written input first protects people who will not speak against a senior colleague's process. Keep the notes anonymous all the way through clustering.
Running it remotely
A shared board with simultaneous reveal. Take the final step live on the call — cancel the series while everyone is watching.