When you deliver a hard verdict in materials review, the reaction splits two ways: an accepting smile, or open resentment. Same words, same order — so why does only the reception differ? This essay looks at that dividing line through the lens of defense mechanisms and procedural justice, in the plain language of the review room.
01Two Exits — the Same Rejection Leaves Two Different Faces
Ten in the morning: I sent back the first piece of the day. It was an explanatory brochure for a new drug, and a caption on the efficacy graph invited readers to see more than the approved indication allowed. I explained the reason to the person in charge and pointed out a direction for the fix. She took notes, nodded twice, said "I'm glad we caught this early," and left the room smiling.
Three in the afternoon: the second piece. Different person, different product. But the reason for the rejection was almost identical — the way the data was presented stepped one foot outside the approved indication. I used nearly the same words as in the morning. Same tone, same order. He never met my eyes. He said only "understood," and the door closed quietly, but unmistakably hard.
That night, on the train home, I set the two exits side by side. The content I delivered was the same. The weight of the finding was the same. Even my level of fatigue could not have differed much. And yet inside one person the rejection became "help," and inside the other it became something else — something close, I suspect, to "rejection of me."
In materials review (= the job of checking whether a drug's advertising and explanatory materials are appropriate under regulation and science), I run into this mismatch several times a week: the same finding, received in entirely different ways. For years I thought only about how to deliver it — choosing words, arranging the order, attaching evidence. But that day the question turned around. After the same words arrived, what was happening inside each of those two minds? The difference was not in me; it was in what happened at the destination. The second half of a rejection — the part that unfolds inside the recipient — is something I may have gone through this whole career barely knowing.
02The Mind Protects Itself: Denial, Rationalization, and Projection as Unconscious Shields
The man who left without meeting my eyes came back to me by way of rumor. At a sales meeting, I was told, he had said "our review is too strict" and "other companies get the same wording through." I felt no anger. What I felt was recognition. I have heard those exact phrases come out of my own mouth.
Psychology has the idea of defense mechanisms (= the patterned reactions a mind takes, unconsciously, to protect itself when it is about to be hurt). Freud named the idea, his daughter Anna Freud organized it into types, and later the Harvard psychiatrist George Vaillant developed it further, showing a hierarchy "from immature to mature." Leading a decades-long study of adult lives, he demonstrated that defenses are not symptoms of illness but everyday equipment built into everyone's mind. What was running inside that man after the rejection was, most likely, this equipment. Let me name just three of the classic types.
Denial
Treating an inconvenient fact as if it never happened (= pretending not to see the finding itself). It shows up as shrinking the finding: "that caption is nowhere near a real problem."
Rationalization
Supplying a plausible-sounding reason after the fact, in place of the real one (= the sour-grapes move). "Other companies get it through" works as a way to swap a question about the material's validity for a question about the review standard.
Projection
Seeing an unacceptable feeling of your own as belonging to the other person (= feeling "they are being aggressive" when the aggression is yours). The story that "the reviewers want to crush the field" is often born here.
A confession: I know these from the inside. Before I moved to the review side, when a senior colleague sent back a document I had written, the first thing I did was not to fix it. "That person doesn't know the field." "It got through under the last reviewer." By that same evening I had stocked up three such arguments — rationalizations, I can see now. I only got down to fixing the document the next morning, once my inventory of excuses ran out. So I have no standing to dismiss his remarks as "dishonest." That was not dishonesty; it was defense. The same equipment ran in the same order inside me and inside him.
One caution, though. Because defense mechanisms are held to be unconscious, you cannot — and must not — pronounce from the outside, "what you're doing is rationalization." Diagnosing in someone else what even they cannot see is itself a way of cornering them. The concept is useful not for classifying people, but for imagining that behind that hard-shut door, a mind may be in the middle of protecting itself. Push one more dose of correctness into a mind mid-defense and it will not go in. What the afternoon visitor lacked, I now think, was not more explanation, but enough time to lower the shield.
03Which of Us Is Irritated? Projection Happens on the Sender's Side Too
On a Friday evening with a deadline bearing down, I once wrote the same finding for the third time. An expression that went beyond the approved dosage range. The first time, I attached the reasoning carefully. The second time it got a little shorter. The third time, my fingers sped up on the keyboard and the preamble vanished from the text. A few days later, reading the reply from the person in charge, I felt: this person is pushing back. The lines between the lines looked bristly.
But when I reread the email later, calmly, it was simply confirming facts. The bristle was not in the text; it was in me, the reader. Projection, as the previous section described, is the mind's habit of seeing a feeling you refuse to acknowledge in yourself as something the other person holds. And this is not only a story about the person being rejected. Exactly the same machinery runs in me, the one delivering the verdict.
In hindsight it was obvious. That day I was chased by a deadline, carrying the hollowness of repeating the same explanation, and holding an anxiety: "will a third finding damage the relationship?" Carrying that anxiety as my own was heavy. So the mind took a shortcut: "I am not anxious — he is angry." My inner irritation got pasted onto his face. Fold the defense mechanisms of the last section back toward my side of the table, like a mirror, and this is the picture you get.
The troublesome part is that projection needs no evidence. The wording of an email, the gap before a reply, a silence in a meeting — all of these are nearly blank, and the blanker something is, the more easily my own state of mind shows up reflected in it. So now, the moment I feel "this person is pushing back," I ask myself one question. Right now — who is tired, who is irritated, who is anxious: them, or me? Before deciding the feeling belongs to the other person, I count my own sleep, my deadlines, and the number of emails I wrote that day. Any "pushback" that disappears under that count was never theirs to begin with.
Of course, sometimes the other person really is unhappy. The self-check is not there to explain that away. It is only a matter of order: wipe off the reflection first, then look at the person. Calling the other person's face cloudy without taking off your own fogged glasses does not deserve the name of review.
04Process over Outcome: A Voice and a Reason Are What Hold People Up
Last week, someone left my room smiling. The conclusion was a rejection (= a ruling that the wording cannot pass as written) — and not on one small point, but on a phrase at the core of the pamphlet. Why was she smiling? Replaying the meeting, I had done nothing special. Only the order was slightly different from usual.
First, before showing any red ink, I asked: "With this wording, what did you want the doctors to take away?" She spent a few minutes explaining the intent. Next, I explained the reason for the ruling concretely, matched against the specific clause it touched (which item of the preparation guideline applied). Not "because it's not allowed," but "because this part falls under this item." Last, we walked through, together, a path by which a revision would pass — down to a phrasing that stays inside the approved range. The outcome was the same rejection, but her voice was inside the process.
This is not my achievement; it lines up with nearly half a century of research. The field is procedural justice (= the question of whether the procedure leading to an outcome is fair, apart from the outcome itself). Thibaut and Walker (social psychologists of the 1970s who studied courtroom procedure experimentally) identified voice (= being heard before the decision is made) as a factor governing whether people accept a judgment. People who feel their side was heard accept even unfavorable outcomes more readily. Lind and Tyler (researchers who carried the field forward) went further, arguing that people care about procedural fairness for more than cost-benefit reasons. Being treated fairly is a signal: "you are respected as a member of this group." A careful process therefore holds a person up in a place separate from the pain of the outcome.
Ask first
Ask about intent before showing the red ink. Voice loses most of its effect if it comes after the decision.
Light up the reason
Tie the ruling to the specific clause it rests on. Leave no residue of "because I think so."
Show a path
Confirm together what a passing revision looks like. Make the rejection a waypoint, not a dead end.
To be clear, this is not a magic claim that a fair process sends everyone home smiling. The research effects come with limits, and a painful outcome stays painful. Still, there are many moments when a reviewer cannot change the outcome. Wording that violates the rules cannot pass, however sympathetically it is heard. For those of us who cannot move the outcome, what remains is the process. And the process is the one place we can still shape at our own discretion, even on a deadline-crushed day. Her smile was not happiness about the rejection. She was heard, given reasons, and shown the next step. That process stayed with her as evidence that she had been handled with conscience.
05Why the Same Rejection Gets Read Two Ways
When I was young, I once sent a rejection notice that said only "this wording is not acceptable." No supporting clause, no path to a fix. What came back the next day was not a revision but a long email of rebuttal, arguing line by line how unjust my finding was. Reading it, I could see he did not misunderstand the regulations — he knew them well. He pushed back anyway. What was happening inside him then, I can now partly explain.
The psychologist Richard Lazarus, a leading figure in stress research, held that emotion is determined not by the event itself but by how the event is sized up. He called this sizing-up cognitive appraisal — the appraisal that runs, unconsciously, in the instant an event arrives. The same rejection can be read as "a threat to my standing" or as "homework I can finish by fixing it," and the emotions that rise from each reading are entirely different. Read it as threat and defense begins; read it as task and coping begins. The inconvenient part: this appraisal finishes within seconds of opening the notice, before the person is even aware of it.
One more name: Jack Brehm (= an American social psychologist). His psychological reactance (= the mind's impulse, the moment it feels a freedom has been taken away, to push back and reclaim that freedom) explains that rebuttal email well. A flat "not acceptable" takes away, from above, the other person's freedom to choose their wording. And then, before examining the substance of the finding, the person comes to reclaim the stolen freedom itself. He rebutted not because my finding was wrong, but because my phrasing had stripped him of any room to choose.
| How the recipient reads it | The appraisal in the head | Likely reaction |
|---|---|---|
| Read as threat | "My reputation drops," "my position is at risk" | Defense, rebuttal, distrust of the person who flagged it |
| Read as task | "Fix it and it's done," "I can choose how to fix it" | Drafting revisions, asking questions, learning for next time |
Lay these two theories over one scene and what I can do with the wording of a rejection comes into view. Show the grounds — that tips the appraisal from "threat" toward "task." And leave room to choose the fix. If I can write "either of these two versions would pass," the person's freedom has not been taken. The correctness of a finding and the way it lands are two different things. Send a correct rejection with the face of a threat, and what comes back is not a revision but a defense. That long rebuttal email was, in effect, a legitimate invoice for my choice of words.
06What Travels Outside the Words: Faces, Voices, and the Brain's Alarm
I once delivered the same written finding to two authors in person, on separate occasions. To one, in the gap between meetings, rushed and fast. To the other, walking over to their desk, laying the materials out side by side. The text was identical word for word, yet the first heard "I got scolded" and the second heard "I got taught." When it reached me secondhand, a chill ran down my back. What had traveled, it seems, was not my words but the hardness of my voice and the direction of my eyes.
Here people often cite the claim that "words carry only 7%." That is a misuse. The original experiments by Albert Mehrabian (= an American psychologist) were narrow: they examined how feelings and liking are judged when words and manner contradict each other — saying "I like it" with a sour face. They were never a claim that in conversation generally only 7% of verbal content gets through. And yet, correct the misuse and a fact still remains: in conveying emotion, nonverbal cues — facial expression, tone of voice, posture — carry great weight. Especially when words and manner disagree, people tend to believe the manner. Say "it's fine" in a hard voice, and what arrives is "it is not fine."
Seen from the brain's side, there is thought to be a reason for this ordering. The amygdala (= a structure deep in the brain that detects danger and sounds the alarm) is held to pick up a grim face or a sharpened voice faster than the meaning of words can be parsed. Weighing arguments, meanwhile, is the work of the prefrontal cortex, the region behind the forehead — and when the alarm rings first, the prefrontal cortex is said to have trouble running at full capacity. None of this can be stated as settled; the brain is still a field with few certainties. But it fits the feel of the review room. Read a clause aloud to someone whose alarm is ringing and it will not get through. Stopping the alarm comes first.
So the more urgent the rejection, the more time I now spend on the staging of the delivery. Drop the voice one register. Before the finding, say one thing the material did well. Talk while looking at the document, not at the person's face. Call it a surface trick if you like. But whether or not an alarm rings in the recipient's brain is the dividing line between a finding that lands and one that does not. Tending to what lies outside the words is, I think, as much a part of the review job as polishing the words themselves.
07The Strictness Cannot Change; the Way We Protect People Can
The following Tuesday, I was again sitting on the delivering side of a rejection. The case was about as difficult as the previous week's: the cited range of the supporting data (the evidence) did not match the claim in the advertisement, and it could not pass as written. The conclusion was fixed. Precisely because it was fixed, that morning I decided to change one step in how I delivered it. Before stating the conclusion, ask. "With this wording, what did you most want to get across?"
The person looked a little startled, then began to talk: a question an actual physician had asked, and the single-minded wish to answer it that had put this sentence in. Listening, I found the material's aim itself was legitimate. The problem was not the aim but the way the bridge was built between evidence and claim. So that is what I said. "I understand what you want to do. But with this data, you cannot say it this way. Here is the reason. Instead, this construction protects the same aim." What procedural justice research has shown again and again is that people can accept even an unfavorable conclusion when the process is fair. Ask first, tie the reason to the rules, walk the path to a passing revision together — this week I simply traced, one by one, the three steps from section 04 across the desk.
I remember that person's exit well. The shoulders were not slumped. At the door, they turned and said, "I'll bring the revision next week." Plainly different from last week's back, hunched over the papers on the way out in silence. The strictness of the judgment did not move a millimeter. A rejection is a rejection. What changed was the order, the reason, and the path — the process, nothing more. The defense mechanisms of section 02 stand up the instant a person feels attacked. Put the other way around: hand over the verdict with the separation made explicit — "I understand your intent; what I am rejecting is one point of expression" — and there is less to defend, so the guard can stay thin. In the language of cognitive appraisal, the same event called "rejection" was appraised last week as "a repudiation of my work" and this week as "a task we fix together." That, and nothing else, divided the two exits.
In an earlier installment I wrote that a claim has a direction. A rejection has a direction too. Do you aim it at the person's character, or at one point in the material? Review looks like the application of rules, but in practice it is the work of choosing this direction anew, every single time. Loosening the strictness would mean loosening the quality of the information that reaches patients, so that cannot be done. But how the other person's heart is handled at the moment a hard conclusion is handed over — that lies in the hands of the one handing it. The rules make the judgment. My conscience decides how to protect the person. Sliding the red-inked rejection into its envelope, I thought: next week, too, I will start with one question before the conclusion.
- The same rejection splits reactions depending on whether the recipient reads it as a "threat" or a "task." This sizing-up (cognitive appraisal) is over within seconds of opening the notice; showing the grounds and leaving room to choose the fix tips the reading toward "task."
- Even when the outcome cannot change, the process can. Ask about intent first, tie the reason to the specific rule, and walk the path to a passing revision together. Procedural justice research has shown that a fair process supports acceptance of unfavorable conclusions.
- When you feel "this person is pushing back," suspect your own projection first. Irritation and anxiety reflect easily onto the other person's face. Wiping your fogged glasses before looking at them is the minimum courtesy of the delivering side.
- Anna Freud. The Ego and the Mechanisms of Defence. Hogarth Press, 1937. (The classic that organized defense mechanisms into a system)
- George E. Vaillant. Adaptation to Life. Harvard University Press, 1977. (Long-term follow-up study showing a hierarchy of defense maturity)
- John Thibaut, Laurens Walker. Procedural Justice: A Psychological Analysis. Erlbaum, 1975. (The original work showing that voice governs acceptance)
- E. Allan Lind, Tom R. Tyler. The Social Psychology of Procedural Justice. Plenum, 1988. (A relational model of how fair process builds trust)
- Richard S. Lazarus, Susan Folkman. Stress, Appraisal, and Coping. Springer, 1984. (The theory that appraisal as threat or challenge divides the emotional response)
- Jack W. Brehm. A Theory of Psychological Reactance. Academic Press, 1966. (The original theory that a sense of lost freedom breeds pushback)
- Albert Mehrabian. Silent Messages. Wadsworth, 1971. (The original nonverbal research; cited here to confirm its limited conditions)
- Joseph LeDoux. The Emotional Brain. Simon & Schuster, 1996. (The workings of the amygdala's threat response)
- Daniel Kahneman. Thinking, Fast and Slow. Farrar, Straus and Giroux, 2011. (A general-reader account of intuitive appraisal versus deliberation)