You’re writing Nadia’s performance review, and you know the sentence that needs to be in it. She’s technically excellent — probably the strongest debugger on the team — but she’s been mass-declining meeting invites for cross-functional syncs, and the product team has started routing questions through you instead of going to her directly. Two sprints ago, a junior engineer told you in a 1:1 that he’s afraid to ask Nadia questions because her Slack replies make him feel stupid.

You know the sentence. Something like:

“Nadia’s communication with stakeholders and junior team members is creating friction that’s limiting her impact and the team’s effectiveness.”

Here’s what you actually write:

“Nadia has opportunities to further develop her cross-functional collaboration skills.”

You read it back. You know it says nothing. “Opportunities to further develop” is corporate anesthesia — it numbs the message until the patient can’t feel it. Nadia will read that sentence, nod, and change nothing, because the sentence asks her to change nothing. It describes a vague direction for future growth, not a specific problem that’s happening right now.

But you leave it. Because the direct version feels like an attack on someone you respect, and the softened version feels like kindness.

It isn’t kindness. It’s abdication.

Engineering leaders soften feedback through a specific set of moves, and the moves are so habitual they’ve become invisible. Worth naming them.

The upgrade. A problem becomes an “opportunity.” A gap becomes an “area for growth.” A pattern that’s actively harming the team becomes a “development focus.” The language implies the person is already good and could become better, when the actual message is that something needs to stop.

The hedge. “Sometimes” and “occasionally” appear in front of feedback that describes a consistent pattern. “Nadia can sometimes come across as dismissive in cross-team meetings” means “Nadia is dismissive in cross-team meetings, and everyone knows it, and I’m adding ‘sometimes’ so the sentence feels less confrontational.” The hedge doesn’t protect Nadia. It protects you.

The redirect. Instead of naming the impact on other people, you frame the feedback as a missed opportunity for the person themselves. “You’d benefit from building stronger relationships with the product team.” What you mean is that the product team has stopped working with you directly, and I’m spending two hours a week acting as a relay because of it. The redirect makes the feedback sound self-interested on the recipient’s behalf, when the reality is that other people are bearing the cost.

The compliment sandwich. The structure everyone learns in their first management training, and nobody believes it when they’re on the receiving end. By the time you’ve praised Nadia’s debugging skills and mentioned her “growth area” and praised her incident response, the critical feedback has been compressed into a subordinate clause buried in the middle paragraph. The message she receives is: I’m doing well, with a side note about collaboration.

These aren’t failures of courage. They’re failures of craft. The engineering manager in each of these examples has the right diagnosis. They see the problem clearly. What they lack is the practiced ability to convert that diagnosis into words that are simultaneously direct, specific, and humane.

The instinct to soften is not irrational. It comes from a reasonable place: you’ve seen feedback delivered badly. The manager who uses review season to score points. The skip-level who drops a critical assessment without context. The peer who confuses directness with cruelty. You’ve been on the receiving end of feedback that felt like punishment, and you’ve internalized a rule: don’t be that person.

The problem is that the rule against cruelty has expanded, silently, into a rule against clarity. The two are not the same. “Nadia, your Slack responses to junior engineers are creating a dynamic where people are afraid to ask you questions — that’s a problem I need you to address” is not cruel. It’s direct, it’s specific, it names the impact on real people, and it asks for change. Nadia might not enjoy reading it. She shouldn’t have to. The point isn’t comfort — it’s information she can act on.

Compare that to “Nadia has opportunities to develop her mentorship approach further.” What, specifically, is Nadia supposed to do with that sentence? She’s not being told there’s a problem. She’s being told she could hypothetically be better at something, in a way that gives her no information about what’s wrong, who’s affected, or what “better” looks like.

The soft version feels kinder. The direct version is kinder — because it gives Nadia an actual chance to change.

There’s a mechanical reason this is hard: most leadership development is verbal, and verbal communication is structurally forgiving of vagueness.

In a live conversation, you can watch the other person’s face and calibrate in real time. If they flinch, you soften. If they nod, you continue. The feedback becomes a negotiation — you advance as far as the other person’s comfort allows, which is rarely as far as the feedback needs to go. You leave the conversation feeling like you addressed it. You didn’t. You addressed what the other person was comfortable hearing, which is a different thing entirely.

Writing doesn’t let you do this. When you compose “Nadia, your Slack responses to junior engineers are creating a dynamic where people are afraid to ask you questions,” you can’t watch for the flinch and retreat. The sentence is either on the page or it isn’t. You have to decide, before you send it, whether you’re willing to say the thing clearly.

This is uncomfortable. It’s also exactly the practice that builds the skill.

The engineering manager who has written that sentence — who has felt the pull to soften it, has seen the softened version sitting on the screen and recognized it as empty, and has revised until the words were both direct and humane — that manager is going to be better at saying it in person, too. Not because writing is a script for speech. Because the act of composing forces you to resolve the tension between clarity and compassion before the conversation, instead of letting that tension resolve itself through avoidance in the moment.

This is the tension at the center of The Quiet Resignation — one of the scenarios in Prism Signal. An engineer on your team has gone quiet. Performance is fine. Deliverables ship on time. But the energy is gone, the initiative has evaporated, and you have a growing suspicion that she’s already mentally resigned. The scenario doesn’t test whether you can diagnose the problem. Most managers can. It tests whether you can write the email that opens the real conversation — without softening it into something she can nod through.

There’s no suggested response. No template. Just a compose window and the specific weight of choosing words that are honest enough to matter and human enough to land.

Your own words, on the screen, doing the work that leadership actually requires.

Your first scenario is free — no credit card, no commitment. Just the conversation you’ve been putting off, waiting for you to write it.

Try for free