Is It Really a People Problem?

You have an employee who keeps missing the mark.

They aren’t getting enough done.

They keep asking the same questions.

They’re dropping balls.

Maybe they’re distracted.

Maybe you’ve coached them three times already.

And eventually, you start thinking:

I hired the wrong person.

Maybe.

But before you make it a people problem, you need to prove it isn’t a systems problem.

Because one of the easiest mistakes we make as owners is blaming a person for failing inside a system that was never clear enough for them to succeed in.

And the opposite happens too.

Sometimes we KNOW it’s a people problem, but instead of dealing with it, we build another process.

Another checklist.

Another meeting.

Another policy.

Another training.

Another layer.

Neither one fixes the real problem.

So how do you know which one you’re dealing with?

Start With Four Things

Before I decide someone is the problem, I want to look at four things:

Clarity. Capability. Capacity. Will.

In that order.

1. Clarity: Do they know what good looks like?

Don’t ask whether you’ve told them what their job is.

Ask whether they could tell you.

What do they own?

What outcomes are they responsible for?

What should they be doing every day?

What decisions can they make without you?

What does “done correctly” actually look like?

We recently had team members across our companies build out their own roles and rhythms.

That exercise was eye-opening.

Some people had incredible clarity.

Others showed us work we didn’t even realize they were doing.

And some exposed gaps where we thought they understood the role—but they didn’t.

That’s not automatically an employee problem.

That’s information.

In fact, that’s one reason I love having employees help document their own roles.

You’re not just building documentation.

You’re testing alignment.

The Q&A exercise had employees brain-dump their recurring work and build the rhythms of their role, which exposed both what they understood and where the role itself lacked clarity.

2. Capability: Have They Actually Been Prepared to Do It?

Knowing what to do and knowing how to do it are different things.

Let’s say you take an incredible field employee and move them into sales.

They’re great with customers.

They’re personable.

They know your company.

So you think:

“They’re going to be great at sales.”

Maybe.

But being good with people isn’t the same as knowing how to sell.

Sales is a skill.

They need training.

They need repetition.

They need practice.

They need time to develop.

If we put someone into a new role without developing the skills required for that role, we can’t immediately blame them when they struggle.

Sometimes we didn’t hire the wrong person.

We promoted someone into a skill they haven’t developed yet.

That exact situation came up during this week’s Q&A: a strong field employee had moved into sales, and the conversation shifted from simply measuring her performance to recognizing the ramp and skill development required for someone with no prior sales experience.

3. Capacity: Can This Job Actually Be Done?

This one gets missed all the time.

Maybe the person knows what to do.

Maybe they’re capable of doing it.

But have we created a job that one human can reasonably perform?

During our role-building exercise, we saw people whose “role” was basically:

General Admin.

Except General Admin wasn’t one role.

It was five roles.

Or ten.

Scheduling.

Customer service.

Payroll.

Recruiting.

Sales support.

Operations.

Whatever else happened to land on their desk that week.

Then we wonder why they’re overwhelmed.

That’s not automatically poor performance.

You may have a capacity problem disguised as a people problem.

This is where a time audit becomes incredibly valuable.

Not because you want to spy on people.

Not because you’re looking for somebody to fire.

Because you need DATA.

What are they actually doing?

How often are they switching tasks?

Where is their time going?

What software are they using?

What work shouldn’t they be doing anymore?

Where are they getting interrupted?

What could be deleted?

What could be moved?

What could be automated?

What could someone else own?

You cannot intelligently redesign someone’s work if you don’t actually know how they’re spending their time.

That’s why I recommend running a real time audit periodically—and why we’re doing them across our own companies right now.

4. Will: Given All of That, Are They Choosing to Do It?

Now we’re somewhere different.

They have clarity.

They know what good looks like.

They’ve been trained.

They have the tools.

The workload is reasonable.

You’ve coached them.

You’ve removed the unnecessary friction.

And they still aren’t doing it.

Now we may actually have a people problem.

You cannot systematize somebody into caring.

You cannot build enough checklists to create ownership in someone who refuses to own the work.

You cannot add enough meetings to manufacture effort.

And you cannot SOP your way around a conversation you don’t want to have.

That’s the distinction.

Clarity.

Capability.

Capacity.

And then:

Will.

The first three force us to examine the environment we’ve built.

The fourth forces us to examine the person operating inside it.

But Don’t Confuse the Wrong Seat With the Wrong Person

There’s one more possibility.

You may have a great person in the wrong seat.

I’ve moved good employees around our companies many times.

Someone can thrive in one role for years and eventually outgrow it.

The company changes.

The workload changes.

Their strengths change.

Their interests change.

What the business needs changes.

The seat that fit them three years ago may not fit them today.

That doesn’t automatically mean they’ve become a bad employee.

It may mean the business evolved and the role didn’t evolve with it.

A business is a living system.

Your roles have to be allowed to change with it.

That’s why we have to keep auditing reality instead of assuming the org chart we built six months ago still represents the business we’re running today. During the Q&A, we talked about roles changing as companies grow, functions moving between seats, and even insourcing or outsourcing changing at different stages.

Here’s the Fastest Test I Know

Before you blame the employee, ask:

Has this happened before?

If one person struggles in the role, it might be the person.

If five people struggle in the same role?

Pay attention.

If every technician struggles with the same quality issue…

If you’ve burned through admin after admin…

If salesperson number ten somehow has the same problem as salesperson number nine…

At some point, you have to stop saying:

“I keep hiring bad people.”

The common denominator might be the system they’re walking into.

That was the final question I left everyone with during this week’s Q&A: Are multiple people struggling with the same thing? Repeated failure across different people is a strong signal to investigate the system instead of continuing to blame the individual.

And Please Don’t Do This…

Once you determine it actually is a people problem, don’t punish everyone else for it.

This is where good owners get themselves into trouble.

We care about our people.

We don’t want to have the difficult conversation.

So instead, we add something.

A checklist.

A policy.

A required approval.

Another manager check.

Another meeting.

Another form.

Pretty soon, 20 good employees are jumping through hoops because we didn’t want to deal directly with one performance problem.

Don’t over-systematize a people problem.

Your system should make good performance easier.

It shouldn’t become increasingly complicated because you’re avoiding accountability.

That’s how owners accidentally become the layer again.

The Q&A hit this directly: continuing to add policies, checklists, meetings, supervision, and training to avoid addressing an individual issue can make the job harder for everyone.

Run a Time Audit Before You Decide

Before you decide you need to fire someone, hire someone, automate something, create another SOP, or restructure a role, get the data.

Run a five-day Time Audit.

Have the employee capture what they’re doing as they move through their day—especially when they switch tasks.

Then look at it together.

You’re looking for:

• Work that shouldn’t exist anymore
• Repeated interruptions
• Excessive task switching
• Work sitting in the wrong role
• Missing systems or training
• Capacity problems
• Unnecessary software or processes
• Work that could be reassigned, simplified, automated, or deleted

A full workweek gives you much better data than guessing from memory, although even a single day can expose surprising patterns.

[DOWNLOAD THE FREE TIME AUDIT →]

Don’t use it as a surveillance tool.

Use it to start a better conversation:

What is this role actually asking this person to do—and have we built an environment where they can succeed?

Then diagnose:

Clarity → Capability → Capacity → Will

Fix the first three.

Coach where coaching is needed.

Move a great person if they’re sitting in the wrong seat.

And when you’ve done all of that and the issue is still will?

Have the conversation.

Because great systems shouldn’t protect us from hard leadership decisions.

They should make those decisions clearer.

This Week’s 1 Layer Deep Question

Before you say “I have a people problem,” ask yourself:

Have I actually earned the right to say that yet?

Align the role.

Delete the unnecessary complexity.

Make execution clear.

Then hold people accountable.

Align. Delete. Execute.