System Thinking · Projects
What a traffic jam teaches about flow

Anyone who has driven in an Indian city during the evening rush knows this scene. A two-lane road. One bus has stopped awkwardly near a bus stop. Within ten minutes, cars, bikes and autos have filled every gap, including the lane for oncoming traffic. Now nobody can move, not even the bus that started it all.
Sitting in such a jam one evening, I started asking myself a simple question: what actually caused this?
The bus is not the reason
It is tempting to blame the bus, or the breakdown, or the one car trying to take a U-turn. But a single obstacle on its own rarely causes a jam. Traffic simply slows down around it.
The jam is caused by what happens next:
- Everyone tries to get ahead. Each driver squeezes into the smallest gap, hoping to gain a few metres.
- Nobody sees the whole picture. From inside a car, you can’t see how the vehicles are placed fifty metres ahead, or which move would free the road.
- Every gap gets filled. The empty space that was needed for vehicles to manoeuvre is gone.
- Small fights become new blockages. Two vehicles scrape each other, the drivers get out to argue, and another lane is blocked.
Do you see what has happened? Each driver made a decision that looked smart for himself. Together, those decisions froze the road for everyone, including themselves.
A road is a system
A road can carry only so many vehicles per hour and still flow. Push more vehicles onto it than that, and the speed doesn’t drop gently. It collapses. Traffic engineers know this well: beyond a certain density, adding cars reduces the number of cars that get through.
When every gap is filled, flow stops. Empty space is not waste; it is what allows movement.
Now replace the road with your organisation.
Your projects are stuck in the same jam
In a company running many projects at once (an engineering firm, an R&D centre, an IT team, a construction company), the picture is remarkably similar.
- Each project is a vehicle trying to reach its destination: completion.
- Each project manager is a driver.
- The shared resources (designers, testers, the one expert everyone needs) are the road.
What do project managers do when things get tight? Exactly what drivers do. They push their own project forward. They fight for the shared resource. The one who shouts the loudest gets served first. Resources are pulled from one project to another, and each switch costs time.
The result is a jam: dozens of projects open, all moving slowly, most of them late, and everyone exhausted. Just like the honking and the smoke, the stress of the environment makes people work even slower.
Three things that clear a jam
When a traffic police officer clears a jam, he does three things. Each has a direct equivalent in managing projects.
1. Stop more vehicles from entering
The first thing an experienced officer does is hold traffic at the next junction. More vehicles entering the jam only make it worse.
In projects, this is work-in-progress control. If the system already has more open projects than it can flow, the fastest way to finish them is to stop starting new ones, and even to freeze some of the open ones until others are completed. A new project enters only when one leaves.
The arithmetic is simple. Picture a design team that completes about 2 projects a month, whatever it does. If 24 projects are open, each one sits in that crowd for roughly a year (24 ÷ 2 = 12 months) before it is done. Freeze half of them and keep 12 open: the team still completes 2 a month, because its capacity hasn’t changed, but each project now takes about 6 months. No output was lost. Half the waiting simply disappeared. And with less switching between projects, the team usually completes more than 2 a month as well.
This feels painful. It may even mean saying no, or saying “later”, to a customer. But it is the only way out of the jam. Map apps do something similar for drivers: they warn us before we enter a congested area so that we can wait or choose another route.
2. Agree on who moves first, and stick to it
A jam clears when drivers accept an order: this lane moves, then that one. If even a few drivers keep pushing in out of turn, the order breaks down.
In projects, this means one priority list for all shared resources, agreed by management, and the discipline to follow it, even when your own project is not at the top. Goldratt called this subordination. It only works when everyone does it. One manager who keeps pulling resources out of turn can undo the gains for all.
3. See where the blockage is, and clear it fast
A traffic officer can be in only one place. Imagine if he could see the whole network and knew exactly where the next blockage was forming.
Managers need the same view of their projects. Traditional plans focus on the tasks on the critical path and ignore the rest, until a neglected task becomes the blockage. What helps is:
- A single picture of all projects and how much of their safety time each has consumed (the buffer status in Critical Chain).
- A daily routine to raise issues the moment they appear, with a clear escalation path if they aren’t resolved quickly.
Is it really that simple?
The principles are simple. Following them is not, because each of them asks people to act against what looks best for their own project, just as the driver who waits his turn feels he is losing out.
But think about the evening jam again. Every driver who waited his turn actually got home sooner than the one who pushed in. Flow is a property of the whole road, not of any single car. The same is true of your projects.