Audience adaptation
The same facts land differently on a beginner and an expert, an engineer
and an executive, a skeptic and a fan. Writing that ignores its reader is
writing for nobody. Adaptation is deciding, for this reader, what to
include, what to assume, and how to frame it.
Method
- Name the actual reader and their stakes. Who reads this, what do
they already know, what do they need from it, and what do they care
about? A page for new users and a page for integrators are different
documents even about the same feature. "General audience" is usually an
excuse not to decide.
- Calibrate assumed knowledge precisely. Explaining what the reader
knows bores and patronizes; assuming what they do not know loses them.
Pitch to their level: define the terms they will not know, skip the
ones they will, and link deeper for the range in between (see
explain-like-im-five and eli-expert prompts for the two extremes).
- Frame in the reader's terms. Lead with what THIS reader values:
executives want impact and risk (see exec-one-pager), engineers want
how and tradeoffs (see design-doc), users want what it does for them.
The same change is "cut costs 30%" to a CFO and "here is the new API"
to a developer.
- Adjust depth and length to their need and attention. A busy
decision-maker needs the answer up front and the detail available, not
required (see structure-and-flow's priority order). A learner needs the
build-up. Match the format to how the reader will actually consume it.
- Match tone and formality to the relationship and context. Peer,
customer, executive, public: each has a register (see voice-and-tone).
Getting this wrong (too casual with a regulator, too stiff with a
teammate) undercuts the content.
- When one piece must serve several audiences, layer it. A clear
summary up top for everyone, deeper sections for those who need them,
glossary or links for the gaps: so each reader finds their level
without the others' content in the way (see docs-information-architecture).
Boundaries
- Adapting to the reader is not pandering or dumbing down; it is meeting
them where they are so the true content gets through. The facts do not
change, the framing and depth do.
- You cannot serve wildly different audiences in one undifferentiated
piece; if the needs truly diverge, write separate versions or clearly
layered sections (see roadmap-communication's audience views).
- Knowing the audience requires real information about them; when you are
guessing, say what you assumed, and prefer the clearer, more inclusive
choice (see clear-writing).
1---2name: audience-adaptation3description: Adapt what you write, how much, and how you frame it to the specific reader's knowledge, needs, and stakes. Use when the same content must reach different audiences, or when writing is missing its reader.4---56# Audience adaptation78The same facts land differently on a beginner and an expert, an engineer9and an executive, a skeptic and a fan. Writing that ignores its reader is10writing for nobody. Adaptation is deciding, for this reader, what to11include, what to assume, and how to frame it.1213## Method14151. **Name the actual reader and their stakes.** Who reads this, what do16 they already know, what do they need from it, and what do they care17 about? A page for new users and a page for integrators are different18 documents even about the same feature. "General audience" is usually an19 excuse not to decide.202. **Calibrate assumed knowledge precisely.** Explaining what the reader21 knows bores and patronizes; assuming what they do not know loses them.22 Pitch to their level: define the terms they will not know, skip the23 ones they will, and link deeper for the range in between (see24 explain-like-im-five and eli-expert prompts for the two extremes).253. **Frame in the reader's terms.** Lead with what THIS reader values:26 executives want impact and risk (see exec-one-pager), engineers want27 how and tradeoffs (see design-doc), users want what it does for them.28 The same change is "cut costs 30%" to a CFO and "here is the new API"29 to a developer.304. **Adjust depth and length to their need and attention.** A busy31 decision-maker needs the answer up front and the detail available, not32 required (see structure-and-flow's priority order). A learner needs the33 build-up. Match the format to how the reader will actually consume it.345. **Match tone and formality to the relationship and context.** Peer,35 customer, executive, public: each has a register (see voice-and-tone).36 Getting this wrong (too casual with a regulator, too stiff with a37 teammate) undercuts the content.386. **When one piece must serve several audiences, layer it.** A clear39 summary up top for everyone, deeper sections for those who need them,40 glossary or links for the gaps: so each reader finds their level41 without the others' content in the way (see docs-information-architecture).4243## Boundaries4445- Adapting to the reader is not pandering or dumbing down; it is meeting46 them where they are so the true content gets through. The facts do not47 change, the framing and depth do.48- You cannot serve wildly different audiences in one undifferentiated49 piece; if the needs truly diverge, write separate versions or clearly50 layered sections (see roadmap-communication's audience views).51- Knowing the audience requires real information about them; when you are52 guessing, say what you assumed, and prefer the clearer, more inclusive53 choice (see clear-writing).
Amey-Thakur