Accountability without capability is not performance management. It is pressure wearing a dashboard.

Leaders love outcomes.

Higher First Contact Resolution. Faster delivery. Better customer satisfaction. Fewer escalations.

Fair enough. Outcomes matter.

But sometimes leadership announces the target, adds it to a dashboard, and behaves as though the measurement itself has created the capability to achieve it.

It has not.

A speedometer can tell you the car is slow. It cannot replace the engine.

The IT delivery example: First Contact Resolution

Imagine a Service Desk is told to increase First Contact Resolution from 62 percent to 75 percent within one quarter.

The analysts understand the goal. Resolving more issues during the first interaction is better for customers, reduces transfers, and lowers demand on specialized support teams.

But the conditions have not changed.

New analysts receive two weeks of compressed training before entering the queue. The knowledge base contains duplicate articles, outdated screenshots, and procedures written for systems that were replaced last year. Password tools are unreliable. Analysts lack access to several diagnostic platforms. Some application teams refuse to authorize the Service Desk to perform routine recovery actions.

Meanwhile, the call mix has become more complex after a major technology rollout.

Management reviews the FCR dashboard every week and asks why performance is not improving.

Team leaders coach analysts to “take more ownership.” Analysts keep customers on calls longer while searching for answers they cannot access. Some guess. Others avoid transferring calls because the transfer lowers their score.

Repeat contacts rise. Average handling time increases. Customers explain the same problem multiple times. Higher-level teams receive poorly diagnosed incidents that are now older and more frustrating.

The target was reasonable.

The operating system beneath it was not.

The consequences spread across the service

For employees: analysts are held responsible for outcomes they do not have the knowledge, authority, or tools to control. Coaching starts to feel like blame. Confidence falls, experienced employees become cynical, and new employees learn to protect the metric rather than serve the customer.

For service delivery: calls become longer, repeat demand grows, and incorrect fixes create additional incidents. The Service Desk may report a temporary FCR improvement while total customer effort and downstream workload increase.

For customers: customers wait while analysts navigate broken knowledge and missing access. They may receive a confident answer instead of a correct one—the operational equivalent of painting over a warning light.

For the organization: leaders make decisions using a distorted picture of performance. Costs move between departments rather than decline, employee turnover increases, and confidence in the measurement system weakens.

What human behaviour tells us

People build confidence partly through successful experience. When effort repeatedly fails because the environment blocks action, employees may reduce initiative and become more cautious. This can resemble learned helplessness, although no single workplace pattern proves a psychological condition.

The more immediate point is behavioural: if employees are punished for transferring a call but lack the capability to resolve it, the system encourages delay, guessing, or metric protection. That response is not mysterious. It is adaptation.

Employees cannot consistently outperform the tools, knowledge, authority, and processes surrounding them. Motivation helps. It does not create system access.

Lessons for managers

  • Diagnose the capability gap. Separate issues of effort from gaps in skill, knowledge, access, authority, staffing, and process.
  • Coach with evidence. Review why contacts were transferred and what would have enabled resolution—not merely who transferred them.
  • Fix recurring blockers. Convert common escalation reasons into training, knowledge, access, or automation improvements.
  • Protect correct decisions. Analysts should not be penalized for transferring work that genuinely requires specialized support.
  • Measure the whole journey. Pair FCR with repeat contacts, handling time, customer effort, quality, and downstream rework.

Lessons for organizations

  • Treat every important target as a dependency map, not merely a number.
  • Give front-line teams reliable knowledge, diagnostic tools, and bounded authority.
  • Make resolver teams accountable for shifting appropriate capability toward the first point of contact.
  • Fund enablement before increasing targets and declaring a performance problem.

Key takeaways

  • A target does not create the conditions required to achieve it.
  • Accountability must be matched with capability and authority.
  • Employees will protect metrics when metrics punish correct operational decisions.
  • First Contact Resolution is an organizational capability, not solely a Service Desk behaviour.
  • Before asking why people missed the target, ask what the system allowed them to do.

Discussion question: Which result does your organization measure aggressively while underinvesting in the capability required to deliver it?