Find the Bottleneck Before Adding Resources

When work starts falling behind, the visible response is often to add something: another person, another meeting, another tool, or another approval step. Those additions can feel productive because they are easy to describe. But a busy team is not necessarily a constrained team, and the loudest complaint is not necessarily the main obstacle. Before adding capacity, identify the point that limits the movement of useful work through the whole process.

Choose one recognizable unit of work to follow. It might be a customer order, a proposal, a service request, or an article awaiting publication. Trace its journey from a clear beginning to a clear finish. Write down where it moves, who takes responsibility, what information it needs, and when it waits. Keep this first map simple enough that the people doing the work recognize their actual day in it.

Pay particular attention to queues. A task may take fifteen minutes to complete but sit untouched for three days because nobody knows it is ready. Another task may be completed quickly, then returned repeatedly because essential information was missing. Both situations create delay, but they call for different solutions. One concerns availability or visibility. The other concerns the quality of the incoming work. Adding people without distinguishing them can make the confusion larger.

Compare a few recent cases rather than relying on one memorable failure. Include ordinary work, an unusually fast case, and a difficult case. Ask what happened immediately before the longest waits. Was someone unavailable? Did a decision require clarification? Were multiple items arriving at once? Were employees postponing an awkward conversation? A useful explanation describes a condition that you can observe and change, rather than blaming a personality or repeating that everyone is overloaded.

Next, distinguish the constraint from its symptoms. If proposals pile up before technical review, salespeople may appear slow to respond. Reminding sales to move faster will not create technical review capacity. Likewise, a crowded production schedule may reflect frequent last-minute changes rather than insufficient production effort. Look upstream for causes and downstream for consequences. The purpose is to locate the leverage point, not to declare one department responsible for every delay.

Try the smallest improvement that addresses the observed constraint. Establish a daily review window. Require a complete intake brief. Let a qualified backup make routine decisions. Separate standard requests from genuinely unusual ones. Limit the amount of work started at once so the constrained stage can finish what matters. Select one intervention and explain the expected effect before implementing it. Otherwise, you will have difficulty determining which change helped.

Evaluate movement through the entire process, not just activity at the changed step. A reviewer who handles more items may still leave customers waiting if rework increases. A faster intake stage can simply create a larger queue elsewhere. Watch completion time, returned work, and the experience of the people receiving the result. Ask whether the improvement made the outcome more reliable, as well as whether it made one local measure look better.

Constraints can move after an improvement. That is a reason to observe again, not a sign that the first effort failed. Keep the work visible and repeat the investigation when conditions change. The practical discipline is straightforward: follow real work, identify its most meaningful delay, test a focused change, and check the end result. Resources become more useful when they are applied to a demonstrated need rather than a general feeling of urgency.