Case Insight #10: When a Performance Gap Is Misdiagnosed as a Capability Gap

Organizations often respond to disappointing performance with development.

More coaching. More training. Better time management. Stronger prioritization. Greater accountability.

Sometimes those are exactly the right interventions. But they depend upon an important assumption: that the constraint sits with the individual.

A recent experience with a newly promoted management group made me question how often organizations test that assumption before acting on it.

The Situation

The managers were relatively new to their roles.

They were also intelligent, motivated, and genuinely interested in succeeding. They wanted to perform well. They wanted to understand what leadership needed from them. They were receptive to guidance and willing to develop.

Yet a gap was growing between how the executive expected the management team to operate and what he was experiencing from them.

The managers needed to ask better questions.

They needed to prioritize more effectively.

They needed to present their KPIs.

They needed to develop strategies for their teams.

They needed to make more decisions independently rather than continually seeking input or approval.

They needed to communicate appropriately and transparently with customers.

From the executive's perspective, these were reasonable expectations of managers.

And they were.

The difficulty was that the managers did not necessarily know what those expectations meant in practice.

What Appeared to Be a Development Problem

The initial interpretation was largely about capability.

The managers needed coaching and development. They needed help managing their time, prioritizing their responsibilities, and operating at the level expected of them.

Training was readily available.

But as I spent time with the managers, a different question began to emerge.

Had anyone actually defined what they were being asked to do?

Ask better questions.

What kinds of questions did leadership consider useful?

Present your KPIs.

Which KPIs mattered, and what decisions were they intended to inform?

Develop a strategy for your team.

What was the broader organizational direction that strategy should support?

Make decisions independently.

Which decisions belonged to managers, and which required executive involvement?

Be transparent with customers.

What did appropriate transparency mean when customer relationships, commercial considerations, and operational realities intersected?

The issue was not that every expectation required a detailed procedure. Management requires judgment precisely because not every situation can be prescribed. But judgment still develops within context. And much of that context had remained implicit.

What Closer Examination Revealed

The managers were being asked to close a gap they could not fully see.

Leadership had an internal understanding of what effective management looked like. Years of experience had created expectations around judgment, escalation, prioritization, communication, and ownership.

Those expectations made sense from where leadership was sitting.

But they had not necessarily been translated into an operating model the managers could interpret.

The managers therefore had to infer what good looked like.

That changed how I interpreted some of the behaviours being observed.

A manager repeatedly seeking approval might lack confidence or decision-making capability. But the same behaviour can emerge when decision rights are unclear.

A manager struggling to prioritize might need stronger time-management skills. But prioritization also requires criteria. When several demands compete, someone needs to understand which customer, risk, deadline, commercial objective, or organizational priority should take precedence.

A manager struggling to create a team strategy may need strategic-development support. But team strategy also requires enough organizational direction to know what the team is aligning toward.

The behaviour was observable.

Its cause was not.

The Diagnostic Risk

This distinction matters because the diagnosis determines the intervention.

If the problem is assumed to be individual capability, the logical response is to develop the individual.

Training.

Coaching.

Mentoring.

More feedback.

More tools.

Those interventions may all be valuable.

But they solve different problems from unclear decision rights, undefined outputs, competing organizational priorities, inconsistent leadership expectations, or insufficient organizational context.

A manager can learn a sophisticated prioritization framework and still not know what the organization wants prioritized.

A decision-making model can improve someone's analytical process without establishing which decisions the role actually owns.

Communication training can strengthen how a manager communicates without answering what the organization expects that manager to communicate to a customer.

The intervention may therefore be perfectly reasonable while still operating at the wrong level of the system.

When the Intervention Creates a Second Gap

There is another consequence that is easy to miss.

Once development has been provided, leadership reasonably expects something to change.

The managers received training. They received coaching. They were given tools. The organization intervened. Expectations therefore rise.

But if the original behaviour was being shaped partly by organizational ambiguity, the environment to which those managers return may be substantially unchanged.

Decision rights remain unclear. Expected outputs remain implicit. Priorities still require interpretation. Organizational direction has not necessarily become easier to translate. The behaviour may therefore persist. Only now, the organization believes it has addressed the problem. An intervention intended to close a performance gap can inadvertently widen the perceived gap between expectation and performance when the condition producing the behaviour remains untouched.

That creates risk for both the organization and the individual. Leadership becomes increasingly frustrated that development has not produced the expected change. The employee may receive progressively stronger feedback about behaviour they are still trying to interpret within an ambiguous environment.

Neither necessarily lacks good intent.

The diagnosis may simply have been incomplete.

What Changed

My focus with the managers became less about providing answers and more about creating enough structure for them to operate.

Frameworks helped make expectations more tangible.

Questions could be organized around the decisions they were intended to support.

Outputs could be clarified.

Management responsibilities could be translated into something more concrete.

The objective was not to eliminate judgment or prescribe every action. It was to give managers enough organizational context to begin exercising judgment with greater confidence.

That distinction is important. Structure does not replace development. It gives development somewhere to go.

Once expectations, boundaries, and organizational context become clearer, mentoring becomes more useful because experienced leaders can explain how judgment is exercised within the organization. Coaching becomes more useful because there is a clearer outcome toward which someone is developing. Training becomes more useful because new skills can be applied within an environment that supports them.

Individual capability and organizational structure can then begin reinforcing one another.

What This Case Reveals

Performance gaps are observable.

Capability gaps require diagnosis.

The distinction is easy to overlook because the behaviour appears through a person. Someone is asking too many questions. Someone is escalating too frequently. Someone is prioritizing poorly. Someone is not demonstrating enough ownership.

The individual becomes the most visible part of the problem.

But the location of the symptom does not necessarily identify the location of the constraint.

The constraint may sit with the individual.

It may sit in the role.

It may sit between organizational levels.

It may sit in governance, decision rights, leadership behaviour, strategic clarity, or the systems through which expectations are translated.

Sometimes it sits in several places at once.

The purpose of diagnosis is not to remove individual accountability.

It is to make sure accountability is attached to something the individual can reasonably understand and influence.

Questions for Leaders

When someone is not meeting expectations, before deciding how to develop them, it may be worth asking:

• Have we defined what successful performance actually looks like?

• Does the individual understand the outputs expected from the role?

• Are decision rights and escalation boundaries sufficiently clear?

• Have organizational priorities been translated into criteria the individual can use to make trade-offs?

• Are we asking someone to exercise judgment without providing enough organizational context to develop that judgment?

• Is the behaviour we are observing evidence of an individual capability gap, or could it be a rational response to the environment?

• Are we intervening at the same level of the system where the constraint actually exists?
  

Training, coaching, and mentoring remain important investments in organizational capability.

But development works best when organizations understand what they are developing people toward.

Before trying to close a performance gap, diagnose where the gap actually begins.

---

Related Content

Organizational Coherence Framework Examines whether strategy, structure, governance, leadership behaviours, incentives, and operating practices reinforce one another. This case shows what can happen when expectations at one level of the organization are not sufficiently supported by the systems surrounding them.

How Strategic Integrators Think Explores how Strategic Integrators look beyond the immediately visible problem to examine the relationships and organizational conditions producing it. This case applies that diagnostic lens to the distinction between observed performance and individual capability.

Seeing Systems Instead of Symptoms Explores why the most visible organizational problem is not always where the underlying constraint sits, and how looking beyond symptoms can lead to better diagnosis and more appropriate intervention.