Recovering Performance Starts With Diagnosing the System

When performance drops, organizations often begin by asking:

Who is underperforming?

Sometimes that is the correct question.

But it is rarely the only one.

Performance is shaped by the interaction between people, goals, workflows, incentives, tools, leadership, and customer conditions.

Focusing only on individual accountability can hide the larger system producing the result.

I experienced this while supporting a high-value portfolio in which delivery performance was at risk.

The work involved multiple teams, significant commercial expectations, demanding timelines, and customers with very different needs.

There was no single dramatic failure.

Instead, the risk appeared through smaller signals:

• Work was not being prioritized consistently

• Teams were reacting to urgent requests rather than managing the portfolio

• Ownership was not always clear

• Some accounts received disproportionate attention

• Performance conversations focused on outcomes without examining the behaviors producing them

• Leaders lacked a reliable view of where intervention was needed

The first step was to make the problem visible.

That meant moving beyond aggregate results and looking at the operation from several angles.

Which accounts were at risk?
Where was work stalled?
Which activities were not happening consistently?
Were expectations realistic?
Were teams using the same definitions?
Which problems required coaching, and which required process changes?

This distinction is essential.

A capability problem requires coaching or training.

A capacity problem may require prioritization or staffing changes.

A clarity problem requires better ownership and expectations.

A process problem requires redesign.

A motivation or accountability problem requires direct leadership action.

Those issues can produce similar performance symptoms, but they cannot be solved in the same way.

The recovery effort focused on creating stronger operating discipline.

That included clearer priorities, more frequent performance reviews, visible action plans, defined ownership, and earlier escalation of risk.

The point was not to add more meetings.

It was to make each review useful.

A strong performance conversation should answer:

• What happened?

• Why did it happen?

• What action is being taken?

• Who owns that action?

• When will progress be reviewed?

• What support or decision is required?

This shifts the conversation from reporting to management.

Another important lesson was that recovery cannot depend entirely on senior leaders personally chasing every issue.

The objective is to build a repeatable mechanism through which teams can identify problems, take action, and escalate appropriately.

Performance improves more sustainably when the organization becomes better at recognizing and responding to risk.

Accountability remains important.

People need clear expectations, meaningful feedback, and consequences when performance does not improve.

But accountability is strongest when the organization has also done its part:

The priorities are clear.
The process is workable.
The data is visible.
The support exists.
The expectations are consistent.

Performance management is not only about managing people.

It is about managing the conditions in which people are expected to perform.