Choose for access, timing, and action
First select the channel that reaches the people who need the update and makes their next action clear. Add a second channel only when it provides something the primary one cannot—for example, a discussion opportunity or a durable reference.
For a message that needs acknowledgement, use an appropriate must-read or acknowledgement feature if it is configured; do not assume every post is acknowledged.
Compare the channel's job
Fictional Northstar examples; confirm actual access and channel behavior before applying them.
| Details | Best suited for | Watch for |
|---|---|---|
| Team briefing | Discuss a change with a team and answer questions | Employees on different shifts may miss the same session |
| Staff digest | Summarize several updates for readers who use the digest | A digest item may be missed or buried among other news |
| Shared reference space | Keep detailed steps available when people need them | Readers need to know where to find it and which version is current |
| Targeted manager message | Give a specific team a relevant action or local context | Important details can vary unless the source message is clear |
Worked example: revised device requests
For a planned process change, pair a timely explanation with a dependable place to check the steps.
Primary: team briefing
The service team briefs affected employees before the revised request steps take effect. The manager explains what changed and invites questions.
- Name the affected request types.
- State when the new steps begin.
- Ask employees to use the revised steps for new requests.
Supporting: shared reference
The service team keeps the full instructions in a shared reference space. The briefing points readers there for the complete steps.
- Include the same effective date as the briefing.
- Label the current version clearly.
- Give readers a route to report a confusing step.
Common channel decisions
When should a message be repeated?
Repeat or adapt it when the intended audience is unlikely to encounter the primary channel at the same time, or when a second route helps people act. Keep the core action and effective date consistent.
When does an update need a permanent reference?
Use a durable reference when readers may need to return to detailed steps, definitions, or current process information after the announcement or briefing.
Should every update go into every channel?
No. Use the smallest channel combination that reaches the intended audience, supports the action, and makes details findable when needed.