Why orgs remember what went wrong and forget what went right
Most teams are performing well most of the time. Deadlines are met, decisions are made, work moves forward. The system is broadly functional. And yet the dominant experience of feedback in most orgs is corrective — focused on what slipped, what missed, what fell short.
The 99% that worked gets silence. The 1% that didn’t gets a spotlight.
Over time, this stops being a feedback problem and becomes a performance problem.
Context
This is not about being kind. It is about what the feedback signal actually teaches.
When the only consistent signal people receive is about failure, they learn to optimise for not failing — which is not the same as performing well. Risk appetite drops. Initiative shrinks. People do what is safe, not what is right. The bar does not rise. It calcifies at “good enough to avoid criticism.”
The irony is that orgs doing this are usually trying to raise the bar. The mechanism they are using is achieving the opposite.
Insight
Raising the bar shouldn’t feel like punishment. But it does when the only time performance is discussed is when something went wrong. The implicit message is: your baseline is expected, your failures are noticed, your wins are invisible. That is not a performance culture. That is a pressure culture — and the two produce very different results.
There is a second pattern underneath this one. In most orgs, feedback flows in one direction: downward. Leaders assess teams. Managers assess reports. The people closest to the work rarely get to surface what is making it harder. The system optimises for accountability at the bottom of the org and insulation at the top. When feedback only flows downward, performance follows — it concentrates where the scrutiny is, and atrophies where it isn’t.
What actually raises the bar is a feedback environment where good work is named and studied with the same rigour as failure. Not celebrated performatively — studied. What made this work? What conditions produced this outcome? How do we make this repeatable? That is the question that compounds.
Implication
A team that only hears about its failures does not become more precise. It becomes more defensive. People spend cognitive energy managing perception rather than improving output. Debrief culture turns into blame culture. Post-mortems become exercises in attribution rather than learning.
The leader who only engages when something breaks signals — clearly, even if unintentionally — that their attention is a threat signal, not a resource. People start managing up instead of managing the work. Visibility becomes something to control, not something to use.
The cost is not just morale. It is the quality of information flowing through the system. When people stop surfacing problems early because they know what the response will be, the org loses its early warning system. Problems arrive late, at full cost.
Action
Name the 99% explicitly. Not in a blanket “great job everyone” way — specifically. What worked, why it worked, what it took. Make good performance as visible as failure. This is not about praise. It is about signal clarity.
Debrief wins with the same rigour as failures. Most orgs run post-mortems on what went wrong. Few run them on what went right. Both contain information. The win debrief asks: what conditions made this possible, and can we design for them?
Separate the feedback conversation from the performance conversation. Real-time corrective feedback on a specific miss is useful. A pattern-level performance conversation requires context, history, and a two-way exchange. Conflating the two produces defensive responses, not behaviour change.
Build feedback that flows both ways. If the people doing the work cannot surface what is making it harder without it being read as an excuse, the system is blind in one direction. Create structured moments — not open-ended complaint forums, but specific questions: what slowed this down, what would have made this easier, what decision upstream created cost downstream.
Raise the bar by defining it, not just reacting when it is missed. Most bar-raising conversations happen after a failure. The more effective version happens before work begins: here is what excellent looks like, here is the standard, here is what we are optimising for. Then the feedback — corrective or affirming — has a reference point. It becomes calibration, not judgment.
The org that only notices failure trains people to avoid it. The org that notices what works trains people to repeat it. One raises the floor. The other raises the bar.