Organizational Feedback: Beyond Individual Correction to Collective Diagnosis

Feedback occupies a central place in contemporary leadership and management practices. Each year, organizations from all sectors invest considerable resources in performance reviews, personality type or behavioral style assessments (MBTI, DISC, Hogan, etc), executive coaching packages, customized or off-the-shelf 360 assessments and feedback training. All are based on a common assumption : people improve when they receive accurate information about their behavior and its impact on others.

However, in my experience, this assumption is only partially correct. Why? Because most feedback processes - whatever the chosen method is - rely on a narrow unit of analysis: they are individual-centric. Behaviors are observed, interpreted, and attributed to individuals, with limited attention paid to the organizational conditions within which those behaviors emerge. But, in my experience, what organizations tend to treat as “personal deficiencies” may actually be “responses” to larger systemic realities.

Consider a manager who avoids difficult conversations. Traditional feedback frameworks are likely to focus on the individual's lack of “managerial courage”, communication skills, or conflict management capabilities. Yet, the same behavior may be understood differently once placed in context. In organizations where the dissent voice is penalized, disagreement is associated with career risk, or psychological safety is weak, avoidance may represent a rational adaptation rather than a personal shortcoming. I see it a lot in hyper hierarchical organizations, or in systems where there is a lot of competition, where conformism and keeping the status quo become the safest bets. In one of the workshops I led, after a participant had named an elephant in the room, we took a break. When we came back from it, he found an anonymous note on his seat. On it was written: “beware of the career-limiting moves”.

What I see is that interventions aimed at individuals almost always leave the underlying currents untouched. The behavior may change temporarily, but the dynamics that produced it remain intact. We just displace the problem, and, in many cases, the same pattern simply reappears, sometimes elsewhere in the system. Or the system pushes out those who cannot withstand the contradicting tensions, a classical scapegoating move.

This limitation reflects a broader tendency which I observe often in organizational life: the attribution of collective problems to individual actors. Teams struggling with accountability search for stronger leaders. Organizations experiencing low trust focus on interpersonal skills. Persistent silence becomes a communication issue rather than a signal about the organization's relationship to authority, risk, or conflict.

In my view, such approaches overlook a fundamental reality: behavior is never produced by individuals alone. It emerges through the interaction of personal history, role expectations, authority structures, cultural norms, and organizational narratives. And these are co-created. Like a set of matryoshkas, we are a system in a system, in a system.

That is the reason why, feedback should be understood not as objective truth but as a form of organizational data. Every feedback statement contains information about at least four elements simultaneously: the person receiving it, the person providing it, the relationship between them, and the system in which both are operating. A manager who describes an employee as "insufficiently proactive" may be identifying a genuine developmental need which could be fixed with a few executive coaching sessions. However, that statement could also reveal assumptions about initiative, expectations associated with the role, frustrations within the relationship, or broader organizational pressures regarding performance and speed. Therefore, the challenge is not determining whether the feedback is true or false, but understanding which reality it describes.

I have studied a few different frameworks, including the radical candor framework which a client asked me to incorporate in a one day leadership training. But I kept seeing its limitations. The main reason is that this model assumes the person giving radically candid feedback has a reasonably accurate access to reality. The sequence as I see it is the following: I see something you do that’s impacting the organization’s productivity and efficiency, therefore I should tell you so you can improve. But what we are “seeing” exactly? Are we talking about neutral observation? interpretation? projection? a role requirement based on the narrative of the company? or an interesting symptom at the individual level of something that is going on in the system? Being the daughter of a GP, I’m accustomed to the way physicians think and advocate to adopt their method. When a patient complains about a twitching finger, the physician does not begin by treating the finger. The symptom may indeed be localized, but it may also be the first visible sign of a condition emerging elsewhere in the body. It could be temporary muscle fatigue, a compressed nerve, or the early manifestation of a neurological condition. In the field of medicine, determining which explanation is most plausible requires expanding the scope of inquiry rather than narrowing it. No competent physician would conclude that the problem resides in the finger simply because that is where it first appears. The finger becomes one data point within a larger diagnostic process. Organizations, by contrast, often move in the opposite direction. The moment a behavior becomes visible in an individual, more often than not, the individual becomes the diagnosis. We mistake the location of the symptom for the source of the problem.

This is why I’m convinced that a more developmental approach to feedback requires expanding the unit of analysis beyond the individual.

The first task should always be collective diagnosis. Before evaluating individual behavior, organizations must identify the recurring patterns, tensions, and adaptive challenges present within the system. This requires careful observation of behaviors, decision-making processes, meeting dynamics, and stakeholder experiences. It also requires identifying the narratives through which organizational members make sense of their environment. I should also add that they rarely are uniform and my experience working with large organizations where one part of the staff are in the headquarters – which carries a specific narrative – and another part in the field, themselves divided between local and international staff, brings a wealth of specific narratives that have been rigidified overtime. Different functions, professional groups, geographical regions, or leadership levels develop distinct assumptions about authority, collaboration, accountability, innovation, and risk. While some beliefs are widely shared, others remain localized within particular parts of the organization. Any meaningful feedback process must account for these variations. It is the background of any feedback conversation and cannot be overlooked.

The second task is relational diagnosis. Feedback is not exchanged between abstract individuals but through relationships shaped by a certain level of trust, by history, dependency, and power, especially in global organizations. The interpretation of a message is influenced as much by the relationship as by its content as Sheila Henne and Kim Scott reminds us in Thanks for the Feedback. A comment delivered by a direct supervisor carries different implications than the same observation offered by a peer. As Adam Galinsky argues in Inspire, authority acts as an amplifier. The higher one's position in a system, the greater the emotional and psychological consequences of one's words. Feedback is never exchanged between equals: a comment delivered by a senior leader is car from only be a piece of “information”. Asymmetry matters and should at least be acknowledged.

Only after examining systemic and relational conditions should our attention turn to the individual contribution. At this stage, it is important to understand that our objective has shifted from identifying “what is wrong with X ” to understanding “how X participate in maintaining or transforming existing patterns”. The central developmental question, for the feedback giver as much as the feedback receiver is: “How am I contributing to the outcomes I experience, and what alternative responses are available to me?”. In this question, in the space it creates between stimulus and reaction, we now have found a little bit of agency at minima, and even the conditions of true empowerment

Of course, this approach does not eliminate personal accountability. But I believe that it places accountability within a more accurate understanding of organizational life. Individuals remain responsible for their actions, but those actions need to be interpreted within the context that helps produce them. Yes, I am saying that even having hired a truly problematic person in the first place has to do with a larger dynamic. Why wasn’t toxic behavior detected in the first place? Does the system unconsciously believe – like it is the case in certain organizations I have worked and consulted for - that it is acceptable that some of their staff have toxic behavior? If yes, what is toxic behavior a corollary to? Efficiency? Competitiveness? Self confidence? That’s a more interesting question. A much more uncomfortable one too.

In increasingly complex organizations, feedback needs to become more complex as well. We need to evaluate individuals and their contributions much less than we need to invest in improving our ability to diagnose systems. I’m convinced that growth occurs when people gain a clearer understanding of the forces shaping their behavior and the role they play in sustaining or changing them.