Find the bottleneck before you hire for it.

When a team is overloaded, the instinct is to add people. Sometimes that's right. Often it's an expensive way to avoid a better question: what, exactly, is the constraint?

A bottleneck is the one step that limits the output of everything else. Improve it and the whole system speeds up. Improve anything else and nothing changes. Hire into the wrong place and you've added cost without adding capacity.

Three questions worth asking first

• Where does work wait? Not where it gets done, but where it sits. Follow a single piece of work from request to finish and note every pause. The longest wait usually points at the constraint.
• What are your most skilled people doing that someone, or something, else could do? Expert time spent on repetitive or manual tasks is the most expensive kind of waste.
• What would break if volume doubled? The first thing that fails is usually the real limit, whether or not it feels like the biggest problem today.

What to do with the answers

Sometimes the answer is a person. Often it's an approval step nobody remembers adding, a manual export, two systems that don't talk to each other, or a process that lives in one person's head. Those are cheaper to fix than a salary, and fixing them makes every future hire more productive.

Hire when you've found the real constraint and it genuinely needs a person. Until then, the best investment is usually clarity.