The Feedback Paradox
We have never had more feedback tools. 360s, pulse surveys, upward feedback, real-time check-ins, AI-generated sentiment analysis. The infrastructure for telling leaders how they're doing has never been more sophisticated — or more widely deployed.
And yet, most leaders will tell you, honestly, that feedback hasn't changed them much.
Not because they don't care. Most do. But because the feedback they receive is too infrequent to feel relevant, too aggregated to feel actionable, and too judgment-coded to feel safe. Instead of unlocking growth, it triggers defense. Instead of creating direction, it creates anxiety. The very systems designed to help leaders become more self-aware are often the ones making them more guarded.
This is the feedback paradox.
The problem with periodic and numeric.
Most formal feedback systems share the same basic architecture: gather input periodically, quantify it, compare it to a benchmark, present it to the leader. It's clean, scalable, and administratively satisfying. It's also poorly suited to how humans actually learn and change.
Learning requires proximity to the moment. A 360 report that arrives three months after the behavior it's measuring has already lost much of its usefulness. The leader can't connect the score to the specific meeting, the specific conversation, the specific moment where something landed differently than they intended. Without that connection, the data becomes abstract — something to analyze rather than something to act on.
And when feedback is numeric, it invites comparison rather than curiosity. A score of 72 on psychological safety prompts leaders to ask is that good or bad? and who gave me that score? The frame is evaluative from the start. Defense is a rational response to being evaluated.
The judgment problem.
There's something deeper going on too. Most feedback systems are, structurally, systems of judgment. They assess leaders against a fixed competency model, identify gaps, and prescribe development. The implicit message — however carefully worded — is: here is where you fall short.
Decades of research on human motivation tells us this is precisely backwards. People grow fastest when they build from what they're already doing well — when development starts from a place of competence and curiosity rather than deficiency and correction. Self-determination theory is unambiguous on this: environments that support autonomy, mastery, and connection produce growth. Environments that undermine them produce withdrawal.
Most feedback systems, as currently designed, undermine all three. The leader has little agency over when or how feedback is gathered. The numeric format obscures rather than develops mastery. And the anonymized, aggregated delivery strips away the relational context that makes feedback feel like care rather than critique.
What leaders actually need.
I've spent a lot of time in rooms with senior leaders processing feedback. What I've noticed is that the moments that actually shift something — that produce real reflection and real change — are almost never the formal report. They're the honest conversation with a trusted colleague. The offhand comment from a direct report that stuck. The moment a leader recognized their own behavior in someone else's story.
In other words: fast, human, contextual signal. Not slow, numeric, institutional data.
Leaders need to understand how their behavior lands in real work — in the actual meetings, the actual one-on-ones, the actual moments that shape how people feel about showing up. They need signal that's close enough to the moment to be meaningful, delivered in a way that invites reflection rather than defense, and grounded in specifics rather than scores.
That's a different design problem than the one most feedback systems are trying to solve.
The opportunity.
The goal was never the 360. The goal was a leader who understands their impact, who can see themselves clearly, and who has the conditions to grow. If the tool is getting in the way of that goal — and for many leaders, it is — then the answer isn't a better tool with the same underlying logic.
It's a different logic altogether. One that starts with the leader's humanity, not their gaps. One that treats feedback not as a verdict, but as an ongoing conversation between a leader and the people they affect.
We know how to build that. We just haven't prioritized it.