There's a diagnosis that gets applied in nearly every leadership team I encounter, and it's almost always wrong. The diagnosis is that the organization has a people problem. Specific staff aren't performing. A function isn't delivering. A team is dysfunctional. Leadership in a particular area is weak. The conversations focus on individuals. Performance reviews. Coaching. Restructuring. Replacement. Significant leadership attention gets directed toward fixing the people. The fixes happen. New people arrive, others leave, structures get redrawn. And the same problems show up six months later, attached to different names. The cycle repeats. The diagnosis stays the same. The actual cause goes unaddressed.

What's almost always happening underneath the people problem framing is a system problem. The systems the organization has built, formal and informal, are producing the conditions that make the people look like the problem. The people are responding to the systems they're operating in. They're applying judgment to ambiguous processes. They're filling gaps that infrastructure should be filling. They're absorbing inconsistencies that would crash the operation if absorbed differently. They're producing outputs the organization has come to expect, given the systems available to produce them. When the outputs are inadequate, the systems are inadequate. The people, with rare exceptions, are doing what the systems make possible.

This framing is uncomfortable for most leadership teams because it points the finger at decisions leadership has made or failed to make about infrastructure, process, and structure. The people framing is more comfortable because it locates the problem in someone else, somewhere else, fixable through decisions about hiring, performance, and accountability. The comfort doesn't change the reality. The system problem keeps producing the conditions that get diagnosed as people problems, regardless of how many times the people get changed.

Here's how the misdiagnosis plays out across common organizational dysfunctions.

The finance team isn't producing decision-ready intelligence for leadership. The standard diagnosis is that the finance leadership isn't strategic enough, that the team lacks the analytical capacity, that the function needs stronger talent. The actual diagnosis is usually that the chart of accounts, the cost allocation methodology, and the reporting structure don't support decision-ready intelligence. The finance team is producing outputs that are accurate against the existing structure. The structure can't produce what leadership wants. Replacing the finance leadership produces a new finance leader who works heroically against the same structural constraints and produces marginally improved outputs that still don't reach what leadership wants. The system problem persists across leadership transitions, and each transition gets used to confirm that the issue must be a people issue, since changing the people didn't solve it. The people aren't the issue. The structure they're operating in is the issue.

Compliance isn't preventing findings. The standard diagnosis is that the compliance function isn't rigorous enough, that the compliance leader isn't strong enough, that the team needs better capabilities. The actual diagnosis is usually that the compliance function is operating reactively because the systems and infrastructure required for proactive compliance haven't been built. The function is processing obligations as they arrive, with no capacity for the structural work that would prevent the conditions that produce findings. Replacing compliance leadership produces a new leader who works inside the same reactive constraints and generates the same kinds of outcomes. The system problem persists. The finger keeps pointing at the people.

Operations are slow and frustrating to work with. The standard diagnosis is that the operations leadership needs to be more accountable, that the team needs better discipline, that the function needs stronger management. The actual diagnosis is usually that the processes operations is running aren't documented at the level of detail the operation requires, the systems supporting the processes don't produce the artifacts the processes need, and the integration between operations and the functions it serves runs on ad hoc communication rather than structured handoffs. Operations is doing what the systems allow. The systems don't allow what leadership wants. Changing the operations leadership doesn't change the systems. The dysfunction persists, with new names attached.

Programs are underperforming. The standard diagnosis is program leadership, program staff, or program design. The actual diagnosis is usually that the cost allocation isn't reflecting actual program resource consumption, the reporting structure doesn't surface what program leaders need to see, the support functions aren't providing what programs require, and the strategic decisions about program investment are being made on financial intelligence that doesn't reflect operational reality. The programs are operating at the level the systems make possible. The systems don't make better operation possible. Replacing program leadership doesn't address what's constraining program performance.

Cross-functional collaboration is weak. The standard diagnosis is that leaders across functions aren't communicating, that the executive team isn't aligned, that the culture isn't collaborative enough. The actual diagnosis is usually that the systems supporting cross-functional work, shared data, integrated processes, common reporting, coordinated planning, don't exist or operate poorly. The leaders are coordinating manually, through meetings and emails and ad hoc agreements, because the systems that would produce coordination as a byproduct of normal operations weren't built. The leaders look like they're not collaborating. They're collaborating heroically against systems designed to operate in silos. Changing the leaders doesn't change the systems.

The pattern repeats across organizational functions. People are diagnosed as the problem. The diagnosis produces interventions that focus on people. The interventions don't address the underlying system conditions. The problems persist, sometimes attached to new people, sometimes returning to the same people after a brief transition period when the new arrangement gets accommodated. The systems keep producing the dysfunction the diagnosis keeps misattributing.

The reason this misdiagnosis is so persistent is that systems work is harder than people work. People work has visible deliverables. Hiring decisions, performance plans, organizational charts, leadership transitions. Each one is a discrete intervention that can be tracked and reported. Systems work is structural and slow. Rebuilding the chart of accounts, redesigning processes, implementing system integrations, embedding compliance into workflows. The deliverables are abstract until they're operational, and operational improvement from systems work shows up over months rather than in immediate visible change. Leadership pressure to act quickly on visible problems pushes toward people interventions. The pressure to invest in systems work, with longer payback and less visible progress, is structurally weaker. So organizations make people decisions repeatedly, in response to symptoms the systems are producing, without ever addressing what's actually causing the symptoms.

The cost of this pattern compounds significantly over time. Leadership turnover in functions where the system constraints are real generates substantial cost. Severance, recruiting, onboarding, transition disruption, lost institutional knowledge. Each cycle costs the organization meaningfully. The cumulative cost across multiple cycles in multiple functions, over years of misdiagnosed system problems, is enormous. None of it gets attributed to the system problems. It gets attributed to talent issues, market conditions, or the inherent difficulty of finding good leadership. The system conditions that are generating the talent turnover stay invisible.

The diagnostic test that exposes this clearly is what happens after a leadership change in a problem area. If the change produces sustained improvement, the people diagnosis was correct. If the change produces a brief improvement followed by the recurrence of the same problems, the system diagnosis is correct, and the leadership change just briefly masked the system condition until the new leader's approach got absorbed by the constraints the previous leader was working against. Most leadership teams can identify multiple areas where the second pattern has played out, sometimes across multiple cycles, without recognizing what the pattern is telling them.

The organizations that produce sustained operational improvement do something different. They start with system diagnosis. When a function isn't performing, they examine the systems the function is operating in, identify the constraints those systems are imposing, and determine whether the constraints are causing the performance issue. If the systems are sound and the people aren't performing, they address the people. If the systems are inadequate, they address the systems first, and reassess people performance in the context of improved systems. The sequencing matters. Addressing systems before people surfaces what the actual people performance is when the systems support good performance, rather than when the systems are forcing heroic compensation. Sometimes the result is that the existing people perform well in better systems, and the people diagnosis was wrong. Sometimes the result is that the people genuinely aren't right for the role, and the people change is appropriate. Either way, the diagnosis is grounded in evidence rather than in the comfort of locating the problem in individuals.

If your organization keeps having the same problems with different people in the same roles, the people aren't the issue. The systems they're operating in are the issue. The diagnosis you've been applying is wrong, and the cost of the wrong diagnosis is the cumulative cost of all the people interventions that haven't addressed what's actually producing the problem.