The Neurodivergent Professional's Guide to Performance Reviews

The stated function of a performance review is to assess your performance, set goals for the next cycle, and calibrate compensation. That's the surface. Underneath, a review is doing four things at once, and reading all four layers is what separates professionals who navigate reviews well from those who don't.

One: it compresses a year of pattern-recognition by your manager into a handful of rated dimensions. The dimensions on the form — "communication," "execution," "leadership" — are containers for hundreds of small moments your manager has been tracking, often unconsciously. The compression process is lossy. The rating you receive on any given dimension is not the average of those moments; it's the manager's gestalt impression, anchored by the three or four moments that were most memorable. Knowing which moments those were is the work.

Two: it produces a written record that HR uses for promotion, calibration, and PIP decisions long after the review meeting is over. The document outlives the conversation. The conversation can be warm; the document can be cold; the document is what travels. For neurodivergent professionals who tend to weight the conversation heavily, this asymmetry is worth naming explicitly. A review that felt good in the room can read very differently to a promotion committee six months later.

Three: it signals what your manager wants more or less of in the next cycle. The rating itself is partly a forecasting tool — your manager is communicating their priorities by what they emphasized, what they glossed over, and what they framed as a development area. The signal is often more useful than the rating. A neurodivergent professional who reads the rating literally and the signal not at all can spend the next cycle optimizing the wrong thing.

Four: it gives your manager an opportunity to ask for things they haven't asked for yet. The "development areas" section is partly diagnostic and partly aspirational — your manager is using it to surface a request they didn't quite know how to make in a normal 1:1. Reading "development areas" as a request rather than a critique changes how you respond. Most neurotypical professionals do this automatically. Most neurodivergent professionals don't, because the literal-first reading takes the development area at face value and tries to fix it in the abstract instead of asking what the request behind it actually was.

The annual review is the visible moment, but the actual review rhythm runs all year. The work that determines the review's outcome is mostly done in the months before the meeting, not in the meeting. There are four points in that rhythm where a neurodivergent professional can shift the outcome the most.

1. The ongoing 1:1 evidence trail. Every 1:1 conversation between formal reviews is a chance to either build or fail to build the written record that supports your eventual rating. The mechanic that works is sending a 3-line written follow-up to your manager after every 1:1 — what you discussed, what you committed to, what you'd like to surface for next time. Most professionals don't do this. The ones who do arrive at the formal review with a year of receipts; the ones who don't arrive with their manager's memory, which has compressed the year unevenly. Building the evidence trail is not adversarial. It makes your manager's job easier.

2. The self-evaluation. Your self-evaluation is not just an account of your year — it's the first draft of the narrative your manager will partly inherit. The temptation, especially for neurodivergent professionals who tend toward accurate self-assessment, is to write a balanced and modest self-eval that includes your real growth areas. This loses. Your manager is reading the self-eval to calibrate, not to verify; they will weight your stated growth areas heavily and your stated wins lightly. Write the self-eval as a narrative of contribution, weight wins specifically, and reserve growth areas for the two or three you actually want to spend the next cycle on. The growth areas you list become the goals; choose them on purpose.

3. The meeting itself. The review meeting is the smallest leverage point in the rhythm, but it's the most visible. Two moves matter most: ask for specific examples behind any rating that surprised you (covered in decoding vague communication feedback), and end the meeting with a clear next-step ask — what's the one thing you should do differently in the next 30 days, and what would change in the next review if you did it well. The specific-next-30-days question transforms the review from a retrospective into a forward-looking conversation.

4. The post-meeting written follow-up. Within 24 hours of the review meeting, send a short written summary to your manager: what you heard, what you're going to do about it, what you'd like to revisit in 60 days. This produces three effects. It creates a written record of the meeting's outcomes that doesn't depend on either of you remembering it accurately. It gives you a chance to surface anything you didn't catch in the moment. And it sets up the 60-day check-in that gives you a chance to adjust course before the next formal review compresses everything again.

The four points are not equally weighted. The ongoing 1:1 evidence trail does most of the work; the meeting itself does the least. In 30 years of coaching, Debra Solomon has watched professionals who treat the meeting as the primary lever lose ground to professionals who treat the year-long rhythm as the primary lever — even when the meeting-focused professional is better in the meeting.

Frequently asked questions

Should I disclose during my review if I haven't already?

Usually not. A performance review is one of the higher-pressure moments to disclose, and disclosing in the same conversation as a critical rating puts the disclosure and the rating in the same memory frame for your manager — which is rarely what you want. The disclosure decision deserves its own conversation, its own preparation, and its own context. If the review surfaced an accommodation need, the order that works better is: respond to the review on its own terms first, then schedule a separate conversation for the disclosure piece a week or two later. The framework for the disclosure decision itself is in our disclosure decision framework guide.

What if my manager gives me feedback I think is wrong?

Depends on whether it's factually wrong or subjectively unfair. Factually wrong — your manager attributed a project you didn't work on, missed a major deliverable, or got the scope of a contribution wrong — calls for a same-day written follow-up with specifics. Subjectively unfair — the rating, the framing, the emphasis doesn't match your read of the year — is harder, and the response depends on whether the gap is a one-time read or a pattern. In either case, the move that beats a written rebuttal is asking for the specific examples that produced the rating. Same-day clarification shapes the next conversation more than a written defense does.

How do I push back on a rating without making it adversarial?

Ask for the evidence behind the rating. The question reframes the conversation from your judgment against your manager's to both of you looking at the same evidence. A specific opener that works: "Can you walk me through the two or three moments from this cycle that most shaped this rating?" It surfaces what the manager actually has on the page, gives you a chance to add context to specific moments rather than the whole review, and signals that you're trying to understand rather than defend. Most ratings shift, when they shift, because the manager's evidence turns out to be thinner than the rating implied.

What if I get a surprise negative review?

Surprise is the most important signal — it means the ongoing 1:1 feedback loop wasn't working. The negative content matters less than the fact that you didn't see it coming, because a healthy feedback rhythm should have surfaced the issue before the formal review. The remedy is structural. This week: get specific examples from your manager and start the 30-day evidence trail addressing them. For next cycle: change the 1:1 cadence to include explicit "anything I should be worried about?" questions monthly. Most surprise reviews are the result of a manager who avoids hard feedback in 1:1s — the structural fix is making the 1:1 the place where small things get named before they accumulate into review-sized things.

Are performance reviews different in tech, finance, healthcare, nonprofit?

The format differs significantly — calibration committees in tech, narrative-only in some healthcare systems, 360 reviews in many nonprofits, ranked stack ratings still common in finance — but the four underlying functions of a review (rating compression, written record, signaling, manager-ask) are consistent. The mechanics differ, the dynamics don't. The biggest practical difference is how much the written narrative matters versus the conversation. In stack-ranking environments, the written narrative is everything; in narrative-only environments, the 1:1 conversation that follows the review carries more weight than the document.

What if my company doesn't do formal reviews?

The rhythm is the same — ongoing feedback, periodic narrative, goal-setting — it just happens informally. The risk of informal-only is that the written record HR uses for promotion decisions never gets created. If you don't have a formal review process, create one for yourself. Twice a year, write a one-page narrative of your contributions over the past six months and send it to your manager with an ask for written feedback. The framing matters: "I'd like to make sure we're aligned on how the last six months landed" is workflow-framed and rarely refused. The artifact you produce becomes your own promotion paper trail.