The Difference Between a People Problem And a Structure Problem
Why repeated performance problems sometimes point beyond the person involved
A deadline slips.
A client handoff breaks.
Someone misses an approval.
A team member waits too long to escalate a problem.
A leader gives unclear direction, then spends the next week answering questions.
The easiest explanation is often a person.
Someone failed to communicate.
Someone lacked ownership.
Someone needed better training.
Someone was not proactive enough.
Sometimes the explanation is correct. People make mistakes. Performance problems exist. Leaders still need to set expectations, give feedback, and hold people responsible for work entrusted to them.
But repeated problems deserve a second question.
Is the person creating the problem, or is the person working inside a structure producing the same result?
The distinction matters because the response changes.
A people problem requires attention to behavior, capability, judgment, or performance.
A structure problem requires attention to the conditions shaping how work moves.
When leaders confuse the two, they often spend months fixing symptoms while the original problem keeps returning.
What a people problem looks like
A genuine performance issue becomes easier to see when the surrounding operating conditions are reasonably clear.
The person understands the expected outcome.
Their role is clear.
They have access to the information and resources needed for the work.
Their authority matches their responsibility.
The handoffs around the work function.
The escalation path is known.
Other capable people working under similar conditions succeed.
Even with those conditions present, one person repeatedly fails to meet a reasonable expectation.
At this point, clearer accountability, coaching, training, reassignment, or a harder personnel decision might be appropriate.
Structure should never become an excuse for avoiding accountability.
Understanding the conditions around performance improves accountability because leaders become clearer about what the person truly owns.
What a structure problem looks like
Structure problems behave differently.
The visible failure often moves from person to person.
A new hire enters the role and encounters the same confusion.
A capable employee performs well until work crosses another function.
A team follows the documented process until an exception appears.
A leader delegates responsibility, but meaningful decisions continue returning upward.
People learn to work around the formal process because the formal route slows or blocks the work.
The founder becomes the safest source of clarification because no other dependable source exists.
These situations often look personal from close range.
Someone did not follow the process.
Someone waited for approval.
Someone failed to communicate.
Someone made the wrong decision.
Step farther back and another picture appears.
The person might be responding logically to the operating conditions surrounding the work.
When the same problem survives a change in people, look at what stayed the same around them.
The same problem following different people is important evidence
One of the strongest signals appears when the problem survives a personnel change.
A project coordinator leaves. The replacement struggles with the same handoffs.
A client-services lead receives feedback about missed expectations. Six months later, another lead encounters the same conflict between what sales promised and what delivery understood.
A founder hires an operations leader to reduce involvement. The new leader still returns for constant clarification because decision boundaries never moved with the role.
Different people do not automatically prove a structural problem. The repetition deserves examination.
Ask what stayed constant while the people changed.
The same unclear authority?
The same missing information?
The same dependency?
The same approval bottleneck?
The same competing priorities?
The same informal exception path?
The person changed. The conditions did not.
Responsibility without authority creates predictable friction
A role description might say someone owns an outcome.
Ownership on paper does not always create authority in practice.
A team lead owns delivery but needs founder approval for schedule changes.
A department head carries revenue responsibility but has little influence over staffing decisions.
A project manager owns the timeline but has no authority to resolve competing priorities across leaders.
A client lead owns the relationship but lacks access to decisions affecting the client.
Each person holds responsibility for an outcome while depending on someone else for choices required to produce the outcome.
Leaders often interpret the resulting hesitation as weak ownership.
The person experiences a different problem.
They have been given responsibility without enough authority to carry the responsibility well.
More accountability will not repair an authority gap.
The organization needs clearer decision boundaries.
Informal coordination works until the work changes
Many founder-led organizations begin with informal coordination because informal coordination works.
People talk frequently.
The founder knows what everyone is doing.
Questions get answered quickly.
Priorities travel through conversation.
A small number of people hold most of the relevant context.
Few formal mechanisms are necessary because proximity carries the information.
Growth changes the conditions.
More people join.
Work crosses more roles.
Projects overlap.
Clients create competing commitments.
Decisions affect people outside the original conversation.
The founder has less direct visibility.
Knowledge spreads unevenly.
Informal coordination starts carrying more weight than the original arrangement was designed to hold.
Problems emerge at the edges.
A handoff gets missed.
Two people interpret the same priority differently.
A decision gets reopened.
Someone waits for an answer already given elsewhere.
A workaround becomes the normal path.
The organization has not suddenly filled with less capable people.
The work has become more interdependent while the structure supporting the work has remained largely informal.
Workarounds tell you something about the structure
People rarely create workarounds for no reason.
They text someone instead of using the project system.
They ask the founder privately instead of following the approval path.
They keep their own spreadsheet because the shared tracker does not answer the questions needed for their work.
They bypass a meeting because decisions rarely happen there.
They maintain a private list because nobody trusts the official priorities to stay current.
A workaround is behavior.
A repeated workaround is also information.
The workaround shows where people found the formal structure insufficient, unreliable, slow, unclear, or disconnected from reality.
Removing the workaround without understanding its purpose often pushes the same need somewhere else.
The better question is: What problem is the workaround solving?
Once the answer becomes visible, leaders have a stronger basis for deciding whether the formal structure needs repair or whether the individual simply chose an unnecessary shortcut.
Pressure reveals the structure people trust
An organization might look well designed under normal conditions.
The real test often arrives when pressure increases.
A deadline moves forward.
A client escalates.
A key person becomes unavailable.
Several priorities collide.
A mistake carries meaningful consequences.
Watch what happens next.
Do people follow the documented authority structure, or does every decision return to the founder?
Do teams use the established process, or do they reopen private communication channels?
Do decision owners retain authority, or do senior leaders begin overriding them?
Do people know which priority wins, or does urgency decide?
Pressure strips away structures people do not trust.
The route people choose under pressure often reveals the operating structure they believe is real.
Repeated founder rescue is another signal
Founder intervention often solves the immediate problem.
The founder knows the history.
The founder understands the tradeoffs.
The founder has authority.
The founder sees connections across functions.
Stepping in makes sense.
Repeated rescue produces a different question.
Why did the organization need the founder again?
If the answer is always personal failure, replacing or coaching the person should eventually reduce the pattern.
If the pattern keeps returning across capable people, the founder might be compensating for something the organization has not yet built.
A decision right.
An escalation rule.
A clearer standard.
A reliable information route.
A stronger handoff.
A way to preserve organizational memory.
A mechanism for resolving competing priorities.
The founder appears to be solving individual problems.
The founder might also be serving as missing operating structure.
Before deciding what needs fixing
When a performance problem appears, leaders do not need to choose immediately between blaming the person and blaming the system.
Start with the situation.
What was the person expected to do?
Did they understand the expectation?
Did they have the information needed?
Did they hold enough authority?
What dependencies sat outside their control?
Was the handoff clear?
Did an exception appear?
Was there a known path for handling the exception?
Have other people encountered the same problem?
What happens under pressure?
What changed after the previous occurrence?
These questions do not remove personal responsibility.
They make responsibility more accurate.
Sometimes the answer will still be a person.
Sometimes the answer will be a process.
Sometimes authority is unclear.
Sometimes information never reaches the person who needs it.
Sometimes two reasonable parts of the organization operate from conflicting priorities.
Often, several conditions interact.
Visible problems are signals
Missed deadlines matter.
Poor communication matters.
Weak performance matters.
Founder intervention matters.
The mistake is treating each visible problem as a complete explanation.
A symptom tells you where to look.
The surrounding structure helps explain why the symptom keeps appearing.
Leaders make stronger decisions when they understand both.
A capable person should not spend months compensating for a broken structure.
A broken structure should not protect someone from legitimate accountability.
The work is to understand which problem exists before deciding what needs to change.
When the same strain appears across several people, roles, decisions, or workflows, the question becomes larger than individual performance.
At Malia Heath Consulting, the Operating Clarity Diagnostic examines those repeated patterns before an organization commits to new roles, processes, tools, or larger structural changes.
Because the first responsible step is not deciding who or what to fix.
The first step is understanding what is producing the result.
