Before You Add Resources

When a process struggles, many organizations reach for the fastest solution: more people.

Add staff. Add hours. Add a contractor. It feels decisive. It feels supportive. It feels like progress.

But often the real question hasn’t been asked yet:

Is this a capacity problem — or a process problem?

Hiring can be expensive in ways that aren’t always visible upfront:

• recruiting time and fees

• onboarding and training

• salary and benefits

• management bandwidth

• lost productivity if the fit isn’t right

• and the need to repeat the cycle if it doesn’t work out

In many cases, the cost of hiring rivals — or exceeds — the cost of taking a step back and reviewing how the work actually flows.

I also hear organizations assume that process review automatically means a large Six Sigma-style initiative. In reality, meaningful improvements often come from something far simpler:
clarifying responsibilities, documenting handoffs, tracking decisions, and identifying where work stalls.

Not every operational problem needs more people. Sometimes it needs clearer structure. Before adding resources, it can be worth asking:

Are we trying to solve workload… or workflow?

If this is something your team is weighing right now, I’m always open to comparing notes.