When something keeps going wrong in your business, there are two things people reach for: blame the people, or blame the process. Both are usually wrong, or at least incomplete. The question isn’t which one is responsible. The question is which one is the root cause. That distinction determines whether the fix you’re about to make will actually work.
I’ve seen founders fire good people because a broken system made them look incompetent. I’ve seen companies add more process on top of a team accountability problem and wonder why nothing changed. Getting this diagnosis right is one of the most operationally valuable things you can do. Here’s how I work through it.
Why Does the Diagnosis Matter More Than the Fix?
Because the wrong fix doesn’t just fail. It wastes months, damages the people involved, and leaves the root cause intact. A people problem and a systems problem look almost identical on the surface. Both produce missed deadlines, dropped balls, customer complaints, and frustrated leaders. The presenting symptoms don’t tell you the cause. You have to dig.
The cost of misdiagnosis is real. Fire someone who was set up to fail, and you’ll hire their replacement into the same broken environment. Build a detailed process around someone who simply isn’t doing their job, and you’ll have an expensive procedure that nobody follows. Either way, the problem persists and you’ve wasted months.
What Four Questions Actually Separate People Problems from Systems Problems?
1. Does the problem follow the person, or does it follow the role?
This is the fastest diagnostic question. If the same failure mode appeared in the last person who held this role, or if every team member handling this function produces the same errors, you have a systems problem. The role is broken, not the person in it.
If the failure mode is specific to one individual, and everyone else in similar roles is executing without the same friction, you’re looking at a people problem. The role is functional. The person isn’t performing it.
2. Is the expectation documented, communicated, and measurable?
You cannot hold someone accountable for a standard they didn’t know existed. Before you call something a people problem, you need to confirm that the expectation was explicit, the person understood it, and there’s a clear way to measure whether it’s being met.
If the answer to any of those three is “not really,” you don’t have a people problem yet. You have an accountability system that was never built. That’s a systems problem, and it belongs to leadership, not the employee.
3. What happens when you give someone excellent a broken process?
One of the best diagnostics is a thought experiment: if you dropped your absolute best performer into this role, would the problem go away? If the answer is yes, if raw talent or diligence could overcome the friction, then you may have a people problem. But if even your best person would hit the same walls, the system is the constraint.
In my experience running operational diagnostics, this question alone surfaces the real issue faster than almost anything else.
4. Has the person ever performed this function well?
If someone used to execute well and now isn’t, something changed. Either the role grew beyond their capability, the environment shifted, or something is affecting their performance. None of those are simple “people problems.” They require different interventions. Capacity problems call for training or restructuring. Motivation problems call for direct conversation. Environmental problems call for leadership attention.
Only the scenario where someone was never able to execute the role, and was hired incorrectly, is a clean people problem at the root.
The Most Common Misdiagnosis I See
Founders who are scaling past the point where they can be in every decision almost always underestimate how much of what looks like a people problem is actually a systems problem. The business has been growing fast. Nobody had time to build clean processes, document expectations, or create real accountability structures. Decisions happen in Slack threads. The “process” for most things is “ask the founder.”
In that environment, even highly capable people will underperform. They spend half their energy navigating ambiguity instead of executing. They make inconsistent decisions because they have no guidance. They miss things because handoffs aren’t defined. Then leadership looks at the output and concludes the team isn’t strong enough.
Sometimes that’s true. Often it isn’t. And the only way to know is to build the system first and see what happens. This is exactly the pattern I surface in a Forge Assessment: separating what’s structural from what’s individual.
What Do You Do When It’s Both?
The honest answer is that most operational breakdowns involve both elements in some proportion. A weak system masks talent. Talent shortage masks system gaps. The sequencing question, which do you fix first, is where strategy comes in.
My default: fix the system first. Build the expectation, the process, the accountability structure. See who rises. The people who were frustrated by ambiguity will perform better. The people who were hiding in the ambiguity will become visible. You’ll make better decisions with that data than you will guessing.
See also: 5 Signs Your Operations Are Killing Your Growth and The Real Cost of Operational Chaos. Both are useful context for what happens when this diagnosis gets delayed.
How to Actually Fix It, Regardless of Which It Is
If it’s a systems problem:
Document the expectation. Map the process end-to-end. Define the handoffs. Build the measurement. Give people the tools and the clarity they need to execute. Then enforce the standard consistently.
If it’s a people problem:
Be direct. Have the specific performance conversation with clear expectations and a timeline. Don’t manage around it. Don’t add supervisory layers that create more complexity. Either the performance changes or the person changes. Both are faster and less expensive than tolerating a misaligned team member in a critical role.
If you’re not sure:
Get an outside set of eyes. I don’t say that as a sales pitch. I say it because the founder who built the culture and designed the roles is usually the last person who can see which it is. Proximity distorts diagnosis. An external operational lens, someone who has no stake in either answer, can separate the two in a fraction of the time it would take internally.
What’s the Fastest Path to Clarity?
If your business keeps breaking in the same places and you’re not sure whether it’s the people or the architecture, that’s what the Forge Assessment was designed to answer. Thirty days of embedded operational work, not interviews from the outside, but real observation of how work actually flows, produces a clear picture of what’s structural versus what’s individual. Most founders find the answer isn’t what they expected.
How do I know if underperformance is a people problem or a process problem?
Ask whether the failure follows the person or the role. If multiple people in the same role produce the same errors, the process is broken. If the failure is specific to one individual while others execute cleanly, you likely have a people problem. The clearest signal: would your best performer have the same issue in this role? If yes, it’s the system.
What’s the biggest mistake founders make when diagnosing operational breakdowns?
Attributing systems failures to individuals. In fast-growing businesses, ambiguity is often the real culprit: unclear expectations, undocumented processes, no accountability structure. Before calling something a people problem, confirm the standard was explicit and measurable. Most of the time, founders find they never actually built the system they assumed existed.
Should I fix the system or the team issue first?
Fix the system first. Build the process, define the expectations, create the accountability structure. See who rises to it and who doesn’t. You’ll have much better information for people decisions once the environment is clear. People who were frustrated by ambiguity will improve; people who were hiding in it will become visible.
What role does a fractional operating partner play in diagnosing these issues?
A fractional operating partner brings diagnostic distance. The founder who built the culture and designed the roles is often the last person who can objectively separate people problems from systems problems. Proximity distorts the view. An embedded external operator can observe how work actually flows, interview without bias, and separate structural issues from individual ones faster and more accurately than internal assessment.
Can a business have both people problems and systems problems at the same time?
Yes, and most do. The strategic question is which to fix first. Systems problems are almost always the higher-priority fix, because a broken system makes talent look weaker than it is. Once the system is solid, you have clear signal on individual performance. Trying to solve people problems inside broken systems usually produces wrong decisions and wasted moves.
If you’re stuck in that diagnostic loop, team problems, process problems, and you’re not sure which is which, the Forge Assessment is where clarity starts. Book a discovery call →
Jason Bonito is the founder of Crucible76, a fractional operating partner practice helping scaling businesses fix operational chaos and build systems that hold. DATA · DECISIONS · GROWTH.
