If you have a disability and you've been through a 360 review, you may have left the meeting carrying a familiar discomfort: the feedback sounded like it was about your work, but it felt like it was about something else. How you communicate. How you move through the office. How you interact with colleagues in ways your disability shapes, in ways they don't always understand.

That discomfort is information. It's not paranoia and it's not oversensitivity. It's pattern recognition, and it points to a real dynamic in how 360 reviews work for employees with disabilities.

360 reviews are designed to give you a fuller picture of your performance by gathering input from multiple sources: your manager, your peers, direct reports if you have them, and sometimes cross-functional collaborators. In theory, that breadth corrects for any single person's blind spots. In practice, when disability enters the picture, the same breadth can amplify bias. Colleagues who haven't worked closely with someone with your disability may offer feedback that's sincere but fundamentally off-target, measuring comfort with difference rather than quality of work.

This guide is here to help you navigate that. Not to make the process harder than it already is, but to help you come to it with more confidence: before the review opens, while you're reading the results, and as you decide how to use them.

How 360 Reviews Work and Why Disability Sometimes Distorts the Picture

A typical 360 cycle starts with rater selection. Your manager chooses reviewers, or asks you to nominate peers. Raters complete an anonymous survey covering areas like communication, collaboration, leadership, and technical skills. They submit ratings on a numerical scale along with optional narrative comments. Your manager aggregates the results, identifies themes, and delivers feedback in a review meeting.

Anonymity is supposed to encourage honesty. The multi-source design is supposed to offset individual bias. But when you're the only wheelchair user on your team, or one of very few employees with a disclosed disability, the dynamics can shift in ways the system wasn't designed to address. If several raters mention "communication challenges" and you have a speech impairment, that pattern may not reflect your clarity as a communicator. It may reflect their unfamiliarity with how you communicate.

Disability affects the 360 process in two meaningful ways. First, peers often lack the context to distinguish between an accommodation and a performance gap. A colleague who's used to spontaneous brainstorming may interpret your need for advance agendas as rigidity, even though it's an accommodation. They're not wrong that your working style differs from theirs; they just don't have the frame to evaluate whether that difference matters for your performance. Second, most workplaces haven't developed clear norms around disability, which means raters default to implicit assumptions about what "professional" or "engaged" looks like. Those assumptions tend to reflect a non-disabled standard.

Understanding this doesn't mean you'll never receive fair feedback in a 360 review. It means you'll be better positioned to tell the difference between feedback that's genuinely about your work and feedback that needs more examination.

Preparing Before the Review Cycle Opens

The most effective time to shape a 360 review is before it starts. Once feedback is submitted, you're in response mode. Before it opens, you have meaningful opportunities to influence how the process unfolds.

Rater selection. If your company allows you to nominate raters or suggest peers, prioritize people who've worked with you on concrete deliverables. Choose raters who can speak to your work, not just your presence in meetings. A cross-functional partner who collaborated with you on a project deliverable will give you more useful and more accurate feedback than someone who only sees you in all-hands. If you've been given a mandatory list, review it. If someone on the list hasn't worked closely with you this year, you can raise that gently with your manager: "I want to make sure the raters are people who've seen my actual contributions. Is there flexibility to adjust?"

Documentation. Bias tends to creep into evaluation when memories are vague. Before the review cycle opens, compile a clear record of your contributions: projects you led, problems you solved, outcomes you influenced. Include dates and deliverables. If you shipped something, link to the result. If you mentored someone, note what they developed. Send this as a "mid-year update" or a "Q2 highlights" note. Your goal is to give your manager something concrete to return to when reading 360 feedback, so your work is anchored in facts rather than impressions.

A brief conversation with your manager. You don't need to go into detail about your disability or relitigate past accommodations. A simple, forward-looking framing works well: "I've noticed some colleagues aren't as familiar with how I work. If feedback comes up about communication or collaboration, I'd really appreciate the chance to talk through it together so we can look at the specifics." You're not asking for special treatment; you're asking for a thoughtful reading of the results, which is something any employee is entitled to.

Reading Feedback That Conflates Disability with Performance

When your 360 results arrive, your most important task is separating signal from noise. Some feedback will be genuinely about your work. Some will be about discomfort with disability. Both need attention, but not in the same way.

Start by asking for specifics. If your manager says "a few people mentioned communication challenges," don't immediately move to explanation. Ask instead: "Can we look at specific deliverables? Which work products weren't clear?" If the answer is vague ("it's more about presence in meetings" or "the sense that you're hard to read"), take note. Presence and readability are subjective. Deliverables are not. Steering the conversation toward concrete examples helps clarify whether the feedback points to something actionable.

Watch for coded language. Phrases like "doesn't seem engaged," "hard to read," or "needs to be more present" often describe visible disability characteristics rather than performance. So does "not a culture fit" when it arrives without any explanation of what the culture expects. This language can feel personal. Vague, adjectival feedback that doesn't cite specific instances is harder to act on for anyone, and it's fair to ask for more detail regardless of whether disability is a factor.

Compare what you're hearing to what you know about your own work. If peers describe you as hard to collaborate with but you co-led three cross-functional projects this quarter, hold both things at once. It's possible something in your collaboration style is creating friction you haven't seen. It's also possible the feedback is reflecting something other than your actual contributions. Bringing your documentation into the review meeting isn't defensive; it's grounding the conversation in evidence.

And be genuinely open to feedback that's substantive. Not all criticism is bias. If feedback is specific, actionable, and tied to observable behaviors you have control over, it's worth taking seriously. The question to hold is whether what's being described is a performance gap or the operational reality of working with your accommodations.

Responding Without Over-Explaining Your Disability

When 360 feedback is entangled with bias, you face a choice about how to respond. The impulse to explain your disability in full is understandable; you want people to understand your experience. But in a review meeting, extensive explanation can shift focus away from your work and toward your condition, which usually isn't the direction you want.

What tends to work better is redirecting to standards. If feedback suggests you're slow to respond to messages, ask: "What's the expected response time? I've been prioritizing same-day replies for anything urgent and 24 hours for everything else. If there's a different expectation, I'd like to know what it is." You're taking the feedback seriously while anchoring it to something measurable. If you're meeting the standard, that becomes clear. If the standard hasn't been articulated, you've opened a useful conversation.

When feedback is directly about an accommodation, naming that distinction is both appropriate and calm. "The need for advance agendas is an accommodation tied to my disability. If there's a performance concern related to how I prepare for meetings, I'm glad to discuss that specifically. The accommodation itself isn't something that's up for evaluation." There's a meaningful difference between a performance issue and an accommodation need, and drawing that line protects both you and the integrity of the review.

If your manager pushes back without specifying what the underlying concern is, asking for more concrete detail is reasonable. "Can you help me understand what 'hard to work with' means in terms of my specific contributions? I want to address real gaps, and I need more detail to do that." You're not deflecting. You're asking for the kind of clarity that makes feedback something you can act on.

Using the Results to Advocate for Your Growth

A 360 review, even an imperfect one, contains information you can use. The question is how to use it constructively.

Start by writing a brief response to the themes that emerged, not a point-by-point rebuttal but a thoughtful acknowledgment that demonstrates you've engaged with the feedback seriously. Note what you're doing to address concerns that are substantive. For feedback that conflates disability with performance, you don't have to call that out explicitly in writing; addressing the underlying performance concern is enough. "I'm scheduling check-ins with a few key collaborators to improve alignment on project expectations" addresses collaboration feedback without accepting the premise that your disability is the problem.

From there, move to your own growth goals. A 360 review is one of the most natural openings for a conversation about advancement. "I've been reflecting on what I want to develop this year, and I'd love to talk about what it would take to move to the next level. What skill areas does this feedback surface, and what would you want to see from me in the next cycle?" That positions you as someone who's engaging with the feedback and thinking forward, which is exactly where you want to be.

If you're concerned that bias-driven feedback might affect future decisions, keep a record of your documentation alongside the 360 summary. You may never need it. But if a pattern develops over time, having a clear record of your contributions alongside vague negative feedback creates a meaningful contrast.

When the Feedback Is Harder Than Expected

Sometimes 360 feedback arrives and it's painful. The ratings are low across the board, or the narrative comments feel harsh or personal. This is a genuinely hard experience, and it's okay to need some time before you can engage with it.

When you're ready, start by understanding what happens next. Ask your manager directly: "Is this feedback suggesting my role is at risk? Am I on a performance improvement plan?" The answer matters for how you proceed. If yes, you need to understand the timeline and what success looks like. If no, the feedback is information, not a verdict on your value.

If you can access a breakdown of the feedback by rater category, it's useful to look at. If your manager rated you highly but peers rated you poorly, you're dealing with a different problem than if every group rated you low. The first may point to a relationship dynamic you can explore. The second calls for a more comprehensive look at what's happening.

A harder question is also present: Is this feedback reflecting something about your performance that you can work on, or is this an environment that fundamentally doesn't value how you work? A single difficult 360 review doesn't answer that. But if your accommodations are consistently framed as burdens, if disability comes up repeatedly in performance discussions without connection to specific work issues, or if you're rated lower than your contributions justify across multiple cycles, those patterns tell you something important about the environment, not just about any single review.

If you decide to stay and reset for the next cycle, focus on building relationships with colleagues who can speak to your actual contributions. Clear, measurable goals make it easier for feedback to be grounded in work rather than impression. Whatever the outcome, keep investing in your own development. Your capabilities and your growth don't depend on any single review cycle.

Common Questions

Can I opt out of a 360 review if I think it will be biased?

Most companies don't offer opt-outs for standard performance processes. What you can do is raise concerns before the cycle starts, with your manager or HR, and use the preparation strategies above to influence the process as much as possible. Opting out is rarely available, but influencing the process often is.

What if my manager cites 360 feedback to deny a promotion?

Ask for specifics: which competencies are you not demonstrating, and what would success look like next cycle? If the feedback being cited conflates your disability with performance, document that and raise it with HR. Under the ADA, performance standards must be job-related. Promotion decisions based on bias-driven peer feedback may not meet that standard, and asking for clarity about the criteria being applied is appropriate.

Should I disclose my disability to my raters before the review cycle?

Disclosure is a personal decision only you can make. If your disability is already known, pre-review disclosure changes little. If it's not visible and you haven't shared it, a 360 cycle usually isn't the ideal moment. Disclosure works best when it's tied to a specific need or a relationship you've already built. Disclosing right before peers rate you can feel abrupt and may not prevent bias.

How do I know if feedback is biased or legitimate?

Legitimate feedback tends to be specific, actionable, and tied to observable behaviors. "Your reports often arrive after the agreed deadline" is something you can act on. "You seem disorganized" is not. Feedback that uses vague, evaluative language without concrete examples is harder to act on for anyone and worth examining carefully.

What if I agree with some of the feedback but it's tied to my disability?

You can acknowledge feedback without accepting that it represents a performance gap. For example: "I hear that I don't engage much in real-time brainstorming. That's accurate; I process information better with time to reflect, so I contribute more effectively in written follow-up or structured proposals. If real-time participation is a requirement for this role, I'd like to understand why, because my written contributions have consistently moved projects forward." That's honest about how you work while keeping focus on outcomes.

Can I request that my 360 feedback be reviewed by HR for bias?

Yes, particularly if you believe the feedback violates anti-discrimination policies or conflates your disability with performance. Frame it as a request for accuracy: "I've reviewed my 360 feedback and I'm concerned some of the comments may reflect my disability rather than my work performance. I'd like HR to look at the feedback alongside my documented contributions to make sure the assessment is fair." Whether HR acts on it depends on your company's policies, but raising the concern creates a record.