Stan Tscherenkow
System-vs-people diagnostic pain

I Can't Tell If This Is A Business Problem Or A People Problem

You have a person who keeps falling short. You also have a role that nobody seems able to fill. Both could be true. Both have very different fixes.

This page is for the owner standing at the diagnostic moment. The third person in this role in two years. The team member who is good in some ways and not landing in others. The decision: is this about the human, or is this about the structure they walked into? The wrong call costs a year. The right one is rarely obvious without looking carefully.

Short answer

If one person fails in a clear role, you may have a people problem. If three people fail in the same shape in the same role, you have a system problem wearing a people mask. The number of failures tells you which one.

Research signal

The hot language is honest. Often guilty.

Owners ask this quietly. Out loud it sounds like blame. Inside it sounds like doubt.

One failure

Could be the person. Could be the fit. Hard to tell from one.

Two failures

Now look at the role. Pattern is starting to form.

Three failures

The role is generating the failure. The person is downstream.

Four failures

Stop hiring. Redesign the role before the next attempt.

Infographic

Read the pattern before reading the person.

When you can name the same failure shape across multiple people in the same seat, the seat is the source. When the failure shape changes person to person, the person is the source.

Pattern visualOne person failsin their own waypeople problem most likelyTwo people failin similar waysinvestigate the roleThree or more failin the same shaperole is generating the failureCount first. Diagnose second. Hire third.
The pattern is the diagnostic. The person is downstream.
Jump map

Fifteen questions you actually ask at 11pm.

"Is this a hiring problem or a system problem?"

"Maybe I keep picking the wrong people."

"Maybe the role itself is broken."

"I have fired three people in this seat."

"I cannot afford to fire a fourth."

Each answer is short enough to finish here and sharp enough to make the deeper page worth opening.

01

How do I tell the difference between a business problem and a people problem?

Count.

One person failing in this seat: probably the person.

Two people failing in similar ways: investigate the role.

Three people failing in the same shape: the role is doing it.

Fast read

Counting tells you which one. Look at the pattern before looking at the person.

Why the count matters

One failure is data. Three failures is a pattern. Patterns belong to systems, not people. If three capable humans cannot succeed in your role, the role is making them fail.

AtlasDecision Architecture TestAtlasCoach For Authority ProblemCaseSenior Executive Backfires
02

What if I have only one person failing?

Then start with the person, but not by firing them yet.

Have one direct conversation about specific gaps.

Watch what they do in the next thirty days.

If the gap closes, you had a coaching moment. If it does not, you may have a fit issue.

Fast read

One person failing earns one direct conversation before any decision.

What that conversation includes

Three specific examples of the gap, with dates. The standard you expect. The timeline for improvement. The consequence if it does not move. Vague feedback teaches nothing. Specific feedback teaches the person where they stand.

AtlasOperator Before Authority ReleaseGlossaryDecision RightsTeam routeBoards and Teams
03

What if I have already had three people fail in this seat?

Stop hiring.

Three is the count where the role is the issue.

The fourth hire will fail in the same shape because the role is generating the shape.

Fast read

Three failures in the same shape closes the case on the role.

What to do instead of hiring

Pause hiring for the seat. Sit down and answer one question: what is this role allowed to close without coming to me? If the honest answer is 'nothing important,' the role cannot succeed.

AtlasThe Authority MapAtlasOperator Before Authority ReleaseCaseSenior Executive Backfires
04

Is one bad hire just bad luck?

Often, yes.

Hiring is imperfect.

Smart owners can pick wrong. The first miss is rarely diagnostic. It is the third miss that says something about you and the seat.

Fast read

First miss: hiring. Third miss: structure.

What to learn from one miss

Update your interview process. Update the role description. Update your reference check pattern. Then hire again, with discipline, expecting it to work.

AtlasWrong Help Feels ProductiveAtlasHow To Choose Outside HelpManualRead Your Own State
05

Why do I keep picking the wrong people?

Maybe you are.

More often you are picking competent people and putting them in a seat that cannot succeed.

The hiring process you blame did not produce the failure.

The role design did.

Fast read

If three competent people fail in the same seat, the seat is doing the picking.

What changes when you redesign the seat

Hiring stays competent. Onboarding stays normal. The new hire arrives into a role with named authority, named decision rights, and named consequences. Same person, different seat, different result.

AtlasConsent Rights and AuthorityAtlasOperator Before Authority ReleaseGlossaryApproval Matrix
06

Are my expectations just off?

Worth checking.

Some owners hold their team to a standard the founder has never written down.

The team is failing against a standard they cannot see.

That is fixable. It is not the person.

Fast read

An unwritten standard is the same as no standard.

How to test

Ask three team members what 'good' looks like in their role. If you get three different answers, your standard is not visible. Write it down. Then watch what changes.

ManualGovern Your Own CompanyAtlasReal Target DisciplineGlossaryDecision Rights
07

Is the role too big?

Possibly.

Many owner-built roles are two or three jobs combined into one title.

The hire cannot do all three.

You read it as 'they cannot keep up.' The honest read is 'this role was never one job.'

Fast read

If you cannot find anyone who can do the role, the role is more than one job.

How to test

Write the role's actual responsibilities. Group them. If they fall into three different functions, you built a stack, not a role. Split it before you hire again.

AtlasDecision Architecture TestAtlasLeadership CeilingCompareAdvisor vs Interim CXO
08

Is the role too small?

Sometimes.

Underpowered roles attract underpowered hires.

The smart ones leave fast.

The ones who stay are not the ones you wanted.

Fast read

Roles with no authority attract candidates with low expectations.

What 'too small' looks like

A title that sounds senior, a salary that suggests senior, and decision rights that match a coordinator. The mismatch eats the engagement. Strong hires read the mismatch in the first six weeks and start looking.

AtlasOperator Before Authority ReleaseCaseSenior Executive BackfiresCompareAdvisor vs Interim CXO
09

What if the structure itself is wrong?

Then no hire will fix it.

The structure produces the failure.

Hiring against a broken structure is hiring people into a trap.

Fast read

Hire into the trap, you get the trap's results.

What 'structure is wrong' looks like in practice

Two people responsible for the same decision. A role without budget authority for the work it owns. An exec whose every move needs founder approval. A team where promotion happens by tenure, not by closure. Structural problems show up as people problems.

AtlasConsent Rights and AuthorityAtlasThe Authority MapManualGovern Your Own Company
10

Should I fire the person or redesign the role?

Both, sometimes.

If the person has been told the standard, given time, and still missed in their own way: fire.

If three people have missed in the same way: redesign first, then hire.

Order matters. Fire-first into a broken role costs you the next hire too.

Fast read

Fire after you fix the role, not before. Otherwise you fire and fire again.

The order of operations

Diagnose. Redesign if needed. Communicate the new shape. Decide on the current person against the new shape. Hire only after the redesign is real.

CaseCEO Who Waited Too Long To FireCaseSenior Executive BackfiresApplyApply
11

How do I redesign the role?

Start with three questions.

What decisions does this role close without my input?

What is its budget authority?

What does success look like in ninety days, in numbers?

If you cannot answer all three, the role is undefined, not understaffed.

Fast read

Three questions. If you cannot answer them, the role is the problem.

Why these three

Decision authority, budget authority, success definition. Without all three, the seat is a coordinator wearing a manager title. Strong hires read this immediately. Weak hires last longer but produce nothing.

AtlasOperator Before Authority ReleaseAtlasThe Authority MapManualGovern Your Own Company
12

What if the team blames the hire and not the role?

The team often does.

The team has a stake in the current structure being correct.

If the role is wrong, the team has been wrong about who to blame for a while.

Their read is loyal, not always accurate.

Fast read

The team's read on the hire is data. It is not the diagnosis.

How to weigh the team's input

Listen carefully. Then ask: 'If this role were better designed, would the same person have succeeded?' Most teams have not considered the question. Their answer often shifts.

Team routeBoards and TeamsAtlasThree Advisors, Three DiagnosesAtlasDecision Closure Before Peace
13

Why do I feel guilty about this?

Because three people landed in a seat you designed, and three people did not make it.

The guilt is appropriate.

It is also an indicator. It says the structural problem has been visible to you longer than you have been willing to act on it.

Fast read

Guilt is data. It is not a verdict. Act on it.

What the guilt asks of you

Not more apologies. A real redesign of the seat before the next person walks into it. The most honest apology to the three who left is the fourth person finally succeeding because the role got fixed.

AtlasDecision Delay CostCaseFounder Who Couldn't Let GoApplyApply
14

Will the next hire fix it?

Only if the role is different than it was for the last three.

Same role, new face, same result.

Different role, even with the same hire, different result.

Fast read

The role decides. The hire executes against what the role allows.

What to change between now and the next hire

The role description, the decision rights, the success definition, the reporting line, the budget authority. Five elements. Change at least three. Then hire.

AtlasThe Authority MapAtlasOperator Before Authority ReleaseApplyApply
15

When should I bring outside help?

Before the fourth hire.

The cost of one wrong hire is twelve months and one salary.

The cost of a read on the role is one conversation.

The math favors the read.

Fast read

Before hire four. The math is on the read.

What this kind of help looks like

Not a recruiter. Not an HR consultant. A read on whether the role itself is built to succeed, given the structure around it. Two hours of work. Output: a written assessment of whether to hire again or redesign first.

AtlasHow To Choose Outside HelpCompareAdvisor vs Interim CXOApplyApply
Second visual

The same shape, repeated. That is structure.

One failure looks personal. Three failures in the same shape look architectural. Different problem. Different fix.

Recurring loopHire 1 failsHire 2 failsHire 3 failsSame shape, three times. The role is doing it.
The loop closes when the role changes, not when the hire changes.

If three capable people failed in the same seat, the seat is generating the failure.

Redesign the seat before you hire the fourth.

Apply when the pattern is active