I was in the middle of a busy operation when everything started stacking up.
Requests were coming from every direction. People were waiting. Pressure was building. You could feel the entire operation beginning to compress.
And, as usual, everyone’s attention shifted toward one position—the one that appeared to be slowing everything down.
It is easy in those moments to point toward the most visible pressure and say, “That’s the problem.”
The delays show up there. The friction becomes visible there. The complaints are directed there.
For a long time, I bought into that conclusion too. It looks like the problem.
But when you stand there long enough and watch the operation unfold, you begin to see something different.
That point is not necessarily broken. It may be doing exactly what it was designed to do.
“In theory, theory and practice are the same. In practice, they are not.” — Yogi Berra
In the real world, every system has a point where work compresses. Inputs converge. Priorities compete. Decisions carry consequences. Someone has to take multiple streams of activity and turn them into an orderly flow.
That is the control point.
It is not automatically a flaw. It is a function.
The Most Visible Delay Is Not Always the Source
Organizations often diagnose problems by looking at where the delay becomes visible.
A project is waiting for approval, so the approving leader must be too slow.
A customer request is sitting with operations, so operations must be inefficient.
Several teams are waiting on one specialist, so that individual must be the bottleneck.
Sometimes that conclusion is correct. But sometimes the visible pressure point is simply absorbing problems created elsewhere in the system.
It may be receiving incomplete information. Priorities may not have been established upstream. Decision authority may be unclear. Too much work may be entering the system at once. Routine decisions may be treated as exceptions because no standard exists for handling them.
The control point becomes where all of those weaknesses finally collide.
Blaming that position may temporarily relieve frustration, but it does not improve the system. It merely directs attention toward the place where the consequences are easiest to see.
What Air Traffic Control Teaches Us About Flow
Air traffic control is built around control points.
During a busy operation, aircraft do not arrive in a perfectly organized sequence. Demand changes. Weather shifts. Runway configurations change. Some aircraft require more spacing than others. A plan that worked several minutes ago may already need to be adjusted.
At some point, those variables must be converted into decisions.
Who goes first?
Where should space be created?
What can be tightened safely?
When does the operation need to slow down to protect the larger flow?
The controller working that position is not simply processing aircraft as quickly as possible. The controller is regulating the system.
When that role is functioning well, most people never notice it. The operation feels smooth. Problems are addressed before they spread. Spacing is created before it becomes urgently necessary. The rest of the system continues moving because someone is actively managing the point where everything converges.
But if that control point lacks capacity, information, authority, experience, or support, the effects begin to spread.
Not always immediately.
One delay becomes two. Coordination increases. Options disappear. People begin reacting instead of anticipating. Eventually, the entire operation feels inefficient—even when the original weakness existed somewhere else.
The Mistake Is Trying to Eliminate the Pressure
When leaders identify a pressure point, their first instinct is often to make it move faster.
They tell the person to process more work. They add urgency. They reduce the time available for decisions. They assign someone without the experience or authority necessary to manage the competing demands. Sometimes they understaff the role because it does not appear productive when the system is quiet.
Then they are surprised when performance deteriorates under pressure.
The goal should not be to eliminate every point of compression. That is rarely possible. The goal is to ensure the control point can manage compression without becoming overwhelmed by it.
That requires more than speed.
It requires structure.
Three Conditions That Strengthen a Control Point
1. Ownership
The person managing the flow must know what they own and what they have the authority to decide.
If every adjustment requires permission, the control point cannot actually control anything. It becomes a relay station—collecting requests, escalating decisions, and waiting for answers while pressure continues to build.
Clear ownership removes that hesitation. It establishes where decisions belong, when coordination is required, and when responsibility transfers to someone else.
2. Standardization
Not every decision should be invented in the moment.
Standards allow routine situations to be handled consistently, preserving attention for the conditions that truly require judgment. They create shared expectations about priorities, handoffs, escalation, and what information must accompany the work.
Standardization does not remove professional judgment. It protects it from being consumed by preventable ambiguity.
3. Refinement
No operating system remains perfect after it meets reality.
Conditions change. Demand shifts. New information becomes available. Leaders must observe how the system is performing and refine it accordingly.
In air traffic control, spacing is continuously evaluated. When conditions allow, it may be tightened. When the operation becomes too compressed, additional space may be needed. The process never truly ends because the operating environment never stops changing.
Organizations need the same discipline. Make the best decision available, observe its effects, and adjust the system as evidence develops.
Diagnose the System Before Blaming the Position
When work repeatedly slows at the same point, leaders should certainly investigate it. But the investigation should go beyond asking why that person or team is not moving faster.
Ask:
- Is the work arriving with the information needed to act?
- Are priorities clear before demand reaches the control point?
- Does the person responsible have genuine decision authority?
- Are routine decisions standardized?
- Is the workload within the position’s actual capacity?
- Are upstream teams creating problems that only become visible downstream?
- Is the organization learning from recurring congestion and refining the system?
Those questions shift the conversation from blame to diagnosis.
They also reveal an important distinction: a necessary control point can become a harmful bottleneck when it is poorly designed, under-resourced, or denied the authority to regulate flow.
The answer is not to remove the control point blindly. It is to determine what that point needs to perform its function.
The Better Leadership Question
The place where work slows deserves attention. But it does not automatically deserve blame.
It may be the only part of the organization preventing competing demands, unclear priorities, and incomplete information from creating even greater disruption.
Strong leaders do not simply ask, “Where is everything slowing down?”
They ask:
Is this control point effectively running the system—or merely trying to survive it?
The distinction matters.
Because if the control point is only surviving, the organization is already behind. The consequences simply have not reached every part of the system yet.