Your manager spent forty minutes telling you you're good at your job. You can probably remember about ninety seconds of it. That's the part that started with one thing I'd like to see more of. You remember the exact wording. You remember where they looked when they said it. That night, while you brush your teeth, you argue with it, and you're still arguing on the drive in the next morning. The compliments were real and they were specific. Already they've gone soft and hard to recall, like a dream you had last week.

This isn't oversensitivity, and it isn't a flaw in you. It's one of the most reliable findings in psychology, and once you see how it works you can stop letting it decide what your review meant.

Bad is stronger than good

In 2001, the psychologists Roy Baumeister, Ellen Bratslavsky, Catrin Finkenauer, and Kathleen Vohs published a review paper with a blunt title: Bad Is Stronger Than Good. They looked at research on relationships, learning, memory, health, and how people form impressions of each other. The pattern was the same almost everywhere. Negative events, feedback, and information carry more psychological weight than positive ones of the same size. We process them more thoroughly and remember them longer, and they shape our behavior more.

The same year, Paul Rozin and Edward Royzman described a related pattern they called negativity dominance. When good and bad are mixed together, the overall impression tends to tilt toward the bad more than simple arithmetic would predict. A single cockroach ruins a bowl of cherries. A single cherry does nothing for a bowl of cockroaches.

The usual explanation is evolutionary, and it makes sense. For most of human history, missing a threat cost far more than missing an opportunity. A mind that pays extra attention to danger survives longer than one that treats a snake and a strawberry as equally interesting. Your brain still runs on that tuning. In a performance review, the snake is a sentence about your presentation skills.

So when the criticism takes over your memory of the meeting, your brain is doing what it was built to do. The trouble is that it's overweighting the evidence, and you're about to make decisions based on the distorted version.

Why reviews hit harder than other feedback

A review is one of the most charged meetings in working life. It's formal and it goes on the record. It's often tied to money, promotion, or the quiet question of whether you're safe here. And it's about you, not a project or a deck or a bug, which is the part that matters most.

In Thanks for the Feedback, Douglas Stone and Sheila Heen of the Harvard Negotiation Project describe three kinds of trigger that block us from hearing feedback. Truth triggers fire when the feedback seems wrong. Relationship triggers fire because of who's giving it: you're one to talk. Identity triggers fire when the feedback shakes your story about who you are. That last kind is the one that keeps you up at night.

If you've always thought of yourself as the reliable one, being told you missed deadlines doesn't register as information about deadlines. It reads as a challenge to your character. And the negativity bias doesn't flag that sentence with useful note. It flags it with threat to self, and that label sticks.

Research on feedback suggests this gets in the way of improving. In a large 1996 meta-analysis, Avraham Kluger and Angelo DeNisi found that feedback interventions improved performance on average. But in more than a third of cases, feedback actually made performance worse. One of their central explanations was where the feedback sent the recipient's attention. When feedback kept people focused on the task, they tended to improve. When it pulled their attention toward themselves, toward what does this say about me, performance often fell.

That explains the 2 a.m. replay. You aren't working on the problem. You're defending your identity, and in that state it's hard to learn anything.

The two mistakes this sets up

Negativity bias usually pushes people into one of two responses, and both are understandable.

The first is collapse. The criticism becomes the whole review. You leave convinced you're failing, quietly start browsing job listings, or overcorrect so hard that you neglect what you were actually praised for. The praise didn't stop being true. It just stopped feeling true.

The second is rejection. The sting is so sharp that the fastest relief is deciding the feedback is wrong. They don't see what I do. They're thinking of one bad week. Sometimes that's accurate, since feedback can be unfair, badly informed, or political. But when you reject it on reflex, you can't tell the unfair part from the useful part. You throw out the whole thing to stop the pain.

Both responses treat the criticism as a verdict. Most of the time it's closer to a data point: one person's view of one slice of your work, filtered through their own priorities and blind spots. It deserves serious attention. It doesn't deserve the final word.

Restoring the real ratio

You can't turn negativity bias off. You can correct for it the way a pilot corrects for crosswind, by knowing it's there and adjusting on purpose.

The first adjustment is about memory. The positive parts of your review are fading faster than the negative ones, so you need to capture them before they go. Your notes aren't trying to argue the criticism away. They're there so you remember the conversation accurately.

The second is about attention. Kluger and DeNisi's work suggests the useful move is to drag the feedback back toward the task: away from what kind of person am I and toward what specifically would be different. Vague criticism keeps the focus on you. Specific criticism gives you something to do.

The third is about timing. In the hours after a hard review you're in threat mode. That's the worst time to write a defensive email, change your whole approach, or decide what the feedback means. Let your nervous system settle before your thinking takes over.

Stone and Heen suggest a useful question for any feedback that stings: before asking what's wrong with this, ask what might be right about it. You don't have to concede the whole point. You're only looking for whatever piece is worth keeping.

Your next moves

  • Within an hour of the review, write down every positive thing that was said, word for word if you can. Do this before you write anything about the criticism. You're preserving the part your brain is busy deleting.
  • Rewrite the criticism as a sentence about a task, not about you. Turn I'm bad at communicating into my weekly updates to the client don't flag risks early enough. If you can't make it that specific, you've found your next question.
  • Send one clarifying question, but wait until tomorrow. Something like: I've been thinking about what you said on X. What would doing that well look like over the next quarter? It's curious, not defensive, and it brings the conversation back to the task.
  • Separate the three triggers on paper. Write one line each: what I think is wrong with the feedback, how I feel about who said it, and what it threatens about how I see myself. Seeing them apart usually shrinks all three.
  • Name one thing that's right about it, even if it's small. Then choose one concrete behavior to try for the next two weeks. One experiment will teach you more than a month of rumination.

The meeting you actually had

The hardest part of a hard review isn't hearing the criticism. It's the version of the meeting you carry around afterward, which keeps getting darker as the compliments fade and the one sentence grows. Most of what you can do comes down to getting a clear, honest record down before your brain rewrites it. That's the idea behind MeetingMortem: a quiet place to write down what was actually said, separate the signal from the sting, and decide what you'll do next while the meeting is still fresh. If your last review is still replaying in your head, it might help you see it more clearly.