You've removed the accusation. Added the offer. Ended with openness.
Three patterns. Eight scenarios. You know the grammar.
Now the counterintuitive ones — the moves that feel wrong until you understand why they work.
New here? Start with Part 1 — it covers the three core patterns this post builds on.
The Surgeon's Move | Blame Diffusion
Every writing teacher will tell you: active voice is better. Passive voice is weak.
They're mostly right. But in one specific situation, passive voice is the most powerful tool in the kit.
When a mistake happened and the relationship matters more than assigning blame, passive voice removes the subject entirely — and that removal is the whole point.
Active: "You missed the deadline."
Passive: "The deadline was missed."
Same fact. But the first version puts a person in the dock. The second version describes an event. The mistake is acknowledged. The blame is diffused into the air. And the conversation can now be about what happens next instead of who failed.
Active: "You sent the wrong version to the client."
Passive: "It looks like the wrong version went out to the client — let's figure out how to address it."
Notice the passive version also adds a forward orientation ("let's figure out how to address it"). That's not accidental. Passive voice works best when paired with a forward question.
When is this appropriate? When the mistake is obvious and acknowledged, when the relationship is more important than the lesson, and when you're focused on the fix more than the post-mortem.
The passive voice isn't a coward's move. It's a surgeon's move — precise removal of the element that would cause damage without adding anything useful.
When does it become dishonest? When the passive voice is used to obscure accountability that genuinely needs to be held. "Mistakes were made" as an institutional cover-up is different from "the deadline was missed" in a one-to-one conversation about recovery. One diffuses unnecessary blame. The other erases necessary accountability.
Use it to cool down a conversation. Don't use it to make important problems disappear.
The Trojan "We" | Shared Ownership
Here's a small word that does enormous work.
When someone has made a mistake and you need them to fix it, saying "you need to fix this" puts the entire burden on them as an individual. Even if that's technically true. Even if it is entirely their responsibility.
"We should revisit this" signals something different: I'm in this with you.
Solo: "You need to redo the data model before we can move forward."
Shared: "We should probably revisit the data model before we push further — there's a mismatch with the API shape."
The fix is still theirs. But the framing changed. Now it's a team problem, not a personal failure.
Solo: "Your estimates are consistently off."
Shared: "I think we've been underestimating this type of work as a team — it might be worth building in more buffer when we scope similar tasks."
The second version is actually more accurate, usually. The estimation problem is rarely one person's fault in isolation. The project, the domain, the sprint pressure — all of it contributes. "We" reflects that reality.
"We" is not dishonest. In most team contexts, it's more honest than "you" — because almost nothing in software is one person's problem in isolation.
When does "we" become dishonest avoidance? When one person did something genuinely harmful, and "we" is used to absorb the blame into the group to protect them. That's not solidarity — that's cover. The test: would a clear-eyed observer see "we" as reasonable shared context, or as deliberate fog?
The Confidence Paradox | Hedge Words
"Might", "could", "perhaps", "it seems", "I wonder if" — these are not weakness. They are social lubricant.
Direct communicators — and I was firmly in this camp — hear hedge words and feel frustration. Just say it. Do you think this is a problem or not? But that's not how they work for the recipient.
Hedge words give the other person room to disagree without feeling attacked. They say: this is my read, but I could be missing something, and you're allowed to tell me that.
Direct: "This code is wrong. The race condition will cause data corruption under load."
Hedged: "This might create a race condition under load — worth a second look before this hits production."
The second version does not weaken the concern. If you're right, you're right either way. But the first version positions it as a verdict. The second positions it as an observation. And someone who receives an observation can respond with "actually, here's why it's fine" — whereas someone who receives a verdict has to either submit or fight back.
Direct: "Your analysis is missing the cost implications. This doesn't work."
Hedged: "I wonder if we're fully accounting for the cost implications here — it might change the picture."
The hedge also protects you. If you're wrong — and sometimes you will be — the hedged version lets you be wrong gracefully. I thought this might be an issue — thanks for explaining why it isn't. The direct version leaves you having publicly declared something wrong and needing to retreat.
Hedge words are not the absence of confidence. They're the presence of intellectual humility. And people trust intellectually humble people more than they trust people who are always certain.
One rule: hedge on your interpretation, not on the facts. "The test failed" — no hedge needed, that's a fact. "This might be the cause of the test failure" — that's your interpretation, and hedging is appropriate.
Anchor First | Lead With What's Possible
This one is about psychology more than grammar.
Our brains anchor to the first thing we hear. If the first thing is a no, a can't, a won't — that becomes the frame. Everything after it is heard through that lens.
Anchored on the no: "I can't get this done by Thursday. Too much going on."
Anchored on the yes: "I can get this to you by Friday EOD — does that work, or is Thursday a hard stop?"
The actual timeline is identical. But in the first version, Thursday is a failure. In the second version, Friday is a delivery.
Anchored on the no: "I can't make it to the 3pm call."
Anchored on the yes: "I'm free from 4pm — could we push to then, or is 3pm fixed?"
Anchored on the no: "We can't add that feature to this sprint. Scope is locked."
Anchored on the yes: "We can look at picking this up in the next sprint — want me to add it to the backlog with a note on priority?"
Every version above contains the same information as its direct counterpart. But the psychological landing is completely different.
The first thing you say sets the frame. Set it on what's possible, and even a refusal feels like a path forward.
This takes practice because the natural instinct — especially under pressure — is to lead with the obstacle. "I can't because..." feels honest. And it is honest. But honest framing can still be bad framing.
The Decoder | What They're Actually Saying to You
This is the section I personally needed most.
Learning to reframe what you send is one problem. But for direct communicators, receiving corporate speak is its own challenge. You hear the polished surface. You don't know what's underneath.
Here's the phrase-by-phrase decoder. What people actually mean when they say these things to you.
"Let's take this offline."
Surface: We should continue this conversation privately.
Actually: One of three things. First possibility: this discussion is getting heated and I want to contain it before it damages the room. Second possibility: you've raised something I'm not prepared to answer in front of this group. Third possibility: this is too detailed/irrelevant for this meeting and I want to protect the other attendees from it.
How to read which one: if it came after tension, it's de-escalation. If it came after a question you asked, it's deflection. If it came mid-rabbit-hole, it's focus management.
What to do: agree graciously and follow up with a specific slot. Don't let "offline" become "never."
"That's an interesting perspective."
Surface: I find your view compelling.
Actually: I disagree, but I'm not going to fight with you about it right now. Or: I don't know what to do with this but I'm not going to dismiss it openly.
This phrase almost never means genuine agreement. When someone genuinely agrees with you, they say "I agree" or "you're right" or "that makes sense." "Interesting perspective" is what people say when they don't want to endorse something but also don't want conflict.
What to do: note that you haven't actually moved them. If the point matters, find a smaller moment to raise it again with more evidence.
"I just want to make sure we're aligned."
Surface: Let's confirm we're on the same page.
Actually: I think we're not aligned, and I'm concerned about it. This is a diplomatic way of saying: I've noticed a mismatch and I'm flagging it without creating a confrontation.
Sometimes it's also a power move — a way of pulling rank softly. "I just want to make sure we're aligned" from a senior person often means: my view is the standard here, and I want to confirm you're meeting it.
What to do: be direct back. "Happy to check — here's my understanding of where we landed. Does that match yours?" If there's a gap, now it's explicit and can be resolved.
"Can you help me understand your thinking here?"
Surface: I'm curious about your reasoning.
Actually: I think your reasoning has a problem, and I want you to either defend it or realize the problem yourself. This is challenge-by-question. It's Socratic, not curious.
Occasionally it's genuinely curious — when it comes from someone you know well who has no reason to be skeptical. But in most professional settings, especially from seniors, it means: walk me through this because I'm not convinced.
What to do: don't get defensive. Walk through your reasoning clearly, and leave space for the gap they're seeing. "Happy to walk through it — I might be missing something." If they are genuinely trying to poke a hole, you either find the hole and acknowledge it, or you seal it with your reasoning.
"We should loop in [person]."
Surface: This other person's input would be valuable.
Actually: One of three things. First: this decision is above my level and I don't want to own it alone. Second: that person will oppose this, and I want them in the tent rather than outside it. Third: I'm protecting myself — if this goes wrong, I want witnesses to my concern.
Occasionally it's genuinely just adding expertise. But when the suggestion comes quickly, without much explanation, pay attention to who the person is and what their role is. If they're upstream in authority, it's escalation. If they're a known skeptic, it's coalition management.
What to do: before the loop-in happens, clarify what you want from the meeting. "Happy to loop them in — is the goal to get their input, or to get sign-off on the direction we've landed on?" That question forces clarity before the meeting balloons.
"Let's circle back on this."
Surface: We'll return to this topic.
Actually: Not now, and possibly not ever. "Circle back" is professional indefinite postponement. If it comes with a specific time ("let's circle back on this after the sprint review"), it's a genuine deferral. If it comes without one, it's a soft no or a polite way of escaping a conversation they don't want to have.
What to do: if the topic matters, don't leave it as a floating circle-back. Propose the specific time yourself. "Happy to — can we block 20 minutes on Thursday?" If they can't find a slot, you have your answer.
"I have some concerns."
Surface: There are issues I'm unsure about.
Actually: I may be about to block this, or I'm signaling that you need to earn my support before we proceed. "Concerns" is the professional word for objections that haven't been formally lodged yet. It's a warning shot.
Sometimes it's used more casually — a genuine "I'm not 100% comfortable, can we talk about it?" But when it comes from someone with authority over the decision, treat it as a serious signal.
What to do: don't dismiss the concern, and don't be defensive. "I'd really like to understand them — can you tell me more?" You want to pull the concern out into the open where you can actually address it. Concerns that live in someone's head kill decisions quietly. Concerns that get named can be answered.
When to Drop All of This
Corporate speak has a context. Outside that context, it's wrong.
With close teammates who prefer directness. Some of your best colleagues will tell you: "just be straight with me, I can take it." Believe them. Softening everything for someone who wants clarity is condescending. Read the person, not just the protocol.
During production incidents. When the system is down, "I wonder if we might want to consider looking at the database" is not the time. This is the time for: "check the DB — connection pool is maxed out." Urgency demands clarity. Nobody's feelings matter more than getting the thing back up.
When the softening becomes dishonest. If someone's work is genuinely dangerous — buggy code that will cause data loss, a decision that will harm users — there is a point where the hedging does real damage. You can be respectful and still be clear. "I want to flag this seriously: this will cause data loss under [condition] — we can't ship it without addressing this." That's direct. That's not cruel. That's necessary.
When you've tried the soft version and it hasn't worked. If you've asked a question, added an offer, ended with openness — and nothing has moved — at some point directness is the appropriate escalation. Continuing to soften a message that's being ignored isn't professionalism. It's conflict avoidance dressed up as politeness.
The authenticity trap. The worst version of corporate speak is when someone who isn't corporate starts performing it unconvincingly. You can tell when someone is speaking a language they don't believe. The tells: overly formal phrasing in a casual context, hedging that feels rehearsed, warmth that doesn't match their face.
You don't need to sound like a corporate insider. You just need to remove the elements that trigger defensiveness. The rest can sound like you.
How to Actually Practice This
Knowing the pattern is not the same as owning it. The brain that wrote every blunt message you've sent this month will write the same message tomorrow — unless you interrupt the loop deliberately.
Three exercises. Pick one and start this week.
Exercise 1: The Five Message Rewrite. Pick five messages you sent this week. Not the ones you're proud of — the ones you sent quickly, without thinking. Copy each one into a note. Read it as the recipient, not the sender. Ask: what does this land as? Then rewrite it using at least one pattern. Do this for one week.
Exercise 2: Read Before Sending. Before hitting send on any message that contains feedback, a status update, or a conflict — read it once as yourself, then read it as the person receiving it. Ask: what state does this put them in? Is that the state that makes action most likely?
Exercise 3: One Pattern Per Day. Don't try to apply all seven at once. Pick one pattern for the day. Monday: remove the accusation. Tuesday: add an offer. Do only that, on every message, for one week. By Friday you'll have seven patterns in your hands.
The rewrite exercise is the most important one. You cannot see your own blind spots in real time. But you can see them in retrospect — and retrospect is where the pattern gets interrupted.
I want to be honest about something.
I still have days where I fire off a blunt message and only realize it after I hit send. The reframe from "accurate" to "will this be heard" doesn't happen automatically. It's a second step that has to be learned.
But the thing that surprised me most — after learning all these patterns — is that the people who are best at professional communication aren't performing gentleness. They've genuinely internalized that being heard matters more than being right.
That shift is not about being corporate. It's about respecting the other person enough to deliver information in a form they can actually use.
Direct communication, when it comes from that place — respect for the recipient — isn't harsh. It's clean. It's efficient. It cuts through.
The patterns above aren't about making you less direct. They're about making your directness land.
The goal was never to soften the message. It was to make sure the message survives the delivery.
That's the only thing professional communication is doing. Surviving the gap between your intent and their reception.
Which phrase from the decoder surprised you most? For me it was "that's an interesting perspective" — the day I realized that no one who actually agreed with me had ever said that, I started reading a lot of my own conversations very differently.
Top comments (0)