Home / Measurement, signals, and sense / Feedback Starvation

Measurement, signals, and sense

Feedback Starvation

When a system lacks the information it needs to self-correct - common in hierarchies where bad news doesn't travel upward

Also known as: Information drought, Feedback desert, Signal deprivation

THE IDEA

Flying blind

Every system needs feedback to function. Feedback is the information that tells a system how it’s doing - what’s working, what isn’t, what’s changing, what’s breaking. Without it, the system can’t self-correct. It keeps doing what it’s doing, regardless of the consequences, because it has no way of knowing the consequences exist.

Feedback starvation is what happens when this information flow is blocked, filtered, delayed, or absent. The system operates without knowing its own state. Decisions are made without knowing their effects. Problems grow without anyone noticing. By the time the feedback finally arrives - if it ever does - the damage is far greater than it would have been if the system had been able to sense and respond in real time.

The most common cause is hierarchy. In organisations with strong hierarchies, information flows upward slowly and selectively. Good news travels fast. Bad news gets filtered, softened, reframed, or stopped entirely. By the time the CEO hears about the problem, it’s been through so many layers of translation that it barely resembles the original signal. The people at the top, who have the most power to act, have the least accurate picture of reality. The people at the bottom, who see reality most clearly, have the least power to act. This is feedback starvation, and it’s the default state of most hierarchical organisations.

IN PRACTICE

The silence that precedes the crash

A company’s product has a growing quality problem. Customers are frustrated. Frontline support staff know exactly what’s wrong. But the reporting structure filters their observations into metrics that don’t capture the nuance. The weekly report shows “customer satisfaction: 78%” which looks adequate. The senior team sees numbers, not the pattern underneath. When the problem finally becomes undeniable - a viral social media complaint, a major client departure - the response is shock. “Why didn’t anyone tell us?” Someone did. The feedback was starved by the system designed to deliver it.

A government agency implements a policy that’s creating problems on the ground. Local workers see the problems daily. But the reporting system asks for compliance metrics, not impact observations. The numbers show the policy is being implemented. The reality is that the implementation is causing harm. The feedback that would trigger a correction never reaches the people who could make it, because the information channels carry compliance data upward and ignore everything else.

A parent asks their teenager “how was school?” every day and gets “fine” every day. The parent believes everything is fine. The teenager has learned that honest answers produce worry, questions, and interventions they don’t want. The feedback loop - which should carry information about the child’s experience to the parent - has been starved by the child’s rational decision to stop providing it. The parent is flying blind, not because they don’t care, but because the system of communication has evolved to filter out the signal.

WORKING WITH THIS

Restoring the signal

The first step is asking: what don’t I know? Not in the abstract, but specifically. Where am I making decisions without current information about their effects? Where is there a gap between what I assume and what might actually be happening?

Design multiple feedback channels so that no single channel can be the bottleneck. If information only flows through one report, one meeting, or one person, the feedback is only as honest as that channel allows. Create redundancy in feedback - anonymous surveys, skip-level conversations, direct observation, customer listening sessions. Each channel carries a different signal. Together, they resist starvation.

Make it safe to deliver bad news. Feedback starvation is almost always a safety problem. If people fear punishment, embarrassment, or consequences for sharing bad news, they’ll filter it. The leader who says “I want to hear the truth” and then reacts badly to the truth once will never hear it again. The feedback environment is set by the response to the last honest signal, not by the policy that says honesty is welcome.

THE INSIGHT

The line to remember

A system without feedback isn’t stable - it’s blind. The silence doesn’t mean nothing is happening. It means the system can’t hear what is.

RECOGNITION

When this is in play

You’re seeing feedback starvation when a problem is obvious to frontline people and invisible to leadership. When the data looks fine but the reality doesn’t match. When bad news consistently arrives late, softened, or not at all. When a crisis “comes out of nowhere” but people on the ground saw it building for months. When the response to a failure is “nobody told me” - that’s not an explanation, it’s a diagnosis of starved feedback.

feedback information hierarchy failure