How to disagree with your boss in an email

Disagreement reads as undermining when the email looks like it's auditing the boss. It reads as engagement when the email looks like it's defending a shared outcome.

Four moves: lead with the shared goal → raise the concern as a question → cite specific precedent → close with the shared outcome.

Amy Edmondson's psychological safety research at HBS shows why this is hard: hierarchical disagreement reads as personal risk by default, even when no one intends it that way. The four moves above are the structural antidote.

For the step-by-step procedure, see How to disagree with your boss in an email.

Then ask permission to give it. "I'm noticing something I think is worth flagging — would it be useful if I sent a quick note?" That sentence does two things: it surfaces the concern's existence (so they know you're not coasting) and hands them control over the timing of the deeper conversation.

The version of this that fails is the unsolicited critique: a long email about a plan they didn't ask you to evaluate. Even when every point is correct, the format itself reads as overreach. The permission ask reframes you as a contributor, not a self-appointed reviewer.

Then email is the wrong medium for it. Email scales well for content; it's catastrophic for tone, especially when the subject is the other person.

When the disagreement is about them — their pattern of decisions, their treatment of you, their judgment on something repeated — schedule a live conversation. Brief, calendar-blocked, with a clear topic line: "Could we set aside fifteen minutes this week? I'd like to talk through how we approach [X]." Email at that point is for arranging the conversation, not having it.

The parent post's When to Stop Writing and Start Talking section covers the broader rule.