The KPI Trap: Why Obsessing Over Numbers Makes Your Team Miss What Matters

In 1999, psychologists Christopher Chabris and Daniel Simons ran a now-famous experiment. They showed participants a video of two teams passing a basketball and asked them to count the number of passes made by one team. Halfway through the video, a person in a gorilla suit walked across the court, thumped their chest, and walked off. Around half the participants never saw it.

They were not stupid or inattentive. They were doing exactly what they were asked to do. The problem was that the task — counting passes — consumed their attention so completely that they became blind to everything else, including something as obvious as a gorilla.

What This Means for How You Set KPIs

Most organisations set KPIs with the best of intentions: create clarity, align effort, measure progress. But when KPIs are too narrow, too many, or set without context, they produce exactly the gorilla problem — teams become so focused on the number that they stop noticing what is actually happening in the business.

A customer support team obsessing over average handle time will reduce it — and quite possibly destroy customer satisfaction in the process. A sales team chasing revenue targets will close deals — and sign customers who churn in month three. A product team tracking feature velocity will ship fast — and build the wrong things quickly.

In each case, the KPI is being hit. The gorilla goes unseen.

The Signs Your KPI Framework Has This Problem

• Teams report green on metrics while the business feels wrong. Everyone hits their number, but customer complaints are rising, margins are eroding, or staff turnover is climbing.
• People stop flagging problems. When performance management focuses on hitting targets, people learn not to surface the issues that threaten them.
• Process bottlenecks persist for months. They are visible to everyone doing the work — but the people reviewing dashboards never see them.
• Managers spend more time explaining KPIs than improving operations. When metrics become the goal rather than the signal, the conversation shifts from outcomes to numbers.

A Better Approach to Performance Measurement

The goal is not to remove measurement — it is to set measures that create peripheral vision rather than tunnel vision. Three principles help:

1. Limit the number of KPIs

The more measures a team tracks, the more of the gorilla problem you create. Three to five meaningful indicators per function is almost always more effective than fifteen. Force the question: if we could only measure one thing in this team, what would it be? Build from there.

2. Balance leading and lagging indicators

Lagging indicators (revenue, NPS, retention) tell you what happened. Leading indicators (response time, pipeline quality, onboarding completion) tell you what is likely to happen. Teams that track only lagging indicators are always reacting. Teams that track only leading indicators sometimes optimise for activity rather than results. You need both.

3. Create space for qualitative observation

Numbers cannot capture everything. Regular structured conversations — team retrospectives, customer listening sessions, frontline feedback loops — give your people permission to surface what the metrics are missing. This is where you find the gorillas.

The Right Question Is Not "Are We Hitting Our KPIs?"

The right question is whether your KPIs are giving you an accurate picture of the business. There is a meaningful difference. The first question drives people to hit numbers. The second drives people to build something that works.

Teams that hit all their KPIs and miss the gorilla are, by definition, measuring the wrong things. Start there.