The Myth: Feedback Automatically Improves Performance
We’ve been told for decades that feedback is an agent for improved performance. If that were true, annual reviews would produce high-performing teams, generic comments would influence behaviour, and being told you “need to do more communication” would make you communicate better.
None of that has been shown thus far to work in any capacity. Furthermore, organizations don’t appear to be starved for feedback. In most, performance reviews happen annually, managers talk to people one-on-one regularly, there are post-project discussions, and feedback is “offered” in casual conversations. Employees continue to rack up “satisfactory” performances with write-ups, and employees’ careers are littered with commentary in the vein of “needs development in A, B, and C,” yet continue to repeat their same errors and get stuck in the same traps. The issue stems from the inability to give people the kind of feedback they might be receptive to.
This in particular is a really crucial distinction: feedback, on its lonesome, is just information.
Information becomes development in four areas:
Understanding
Acceptance
Retention and Translation to Behaviour
Action
Fail any of these four, and feedback may have been delivered, but it hasn’t been useful. This is where a deeply cherished organizational myth crumbles. So many leaders believe that they have “delivered the feedback” and thus have “done” the change development side themselves; the remainder is up to the employee.
Research clearly shows it does not work that way. In 1996, research conducted by Avraham Kluger and Angelo DeNisi undertook a meta-analysis of hundreds of studies of feedback interventions. While many feedback interventions were helpful, the research found that nearly a third of feedback interventions actually caused people to do worse.
This then begs the question: if feedback was so good for people’s performance, why would it be negative one-third of the time?
Such a realization clarifies why simply giving feedback isn’t the issue; rather, it’s the quality of that feedback across these different areas, as only good feedback develops behaviours.
Why Most Feedback Fails to Improve Performance
Unfortunately, most workplace feedback is not very useful. If you’re in a managerial position, think about what your employees hear every day:
“You need to be more strategic.”
“Improve your communication skills.”
“Take more ownership.”
“That didn’t turn out well.”
On the surface, these are all well-intentioned pieces of feedback. They acknowledge that something needs to change, but they don’t answer the most important question:
What, precisely, do I need to do differently?
Without this question, feedback is mere judgment and becomes an exercise in frustration. Imagine telling a person to “do a better job of taking care of their health.” Should they get more sleep? Exercise? Eat differently? Reduce stress? Drink more water?
The advice is not wrong; it is simply so broad that it is impossible to act on and will just be taken as something given in bad faith.
The same is true of workplace feedback. Telling your employee to “communicate better” leaves them with no direction on what behaviour to modify, when & how it needs to change, and how success will be assessed. Employees typically end such meetings knowing they didn’t meet expectations, but still unclear on what “different” looks like.
Clarity gives people confidence while vagueness makes them hesitate, and hesitation has a cost.
Employees unable to see what “good” is may second-guess their decisions, delay taking action, become silent rather than speak up, or fall back on familiar work patterns rather than try something new. We thus run into this weird scenario where the goal of feedback-to-performance-improvement can actually decrease this ratio.
Timing causes another major problem.
The annual or semi-annual performance review is the norm in many organizations. By the time the manager and employee gather to discuss an employee’s work, the events in question may have transpired months earlier.
Human brains are not wired to learn from events distant in the past; details, along with context, are lost, and emotions often overlay objective observation. Instead of an opportunity for improvement, the performance review turns into a historical document, and changing one’s behaviour yesterday is impossible. The more employees can effectively influence their behaviour tomorrow, the higher the quality of their outcomes will be. That is why organizations around the world are shifting from treating feedback as an event to treating it as a process.
Gallup, for example, asserts that feedback has an expiration date: the closer it comes to the event it is about, the more helpful and actionable it is. Employees who receive frequent meaningful feedback are significantly more engaged than those who receive it only once a year.
Sense & Direction – another common mistake involves turning feedback into a one-way street.
The manager delivers the feedback, the employee receives it, neither party is certain whether they understood each other, and the meeting ends.
As it should be obvious, learning doesn’t tend to work this way. Employees have to ask questions, be sure expectations are clear, reflect on their own point of view, and discuss the desired results; otherwise, assumptions, not clarity, will prevail.
Emotion (or lack thereof).
Nobody likes to feel that they have done something wrong. When feedback intended to encourage development is interpreted as evidence of incompetence, recipients’ defenses go up. People are more likely to work on solutions when they are not afraid of being judged by their manager. Ultimately, the purpose of feedback is to help the person grow, not to prove the manager was right.
Moving beyond evaluation and toward development is the first step in feedback, and, ironically, one factor has proven more valuable than anything else: stop thinking about the past and begin planning for the future.
The Science Behind Feedback That Actually Works
If bad feedback does not lead to performance improvement, the immediate thought is, what does?
As shocking as this may be to some readers, the answer is not, in fact, “more feedback.”
What happens in a lot of instances is that companies, when bad feedback doesn’t produce positive results in the organization, try giving more feedback, more feedback check-ins, reviews, or telling people the managers should provide feedback more regularly.
Although this would naturally spring up from good intention, more feedback won’t do any good as the problem isn’t frequency. Bad feedback is still bad feedback, however much you try and disguise it or apply layers of make-up over it. The crux of the problem lies in how we conduct a feedback conversation.
One of the very fascinating results of the studies being carried out into feedback research is that conversations that deal with past activities may result in managers obtaining just the reverse result. The objective of the discussion about a failed outcome seems to be to identify what exactly the problem was, to address why the results of a certain output did not quite match the standards, and to allocate blame.
So, if it is to make us understand the exact reasons behind a specific issue, it is surely easier to avoid its repetition? Well, most of the time it isn’t so.
Research conducted in 2020 found that conversations that focus solely on addressing the output from the previous stage can cause issues between a manager and employee regarding why it is likely not up to the mark. Quite contrary to creating a shared mindset, it becomes an act of making the employees defenseless towards their conduct and a tendency to self-assess the positive sides and look for external explanations for failure, increasing this discrepancy in their minds, which leads them to accept less and be less likely to adopt the feedback given to them.
If we want to have a better grasp of such findings, we need to ask ourselves: how do performance review meetings start most of the time?Do any of these lines sound familiar?
“Let us discuss this past performance and rectify the shortcomings.”
“Why was this project a failure?”
“Explain to me why you were not up to par with your deliverables.”
“What could you have done differently to achieve better results?”
“Can you explain why your performance did not meet expectations?”
“Let’s go over the areas where you fell short and discuss how to improve.”
Even though these are not bad questions, they place the focus of attention on proving oneself, not on learning in context. Once one starts doing that, they can only move their focus from learning towards showing themselves to others; in proving that they are competent or to explain their actions. After all, that’s the way one’s brain is formed.
The interesting thing, though, from this research is that managers do not need to withdraw this kind of feedback completely, but rather should aim to move their focus to discussions of the subject matter & its progress. What mostly determines whether employees accept and intend to change through a feedback process is a forward-focused discussion.
When an employee feels that a feedback discussion about their performance pertains to the future course rather than past failures, they become more receptive (also, this encourages the employee’s intention to implement the changes). So the subtle alteration could have immense significance.
To better illustrate this, ponder upon the following options:
“Your presentation lacked engagement, and the audience became unenthusiastic.“
Vs
“What steps can we take to enhance the presentation to fully capture the attention of the audience right till the end of the presentation?”
Whereas the previous sentence will attempt evaluation, the other one, in contrast, would be development. One is backward-leaning, whereas the other is forward-facing. The one that is toward a bright future focuses the discussion on the future, not only on issues or deficiencies of the past.
The reason many leaders emphasize the need for managers to become coaches is that coaches develop and coach people. Managers, rather than just criticizing a situation, can ask the following questions: “What is the thing that we learned here?“, “What will we try this time round differently?“, “Is there any assistance or resource required to have an impact this time?“, “How can we make our future attempt a successful one?”
Effective Feedback Is About Behaviour, Not Personality
What’s another key element common to all great feedback?
It addresses observable behaviours, not a person’s inner traits.
That may sound obvious enough that you wonder if we need to say it out loud, but the two often get tangled into one in the real world. Here are a few examples:
“You aren’t a great communicator.”
“You’re disorganized.”
“You don’t take ownership.”
The problem is you’ve now just defined who the person is, what their traits are, which are often deeply ingrained or even impossible to alter in real time. Think about trying to tell someone they “aren’t” good at communication; how would you even begin to prove that statement wrong? How can you work on what such a statement wants from you?
Now let’s think about how such assertions could be changed:
“During today’s client meeting, several key questions weren’t addressed before moving to a decision. Next time, I’d like you to pause and invite additional perspectives before wrapping up.”
“The report was submitted two days after the agreed-upon deadline. Let’s take a look at what might have been standing in your way and figure out what we can do differently for the next project.”
Actual change occurs when we use the right words and the right amount of words, to boot. Using both the right words and the proper amount requires going in-depth and pinpointing particulars. When we do that, you’re going to want to pinpoint things that can actually be changed, because behaviour is observable, measurable, replicable, and above all else, changeable.
Personality isn’t what needs improving – performance is. In other words, great feedback doesn’t make judgments about character or intent; instead, it describes what they did, explains why it mattered, and offers suggestions for what to do next & how to achieve it.
No employee should leave a performance discussion feeling unsure if they can even do their job. They should walk away with a clear understanding of exactly what success looks like the next time around. This is the key difference between criticism and coaching, and the key reason why the most effective feedback possesses characteristics that elevate it far beyond simply being “honest.“
Five Characteristics of Effective Feedback
Hopefully by now you’re noticing one thing fairly plainly: feedback isn’t so much about constructive versus damaging feedback. That is nonetheless a relevant difference and an important one to keep in mind, but feedback, what it should be at its core, means facilitating higher conduct from others.
However, if that is the case, we then have to think about another aspect: what makes one bit of feedback more likely to be seen and acted upon as an alternative, rather than met with quiet resentment and forgetfulness?
Though the precise context in every workplace may differ, researchers agree there are five elements more likely to have success.
1. It’s Timely
Feedback is time-sensitive.
The longer a manager waits to engage on a particular topic, the less valuable that conversation becomes. Details and context are lost, and both parties have to recall facts relying on hazy memory. As a coach, would you wait until the end of the season to give one piece of advice on positioning to one player? As a drama teacher, would you wait until a child’s annual recital to mention a few words of advice for playing correctly?
While these examples seem silly, there is a grain of truth there: we don’t learn that way.
Small adjustments in experience improve performance the most effectively when they occur as experience is unfolding. In light of this, some of the best-performing organizations have increasingly embraced the notion of “ongoing” rather than “formal” feedback practices.
They have shifted from the expectation that feedback primarily occurs in quarterly, bi-annual, and annual reviews to encouraging short check-ins on a daily and weekly basis. A five-minute chat between a team leader and report following an interaction with a client, a project kickoff, or the completion of a key milestone often adds far more value than a lengthy review two months later.
To this, we should mention an added benefit of timely feedback: it has an effect beyond improving recall – it impacts momentum too.
2. It’s Specific
One of the quickest ways to make feedback useless is to keep it too vague. Statements such as “You need to work on your communication” or “Be more proactive” may seem like they convey information but are highly unlikely to provide an employee with the specific behaviour they need to adjust.
Specific feedback defines behaviours that are observable and concrete. Instead of saying,”Your communication could use some work,” you can rephrase it in a manner that actually carries realistic improvement capability:
“In today’s client meeting, you did an excellent job answering their specific questions. However, you moved to a decision without asking for other stakeholders’ input, and a few people left the meeting with unanswered questions. In future meetings, be sure to pause after asking a question and wait for other people’s questions before making a final decision.“
Now the employee has a clear understanding of what the problem was, why it was a problem, what success looks like, and how they can achieve it. The guesswork is all but removed.
3. It’s Actionable
Identifying a problem doesn’t mean solving a problem. If it worked like that, snipers would make the best doctors.
Think about a personal trainer telling a new client, “You should get in better shape.” This is little more than a truism. Good trainers tell us what exercises to do, when to practice, how often, and what to track over a period of time. The same applies at work, where great feedback will answer the question ”What next?”
It should be noted that this kind of change might involve experimenting with how you run meetings, plan a presentation, ask questions during client discussions, or break projects down into smaller stages.
4. It’s Psychologically Safe
The trick to good feedback is the existence of psychological safety – a space in which feedback can exist without its recipients feeling mortified, culpable, or punitively chastised; if people are convinced that errors are equivalent to accusation or punishment, they will inevitably be either cautious or deceptive.
The key is a framework that does not reduce standards, nor obviate the necessity of conflict (conflict IS good when one understands how & why). It is a framework that signals the desire to develop through the feedback exchange, and in determining this climate, managers are critical.
By their very nature, curiosity offers a better way to communicate than accusation; questions teach more than assumptions; and listening matters more than lecturing. Furthermore, feedback is more effective when recipients believe the purpose is to develop, not to disgrace, so the intention is to learn when the feedback is intended to help you succeed, not to catch you out making mistakes.
5. It’s Future-Focused
As we’ve iterated a few times in this article, effective feedback enables forward progress. You may remember how past failures often create more than one story about why they happened. These can turn a conversation into an argument that quickly spins into finger-pointing and defensiveness, rather than learning.
A future-focused discussion shifts the entire goal.
Instead of asking: “Why did you do that?”
Ask: “What will you do differently next time?”
Instead of saying: “That strategy failed clearly.”
Ask: “How can we approach the next project to achieve a different result?“
This is a much softer approach that moves the conversation from “who” to “what,” and avoids rewriting the past, shaping the future instead. It sets people up for future success, not failure.
Replace Performance Reviews With Performance Conversations
There’s no greater example of the distinction between providing feedback and fostering improvement than the annual performance review at work.
For decades, companies have used an annual check-in to review performance, highlight gaps, pinpoint areas for improvement, and plan for the coming year. The logic is straightforward: gather observations for an entire year, get together for one meeting to rule them all, deliver feedback, and performance improves.
It feels like magic & sorcery, almost surreal…because it is!
At the time of the meeting, events may already be months old, and employees likely don’t recall the circumstances surrounding it. Managers may bring up very recent issues and ignore the whole year’s data. Both parties struggle to draw insights out of situations that have already passed and cannot be changed. Far too often, however, employees anticipate these conversations and prepare to endure them, rather than get anything valuable out of them.
Now compare that to organizations that weave feedback into their daily work. Here, instead of a single meeting a year, managers coach employees on an ongoing basis:
They praise positive performance as it is happening
Make corrections to minor habits before they become significant issues
Provide employees with opportunities to reflect and learn from their experiences
Embed feedback as an integral part of how the team gets things done, not an event that interrupts it.
Now, this is not to say that organizations should eliminate performance reviews wholesale. They do serve important purposes as documentation of employee achievement, conversation points for career growth, and discussions to align expectations and support administrative decisions.
The review, however, should not be the key mechanism for employee development. Instead, true growth occurs through the many minor interactions between formal performance evaluations. The most effective managers don’t merely review work – they actively contribute to its shape.
Final Thoughts
Feedback Doesn’t Change People ➔ Better Conversations Do
Giving feedback is just the first step in a long series up the stairs of improvement.
The real performance increase comes from the next steps.
Did you tell someone their feedback while the context was still clear?
Did you focus on specific behaviour rather than personality judgment?
Did you give the other person something specific they could do to improve?
Did you create a psychologically safe space for conversation?
Did you help the person understand what success actually looks like for them next time around?
If the answer to any of these questions is no then your feedback will not translate into any lasting growth, rather just another conversation that’s lost from memory by Friday afternoon. The best leadership practices not only evaluate but build capacity in people to step up and try to deliver on something new.
Realistically speaking, most people don’t act because somebody just told them they should. Most people grow because somebody shows them how they could become better, and then supported them with the confidence required to get there.
Perhaps a customer service associate started making mistakes.
Mayhaps a project that seemed like it was a winner suddenly tanked.
Perchance a government department that consistently hit its KPIs suddenly started missing them.
Possibly a construction site that was on track suddenly started falling behind schedule.
Presumably a real estate project that looked like a sure success suddenly stopped attracting buyers.
What’s the first question that pops into most organizations’ minds at that very instant?
“What’s wrong with the employee?!”
It can be a myriad of matters, ranging from motivation, discipline, lack of care, or just a rough attitude. It’s an easy question to ask. When things aren’t going well, after all, our first inclination is to examine the person at the center of the work. It feels equally easy to answer, too. Unfortunately, it’s often the wrong question to ask. In our last piece, we examined the oldest myth in performance management – the one about great performers simply being born with more talent. While talent plays a role, it’s not the full picture. You can develop skills, acquire knowledge, improve abilities, and gain experience nowadays more than ever before in the history of humanity. So, if performance isn’t just about raw talent, though, what is it about? The answer is a bit more intricate and poses several interesting questions, more than many people like to admit, because often, questions don’t give answers, but open up more of the same. Performance isn’t created in a vacuum. It’s not the sum total of how smart, hard-working, or driven someone is. Performance is moreso the result of dozens of forces (seen and unseen) acting upon a person on a daily basis. This has been repeated thousands of times, but it’s valuable to look at it from different angles.
For example, think about growing a plant. If a plant isn’t growing well, we don’t assume it’s a “bad plant,” with a “bad attitude” or a “lack of drive.” We examine everything that has to do with the plant: the soil, sunlight, water intake, temperature exposure, and whether anything is getting in its way. However, when an employee isn’t performing well, we tend to examine the person first. Sometimes that’s appropriate; that much is true. Other times, more often than not, the environment has already created the conditions for poor performance, and this is the myth that we aim to bust in this article: employee performance isn’t primarily determined by attitude. All of the internal elements matter: attitude, effort, accountability, and resilience. Yet, in addition to all these, we also have external elements: bosses, peers, organizational systems, cultures, and outside influences. Understanding the role these external forces play doesn’t mean absolving employees of their responsibility, but rather explaining their performance in relation to all of them. Once we can explain performance by taking into account every layer that can sway it one way or another, we can finally do something about improving it.
Layer 1: The Individual – Capability Is Only the Starting Point
You can’t talk about employee performance without talking about the employee (duh). Each employee comes into a workplace with a unique set of knowledge, technical skills, experience, personality, motivation, and natural talents that undoubtedly play a role in how well they perform. To ignore that fact would be as foolish as saying talent doesn’t matter at all…which is where something breaks in a lot of organizations, and the collective thought bubble pops. If someone isn’t performing, the quick assumption becomes the person lacks something, and they need MORE of something else: more motivation, more discipline, more commitment, more resilience, more passion, more energy, more footwork, like the workout videos of old. Now the environment has become a weird gymnastics exercise of jumping through mental hoops to reason something that might be true, but may not, into a definitive state of truth. One of the most surprising findings from recent research on workplace wellbeing is how much of an employee’s performance is affected by things that their manager may never see. Research from Humankind found nearly 73% of employees felt personal stress was hurting their ability to focus, engage, be motivated, make good decisions, and perform well at their job. Whether it was finances, poor sleep, childcare duties, health concerns, or emotional burdens, these personal factors were quietly depleting the cognitive bandwidth individuals have to deploy at work. None of these struggles will ever show up on a performance review.
A manager doesn’t see the parent who spent the night up with a sick child.
A manager doesn’t see the employee who’s losing sleep over bills.
A manager doesn’t see the hours spent in transit to a job, taking care of aging parents, managing relationship drama, or coping with illness.
What a manager does see is work that’s slowing down, deadlines being missed, less enthusiasm, and lower productivity. By the time that these performance indicators appear, the underlying causes may have been developing for weeks or months.
This is not to say organizations should be tasked with fixing every one of a person’s personal challenges (that’s neither realistic nor appropriate), but it does mean that we must stop deluding ourselves into thinking that individuals somehow become different human beings the moment they enter our buildings. Employees don’t leave their lives at the door; they merely get better or worse at hiding them. Even if there’s nothing overtly going on in a person’s life, we fall into another trap when discussing performance. We often assume that if someone has enough talent, performance will automatically follow, but that’s not how real, everyday life functions. We’ve covered previously how Gallup has long pushed for the argument that while natural talent is a relatively stable proclivity, knowledge and skills can be acquired over time, rendering talent-only advantages null.
Thus, while hiring individuals with a high natural ability does increase your chances of having a top performer, it’s far from a guarantee. Likewise, a person with only average natural abilities may exceed expectations if they’re placed in the right role, have the right skills, and work within the right environment. The same principle is emphasized by management professor Morten Hansen in his research of thousands of professionals. Hansen discovered that how people work accounted for more of the difference in performance than almost anything else. While talent mattered, it was far from the single largest differentiator. High performers didn’t simply outwork the competition; often, they were outworking their competitors more strategically, since capability only sets potential; it doesn’t guarantee performance. Two people with very similar backgrounds and intellectual capabilities can perform in vastly different ways. If we’re only focusing on the person, those discrepancies can seem baffling, yet in truth they are being influenced by forces that we have yet to examine. This is because, after the person, perhaps the single biggest factor affecting performance is their manager.
Layer 2: The Manager – The Greatest Performance Multiplier or Subtracter
If you ask someone why they love working for their company, they’re likely to mention their team or their opportunity to learn & grow. If you ask someone why they left, you’ll notice that a very consistent answer emerges: “my manager.“
Oh, the age-old truism that people don’t leave companies, they leave managers. It’s not universally true, of course, but there’s a reason this saying endures. Managers are our window onto the company. They are responsible for our expectations, the feedback we receive, our access to opportunities, the obstacles we must overcome, and the emotional temperature of the place we work each day.
Two employees can be in the same company, earn the same salary, work with the same policies, have the same benefits, and yet have drastically different experiences because they have different managers.
Psychologist Amy Edmondson has devoted decades of research to identifying a critical ingredient of high-performing teams: psychological safety. In a nutshell, it’s the belief that people can be their genuine selves at work without fear of embarrassment or punishment, can take risks without fear of repercussion, and can challenge one another without damaging personal relationships.
Notice what psychological safety is not: it’s not a lowering of standards. It’s not about avoiding accountability. It’s not about making people comfortable all of the time. Instead, it is about enabling them to contribute without fear of appearing incompetent, even if it feels inherently risky. This is a crucial distinction, because fear changes our behaviour. When we’re afraid of appearing incompetent, we stop asking questions. When we’re afraid of being criticized, we stop pitching new ideas. Eventually, our performance begins to dip because fear has begun to eclipse curiosity.
In fact, a well-known Google study called Project Aristotle, which investigated the reason behind their consistently high-performing teams, came to a strikingly similar conclusion. After scrutinizing hundreds of teams, Google’s researchers found that the most important factor in success, more so than any other, was the degree to which teams were psychologically safe. The other factors (dependability, role clarity, meaning, and impact) were all secondary, built on the foundation of safety.
We invest considerable money and effort trying to find and hire exceptional individuals. Yet, very few of us invest the same resources in creating conditions that allow those individuals to actually achieve their exceptional potential. Moreover, psychological safety is just one factor. There are many others, such as recognition, constructive feedback, trust, autonomy, and role clarity, just to name a few.
Employees who have to second-guess priorities, wait days for simple approvals, or are terrified of making small errors spend the bulk of their mental energy protecting themselves rather than doing meaningful work. Good managers work hard to minimize that friction, while bad managers create it.
In short, the management of performance doesn’t just happen in annual performance reviews. It’s influenced every day by the culmination of dozens of seemingly small interactions between a manager and their reports. Eventually, those interactions ripple out beyond individual relationships and shape the team itself.
Layer 3: The Team – Why Great Individuals Can Still Become Average Teams
Consider five of the most exceptionally gifted individuals and gather them together in one room. Common sense would suggest this would inevitably result in an exceptional team. In reality, things get complicated.
We’ve all experienced teams that, while absolutely flush with talented, experienced professionals, somehow stumble from one deadline to the next. Their meetings become an exercise in repetition and good ideas fester in the far corners of their minds, never shared, never discussed. Elsewhere, teams comprised of average employees somehow manage to turn out exceptional results like high-speed conveyor belts.
When the environment that a tight-knit group builds together starts to shape their work experience, performance starts shifting from individual to collective. By the very nature of work in an organization, no team can avoid this, and every one nurtures its culture, willingly or unconsciously. Over time, everyone learns what gets rewarded, what gets ignored, and what gets punished. Most of these lessons don’t make their way into employee handbooks, but they often exert a far stronger influence on behaviour than any formal policies.
Every team has rules, but what’s more interesting is how many were never written down.
Maybe it quickly becomes apparent that it’s not worth disagreeing with the boss.
Perhaps people learn that asking for help is interpreted as a sign of weakness.
Possibly they notice the loudest voice in the room always wins the discussion, regardless of the actual quality of the ideas presented.
Mayhaps people learn that taking risks is celebrated only when they succeed, but punished harshly when they fail.
Perchance it becomes obvious that keeping your head down and avoiding difficult conversations is the safest way to get ahead.
None of this has to be codified in an internal policy. People simply observe it, adapt to it, and then, over time, pass it along to new team members. This is why culture can spread like wildfire. Almost nobody changes because someone announced new values at an all-hands meeting, but everyone changes when they watch how behaviour is rewarded or punished.
Psychologists call this social proof.
People look to those around them to signal how to behave, particularly in times of uncertainty. In workplace settings, that means employees often adopt the norms of their colleagues long before they consider their company’s stated policies.
If everyone in a team talks freely in meetings, then new team members are usually inclined to speak freely as well. If everyone in a team falls silent when something goes wrong, new team members learn that silence is golden.
Another invisible force comes in what researchers call emotional contagion.
Emotions spread, and that affects team performance. If you’ve ever worked in a team environment, you’ve undoubtedly seen it. A perpetually pessimistic person can single-handedly drain the energy of an entire department. Conversely, an optimistically positive and solution-oriented teammate can boost everyone’s motivation during challenging times.
Managers certainly affect the emotional climate of their teams, but the teammates amplify it day by day. A culture of trust or fear becomes a self-reinforcing loop. This leads into another point taken from Project Aristotle.
Google’s Project Aristotle identified dependability right after psychological safety in their findings.
Trusting your teammates goes beyond their ability to emotionally support you; it involves relying on their execution. Few things sink a team’s performance faster than unpredictability. When employees are unsure about whether their teammates will come through on their assignments, they start to contingency plan or hoard information just in case. Self-protection, rather than collaboration, becomes the default.
The reverse is also true: when employees are confident their teammates will come through, coordination is smoother, and meetings are more efficient as trust replaces excessive oversight.
This is perhaps the least understood ingredient in the recipe for high-performance teams: they don’t eliminate conflict – they eliminate unhealthy conflict.
High-performing teams do disagree. They do question assumptions, debate ideas, ask uncomfortable questions, and clash in their value systems. However, they do so in a way where disagreement isn’t a personal affront. Disagreement becomes a function of the problem-solving process.
That’s what psychologist Amy Edmondson found over and over again in her studies as well: teams that had a high level of psychological safety didn’t necessarily commit fewer errors than others; they actually reported more errors because they were way more willing to admit they had made a mistake. The result wasn’t decreased performance; it was faster learning.
Ironically, cultures that punish mistakes foster conditions where mistakes grow costly and become harder to fix. Hidden problems are invariably more dangerous than problems in plain sight.
As you might have noticed, by this point, a pattern is emerging.
So, what does all of this lead to?
Individuals matter. ✔️ Managers matter. ✔️ Teams matter. ✔️
Yet there is something bigger. They all exist within something larger – the organization.
Layer 4: The Organization – The Structures Behind the Results
Companies love to measure outcomes: sales, revenue, productivity, customer satisfaction, profit margins. What companies don’t really love to measure is the systems that drive those outcomes.
Systems
This is an issue because employees don’t operate in isolated moments; they operate within systems, and those are the quiet forces that make succeeding easy or painfully hard.
Think about how many performance issues are actually system issues hiding in plain sight:
An employee misses deadlines.
Is it poor time management?
Or was that employee’s priorities changed three times in a single week?
A project is dragging.
Is the team unmotivated?
Or does every single decision need to go through a four-department approval process?
Innovation has disappeared.
Are your people less creative?
Or have they learned that challenging the status quo is more risky than rewarding?
It’s all too easy to chalk performance problems up to individual accountability because individual behaviour is visible. Systems are much harder to see, but they often exert much more influence.
Management pioneer W. Edwards Deming famously asserted that 95% of organizational problems are systemic in origin. Accountability matters, yes, but he insisted that people cannot perform better than the systems they are asked to work within.
Just think about your local governmental bureaucracy.
It functions chiefly by rulesets. We need rules. Rules are good – they provide consistency, mitigate risk, offer direct A-to-B avenues for solutions, and enable scalability.
However, we reach a tipping point for every added approval, every unnecessary report, every meeting, every administrative layer, every conflicting process. When rules outweigh the necessity for which they exist, they begin creating friction. They shift focus away from delivering value and toward navigating the organization itself. Eventually, the process itself becomes the focus, not the work.
Role Clarity
Very few things sap performance faster than confusion around what’s expected.
Who’s making this decision?
What does successful work look like here?
Which of the two conflicting priorities should I tackle first?
When expectations are unclear, even talented employees will pause before acting for they fear doing the wrong thing. Studies have shown that clear roles correlate strongly with employee engagement, confidence, and overall performance. Role clarity frees employees to focus energy on solving problems instead of figuring out the answers.
Politics & Culture
Life is a series of politics at play, and organizations are part of daily life.
With that in mind, however, issues arise when politically motivated behaviour are more rewarded than productive behaviour.
If a promotion system reliably favors visibility over contribution
If challenging colleagues’ ideas is riskier than agreeing
If employees are incentivized to compete with one another instead of solving problems collaboratively
If protecting your own department is rewarded more than helping the organization as a whole
The organization trains people that success is a result of politics, not formal policy.
This leads to a distortion of culture.
Culture, much like politics and behaviour, is learned. Despite an army of mission statements, posters, core value initiatives, and well-wishing sticky notes, organizational culture isn’t created by what organizations say they are, but what they do.
Culture is built on what organizations repeatedly tolerate, reward, punish, or ignore. That’s why two companies can claim the exact same values, but have wildly different experiences for their employees. Organizational culture isn’t the motto on the wall; it’s what happens when no one’s watching. These hidden structures influence performance daily, often without managers’ awareness, since they are felt & lived, rather than examined in a performance sheet.
Yet, even organizations with excellent managers, healthy cultures, and efficient systems have one final, insurmountable challenge: people are, at heart, human beings who exist long after clocking out.
Layer 5: The World Outside Work – The Part Performance Reviews Never Measure
There is one last layer to performance, which organizations know conceptually, but often fail to account for realistically: life. It almost seems self-evident, yet, a pervasive, almost subconscious bias exists in the workplace that assumes employees somehow leave their personal lives at the door.
They didn’t – your employees didn’t stop being parents the moment they logged onto Microsoft Teams. They didn’t stop worrying about a sick loved one just because it was Monday morning. Financial worries don’t cease at 9 AM. Anxiety, grief, burnout, sleep deprivation, relationship troubles, and the many other stresses of being human don’t simply fade away as business hours commence.
The point is that people don’t perform in a vacuum; they perform as people. Recent research from places like the Harvard Business Review underscores the impact of external stresses. Studies have demonstrated a direct link between personal stress and difficulties with focus, decision-making, motivation, and engagement.
By the time an employee’s performance visibly dips, mental energy needed for problem-solving, collaboration, and creative thinking may have already been diverted to managing these personal issues for weeks or months. Of course, this doesn’t mean employers need to become therapists or feel personally responsible for their employees’ personal problems. Boundaries are important, and so is recognizing that between 9 and 5, we don’t automatically morph into machines.
Organizations that understand this do a better job of not trying to manage people’s lives, and a much better job of not creating undue stress in the workplace.
Flexible work schedules.
Employee assistance programs.
Access to mental health resources.
Realistic workloads.
Predictable schedules.
Empathetic managers.
These aren’t magic cures or arcane sorceries. They simply remove a potential unnecessary source of pressure at work, and they are incredibly important for one specific reason: performance isn’t a flat line.
No one, not even the highest performer, is running at peak capacity every moment of every day for every year. People have seasons, and there are periods where they have tremendous energy, creativity, and focus. Then there are periods where life’s demands briefly require a greater portion of their attention.
High-performing organizations recognize the difference between a temporary dip in performance and a systemic problem. They don’t treat every deviation as a failure; they ask a much more helpful question: “What has changed?”
Sometimes the change is skills or motivation. Other times, it’s work overload. Lastly, on other occasions, it’s just life, and because each of these changes requires a different solution, differentiating is critical.
Treat every issue as an attitude problem, and you won’t fix very many things. Treat every issue as a systems problem, and you’ll neglect individual responsibility. Effective performance management sits somewhere in between. It acknowledges accountability for an employee’s work, while simultaneously recognizing that no work exists in a void because when you zoom out, you see that every layer impacts the other.
A talented employee will be limited by poor management.
A brilliant manager will be hampered by a dysfunctional system.
A great system will see reduced productivity when the people within it are struggling with overwhelming personal challenges.
No one element creates performance alone, rather it’s the interplay of an entire ecosystem that creates it.
Final Thoughts
Organizations have sought the silver bullet for performance for decades: hire better people, pay more, set big goals, measure everything, and reward the top performers.
All of those things count, but they’re only one part of the picture. Performance isn’t a function of talent alone, nor is it just a product of attitude or effort. Performance emerges from the interaction between an individual and their environment.
The individual
The manager
The team
The organization
The outside world
Every one of these levels either builds on an individual’s potential or subtly works to undermine it. This is why explaining poor performance simply as employee error is so incomplete. If a garden doesn’t grow, we don’t just blame the seeds. We look at the soil, the light, the water, the environment.
Organizations should be willing to ask the same questions not because employees shouldn’t be held accountable (they most certainly should be) but because blame without understanding never results in sustained change. The most effective leaders don’t ask, “Who caused this?” They ask, “What conditions created this result?”
Changing your perspective from who did it to what created it changes everything. It shifts performance management from blame to removal of obstacles and turns the manager from an evaluator to a coach. Moreover, it prompts organizations to build systems for employee success instead of relying on individual grit to overcome the odds, and most important of all, it reminds us that performance isn’t usually an individual effort but a collective one at that.
*********
Performance problems rarely have a single cause. Learn to examine the people, managers, teams, and systems behind the results. Build a more complete approach to performance management with Certified Employee Performance Management.
Emotional intelligence in strategic leadership is becoming an important topic in modern management. In the past, leadership was often measured mainly by financial results and decision-making skills. Today, many organizations also look at how leaders manage themselves, connect with their teams, and handle change.
Strategic leaders work in complex environments where they need to align people, resources, and goals. In these situations, technical knowledge alone is not enough. Emotional intelligence helps leaders understand their own emotions, read the emotions of others, and use this awareness to guide better decisions.
For organizations that want to build stronger leadership cultures, understanding the role of emotional intelligence in strategic leadership is becoming increasingly important. This makes emotional intelligence not just a personal trait but a strategic asset: research from the Center for Creative Leadership has found that leaders who show more empathy toward their teams are consistently rated as stronger performers by their own managers.
What Is Emotional Intelligence?
Emotional intelligence is often defined as the ability to recognize, understand, and manage emotions—both in oneself and in others. The concept has become widely used in the fields of psychology, leadership, and organizational behavior, and is now considered an important skill in modern workplaces.
Emotional intelligence is usually described through four main areas. The first is self-awareness, which means understanding one’s own emotions and how they affect behavior. The second is self-management, which is the ability to control emotional reactions, especially in difficult situations.
The third area is social awareness, which involves understanding the emotions and needs of others. The fourth is relationship management, which is the ability to build trust, communicate clearly, and manage conflicts in a healthy way. Together, these four areas form the foundation of emotionally intelligent behavior in the workplace. This four-part structure, often called the Boyatzis-Goleman model, remains one of the most widely applied frameworks for measuring and developing emotional intelligence in professional settings.
Why It Matters for Strategy
Emotional intelligence plays an important role in strategic leadership because strategy is not only about numbers and analysis. It also involves people, relationships, and the ability to guide teams through change. Leaders who understand this dimension can often manage complex situations more effectively.
One area where emotional intelligence supports strategy is decision-making. Strategic leaders often face difficult choices with limited information and high pressure. When they can manage their own stress and stay focused, they may make more balanced decisions instead of reacting emotionally to short-term problems. This connection is supported by recent research: a 2026 study published in Scientific Reports found that emotional-intelligence training measurably improved stress regulation and decision-making performance among professionals in high-pressure roles.
Another important area is leading change. Most strategic initiatives require changes in processes, roles, or culture, and these changes can create resistance among employees. Leaders with strong emotional intelligence are usually better at understanding this resistance, communicating the reasons for change, and building the trust needed to move forward. This is consistent with change management research: Prosci has identified a lack of awareness about why a change is happening as the leading cause of employee resistance, underscoring why clear, empathetic communication from leaders is critical to overcoming it.
How Leaders Can Develop It
Emotional intelligence is not a fixed trait. It is a skill that leaders can build and improve over time through practice and self-reflection. The first step is developing self-awareness. Leaders can do this by asking for feedback from colleagues, keeping a personal journal, or working with a coach who helps them understand their emotional patterns.
The second step is practicing self-management in daily situations. This can include simple habits like pausing before reacting to stressful news, taking time to think before making important decisions, or using techniques such as deep breathing to stay calm during difficult meetings.
The third step is investing in social skills. Leaders can improve their empathy and communication by listening more actively, asking open questions, and paying attention to non-verbal signals during conversations. Regular one-on-one meetings with team members can also help leaders understand different perspectives and build stronger relationships across the organization.
Conclusion
Emotional intelligence is becoming an important skill for strategic leaders in modern organizations. It supports better decision-making, smoother change management, and stronger relationships across teams. Technical knowledge and financial skills remain important, but they are more effective when combined with the ability to understand and manage emotions.
Organizations that invest in developing emotional intelligence at the leadership level are more likely to build cultures where trust, communication, and collaboration support long-term strategic success.
For professionals who want to build the skills needed to lead effectively in complex environments, exploring a certification such as the Certified Strategy and Business Planning Professional program can provide a strong foundation in strategic thinking, leadership, and organizational alignment. These skills are becoming increasingly important in modern strategic leadership environments.
********** Editor’s Note: The article was written by Ms. Sarah Binsaied.
“The greatest danger in performance measurement is not seeing too little, but believing you’ve finally seen everything.”
Nine KPI Lessons, One Underlying Problem
Throughout this series, we have explored what might seem like nine separate problems with measuring performance. Each article examined a different symptom, manifestation, paradox, or unexpected consequence of using KPIs to understand a complex organization. Viewed on their own, these issues seemed only loosely related. When viewed collectively, however, they tell a surprisingly coherent story.
Our journey began with the KPI Theatre, where we observed how the act of measurement changes behaviour. Once individuals know they are being observed, they instinctively begin to focus on what is visible. This is not necessarily because they are engaged in manipulation or deceit, but simply because human attention is finite and people attend to that which attracts attention. Slowly, performance shifts from being good to looking good.
Then, we examined Goodhart’s Law to see what happens when that observation becomes a target.
What began as a useful indicator of performance becomes, over time, the objective itself. People stop asking whether the organization is serving its purpose and start asking if the numbers look OK. The simple act of optimizing has quietly replaced the process of understanding.
It would seem natural that if one metric blinds you, then two will be better, but that then begets something called KPI Saturation – when everything, every function, every initiative, every strategic priority, and every operational process is represented on a dashboard.
Everything becomes so overwhelming that we are blinded by what is actually present.
Information overload has given way to attention scarcity, and when attention becomes a scarce organizational resource, metrics themselves become valuable. In The Politics of KPIs, we examined how indicators gradually evolve beyond measurement tools into instruments of influence. As dashboards grow more central to an organization’s decision-making, knowledge that is difficult to reduce to a number becomes marginalized and increasingly ignored.
Institutional knowledge, relationships, craftsmanship, intuition, judgment, and the trust required for collaboration – all fall off the strategic radar as information that cannot be easily expressed in numerical terms disappears from the conversation, as was illustrated by KPI Memory Loss.
Organizations do not necessarily fail because they lack information. Rather, they fail because certain forms of knowledge no longer receive attention, or, even worse, are actively dismissed by those who treat them as irrelevant data points. The effects of these trends, however, do not remain confined to the organization itself. The final issues that we uncovered in this series impacted the very people who were employed to deliver on those numbers.
In the KPI Identity Trap, we witnessed how those being measured can become so completely identified with the metrics by which they are assessed that they forget to ask whether they are doing worthwhile work and simply focus on what the dashboard or scorecard shows. It could be seen that the last, and perhaps most fundamental point in this series – KPI Blind Spots – is almost a natural consequence. At best, a dashboard tells us something about the reality of our situation and, at worst, it tells us an unintentional lie.
Yet the lie is never told; it simply emanates from what is left unsaid: the part of reality deliberately omitted to focus on what is believed to be most important.
Realistically, none of these were separate problems at all: behaviour, targets, information overload, politics, organizational memory, personal identity, blind spots. These are not independent phenomena, but simply different facets of the same flawed logic. A logic that proceeds on the basis that reality, as it is currently expressed in KPIs, continues to surprise us only because we have not yet measured enough.
This is what can be called the Completeness Fallacy, perhaps the most insidious belief underpinning modern performance measurement – the belief that performance (and measurement) can eventually be made complete.
Why Every Surprise Seems to Demand Another KPI
These are scenes every seasoned executive has lived out.
An unforeseen event derails a critical business process.
A major customer segment starts leaving faster than anticipated.
A manufacturing defect escapes quality control.
A major project comes in late even though all milestone flags are green.
A cyber attack bypasses the security systems that should have prevented it.
A high-performing, tenured employee quits with little notice.
The post-mortem begins, with executives staring at dashboards and data visualizations, trying to pinpoint where the red flags should have popped up and when someone should have noticed that something was going terribly wrong.
One question invariably surfaces: “Didn’t we have a KPI for this?”
Sometimes the answer is yes, and it was simply ignored. Most of the time, more frequently than many organizations are comfortable admitting, the answer is no. Thus, the logical conclusion seems obvious.
“Let’s add one.”
On its face, this is completely reasonable. Every failure is an opportunity to refine the measurement system. If an important early warning was missing, then the dashboard should be augmented to track it. It often is the right solution, truth be told.
The danger emerges when adding a new KPI becomes the default response to unexpected events, because the next time the unexpected happens (and it always does), another KPI is added. Then another and another.
The dashboards get bigger, the reports get longer, the task manager bloats, and the analytical tools become more sophisticated. Still, unexpected events persist doggedly. Each surprise seems to reinforce the idea that something else must still be missing, driving the organization toward the impossible goal of complete measurement.
This is what can be called the Completeness Fallacy.
The Completeness Fallacy is the mistaken belief that all organizational surprises stem from missing dashboard metrics and that simply adding enough KPIs will eliminate uncertainty entirely.
Complex organizations aren’t like simple machines, made of gears & cogs. They are living, breathing systems made up of people, incentives, cultures, relationships, informal networks, dynamic markets, shifting customer expectations, evolving technologies, and countless interactions that cannot be fully predicted.
Every solution creates its very own new problems. Every intervention changes the system it attempts to measure. Having a complete representation of all possible futures is impossible. Ironically, as organizations pursue completeness, they move further away from true understanding because the question asked subtly changes.
We stop asking:
“What have we misunderstood?”
Instead, we start asking:
“What KPI are we missing?”
These two questions sound similar, but there is a profound difference. The first question is about understanding and assuming that the reality of the situation is more nuanced than the dashboard’s representation. The second question focuses on measurement and suggests that the dashboard just needs an additional piece.
The Endless Expansion of the Dashboard
Think about a dashboard that includes 50 carefully chosen KPIs. A few weeks pass, and then a completely unanticipated problem arises that those 50 KPIs couldn’t have foretold.
“We need to add one more KPI!” – Leadership.
The dashboard grows to 51 KPIs. A few months later, an even greater shock arises. A new KPI is added. The dashboard now has 60. Soon 80. Then 100. Eventually, someone gets tired and asks, “If we have 100+ KPIs on our dashboard, how did this still catch us out?“
It’s a strange psychological paradox at work here.
On the one hand, leaders think “everything that is important must be on the dashboard.”
On the other hand, when something isn’t on the dashboard, it is, at least initially, discounted precisely because it is unmeasured.
Whenever reality disappoints, we try to achieve completeness by expanding the dashboard. As the dashboard grows, our confidence in it grows. That, in turn, makes the next surprise that happens all the more baffling. People begin to wonder in dismay how all of this can be happening, since they are measuring everything.
Except they are not. They never can and will never be able to. No dashboard can perfectly mirror reality; reality is always larger than its reflection.
The danger isn’t what dashboards leave out; the danger is that we forget what they have to leave out.
Babies & Video Games: Why More Doesn’t Always Mean Better
The Puzzling Perplexity of Predicting Progeny
The experience of dealing with babies is a universal (if not always enjoyable) one. Say your baby – a perfectly healthy baby, no less – is inconsolable, though not crying as a result of any obvious issue. They have been fed, cleaned, kept comfortable, and healthy, so why do the tears persist?
You hand the child a colorful toy, and for a brief moment, the wailing subsides before resurfacing with renewed vigor.
“Maybe the problem is simply that we don’t have the right toy!” and so you rush out and acquire one, only to have it achieve the same limited result. You then acquire another that sings, and another that flashes. The child continues to cry, and your resolve is steadfast: there has to be one “right” toy out there to soothe their little agitated spirits!
This process seems almost logical, and the conclusion (that another toy is just around the corner) feels almost automatic. After all, if there were a truly suitable toy, the baby would just stop crying. Right? RIGHT?
This assumption misses a crucial detail: the baby wasn’t looking for another toy at all. Maybe they simply wanted to be held, or was bored lying in one position for too long, or maybe they wanted someone to talk to them, or just to feel the comfort of their parents’ closeness. The parents didn’t need a better toy; they needed to understand the baby.
In the course of our lives, we will all learn an invaluable lesson. Sometimes the quickest, easiest path to resolution doesn’t lie in introducing a new component or finding a missing element, but in paying more attention to the subject of our concern.
Organizations are remarkably similar. Organizations often take a very different, and rather analogous, approach. Every unforeseen problem requires a new key performance indicator (KPI); every anomaly requires a new dashboard; every overlooked blind spot demands a new metric.
It’s quite possible that the problem isn’t that another metric is needed. It might be that the organization needs to better understand what it is trying to achieve in the first place. Instead of reading reports, managers might need to speak with their employees more often. Instead of filling out surveys, customers might want to talk to real humans to air their frustrations.
For example, to understand a problem in production, supervisors should walk the factory floor rather than stare at a production-tracking dashboard. While the dashboard asks, “What else can we measure?” reality is asking, “Have you truly understood me?” That distinction is at the heart of the Completeness Fallacy.
The Curious Compulsion to Continue
It plays out just as clearly in an area where organizational management can’t possibly be expected to surface: video games.
Any person who plays role-playing games or massively multiplayer online games knows that optimization quickly becomes a way of life if left unchecked. Let’s assume you load one up, make a character, and it just isn’t putting out the damage-per-second (DPS) that you were aiming for.
The logical first step, you assume, is to get a DPS meter, take some measurements, and look for the source of the deficit.
The meter tells you that you’re falling short of the damage output of everyone else on your team. You now have an answer to your problem. Or do you?
Upon inspecting your equipment, you notice that some items are suboptimal, so you immediately replace them with better ones.
You head back into the game’s content, only to see a minuscule difference in your damage output. There must be some other missing factor, something else you did not account for yet again.
You realize your equipment isn’t enchanted, and so you spend hours painstakingly applying the most potent enchantments possible.
The result is still marginal. You now invest in better gems, talent points, food buffs, consumable potions, and specialization changes. Eventually, you end up with half your screen clogged by meters tracking DPS, timers, combat logs, raid frames, cooldowns, boss warnings, and who knows what else. Still, your character’s damage output does not noticeably improve.
Add-ons are useful, but the most obvious limiting factors, such as positioning, decision-making ability, encounter awareness, or knowing when not to attack, cannot be directly measured by another number or add-on. These qualities must be learned through trial and error and by recognizing patterns. However, the more information cluttering your screen, the easier it becomes to miss the giant boss looming directly in front of you.
The Misguided Mission to Measure More
Organizations can find themselves facing this type of music in exactly the same way. The dashboards continue to grow, the reports become more elaborate, the metrics increase, and the alerts pile up, giving executives an enormous volume of information to analyze.
In practice, the actual amount of real-world understanding often advances at a far slower pace because it becomes so easy to confuse the process of measurement with actual understanding:
You can measure customer satisfaction and learn that it’s trending downwards. However, you can’t measure the sound of disappointment in a customer’s voice on a support call.
You can check a productivity dashboard, which will tell you that the project velocity has decreased, but it won’t reveal the engineer who’s afraid to challenge a deadline they know is unrealistic.
You can monitor employee morale via an engagement survey, but that can’t capture the quiet moment in the hallway, months ago, when confidence eroded just a little bit more.
You can assess sales conversion rates and identify where prospects drop off, but you can’t measure the trust that was lost in a single rushed conversation.
Wisdom doesn’t grow automatically simply from an increasing quantity of observations. Wisdom is built through an interpretation of those observations within the human context in which they occurred.
This is the true danger of the Completeness Fallacy: it persuades leaders to believe that the missing piece of the puzzle is simply another data point, and that there is never a need to stop looking at data and start listening to their people.
From Hospitals to Software: How Industries Share the Completeness Fallacy
The form in which the Completeness Fallacy shows up may vary significantly between industries, but the core principle doesn’t: whenever the world spits out an answer that surprises us, we start hunting around for some new measure, instead of asking a question: “Are we perhaps measuring the wrong thing to begin with?“
Healthcare: Measuring Patients While Missing Care
Modern hospitals amass vast quantities of data: Patient wait times, Bed capacity, Readmission rates, Length of stay, Medication adherence, ED wait times, Length of procedure, and Infection rates, among many others.
They’re all crucial metrics, but none of them fully explains why some patients with similar clinical profiles take weeks to recover while others take days. Many of the things that drive outcomes – whether the patient actually grasps what the doctor just said, has someone to nudge them about medications, or simply trusts their physician with what’s bugging them – are tough to fit into a standard spreadsheet.
We see a bad readmission outcome and naturally reach for a new quality measure. Sometimes that makes sense, but more often than not, we need to make sure the conversation was handled properly, not simply as a way to create another quality benchmark.
Manufacturing: Perfect Machines, Imperfect Systems
Manufacturing organizations usually have extremely detailed operational dashboards: Machine usage, Cycle time, Defect rates, Overall Equipment Effectiveness (OEE), Scrap rates, Downtime, or Energy usage, to name just a few.
When product quality drops inexplicably, the first reflex is often to monitor it even more closely. Very often, the mentality is “time to add another production KPI and slot in another quality check.”
Yet, investigations often find that technical issues are not at the heart of the matter; rather, the heart itself is gone.
Production targets subtly discourage the workforce from signaling minor deviations until they become significant ones.
None of these had anything to do with a lack of data regarding the machinery – these were all human systems impacting technical ones. What was needed wasn’t more sensors but a better understanding of those humans operating them.
Software Development: Measuring Productivity Without Seeing Complexity
Software teams today arguably measure more things than any team has before: Sprint velocity, Story points completed, Lead time, Cycle time, Deployment frequency, PR approvals, Bug counts, Code coverage, or Incident response time.
When the wheels are slowing unexpectedly, leadership frequently adds a new metric for engineering teams to work with.
“Maybe we need more code!”
“Maybe the reviews are taking too long!”
“Maybe the deployments aren’t happening often enough!”
Maybe the real problem might be that a legacy architecture is now extremely difficult to maintain. The team has quietly accumulated technical debt over the years and is now spending much more time understanding systems than developing features, and on top of that, cross-functional communication has broken down.
The biggest thing stopping the team from shipping may not be an absent KPI, but decades of accrued complexity that only a truly seasoned engineer can even see. Such nuance cannot be encapsulated in a dashboard.
Aviation and High-Reliability Organizations: When Safety Lives Between the Metrics
Few industries are more serious about measurement than aviation. Aircraft systems generate vast amounts of operating data, which are measured and remeasured with exceptional rigor.
Flight schedules are closely monitored.
Safety incidents are rigorously documented.
Procedures are formalized.
Performance is routinely assessed.
Nevertheless, aviation professionals know a secret that few leaders recognize: if no safety event has occurred, it doesn’t mean that safety is present.
The organization could show perfectly good safety performance on its metrics, while easily and effectively hiding its own psychological limitations regarding the issue from itself. Pilots may be unwilling to speak about hazards. Maintenance crews might be reluctant to acknowledge near-miss events because they might feel embarrassed or appear incompetent. A Junior team member might have no idea how the process could be made safe and would have no incentive to raise such concerns.
The overall safety indicators might be beautifully and blissfully green right up to the day of a disaster. When such a disaster occurs, the investigators rarely attribute the failure to a single additional KPI or a particular missing index or tool. Instead, they generally attribute the disaster to communication failures or human errors that may have predated the measurement systems.
The organization didn’t lack yet another metric – it lacked a deeper understanding of the system it thought it had measured.
In all 4 of the industries we’ve showcased, the situation repeated itself:
Disasters occurred
Organizations assumed they must be missing a metric
The metrics were expanded
They were surprised again and again
Such scenarios don’t happen because leaders lack the intelligence to be able to design and implement appropriate measurements, but because no complex system, as a matter of principle, can ever be as large as its own representations of itself. No dashboard can become the entity being measured.
When organizations reach that stage, they focus so intently on measurement devices that they neglect the journey and miss where they are going.
Final Thoughts
Looking Through the Windshield Instead of at the Dashboard
Never before has there been so much readily accessible operational information available. Never before has there been a way to see performance across continents in real-time, spot emerging trends within minutes, or turn vast amounts of raw data into simple, intuitive pictures. Organizations have become faster, more coordinated, better informed, and ultimately, more agile.
Problems arise only when dashboards stop being tools for understanding and start becoming substitutes for it. This is, ultimately, what’s dubbed the Completeness Fallacy.
It has nothing to do with whether KPIs are useful or useless, or whether measurement systems need upkeep or not. Rather, it is the false belief that uncertainty can eventually be engineered out of the organization by judiciously selecting enough indicators.
In modern-day organizations, every KPI answers one question but begs another. Every bit of extra visibility alters behaviour, thereby changing what the measurement actually means. Performance measurement isn’t a race towards a state of completeness. It’s a never-ending conversation between what can be measured and what requires only observation, judgment, curiosity, and experience.
Dashboards are the thing that should inform a conversation, never replace it. Think of them as a car windshield. It has never been designed to capture every detail of the road ahead. It won’t reveal what is hiding behind every building, nor will it show every hidden pitfall lurking around the bend. Its purpose is to provide just enough visibility to help us navigate while, at the same time, reminding us that the road itself deserves our attention.
Modern performance dashboards have precisely the same role. They are not the organization, but the windows through which we may view organizations in a richer, more dynamic manner than any collection of KPIs can adequately convey.
If we start to look at the windshield instead of through it, we are liable to lose sight of where we are going, and that may well be the most profound irony of modern performance management:
We have never measured more, and with better tools. At the same time, we have never depended more on the interpretation, conversation, experience, and context provided by the people powering the soul of our workplaces.
*********
Looking to strengthen your expertise in KPI design and performance measurement? Gain practical knowledge, proven methodologies, and globally recognized certification through The KPI Institute’s Online Certified KPI Professional.
A flashlight has a most mundane but curious property: the moment you flip the switch, the room becomes both brighter and darker. Wherever the light beam hits, details are rendered in sharp focus, and objects you hadn’t realized were there become clearly visible. At the same time, the opposite occurs everywhere: the rest of the room not illuminated by the flashlight beam falls into deeper shadow. The darkness is not a flaw of the flashlight; it is a necessary trade-off for the light it produces. The same is true of performance measurement. Each KPI illuminates one dimension of a company’s operations, whether that be revenue growth, customer satisfaction, employee productivity, inventory costs, or operational efficiency. KPIs make it easier for executives to understand, analyze, and (one hopes) improve organizations, converting complexity into data points that facilitate decisions, rather than gut feeling or anecdote alone. For decades, the standard solution has been the same: if one KPI helps uncover something important, perhaps 10 KPIs can provide a better understanding, and 100 can illuminate everything clearly. That’s the rationale behind the modern dashboard: displays of gauges and graphs, crammed with performance indicators, accompanied by meetings to debate the resulting data, all aimed at dispelling ambiguity.
For all intents and purposes, this is a completely reasonable yet equally impossible aspiration. That may sound startling given how much more access we have to data than ever before. We store it on massive servers at minimal cost. We use sophisticated analytics and AI to glean insights from terabytes of information. It seems that if we just gather enough data and track enough metrics, we should eventually be able to eliminate the shadows completely, but we never do. This isn’t because organizations aren’t diligent, or their dashboards are poorly designed, or due to management failing to pick the right KPIs. It is because measurement always has its limitations. The first step in any measurement is deciding what we want to measure, a step often so mundane that it slips below notice.
Someone first decided that customer retention was a worthwhile thing to track.
Someone first determined that employee productivity could be represented and measured in an operational way.
Someone decided to define and track inventory turnover.
While individually unremarkable, these choices coalesce to determine how an organization understands itself, and this is where a conversation about management science turns toward a more ancient philosophical inquiry: is it possible to represent all aspects of reality? As the history of thought suggests, the answer is no. All representations of something omit something from it. Every descriptive attempt leaves something else out. A given perspective must, by its very essence, exclude other perspectives. The limitation of KPIs is not that they don’t capture enough, but that they cannot capture everything simultaneously…and maybe they shouldn’t. Imagine that a cartographer were asked to draw a complete map of a country, including every road, every river, every building, every tree, every shifting cloud, and every stone on its surface. If the map were rendered with perfect accuracy down to the atomic level, it would no longer function as a map – it would be indistinguishable from the country itself. In that case, its utility would depend entirely on what it had omitted.
The Argentine author Jorge Luis Borges nailed this with his short tale “On Exactitude in Science.” The empire there had grown so hung up on perfection that the imperial cartographers had produced a map so detailed and at precisely the same scale that it mirrored the entire empire. This was an incredible (and utterly useless) feat of accuracy.
A map as large as reality provides nothing useful because it has forfeited the very abstraction that made maps useful.
Organizations seem to be striving toward the same ambition when they set out to create dashboards. Each new initiative seems to yield yet another metric. Each new blind spot feels solvable if we can just add one more indicator. Along the way, however, we realize that the dashboard has ceased to represent reality by abstracting from it and has begun to become reality itself by trying to represent every aspect of it.
Rather than helping us understand the world by reducing its complexity to a set of meaningful patterns, the dashboard simply introduces its own brand of complexity. It becomes another source competing for our attention, rather than helping to direct it. The ultimate irony, of course, is that by attempting to eliminate uncertainty, we’ve somehow succeeded in regenerating it.
Therein lies the discomfort. Performance measurement has never been about completeness. It has always been about selection. The pertinent question isn’t whether or not our dashboards contain blind spots. They always will – that is a foregone conclusion. The truly germane question is this:
On which blind spots have we collectively and knowingly chosen to focus, and what price does this quietly cost us?
Every Map Leaves Something Out
Abstraction is the very reason measurement exists.
1933: a philosopher and scientist named Alfred Korzybski made a statement that has endured as one of the most profound observations about the nature of human knowledge: “The map is not the territory.” Maps work precisely because they are incomplete.
A road map omits soil conditions.
A geological map omits speed limits.
A weather map omits property boundaries.
A subway map omits actual geographic distances.
A political map omits mountains and rivers.
None of these maps is wrong per se; they simply emphasize certain features by ignoring others. In other words, every map imposes an opportunity cost.
By helping you see one thing more clearly, it forces you, however temporarily, to stop looking at countless others. The same subtle truth underpins every single KPI we have ever created.
Imagine a manufacturing plant decides to elevate production speed to the top of its list of indicators. Almost immediately, the company begins to view itself through that lens. Conversations about throughput take center stage, and managers trumpet short cycle times. None of that is necessarily bad in itself, but the problem lies elsewhere. As the spotlight shines brighter on the speed-of-production-indicator, other valuable activities start to fall into the shadows. Craftsmanship becomes hard to recognize because it never moves at maximum velocity.
Careful experimentation with new processes is slowed by the urgency to produce.
Mentoring inexperienced workers becomes harder to justify because it doesn’t contribute directly to immediate output.
Knowledge sharing is quietly abandoned because documenting lessons learned doesn’t increase this month’s production figures.
Preventive maintenance suddenly feels like a costly delay rather than a wise investment.
None of those things become any less valuable; they just become less visible, and that is a critical distinction.
Organizations don’t typically abandon what matters because they consciously decide they don’t care about it. More often, they abandon it because attention shifts. Like a river changing its course, attention reinforces whichever pathway it flows through, gradually starving its adjacent tributaries of life. Every KPI generates the current:
Measure costs mercilessly, and resilience is slowly yielding ground to pure efficiency.
Measure speed aggressively, and craftsmanship begins to politely negotiate for a little bit of air to breathe.
Measure customer acquisition relentlessly, and customer loyalty quietly slips into the background.
Measure individual performance exclusively, and collaboration starts competing for recognition.
Measure short-term results obsessively, and long-term capability becomes an investment nobody feels they can afford.
Measure productivity and some amount of creativity has become the opportunity cost.
These aren’t implementation problems but a natural consequence of choosing one map over another. No organization, however sophisticated, escapes this inherent trade-off. The only question is whether it acknowledges it.
To believe otherwise is to believe that light can exist without shadow, or a river can flow down all of its tributaries simultaneously. Neither is possible regardless of how much wishful thinking we may engage in.
Self-reflection: What parts of your organization exist only because they were left off the map? What have your dashboards quietly trained you to stop seeing?
The Things We Know but Cannot Measure
A lot of an organization’s most significant strengths never make their way into a spreadsheet or a performance dashboard. That doesn’t mean they’re worthless. It simply means they’re unquantifiable.
There was once an old tale about a master luthier. Years ago, his apprentice learned how to master every single measurable aspect of the luthier’s art. They learned the ideal wood thickness, neck angle, and sound box dimensions. They learned precise moisture levels for every species of wood. They learned about ratios honed by centuries of master violin makers.
One afternoon, after completing their masterpiece, a violin so technically perfect that it was a work of art, the apprentice presented it to the master. The old craftsman peered at the instrument, ran his hand over its smooth, polished surface, and asked the apprentice one simple question: “Did you listen to the wood?” The apprentice stared at him, confused. He’d measured everything to a T, but he’d never thought to listen. “What does it even mean to listen to wood?”
The story may be apocryphal, but the phenomenon it describes is undeniably real. There’s a form of knowledge that cannot be expressed in mathematical equations or codified in best practices manuals. However, we can recognize it immediately when we see it, though we have difficulty pinpointing its nature.
The experienced doctor whose intuition alerts them to a problem that’s not yet showing up on the medical monitors.
The teacher who somehow senses that a perfectly attentive student with straight A’s is secretly struggling.
The firefighter who somehow knows when a building’s imminent collapse.
The negotiator who intuitively understands when utter silence will be more effective than a persuasive argument.
Ask any of these individuals how they knew, and you’re likely to get equally unsatisfying answers: “It just didn’t feel right.” / “Something was off.” / “You get a feel for it.“
From the perspective of someone seeking concrete data, these explanations can feel maddeningly elusive. Nevertheless, organizations implicitly rely on such judgment calls all day long.
For example, most of Michael Polanyi’s thought process was organized around that observation. He had the famous concept, “We know more than we can tell,” as a challenge to the notion that any valid knowledge eventually would be captured, measured, standardized, and written down. Some knowledge can easily live in a spreadsheet, yet other knowledge lives in people. They accumulate it from experience and mistakes, from gut feeling and intuition, and the kind of pattern recognition and observation which is rarely explicit enough to measure, which Polanyi referred to as tacit knowledge.
Maybe one of the best illustrations comes from something as simple as bicycle riding.
All but the most clumsy can ride a bike, hardly thinking, balancing, managing pressure and momentum, timing the minute variations in the bars, and coordinating muscles all at once. Now try asking someone to describe every single detail needed to balance, and you get a clear sense of just how much their knowledge lies beyond their words.
Knowing how differs from knowing about.Organizations have vast storehouses of this tacit knowledge:
The repair specialist who can listen to a car engine and sense what needs repair down the line.
The customer service rep who detects someone’s incipient dissatisfaction long before the complaint is lodged.
The project leader who picks up on tensions in a team meeting long before the employees are even conscious of it, or the survey forms do.
The production supervisor who notices a subtle change in a machine’s rhythm before any sensor or maintenance report flags an issue.
The sales manager who recognizes that a long-standing client is preparing to leave, not because of declining revenue, but because of a slight shift in tone during routine conversations.
All those things, those pieces of organizational know-how, don’t fit into a nicely curated dashboard, but that doesn’t make them less true. Unfortunately, just because they don’t fit, that can be an excuse to ignore them, since what can be measured tends to take precedence over what cannot.
It is here that another philosopher enters the picture, not to tell anyone how to run a meeting, but because he wrote so clearly about human thought: Nobel laureate and psychologist Daniel Kahneman, who coined the acronym:
WYSIATI –“What You See Is All There Is.”
His point was simple: human beings naturally construct stories based on the information available to them in the moment. We seldom consider what’s missing. This makes our lives easier in countless day-to-day decisions. Within organizations, it quietly sculpts our culture.
Imagine two leadership meetings.
The first features executives spending an hour analyzing revenue trends, customer acquisition costs, production efficiency, and employee utilization.
All the charts are ready. All the numbers are current.
The second meeting begins with a question that causes a flicker of discomfort: “How much institutional knowledge have we lost this year?”
Now, everyone is hushed, almost deathly silent. This is not because the question is irrelevant, but because no one has a chart tracking decades of experience retiring with long-time employees. No dashboard shows the slow erosion of mentorship. No KPI reports on the silent confidence a junior engineer accumulates watching a senior colleague solve tough problems over half a decade. Thus, the conversation inevitably circles back to the numbers, not necessarily because they are more important, but because they are present.
This is the subtle peril Kahneman described. Visibility masquerades as importance so powerfully that the longer a metric appears on a dashboard, the more likely we are to assume it deserves our attention. Soon enough, the organization behaves as though the measurable world is indistinguishable from the genuinely important world. Hardly. We don’t see trust appear on a dashboard. Nor does curiosity, judgment, wisdom, humility, psychological safety, institutional memory, craftsmanship, talent, or brilliance.
These qualities do not diminish in value because they defy quantification; they simply attract less attention, and attention (arguably more than money or time) is an organization’s most scarce resource. Consider the origin of a great river. Initially, it has countless tributaries – some narrow and tortuous, others wide and majestic. It cannot flow down all of them simultaneously, and once it commits to one path, the others quickly recede. Attention works the same way.
Every meeting agenda, every dashboard, every quarterly objective, every KPI selects one path for the organization’s energy and focus, while the rest begin to fade into the background. This is the opportunity cost of our dashboards, which we seldom discuss. When leaders choose to measure productivity, they aren’t simply choosing to observe productivity; they’re choosing to commit meetings, incentives, conversations, budgets, promotions, and intellectual energy to it.
Something else will inevitably receive less attention: maybe it’s creativity, mentoring, experimentation, or reflection. What is certain is they won’t vanish overnight, but, like an abandoned riverbed, they’ll receive a little less water each season until we eventually wonder what happened to the current. Organizations often assume culture changes because people change. In fact, culture sometimes changes simply because attention changes. The dashboard didn’t tell employees to stop mentoring one another; it simply stopped reminding them to do so. This is the quiet paradox of measurement: not that it tells us what to value, but that it gently nudges us to value what it tells us.
It is perhaps why the most enduring qualities within an organization often remain nearly invisible: the quiet conversations after meetings end, the intuitive grasp that builds over decades, the acts of kindness that, while never appearing on a quarterly report, fundamentally shape the workplace over many years.
No dashboard will ever fully capture them, and maybe it is for the better that none should ever try. After all, the purpose of a map is not to be the territory itself, but to guide our journey through it, without allowing us to forget that the territory is always infinitely richer than the paper upon which it has been sketched. Self-reflection: If your dashboard vanished tomorrow, what knowledge within your organization would still be accessible? What invaluable capabilities might have quietly receded, not for want of value, but for want of attention?
When Measuring Changes Reality
As soon as a metric becomes important, people will start to restructure their lives and their behaviour around it, and, in doing so, the organization has quietly transformed into something new.
Imagine you take a walk through a forest and carry a compass. When you are in wild country, confused as to which way to proceed, it gives you absolute assurance.
It consistently points north regardless of which direction any of the trees are oriented, and no matter how uniform all the trees look. Despite all of this, the compass does not tell you about cliffs. It says absolutely nothing to you about riverbanks or unstable ground, about poison berries or an oncoming storm. It performs perfectly for the set purpose, and it says nothing to you at all about most of the rest of the landscape.
We know that this instrument exists for the sake of asking one particular question, and not for the asking of all these questions. The problem arises when we start treating an instrument as the territory itself. It is on this basis, among others, that KPIs may have gotten themselves into trouble.
When they are first instituted, they do not, at the start, look so obviously bad as things become. What they are expected to do is help people find the way: help us see where things stand, where we are with regard to the world around us. Over time, however, they morph into something rather different.
Instead of helping people make sense of the world, they actually start to shape and create it.
What people ask no longer comes out as: “How can I do something that will help me add value over the longer term?” Instead, people begin to ask: “How can I do something to make the number for this month better?” That is not a good change at all, and neither is its effect.
This is a thought that spills over beyond the confines of business and out to the philosophers again.
German philosopher Martin Heidegger argues that technology does more than simply provide us with tools to perform useful tasks. Technology can also fundamentally change how we see the world. Heidegger’s notion of “enframing” or “Gestell” means, more simply, our tendency to see the world only in relation to how we have divided and framed it for organizing purposes.
The forest can be many things depending on how you see it:
A painter’s inspiration
An adventure park for a child
A natural ecosystem of incredible complexity to a biologist
A resource for a timber company, ripe for extraction
At its core, the forest remains unchanged. The lens through which we view it shifts.
The same phenomenon often occurs in performance management across an organization:
One manager might view an employee just as an 87% score on one dashboard.
A second manager, however, may believe this employee is the lynchpin holding a team together and should be regarded as an experienced mentor.
A third might see them as an untapped potential who will eventually revolutionize company culture.
A fourth could turn to them when a critical problem has no documented solution.
The person hasn’t altered, only their apparent visibility, and this is why the dashboards you install to “measure performance” may end up having a much more profound impact: they do not just capture a representation of an organization – they actively teach that organization what it should consider meaningful.
Take, for example, a call center team for which “Average Handle Time” is the primary KPI. At the outset, this is an appropriate metric. Nobody wants their time on hold, nor for calls to drag on indefinitely, so reduced handling times should, in principle, improve the customer experience. After a period of months and a growing emphasis on meeting the metric, you might see some subtle shifts:
Customers might find their calls cut short, and complex queries are often quickly passed on to someone else.
Calls requiring additional customer support may be concluded sooner than necessary to avoid negatively affecting the metric.
Eventually, employees might be actively encouraged to make calls as brief as possible, even when there is a clear need to spend more time with an individual. No one asked or directed the staff to stop being caring, but they learned that caring did not reflect well in the KPI. This effect isn’t isolated to call centers.
We’ve seen it time and again in organizations:
Hospitals boost patient throughput, but the time available for each patient to connect with their nurse decreases.
Universities champion graduation rates, but in practice, they have reduced the number of required in-person teaching hours to free up resources to process more students.
Software companies are on track to close out their backlog, but accumulate huge amounts of technical debt in the process, which will be handed on to someone else down the line.
Retail chains are promising ever-faster delivery times but work their warehouse employees to the point of burnout during peak periods.
Banks reduce average loan processing times, but the depth of conversations needed to truly understand a customer’s financial situation becomes increasingly rare.
Construction companies meet aggressive project deadlines, but quality inspections become compressed, allowing small defects to accumulate into larger problems later.
The KPI is a success. Reality simply adjusted to accommodate it and, in doing so, became the embodiment of Goodhart’s Law. However, this doesn’t mean people are gaming a metric. We are observing the metric changing the environment, which it was always meant to reflect.
Imagine you put a large rock in a river. ↩️
The river doesn’t stop; instead, it has to reconfigure itself around the obstruction. The water flow is altered, new streams emerge, and debris begins to accumulate in various places. The river becomes something new as a result of a piece of infrastructure that wasn’t built to redefine its flow, but that had that very effect nonetheless.
↪️ KPIs are much the same.
If you introduce a KPI within an organization, it naturally triggers a cascade of reconfigurations. Budgets change, conversation topics shift, job titles are reassessed, and career progression criteria implicitly shift as people respond to whatever behaviour is sanctioned or rewarded. None of this happens as the result of deliberate manipulation; it simply emerges from the fact that people, just like rivers, respond to their environment and incentives in quite natural ways.
Nassim Nicholas Taleb can help us understand why. His career has been dedicated to distinguishing between systems that appear efficient and those that are actually resilient.
Picture a bridge for which a designer aiming to optimize for efficiency might shed every pound of weight considered extraneous. The structure is lighter, streamlined, less costly to build, and mathematically perfect. In theory, it is nothing short of an engineering masterpiece…until an earthquake shakes its foundation or heavy traffic grinds it mercilessly. Suddenly, what was so-called “excess” turns out to be strength. It was resilience, which to an inexperienced eye looked like inefficiency.
Organizations do the same thing every single day.
A business that meticulously limits its inventory appears brilliantly efficient-until supply chain networks fail.
A company paring down its staff to achieve peak productivity appears financially responsible until demand surges, and there’s no one around to respond.
A factory delaying routine maintenance to keep machinery humming may look great on utilization metrics-until an easily avoidable mechanical failure brings everything to a standstill.
An organization minimizing cybersecurity spending appears fiscally disciplined until a single breach costs more than years of preventive investment.
Every optimization quietly borrows against resilience, and every optimization comes with a price tag paid in foregone opportunities. The problem is that resilience is silent until it is needed. It’s like the unseen roots of a wise old tree, readily ignored as long as the wind doesn’t howl, yet absolutely essential once it does.
Perhaps this is why we so often hail visible efficiency while neglecting invisible capability.
Resilience is expensive, slack is wasteful, redundancy feels inefficient, curiosity feels unproductive, reflection is just a delay, until uncertainty strikes and the very things we criticized for slowing down progress become the reason progress remains possible.
This isn’t a case against optimization; it is rather an argument against ignoring its cost. Every optimization narrows the river, forsaking countless tributaries. Every intensification of a beam of light plunges another part of the field into shadow. The practice of leadership is therefore not merely about pursuing improved performance against metrics. It is about the disciplined recall of all that this pursuit inadvertently leaves in the shadows.
Self-reflection: If the uncertainty we know is lurking should arrive tomorrow, what might your dashboard wish it had kept safe? What unseen resilience has it already surrendered in favour of something far more tangible?
The Blind Spots We Choose
Leadership is not about the search for perfection or visibility. It is the wisdom to choose which shadows you can live with.
If there is one temptation that has been with us in every civilization, in every scientific breakthrough, it is the notion that the next tool will at last allow us to see it all: a better telescope, a more detailed microscope, a faster computer, a larger database, a smarter algorithm, a more inclusive dashboard. With each passing generation comes this same silent belief: this time, maybe this time, the blind spots will be gone. Inevitably, history shows a different pattern. Every innovation expands our view only to make evident what we had not yet seen.
The telescope opened the sky only to reveal a far larger universe than we had ever imagined.
The microscope unveiled worlds unseen, only to reveal how much more complex life was than we had ever known.
The process of discovery is the same again and again. The more we illuminate, the more we realize what remains to be illuminated, and businesses are no different when it comes to this topic.
Every metric answers a question but raises ten more. Every dashboard reduces uncertainty in one area while allowing for endless uncertainty to persist elsewhere. The goal, then, was never to create a dashboard that had no blind spots (Borges’ perfect map). The goal, instead, was something far humbler & more valuable: to understand what blind spots we have accepted.
Herbert Simon offers another key insight here. He famously noted: “A wealth of information creates a poverty of attention.”
Businesses today, almost without exception, do not lack information. Quite the contrary, they have way too much of it. Every department, every software system, every meeting, every team, every person – everyonepours information ceaselessly, splitting attention like atoms.
Yet, attention is a very limited resource; like sunlight, it brightens the spots where it lands but does little elsewhere.
Every meeting on one topic takes time that might otherwise have been devoted to another.
Every incentive reinforces one behaviour and subtly undermines another.
Every promotion tells employees (intentionally or unintentionally) what is valued.
Every promotion carries an opportunity cost, just as surely as a cash purchase.
It may also explain how an organization seems to lose characteristics it never deliberately gave up:
Curiosity gives way to Conviction ➔ Thought becomes Action ➔ Action becomes the new Thought ➔ Reflection cedes to Urgency ➔ Long-term Thinking collapses under the weight of Quarterly Performance Reviews.
No one sets out to make a career of being certain or impatient. The river simply shifts its course: a bit more attention to one side, a bit less to the other, and so it continues, day by day, until the landscape has changed beyond recognition. That may be the paradox of measurement.
When we measure, people move in the direction we point the lens. They engage with what is presented in meetings and what leaders routinely ask about. Everything else slowly slips out of view, not for lack of value, but because it has fallen out of organizational focus.
Thus, we arrive at the point that measurement always requires humility. Humility reminds us that no dashboard, however powerful, is the absolute truth of the world. Every measure is a perspective, and every perspective is incomplete. The question is not to eliminate our blind spots, but to come back to them again and again and ask:
What have we stopped noticing?
What assumptions have become so deeply embedded that they no longer warrant questioning?
What capabilities have we quietly allowed to atrophy because they didn’t make their way into a report?
These questions are important because organizations are dynamic systems in constant flux.
There’s a famous observation attributed to the ancient philosopher Heraclitus: “No one steps into the same river twice.”
The person has not changed, but the river has moved on. An organization is similar in this regard: it itself might not have changed, but the markets it operates in, the customers it serves, the technology it uses, and the culture it promotes have changed.
Even if a KPI reads the same numerically, the underlying reality it represents may have morphed beneath the surface. An 85% customer satisfaction rating now may not reflect the same customer expectations as five years ago. A current employee engagement survey, using the same wording as previous surveys, may be interpreting an evolving sense of what meaningful work means today.
The numbers endure, but their meaning shifts, which is why our dashboards can never be sacred. The minute we cease to scrutinize our metrics, we cease to scrutinize the reality they represent. It may be that the best leaders aren’t the ones with the most sophisticated dashboards or who track the most metrics. Maybe the best leaders are those who:
Never mistake the map for the territory
Remember that each illuminated beam also casts a shadow
Know that every river in the organization might have flowed somewhere else
Have the insight to put down the dashboard now and again, and wonder what it cannot show us
Final Thoughts
Learning to Respect the Shadows
Every photographer chooses a frame. Every sculptor removes stone to reveal a statue. Every author leaves unwritten pages behind. Every traveler follows one road while countless others disappear beyond the horizon. Every act of creation is also an act of exclusion. Every KPI is a decision about what deserves to be seen. Every dashboard is a statement about what an organization believes is worth discussing. Every target shapes behaviour long before it records it. Every number carries an opportunity cost that cannot be eliminated, only accepted. The problem has never been the existence of these tools, but more so forgetting that they are tools in the first place. A map is invaluable precisely because it is not the territory. A flashlight is useful precisely because we understand it cannot illuminate the entire room. Likewise, a KPI is powerful precisely because it simplifies reality enough for us to act, yet that simplification comes at a great cost:
It purchases clarity with incompleteness
It exchanges breadth for focus
It gains certainty by accepting blindness elsewhere
This is the opportunity cost of knowledge itself.
Therefore, we can infer that the purpose of performance management is neither to eliminate uncertainty nor to measure everything that matters, but to consciously and deliberately choose where we wish to shine the light, and to remember that, somewhere just beyond its edge, the rest of reality patiently waits in the shadows.
*********
Looking to strengthen your expertise in KPI design and performance measurement? Gain practical knowledge, proven methodologies, and globally recognized certification through The KPI Institute’s Online Certified KPI Professional.
