Make it relevant without changing the facts
Adapt context, terminology, and action to the work readers do.
Start with one confirmed version of the facts. Then ask what each audience already knows, what could affect its work, and what action is relevant. Tailor the explanation, not the underlying change. Avoid assumptions about people based on their role or work location.
Same update, three useful angles
Fictional shared facts: service desk hours change to 8:30 a.m.–5:30 p.m. from Monday, 14 September; the usual support request route remains available.
| Details | Audience | Adapted message |
|---|---|---|
| Frontline operations | From Monday, 14 September, the service desk is open 8:30 a.m.–5:30 p.m. Check the new hours when planning work that may need desk support; use the usual support request route outside those hours. | Connect the change to shift planning and the established support route, without assuming every task depends on the desk. |
| People managers | From Monday, 14 September, the service desk is open 8:30 a.m.–5:30 p.m. Please share the confirmed hours with your team if you maintain local reference notes; the usual support request route remains available outside those hours. | Give managers a specific sharing action only where it applies; do not make them responsible for facts they do not own. |
| Office-based teams | The service desk's new hours are 8:30 a.m.–5:30 p.m. from Monday, 14 September. If you need help outside that window, use the usual support request route. | Keep the message concise for readers who need the hours and the next step. |
Check what each group needs
Use these questions before producing audience versions.
What do they already know?
Add only the context needed to understand this update.
- Check whether the date or change has already been announced.
- Define internal terms that may not be familiar to every group.
What part affects their work?
Connect the confirmed change to a real task, not an assumed concern.
- Name the relevant action only for readers who need to take it.
- Keep shared facts consistent across all versions.
How will they find the update?
Make the message accessible in the channel readers use for that task.
- Use a scannable format for a quick notice.
- Keep a stable reference for information readers may need again.
Keep versions consistent and fair
How do I avoid stereotyping an audience?
Base differences on work context and confirmed needs, not assumptions about preferences, ability, or behavior. When unsure, ask a representative subject-matter owner.
Should every group receive a separate message?
No. Use one clear message if the facts and actions are the same. Create audience-specific versions only when the context or next step genuinely differs.
How can I prevent conflicting versions?
Work from one approved set of facts and compare each version for matching dates, changes, and support routes before publishing.