WHEN FEEDBACK GETS LOST
An anonymised workplace case highlighting how everyday decisions about communication, feedback, and coordination can shape performance in ways not immediately visible.
OVERVIEW
This insight examines a real feedback interaction from a company’s department away day. By most conventional measures, the interaction appears unremarkable. What makes it worth examining is that it looked like a functioning feedback process while producing none of the outcomes such a process should deliver. Conditions were put on acting on feedback, the employee stopped raising concerns, and the organisation learned nothing.
The analysis reveals systemic and not solely individual issues. Four structural failures are identified operating simultaneously, often less visible through conventional measures such as engagement surveys and exit interviews. In practice, the cumulative effect is that leaders are left making decisions without a complete view of what is actually happening within their organisation.
THE SITUATION
A department of around sixty people held a team away day comprising strategy sessions, recognition and a team-building exercise in which groups competed to build a weight bearing structure using food. The following day, an employee emailed their manager with a concern about the food waste the team building exercise generated and what that waste said about the organisation's relationship with its own stated sustainability commitments.
The employee cited the company's Sustainability and Social Impact Report directly, referencing its published values to operating efficiently, using natural resources responsibly, and embedding sustainable behaviours across the workforce. They were explicit that they were not questioning the management team's intentions. They were raising a question about consistency between what the organisation says and what it does.
WHAT FOLLOWED
The manager's response acknowledged the concern before moving to defend the decision stating that, budget constraints had shaped the choice, alternatives had been considered, the department head was personally committed to environmental responsibility.
However, the substantive point of whether the activity was consistent with the organisation's published values was not addressed. The employee was instead invited to contribute ideas to the planning pipeline for the next team event.
The employee replied maintaining their position while acknowledging the genuine difficulty of event planning at scale. They suggested opening the ideas process to the wider team and noted that they were better at identifying problems than proposing solutions.
The manager's second response made the system's logic explicit. Feedback, they wrote, is always welcome but it is better received when accompanied by solutions. They would rather present the concern to the broader management team with alternative suggestions attached than without.
The employee was asked to provide an idea or two against a brief covering five criteria: fun, inclusive, enabling of team dynamics, focused on communication, and achieving zero cost and zero waste.
The employee did not respond, and the exchange closed without resolution or follow-up.
ANALYSIS
Examined through a Human Factors framework, this case illustrates four structural failures operating simultaneously none were attributable to individual fault.
Conditioned feedback acceptance.
The requirement that concerns be accompanied by solutions places a secondary burden on the person raising the issue. In practice, this filters out a significant proportion of organisational intelligence, specifically from those who are observant rather than generative, or who lack the seniority or capacity to take on additional problem-solving work.
Research on psychological safety is consistent on this point: people make an implicit calculation about whether speaking up is worth the personal cost. When the conditions placed on feedback raise that cost, contribution declines, not through conscious disengagement, but through the gradual withdrawal of effort from a process that has stopped feeling worthwhile.
Signal loss at the relay point.
The manager framed their role as a conduit, that is someone who would carry the concern forward to the broader team. That relay, however, was made conditional on prior action by the employee. As a result, the feedback including its most substantive element, the direct citation of the organisation's own values documentation, was not structurally ensured to reach anyone with the authority or remit to examine it.
Unowned improvement accountability.
The exchange exposed the absence of any clear ownership for the question the employee had raised: who is responsible for ensuring that operational decisions reflect the organisation's values commitments? Without that accountability sitting anywhere structurally, well-articulated feedback had no functional destination – or if it did it was not communicated to the employee. This results in not only a potential communication failure but also an organisational design gap.
Pattern normalisation.
Because the original concern had low material impact, the mechanism that suppressed it was easy to overlook. The same mechanism - conditional acceptance, redirection through task assignment, absence of follow through - tends to operate in the same way when the organisational impact is considerably higher. Organisations that embed this pattern in low-impact scenarios are, in effect, establishing the default response for when it matters most.
SIGNIFICANCE
What distinguishes this case is not the nature of the concern but the normality of the response.
The manager's behaviour (defending a team decision, encouraging solution-focus, framing the exchange constructively) reflects widely taught and reinforced management practice. A different manager, in the same role, under the same pressures, would likely have responded in a similar way. That is precisely what makes this a systemic issue rather than being solely individual.
The organisational consequence of patterns like this, accumulated across teams and over time, is a leadership function making decisions with incomplete information. This is not because the information didn't exist, rather it is because the systems through which it should have travelled were not designed to carry it.
WHAT THIS MEANS IN PRACTICE
The gap this case exposes is sometimes difficult to see through conventional measurement. For instance, engagement surveys capture sentiment, not signal loss and exit interviews surface conclusions, not necessarily the accumulated interactions that produced them. What goes unmeasured is the steady erosion of the conditions under which people decide it is worth contributing and the progressive narrowing of what leadership knows about its own organisation.
In this context Human Factors analysis maps that gap directly. It examines how feedback moves or fails to move through the structure of an organisation, identifies where conditions are placed on it that distort or suppress it, and establishes where ownership for improvement is absent. The result is a clear picture of where the system is working against the organisation's stated intentions, and what a more functional design would look like.
The full case analysis including the causal map and intervention points is explored in detail in our training programmes.
NEXT STEPS
If this pattern is present in your organisation, it is almost certainly broader than any single interaction suggests. A short diagnostic conversation can establish where feedback is breaking down, what signals may not be reaching decision-makers, and what the structural options for addressing it look like.