The person is struggling.
The output is inconsistent. The deadlines are missed. The quality isn’t there.
The founder’s instinct is to address the person. Raise the standard, have the harder conversation, manage them more closely, or eventually replace them.
Sometimes that’s the right call. But a significant portion of the time, the process never gave the person a real chance to succeed. The outcome definition was vague. The decision authority was unclear. The steps existed somewhere but nobody had shown them where.
When that’s the case, replacing the person produces the same outcome with a different face attached to it. The structure doesn’t change. The next person inherits the same gaps.
Getting the diagnosis right before making the personnel call is one of the most valuable habits a founder can build. The misdiagnosis is common, it’s expensive, and it’s almost always avoidable.
Why the Misdiagnosis Happens So Often
Behaviour is visible. Structure isn’t.
When something goes wrong operationally, what the founder sees is a person who didn’t deliver. The missed deadline, the inconsistent output, the client who came back with a problem that should have been caught internally. The person is the observable variable. The process that surrounded them is invisible.
This isn’t a failure of judgment. It’s a natural response to where the evidence shows up. The performance conversation is concrete: this person, this outcome, this standard not met. The structural conversation is more abstract: the process, the design, the gaps in ownership and clarity that shaped what was possible.
Add to that the reality that accountability conversations are uncomfortable. It’s often easier to name a person as the problem than to sit with the more complicated question of what the business built around them.
The result is a pattern that many founder-led businesses know well: the hire who didn’t work out, followed by the next hire who also didn’t work out, followed by the slow realisation that the person wasn’t the variable.
What a Process Problem Actually Looks Like
A process problem produces a specific set of signals. They’re worth knowing, because they’re often misread as performance signals.
Inconsistency across the team. Different people doing the same task produce wildly different outputs. Some get it right. Some don’t. The variation isn’t explained by skill or attitude. It’s explained by the fact that each person is solving the task in their own way because there’s no defined way to do it.
Recurring errors at the same point. The same type of mistake keeps appearing. Different people, different contexts, same failure mode. When an error is structural, it recurs. When it’s individual, it tends to be isolated.
Work that only functions when a specific person does it. If one team member produces excellent results on a task and everyone else struggles, that’s usually a sign the process lives in that person’s head rather than in a shared system. The process isn’t documented. It’s modelled.
New hires taking too long to get up to speed. When onboarding is slow and the standard varies dramatically between people, it’s usually because the process isn’t clear enough to transfer. The experienced person knows how to do the work. They just can’t explain it in a way that lets someone else replicate it.
In all of these, the person isn’t the root cause. The person is experiencing the process problem. The same person, in a well-designed process with clear ownership and outcome definition, often performs at a significantly higher level.
What a People Problem Actually Looks Like
A people problem has a different signature.
The process exists. It’s documented well enough. The outcome is defined. The person has been shown what good looks like. The decision authority is clear. The tools are in place. Other people are doing the same work and delivering.
And this person still isn’t.
That’s a people problem. Not a process problem dressed up as one, not a structure gap that looks like underperformance. A genuine mismatch between what the role requires and what this person consistently delivers, in conditions where delivering was genuinely possible.
The distinction matters because the intervention is different. A process problem is addressed by designing the process. A people problem is addressed through the performance conversation, the coaching, the clear expectation reset, and if none of that works, the personnel decision.
Running a performance conversation on a process problem doesn’t fix the process. It adds pressure to someone navigating a system that wasn’t built to let them succeed.
The Test Before Any Personnel Conversation
Before raising a performance issue with a team member, three questions are worth asking honestly.
Has this person had a real process to work within? Not a rough outline or an informal understanding of how the work gets done, but a documented process clear enough that someone new could follow it. If the answer is no, the process gap is the first problem to address.
Has the outcome been defined specifically enough to be measured? “Do this well” is not an outcome definition. If the standard isn’t clear enough to compare against, the team member is being held accountable to a benchmark they couldn’t fully see. That’s a process problem.
Has this person had real decision authority? If they had to ask permission for decisions that should have been within their scope, or if they were second-guessed when they made calls the role entitled them to make, the accountability structure isn’t supporting their ability to own the outcome.
If any of these answers is no, the personnel conversation is premature. The structural gap comes first. Once the structure is in place, the performance conversation, if it’s still needed, has a clear foundation.
Why the Wrong Diagnosis Is Expensive
Replacing the person in a broken process doesn’t fix the process. It restarts the clock.
The new hire comes in. They’re shown the role. They navigate the same gaps the previous person navigated. They either compensate for the structural problem through individual effort (which means the system is still dependent on a specific person’s workarounds), or they run into the same issues and deliver the same inconsistent outcomes.
The cost is real: the time to hire, the time to onboard, the disruption to the team, the client impact during the transition. And at the end of it, the business is back at the same point with a different person in the seat.
There’s also a less visible cost. When the team watches someone be held accountable for a problem that the structure caused, they notice. It signals that performance is judged on outcomes without accounting for whether the conditions for those outcomes were in place. That erodes trust and dampens the discretionary effort that good team members bring to their work.
How to Tell Which One You Have
The diagnostic is more straightforward than it sounds.
Map the process before the performance conversation. What does the work actually require? What steps are involved? Where does the process hand off from one person to another? Where are the decisions made and by whom?
If that map doesn’t exist, or exists only in someone’s head, the process hasn’t been designed. That’s a process problem.
If the map exists, check whether the person in question had access to it in a usable form. A documented process that lives in a folder nobody knows about isn’t a functioning process.
Then check the output from other people doing the same or similar work. If the variance is high across the team, the process is the variable. If the variance is low and this person is the outlier, the person is more likely the variable.
This takes honesty. Founders who have already decided the answer tend to find evidence that confirms it. The diagnostic is only useful if the question is genuinely open.
When It’s Genuinely a People Problem
Structure doesn’t solve everything.
There are situations where the process is well-designed, the outcome is clearly defined, the person has been given real authority and real support, and the delivery still doesn’t meet the standard. Sometimes the role isn’t the right fit for this person’s strengths. Sometimes the values aren’t aligned with how the business operates. Sometimes the person has reached the edge of their current capability.
In those cases, the performance conversation is right. Not because the structure failed, but because the structure has done what it can and the constraint is elsewhere.
The important thing is sequence. Structure first. Process clarity first. Outcome definition first. Decision authority first. When those are in place and the performance still doesn’t hold, the conversation becomes about the person and what they actually need, which might be development, might be a different role, or might be a different business.
Arriving at that conversation having genuinely built the conditions for success makes it a more honest conversation for both sides.
For a deeper look at how to build accountability into the structure rather than leaving it to the performance conversation, read [how to build accountability into your team’s structure].
Frequently Asked Questions
How do I know if a performance problem is structural or individual?
Check whether the same type of failure recurs across different people in similar roles. If it does, the structure is the common variable. If the failure is isolated to one person while others in similar conditions are delivering, the individual is more likely the variable.
Should I fix the process before having a performance conversation?
If the process gap is contributing to the performance problem, yes. Having the performance conversation before fixing the structure puts the person under pressure for a problem they didn’t fully cause. Fix the structure first, reset expectations clearly, then assess performance against the new standard.
What if the person resists the process even after it’s been fixed?
That’s a different conversation. A person who won’t work within a clear, well-designed process even after it’s been explained and supported is showing you something about fit and values, not about process design. At that point, the people question is appropriate.
Can a good process compensate for a poor hire?
Up to a point. A good process reduces the variance between a strong hire and an adequate one. It can’t fully compensate for a significant skills gap or a values mismatch. It does, however, make both of those things easier to identify clearly, because the gap shows up against a defined standard rather than a vague expectation.
What’s the most common process problem founders mistake for a people problem?
Unclear ownership is the most common. When two people think the other is responsible for an outcome and it falls through, both look like they underdelivered. But the problem is that ownership was never assigned. Neither person failed. The structure failed to define who was accountable.
See What’s Structural in Your Business Right Now
If you’re not sure whether the problems you’re dealing with are people problems or process problems, the Business Diagnostic Quiz can help you see where the structural gaps actually live.