The Bottleneck Game
Time for the team building activity: 20–25 minutes
Setup effort: Easy
Estimated cost: Free to low
Business value: Helps teams understand workflow inefficiencies, strengthens systems thinking, and improves collaboration around process optimization in team building activities
What is The Bottleneck Game?
The Bottleneck Game is a systems-thinking team building activity where teams simulate a workflow and identify where delays or inefficiencies occur. Participants run a simplified process with several steps (such as reviewing a request, processing information, approving a decision, and delivering an output). As tasks flow through the system, teams observe how one slow step can delay the entire process. The challenge is to identify the bottleneck and redesign the workflow to improve overall efficiency. The activity demonstrates a key operational principle: improving the slowest step often has the greatest impact on performance.
How do you play The Bottleneck Game?
Divide participants into teams of 4 to 6 people. Create a simple workflow simulation with steps (for example: Step A receives requests, Step B processes information, Step C reviews results, Step D delivers the final output). Assign one participant to each step and provide small tasks such as moving cards, completing short calculations, or organizing objects. Start the simulation and observe how tasks move through the process. After a few minutes, teams will notice that one step slows the entire system. Once identified, teams propose improvements to reduce the bottleneck and increase throughput.
Why it’s great for a team
The Bottleneck Game makes systems behavior visible and memorable. Participants practice systems thinking (seeing the workflow as interconnected), problem identification (spotting the constraint), collaborative problem-solving (redesigning the process), and efficiency awareness (understanding that local improvements don’t always improve the whole system). It also helps teams talk about workload, handoffs, and capacity using a shared language.
How to organize it effectively
Keep the simulation simple enough to run quickly but realistic enough to reveal a bottleneck. Use cards, tokens, or repeatable micro-tasks. Run a first round without changes so the bottleneck emerges naturally, then a second round where teams apply improvements (rebalancing roles, simplifying steps, adding a buffer, clarifying inputs). Debrief with: Which step created the biggest delay? What change improved flow most? Where do we see bottlenecks in real work? When facilitated well, The Bottleneck Game strengthens systems thinking, collaboration, and process optimization.