
"How's the team?"
"Busy."
Said with a little pride, isn't it? Busy sounds like growth. Busy sounds like demand.
Sometimes it is.
More often, busy is a symptom.
What busy usually means
When I map how a team spends its week, the pattern is nearly always the same. The real work, the thing you hired them for, is squeezed into the gaps between everything else.
Re-keying. Chasing. Checking someone else's spreadsheet. Fixing the mistakes that re-keying created.
That isn't a capacity problem. It's a process problem wearing a capacity problem's clothes.
The expensive response
The natural answer to "we're too busy" is to hire.
So you hire. The new person learns the same broken process. Six months later, they're busy too.
I spoke to one business that had to employ one and a half extra people just to work around a new system that didn't do what they needed. The system was meant to save time. It created a job.
The cost nobody counts
There's a human cost too.
Good people don't leave because they're busy. They leave because they're busy doing work that doesn't matter, and nobody seems to notice.
Overtime spent on genuine growth feels like progress. Overtime spent on copy-and-paste feels like a trap.
What to do instead
Ask a different question. Not "how busy are you?" but "what are you busy WITH?"
Count it. Hours per week on manual, repeated tasks, multiplied by what those people cost. Put a pound sign on it.
Fix before you hire. Remove the steps that shouldn't exist. Automate the ones that must. Then see if you still need the extra person.
Sometimes you will. That's fine. At least you'll be hiring for growth, not for workarounds.
Busy isn't a badge.
It's your business telling you something. Worth listening.


