Is the 360 Feedback Process
Being Used Against You?
How to read whether the feedback process you are inside is developmental or political. And what the signals look like when it is the latter.
There is a particular kind of disbelief that comes with reading feedback that is partially true.
Not without truth, not invented: some of it you recognise and agree. A delivery that could have been softer in one meeting. A moment when you moved quickly on a decision and did not bring everyone with you. The conversation where you gave candid feedback to your team member that they were not performing, which is now being interpreted as micromanaging or having perfectionist leader tendencies. You know these things happened. You have reflected on them before.
But the weight is off.
The proportion is off. The things you handled well: the project that came in on time after three months of navigating a restructure, the relationship you repaired with a stakeholder who had been a persistent blocker, the team you steadied through six months of ambiguity. None of that appears. Or it appears briefly, then disappears inside a list of concerns that reads as though your entire tenure has been a mounting problem.
Minor friction has been elevated into a pattern. Something said once in a corridor has become evidence of something systemic. The picture does not match the year you remember living.
And yet you cannot quite dismiss it. Because some of it is real.
This is the disorientation that brings most people to this question: is this feedback a genuine reflection of how my leadership is landing, or is something else happening here? Not knowing whether to trust what you are reading or trust what you know. Not certain whether the instinct that something is off is accurate or defensive.
There is a specific set of instruments through which feedback can be gathered and used, each of them legitimate on its face, each of them capable of serving a very different purpose than the one they appear to serve. Understanding those instruments, how they work, and what the signals look like when they are being used politically rather than developmentally, is the work of this guide.
The four instruments
Feedback on your leadership can be gathered in several ways. Most of them are, under normal circumstances, reasonable tools. A manager who wants to understand how a leader is experienced by their team has legitimate reasons to use all of them. The question is not whether these instruments exist. It is whether the way they are being used in your situation matches the purpose they are supposed to serve.
Instrument 01
The 360-degree feedback process
A structured assessment in which feedback about your performance and leadership is gathered from multiple sources: your direct manager, your peers, your direct reports, and sometimes stakeholders outside your immediate team. The outputs are typically aggregated and anonymised before being shared with you, on the basis that anonymity produces more candid responses. The formal 360 is the most visible of these instruments. It has a process. There is usually an HR owner. There are documented criteria. There is a report. There is a debrief conversation. All of this gives it the look and structure of objectivity, which is precisely what makes it effective as a political instrument when it is used as one. The features designed to reduce bias (anonymity, multiple sources, aggregation) also make the data very difficult to contest.
Instrument 02
The formal skip-level meeting
A conversation between a leader and the team members who report to someone below them, conducted without the immediate manager present. Many organisations run these on a regular schedule as part of their leadership infrastructure. The premise is sound: it gives senior leaders direct access to how things are experienced at the ground level, independent of the filter that any single manager represents. When this process runs on its normal schedule, with its normal scope, it is a legitimate part of how an organisation takes its own pulse. The political question is not whether the meeting happened. It is what was being looked for, how the conversation was framed, and what happened to the information afterwards.
Instrument 03
The impromptu skip-level
A skip-level meeting that is called outside the normal cadence. Not part of a regular schedule, not triggered by a routine review point, but convened specifically in response to a situation. The manager's manager requests time with your team, or with selected members of it, at a moment that does not fit the ordinary rhythm of organisational life. The impromptu skip-level is harder to ignore than the formal version precisely because it is unusual. When something outside the ordinary schedule happens, it is because someone has decided it needed to happen now. The timing is itself a signal, and it is one that the people being asked to attend will also have noticed.
Instrument 04
The covert informal gathering
The least visible of the four instruments and, in some ways, the most significant. It does not have a name on a calendar. It does not produce a report. It happens in corridors, in brief conversations after a meeting has ended, in a casual check-in framed as routine management: "How do you think she's getting on? What's your honest read of her? Is the team feeling supported?" Research and practitioner experience consistently suggest that this kind of informal gathering happens more often with women leaders than with men. The threshold for treating a woman's leadership style as something that needs to be informally investigated is lower. The conversations are undocumented. The person being discussed has no knowledge they are happening. And the impressions gathered feed directly into the formal concerns that surface later, stripped of the context in which they were collected.
The mechanism underneath
Each of these instruments has a legitimate use. Understanding the political use requires understanding a specific dynamic that organisational behaviour researchers have named and documented.
In most organisations, when a senior person has concluded that a role needs to be filled differently, or that a particular leader is not the right fit for the direction they want to take, they face a practical problem. "I have decided I want someone different in this role" is not, in most professional environments, a sufficient basis for action. It is not documentable in the way that HR process requires. It does not survive scrutiny. It does not protect the organisation from a challenge.
What does survive scrutiny is a pattern of concerns, raised through legitimate processes, supported by multiple independent sources, presented as evidence rather than opinion. The formal process, whether a 360 or a skip-level or both, provides something the manager's view alone cannot: the appearance of objectivity.
Applied to this situation: in some cases, the 360, the skip-level meeting, the informal conversations, are not how a manager discovers a problem with your leadership. They are how they construct the documentation for a conclusion they have already reached. The process does not precede the verdict. The verdict precedes the process.
This is not the same as saying the feedback gathered is entirely fabricated. In most cases it is not. Partial truths are more useful than invented ones precisely because they are harder to dismiss. What the political use of these instruments does is select, frame, weight, and present real observations in a way that builds a case rather than a picture.
One of the most consequential ways this happens is through reframing. A legitimate leadership act is taken and given a different name. The candid performance conversation you had with a team member, the one that was your responsibility to have, becomes evidence of micromanaging or perfectionist leader tendencies. The decision you made quickly under time pressure, which delivered results, becomes evidence of not bringing people with you. The high standard you hold your team to becomes evidence of being difficult to work for.
None of these observations are invented. All of them are real things that happened. But they have been taken out of their context, stripped of the circumstances that explain them, and filed under a character conclusion rather than a situational one. That is the reframing move. And it is effective precisely because you cannot deny that the original events occurred.
Understanding this changes what you are looking at. You are not primarily dealing with a perception problem that accurate performance data can correct. You are looking at whether a political process is using the structure of a development process as its instrument. These are different situations and they require different responses.
Reading the signals
How do you know which situation you are in? You cannot always be certain, and this guide will not pretend otherwise. Some of what follows can also describe a feedback process that is simply badly designed, under-resourced, or running without sufficient rigour. Poor process and political process can look similar from the inside. The signals below are not proof. They are patterns, and what matters is whether they cluster.
Signals that apply across all four instruments
- The timing does not fit the developmental logic. Genuine development processes are designed around the person being developed. They happen at a point where there is enough runway ahead to act on what is learned. When a 360 is commissioned, or a skip-level is called, immediately after a significant structural change, a new hire above your level, a budget conversation that did not resolve in someone's favour, or a project that exposed a disagreement with your manager, the timing tells you something. Ask yourself: what else was happening in the organisation when this process was initiated?
- The concerns appearing now have never been raised with you directly. If your manager has raised a concern in a one-to-one, documented it, and followed up on it, the appearance of that concern in a formal process is not surprising. If the concerns surfacing now are ones you are hearing for the first time, that gap matters. Feedback that has never been offered to you, and appears for the first time as evidence of a recurring pattern, has not gone through the ordinary cycle of being given, received, and acted upon.
- The criteria are vague, undefined, or appear to have shifted. If you are being assessed against dimensions that were not clearly established when the work being evaluated was done, the framework is being constructed around a conclusion rather than the other way around. Ask, in writing where possible, what the specific criteria are and what the standard of performance against each of them looks like.
- The feedback focuses on character rather than specific observable behaviour. "She creates a difficult environment for the team" is not the same as "in the Q3 planning session, she overrode three team members' input without acknowledgement." The first is a characterisation. The second is a behaviour in a specific context. Feedback weighted toward characterisations is less useful for development and more useful for building a case. It is also much harder to dispute.
- You are being excluded from conversations you would ordinarily be part of. The feedback process itself is rarely the only signal. If you are being left off meeting invitations, if decisions that would normally come through you are being made around you, if peers have become subtly quieter, the formal process may be one element of a broader pattern. Political situations rarely operate through a single mechanism.
Signals specific to the 360-degree feedback
- The rater pool has been substantially controlled by your manager. When your manager determines who provides input on your performance, they determine the data. This does not mean the data will be biased, but it means the design of the process does not structurally prevent it. Find out, where you can, how raters were selected and by whom.
- The debrief is rushed, absent, or focused on presenting conclusions rather than exploring patterns. A genuinely developmental 360 does most of its work in the debrief: examining patterns, exploring context, building development intentions. When the debrief is treated as a formality, or focuses primarily on delivering concerns rather than working through them collaboratively, the process is not functioning as a development tool.
Signals specific to the formal skip-level
- The framing of what the meeting was for has shifted. A skip-level meeting scheduled as a routine culture conversation and then referenced afterwards as evidence of team concerns has changed its function between the scheduling and the debrief. Pay attention to how the meeting is described before it happens and how its outputs are characterised afterwards.
- You were informed after the fact, not before. In organisations where skip-levels are a standard practice, leaders are typically informed that the meeting is happening as a matter of professional courtesy. When you learn about a skip-level only after it has occurred, or through an indirect channel rather than directly from your manager, the process is not being run transparently.
Signals specific to the impromptu skip-level
- The timing is the most reliable signal here. An impromptu skip-level called in the weeks following a specific incident, such as a disagreement, a decision that went against your manager's preference, or a moment of visibility that positioned you independently of your manager's narrative, is rarely coincidental. The question to hold is: what happened recently that might have prompted someone to want to know what your team thinks of you right now?
- Selected rather than full team. If only certain team members were included in an impromptu skip-level, the selection itself is information. Who was invited and who was not tells you something about what the conversation was designed to find.
Signals specific to the covert informal gathering
- Your team's behaviour shifts without explanation. When people who have been straightforward with you become careful, or when the dynamic in a room changes in ways that are hard to name, something has happened that you are not aware of. This is not always evidence of informal gathering, but it is worth paying attention to when it coincides with other signals.
- Concerns are raised with you that carry the texture of a rehearsed conversation. When a team member raises a concern that sounds unusually complete, that has a shape to it, that lands as though it has been discussed before it was delivered to you, it may have been. Managers who gather informal impressions sometimes use those conversations to prime people before a more formal process begins.
- You are told, in a formal setting, about concerns that your team members would be surprised to learn they had raised. When feedback attributed to your team does not correspond to anything you would expect them to have said, either because your relationships with them are strong or because the concerns described do not match the interactions you have had, ask yourself where those concerns actually originated.
The India and GCC dimension
Cultural and Geographic Context
In high power distance environments, where deference to authority is culturally embedded, each of these instruments carries additional weight.
Hofstede's Power Distance Index places India at 77, compared to the UK at 35. In a high power distance culture, when a senior person signals, even indirectly, that they are gathering views about a particular leader, the people being asked are acutely sensitive to what is being sought. This does not mean they fabricate responses. It means they read the room and respond accordingly. The concerns they raise are real concerns, but the threshold for raising them, and the weight given to them, is shaped by an awareness of what the person asking seems to want to hear.
The result is that in a high-PDI context, a manager with a settled view of a leader will often find that the feedback gathered confirms it. Not because the data has been manufactured, but because the social dynamics of the gathering process have already shaped what gets said. The feedback looks like independent evidence from multiple sources. It may be, in part, a distributed reflection of one person's view.
For women in GCC or India-based roles, working within multinational organisations where the power centre sits in a different geography, this dynamic is compounded by a second layer. The people with formal authority over your career may have limited direct visibility of your work, limited understanding of the local context in which you operate, and primary access to you through the very filter you are questioning. The feedback they receive confirms what they already had limited capacity to interrogate.
How to hold what you have found
When several of these signals are present, you are probably not in a development conversation. You are in a political one.
That conclusion, when you reach it, tends to produce one of two responses. The first is relief: a name for something that has felt off but has been hard to articulate. The second is a kind of grief: the recognition that you are being managed out of something using processes that were supposed to be on your side.
Both are reasonable responses. Neither of them is the same as knowing what to do next.
This guide has tried to give you the diagnostic layer. The ability to look at what is happening, to understand the instruments being used and the mechanism underneath them, and to read your own situation with enough clarity to move forward from a place of comprehension rather than confusion.
If you want to work through what you are seeing in your specific situation, the Organisation Politics 101 guide provides the foundational framework for reading how power moves in your organisation. And if your situation needs a direct read from someone who has worked with senior leaders navigating exactly this kind of landscape, the Political Intelligence Audit is built for that.
Further Reading
- Cohen, M. D., March, J. G. and Olsen, J. P. (1972). A garbage can model of organizational choice. Administrative Science Quarterly, 17(1), 1–25.
- Correll, S., Wynn, A., Wehner, J. and Weisshaar, K. Stanford VMware Women's Leadership Innovation Lab research on performance review language and gender bias.
- Ferris, G. R., Treadway, D. C., Kolodinsky, R. W., Hochwarter, W. A., Kacmar, C. J., Douglas, C. and Frink, D. D. (2005). Development and validation of the political skill inventory. Journal of Management, 31(1), 126–152.
- Hofstede, G. (2001). Culture's Consequences: Comparing Values, Behaviors, Institutions and Organizations Across Nations. Sage Publications.
- Ibarra, H. and Obodaru, O. (2009). Women and the Vision Thing. Harvard Business Review, January 2009.
- Williams, J. C. (2014). What Works for Women at Work. NYU Press.