There's a particular kind of relief that comes from deciding to hire. The team is stretched, something's slipping, and adding a person feels like decisive action — you've acknowledged the strain and done something about it. I've felt that relief many times, and I've learned to distrust it. More often than I'd like to admit, the headcount didn't fix the problem. It gave the problem a person to hide behind.
A role you add under pressure tends to get defined by the pressure. You're not hiring for a job you've thought through; you're hiring for the feeling of being underwater. So the job description is really a list of everything that's currently on fire, and the person who arrives inherits a mandate that's less a role than an apology for the last few months. Six months later you have a talented person doing a job nobody actually designed, and the underlying tangle — the unclear ownership, the process that never got fixed — is still there, just staffed.
Headcount is the most expensive way to avoid a decision
Most of the time, the strain isn't a shortage of hands. It's a shortage of decisions. Two people quietly own the same thing, so nothing moves cleanly. A process that made sense at half the size is now taxing everyone. A priority nobody will kill is eating hours that should go elsewhere. None of these get better with another hire; they get more crowded. Adding a person to an undecided situation just means one more person navigating the ambiguity — and now you're paying for the ambiguity, at salary.
Earn the hire
So before I approve a role now, I make myself answer a harder question than "are we busy." I ask what decision I'm avoiding by hiring. Sometimes the honest answer is none — the work is real, the design is clear, we simply need more capacity, and then hiring is exactly right and I move fast. But often the answer is that a hire is cheaper, emotionally, than a hard conversation or a killed project, and that's the trap. The role that gets approved to avoid a decision almost never repays it.
The discipline isn't to hire less for its own sake — understaffing is its own slow damage, and I've done that too. It's to make sure a new person is joining a job that exists, not absorbing a problem you didn't want to face. The best hires I've made walked into clarity. The ones I regret walked into a mess with a title on it, and no amount of talent survives that for long.