Is It a Systems Problem or a People Problem?

A team keeps missing deadlines. Morale is low. The same arguments surface in every meeting. Someone isn't pulling their weight or at least, that's how it looks from the outside.

The instinct is immediate: we have a people problem.

It's a natural conclusion. People are visible. Their behavior is observable. And when things go wrong, it's easier to point at a person than to interrogate the invisible architecture of how work actually gets done.

But here's what two decades of organizational research, and our own work inside hundreds of teams, consistently shows: most team dysfunction is a systems problem wearing a people costume.

Getting this diagnosis right isn't just an intellectual exercise. It determines whether your intervention actually works.

When we talk about a system, we don't mean software or org charts (though those are part of it). We mean the full set of structures, processes, norms, incentives, and information flows that shape how people behave at work.

The system includes:

• How decisions get made: who has authority, who gets consulted, who finds out after the fact
• How work is coordinated: handoffs, dependencies, meeting rhythms, communication channels
• What gets measured and rewarded: the metrics on the dashboard, the behaviors that get praised in all-hands
• What information people have access to: whether frontline employees know what leadership knows
• The psychological environment: whether it's safe to raise problems, admit mistakes, or challenge assumptions

Most of this is invisible. It's the water the fish swim in. And because it's invisible, when something goes wrong, we look at the fish.

Here's the most reliable test for distinguishing a systems problem from a people problem:

If you replaced this person with someone equally skilled and motivated, would the problem go away?

If the answer is yes, the new person would thrive where the current one is struggling, you likely have a people problem. The role is workable; this individual just isn't the right fit.

If the answer is probably not, the new person would eventually hit the same walls, develop the same frustrations, produce the same results, you have a systems problem. The system itself is broken.

We've seen this play out countless times. A company fires a "low performer" and hires a replacement. Six months later, the replacement is struggling in the same ways. The problem wasn't the person. The problem was a role with no clear authority, a team with no shared definition of done, and a manager who communicated expectations only when they weren't met.

If multiple people in the same position have struggled or if the person performs well in other contexts then it's the role is the problem. A talented professional who consistently underperforms in one specific environment is almost always being set up to fail by that environment.

Watch for: high turnover in a specific seat, a "difficult" team that cycles through managers, or a department that always seems to be in crisis regardless of who's running it.

When dysfunction is isolated to one individual, it might be a people problem. When it's distributed across a team or the entire organization, when everyone seems disengaged, or everyone is missing the same type of deadline, then the common denominator isn't the people. It's the system they're all operating inside.

Watch for: patterns that cut across tenure, seniority, and personality type. If your most experienced people and your newest hires are both struggling with the same thing, the system is the culprit.

If you've given clear feedback, provided support, and the behavior hasn't changed the question to ask isn't "what's wrong with this person?" It's "what in the system is making this behavior rational?"

People are remarkably adaptive. When someone keeps doing something that seems counterproductive, they usually have a reason, even if they can't articulate it. Maybe the incentive structure rewards the wrong behavior. Maybe the process makes the "right" way harder than the workaround. Maybe they've learned that raising problems leads to being assigned more problems.

Watch for: behavior that makes sense from the individual's perspective, even if it's harmful to the team.

None of this means people are never the issue. Sometimes they are.

A genuine people problem looks like this: the system is functional, other people in similar roles are succeeding, clear expectations have been communicated, support has been offered, and the individual still isn't performing or isn't aligned with the team's values.

At that point, the conversation shifts. But even then, the question isn't just "is this person the problem?" It's "did we hire well, onboard well, and give this person a real chance to succeed?" If the answer to any of those is no, the system still shares the blame.

The honest truth is that most "people problems" have a systems component. The person may need to go, but if you don't fix the underlying system, you'll be having this conversation again in twelve months with someone new.

There are a few reasons the people diagnosis is so seductive.

It's faster. Replacing a person feels like a decisive action. Redesigning a system is slow, ambiguous, and requires admitting that leadership may have built something broken.

It's less threatening. If the problem is a person, the solution doesn't require examining your own decisions. If the problem is the system, you have to ask: who built this system? Who allowed it to persist?

It's culturally reinforced. We live in a culture that prizes individual accountability. Attributing outcomes to systems can feel like making excuses. But accountability and systems thinking aren't opposites; they're complements. You can hold people accountable and fix the system that made failure more likely.

At Resilient Team System, we start every engagement with a diagnostic question: is this team struggling because of who they are, or because of how they're organized?

The answer is almost always "both, but mostly the latter."

Our three-force framework, Principle, Practice, and Purpose, is designed to surface the system. Principle examines whether the team has shared values and clear decision-making structures. Practice looks at how work actually flows: the rhythms, the handoffs, the feedback loops. Purpose asks whether people understand why their work matters and how it connects to something larger.

When a team scores low on Practice, for example, it rarely means the people are lazy or incompetent. It usually means the coordination structures are broken: meetings that don't produce decisions, unclear ownership, information that doesn't reach the people who need it.

Fix the Practice, and the "people problem" often resolves itself.

Before you conclude you have a people problem, work through these questions:

1. Has this problem appeared with multiple people in this role or context? If yes, look at the system.
2. Does the person perform well in other environments? If yes, look at this specific environment.
3. Is the expected behavior actually supported by the incentive structure? If not, fix the incentives.
4. Do people have the information, authority, and resources to do what's being asked of them? If not, fix the system.
5. Have expectations been communicated clearly and consistently? If not, that's a systems failure too.
6. Is the problem isolated or widespread? Widespread problems are almost always systemic.

If you've worked through these questions and the answer still points to the individual, then you have a people problem. But in our experience, most leaders who do this exercise honestly find themselves redesigning the system.

When you correctly identify a systems problem and fix it, something remarkable happens: people who seemed like problems become contributors. Conflict that seemed interpersonal turns out to be structural, two people fighting over a boundary that was never clearly drawn. Disengagement that looked like attitude turns out to be a response to a system that made good work impossible.

This is why the diagnosis matters so much. Not just for the individual involved, but for the whole team. Every time you blame a person for a systems failure, you lose the opportunity to fix something that's affecting everyone.

And every time you fix the system, you don't just solve the immediate problem. You build the kind of organization where talented people can actually do their best work.

That's what resilience looks like in practice.

Ready to find out whether your team's challenges are systems problems or people problems? The Team Resilience Assessment gives you a scored breakdown across Principle, Practice, and Purpose, so you can see exactly where your system is strong and where it needs work.