Disagree in Writing — Make the Case Without Making an Enemy
A written disagreement can win the point or start a war. The claim → evidence → alternative structure lets you push back on the record — clearly, respectfully, and without damaging the relationship.

The idea
Disagreeing over email or chat is where careers quietly stall — a blunt reply reads as an attack, a mushy one changes nothing. The fix is a three-part structure: acknowledge the other view, then make your case as claim → evidence → alternative. You start by showing you understood them, state your position plainly, back it with a concrete reason or data point, and offer a specific alternative instead of just objecting. It stays about the idea, not the person — so you can push hard on the point while keeping the relationship intact.
Who is this for?
Faisal Khan
Product Analyst · Lucknow
Faisal thought a planned feature would hurt users, but the last time he pushed back over email it came across as combative.
This time he wrote: "I see why we'd ship this for the deadline (acknowledge). I think it'll raise support tickets (claim) — churn rose 8% last time we did something similar (evidence). Could we ship a smaller version first and test? (alternative)."
His lead replied "Good point — let's test it." Same disagreement, opposite outcome.
"I used to think disagreeing politely meant backing down. It just means arguing the idea, not the person."
What you'll get
Pushback that keeps the relationship
Disagreement framed so it lands as sharp thinking, not an attack.
The claim → evidence → alternative structure
A repeatable format that makes your case clear and hard to dismiss.
One real disagreement, written well
A message you actually need to send, drafted on the record and respectful.
A reputation for reasoned pushback
The person who disagrees well becomes the person leaders trust to be honest.
Watch
Harvard Business Review · ~7 min
Do the challenge
1Acknowledge their view first
Open by showing you understood the other side: "I see why we'd want to ship this for the deadline." This one line lowers defenses and proves you're engaging, not just objecting.
💡 Skipping the acknowledgement is the #1 reason written disagreements blow up. One honest sentence of "I get why…" changes how the whole message is read.
2State your claim plainly
One clear sentence of what you actually think: "I think this will increase support tickets." No hedging, no ten qualifiers — a plain claim is easier to respect than a vague worry.
3Back it with evidence
Add one concrete reason, number, or example: "Churn rose 8% the last time we shipped something similar." Evidence turns your opinion into a case worth weighing.
💡 I need to disagree in writing about: [the decision]. My position: [your claim]. My evidence: [reason/data]. Rewrite my message using: (1) acknowledge their view, (2) my claim, (3) my evidence, (4) a specific alternative. Keep it respectful, confident, and under 120 words. Then tell me one line that might read as an attack, and fix it.
4Offer a specific alternative
End with a concrete path forward, not just an objection: "Could we ship a smaller version first and test?" An alternative gives them something to agree to — that's what turns disagreement into progress.
Your template
DISAGREE IN WRITING — Claim · Evidence · Alternative 1) ACKNOWLEDGE (lower defenses): "I see why we'd [their reasoning] — [genuine point of agreement]." 2) CLAIM (your position, plainly): "That said, I think [your clear claim]." 3) EVIDENCE (one concrete reason/number/example): "[Data point / past example / specific reason]." 4) ALTERNATIVE (a path to say yes to): "Could we [specific alternative] so we [shared goal]?" — RULES: □ Argue the idea, never the person □ One claim, one piece of evidence — don't pile on □ End with an alternative, not just a "no" □ Re-read once: would I be okay receiving this?
Knowledge Check
5 quick questions to make sure the main ideas landed.
Know someone who needs this?
Share the challenge — streaks are more fun together.
Tomorrow
Name the Real Problem — The 5 Whys Before You Fix Anything
Most fixes fail because they treat the symptom, not the cause. The 5 Whys — ask "why" five times — drills past the obvious problem to the real one, so your fix actually holds.



