You Can’t Hire Your Way Out of a Broken System

If you’re a mid-market CEO in a season of growth, you’ve probably said some version of this recently:

We keep hiring and still feel behind—what’s the real problem?

It’s a natural response. Revenue is up. Demand is up. Everyone’s busy.

The problem is, if your operating model is already straining, adding headcount usually does one thing:

It gives you more people to exhaust inside a system that already doesn’t work.

In an earlier piece we talked about how revenue can grow while enterprise value quietly lags. One of the biggest reasons?

Leaning on hiring instead of fixing design.

The Headcount Reflex

In $20M–$150M companies, there’s a predictable moment:

Firefighting becomes the default
Projects slip
Customers feel the wobble
Your best people look tired

The chorus starts:

“We need another project manager.” “We need more ops people.” “We need another layer of leadership.”

Sometimes that’s true.

But often, hiring is just the fastest-feeling option, not the most effective one.

Here’s what I see inside those businesses:

People spend a huge portion of their week working around broken processes
Roles and outcomes are fuzzy, so high performers fill every gap
Decisions bottleneck in the same places
Tools and systems don’t talk to each other

In that environment, each new hire becomes a bandage, not a solution.

You grow payroll. You don’t grow leverage.

How Do You Know You’re Trying to Hire Your Way Out of a System Issue?

Here are a few signals I listen for when I talk with CEOs:

1. Every problem sounds like a staffing problem

“We just don’t have enough people.”
“We need a more senior person in that seat.”
“We could fix this if we had another layer.”

2. Nobody can describe the real work clearly

Ask three people what a role is accountable for.
Get three different answers.

That’s not a hiring problem. That’s a design problem.

3. Time-to-productivity is getting longer

New hires take months to get to full contribution.
Not because they’re weak—but because navigating the system is the real job.

4. Your best people are becoming traffic cops

High performers spend more time chasing updates, clarifying ownership, and “herding cats” than doing the work they were hired to do.

5. You’re adding people, but feeling more behind

The team is bigger.
The meetings are longer.
The results feel… the same.

If any of that sounds familiar, the issue isn’t “we just need more bodies.”

The issue is how the work is designed and moves through the business.

Headcount vs. Leverage: A Simple Map

When a CEO tells me, “We need to hire,” I walk them through three questions:

Is this really a capacity problem?
Or is it a clarity problem?
Or is it a system problem?

From there, we build a simple Headcount vs. Leverage Map™ for a few key roles and workflows.

Example:

1. “We need more project managers.”

What it looks like: PMs overloaded, chasing info, constant reschedules
What you actually need: Clear ownership, clean handoffs, better tools

2. “We need more ops people.”

What it looks like: Ops fixing the same issues over and over
What you actually need: Root-cause fix on upstream process

3. “We need a more senior leader here.”

What it looks like: Leader stuck mediating conflicts between functions
What you actually need: Clear decision rights & priorities

4. “We need another layer of management.”

What it looks like: You’re still making too many calls yourself
What you actually need: Real delegation + role clarity above & below

Nine times out of ten, you discover this:

You don’t have a people shortage. You have a leverage shortage.

Why Hiring into a Broken System Makes Things Worse

When you hire into a system that isn’t working, three things usually happen:

1. You institutionalize workarounds.

New hires learn the shortcuts and heroics from the people who’ve been there the longest.

The workarounds become “how we do it.”

2. You make accountability even fuzzier.

You add another person into an already unclear flow.

Now it’s even harder to know who owns the outcome.

3. You drain your best people faster.

Senior people now have to onboard, manage, and shield new hires from the chaos.

The “fix” becomes another reason they’re exhausted.

In my experience, this is when CEOs start saying:

“I keep hiring good people, and they struggle here. Maybe I’m just bad at hiring.”

Well, you might be right about a couple of individual hires.

But in my experience, if good people keep struggling in your company, it’s not your hiring process. It’s the environment you’re dropping them into.

Before You Hire: Three Design Questions

I’m not anti-hiring.

I am against using hiring to paper over a broken operating model.

Before you greenlight another role, sit with your team and ask three questions:

1. What outcome are we trying to improve—and where is it really breaking down?

Is the problem volume (we can’t do the work)?
Or is it rework, confusion, or delay (we’re doing the same work twice)?

2. If we froze headcount for six months, how else could we solve this?

Could we clarify ownership?
Could we simplify the workflow?
Could we fix the handoffs?
Could we automate or eliminate a step?

You don’t need another stand-up meeting; you need to stop making people do the same work twice.

3. If we do hire, what has to change in the system to make that hire effective?

What will they stop others from doing?
What broken process will they no longer have to work around?
How will we know 90 days in that this hire is creating leverage, not just absorbing chaos?

If you can’t answer those questions clearly, you’re not ready to hire.

You’re just about to add cost and complexity to a system that isn’t ready to support it.

A Quick Audit: Capacity, Clarity, or System?

Here’s a simple exercise I use with leadership teams.

Pick one team or function where you feel “understaffed” and walk through this:

Capacity

Are people consistently working unreasonable hours?
Is there a clear, measurable backlog of work that truly can’t be done with current resources?

Clarity

Can each role articulate, in one sentence, the outcomes they own?
Are there decisions that “float” because nobody is sure who should make them?

System

Are there 2–3 recurring fires that everyone can name instantly?
Do you see the same issues in handoffs between the same functions?

If capacity is red but clarity and system are green, hiring probably makes sense.

If clarity and system are red, hiring is like pouring water into a leaky bucket.

Case Snapshot: “We Just Need More People in Ops”

A CEO I worked with was convinced they needed to “double the ops team.”

Customer complaints were rising
Project timelines were slipping
The ops team was vocal about being overloaded

On the surface, more people sounded logical.

When we mapped the work, here’s what we found:

Sales was handing off deals with inconsistent information
Ops was spending hours every week tracking down missing details
Decision rights on “can we commit to this timeline?” were unclear
The same 3–4 people were making judgment calls in side conversations

We didn’t hire.

We:

Clarified what “clean handoff” meant and enforced it
Tightened decision rights on timelines and exceptions
Built a simple weekly cross-functional huddle to clear blockers

Within 90 days:

On-time delivery improved
Customer noise quieted
Ops felt less overwhelmed—with the same headcount

Later, we did add a role.

But by then, the system could actually use that hire as leverage, not a life raft.

Where to Start: One Hiring Decision You Can Redesign This Quarter

If you’re already planning to add people this year, don’t cancel everything.

Instead, pick one critical hire you’re considering—maybe in operations, project delivery, or leadership—and run this process before you post the role:

1. Name the outcome.

“What business outcome is this hire supposed to improve?”

2. Separate capacity from clarity and system.

“If we were not allowed to hire, where would we look first to fix this?”

3. Redesign one piece of the system first.

Clarify ownership
Clean up a handoff
Eliminate one recurring fire

4. Then decide: do we still need the hire?

If yes, update the role description based on the improved system
If no, you just protected margin and leadership bandwidth

You’ll still hire.

But you’ll do it in a way that adds leverage to a better-designed operating model, instead of adding more people to compensate for one that’s breaking.

Let’s Make This a Conversation

If your default answer to stress has been “we just need more people,” you’re not alone.

The real opportunity is to become the CEO who can say:

“We need to fix the system first. Then we’ll decide if we need more people.”

If this describes you, schedule 30 minutes on my calendar and we can talk about:

Where you’re trying to hire your way out of design problems
What to fix in the operating model before you add headcount
How to use a simple Headcount vs. Leverage Map™ so every future hire actually creates lift

Not quite ready for that conversation? Save this and use the questions with your leadership team before your next hiring decision.