Start With the Audience
Beat the curse of knowledge — write for their head, not yours.
- ✓Name your reader and what they already know before you write
- ✓Translate jargon into consequences the audience cares about
- ✓Lead with their stake — what's in it for them
Before any technique, ask: who is reading this, and what do they already know? The single most reliable way to be misunderstood is to write from inside your own head — assuming the reader shares your context. Great communicators start from the audience and work backward to the message.
The curse of knowledge
Once you know something, you can't un-know it — so you systematically overestimate what your reader shares and skip the context they need. This is one of the most robust findings in communication research: it persists even when people are explicitly warned about it or paid to avoid it. 'Just simplify' doesn't fix it. What works is concrete: name your audience, ask what they already know and what they need, and build the missing bridge before the detail.
Answer 'what's in it for them?'
Readers filter everything through their own stake. Frame your message around what the audience cares about — their goals, risks, decisions — not what's interesting to you. The same fact lands differently for a CFO (cost and risk), an engineer (effort and dependencies), and a customer (impact on them). Lead with the version that matches the reader.
Calibrate altitude to the reader
Same facts, different altitude. A board wants the decision and the one number that matters; a peer may need the mechanism. More senior and more time-pressed almost always means higher-level and shorter. Don't flatten everyone to one register — pick the altitude for your actual reader.
Write to one primary audience
Trying to address everyone at once produces a message that lands with no one. When a note has several readers, choose the primary decision-maker, write for them, and let others read over their shoulder. One message, one audience.
The curse of knowledge is robust and cross-cultural — it doesn't go away when people are warned or even paid to overcome it, so audience-translation has to be a deliberate step, not an afterthought. MIT Sloan's management-communication courses open with exactly this: a 'strategy checklist' that fixes audience, purpose, and message before a word is written.
Before & after
The migration to the new event-sourced architecture hit a race condition in the Kafka consumer group rebalancing, so we added idempotency keys and replayed the dead-letter queue, which is why we slipped.
We're a week late because a data-pipeline bug corrupted some records; we've fixed it and recovered the data, with no customer impact. Full timeline below.
We should adopt the new tool because it has better observability and a cleaner API.
To the CFO: 'This tool cuts our incident downtime ~30%, which is ~$120k/year in avoided losses, for $40k.' To the team: 'It kills the 2am pager pain — alerts that actually tell you what broke.'
Practice
Write a response, then get coached. Revise and re-score as many times as you like — iteration is the point.