Rules
Part of Internal communications: a planning framework
Internal communications improvement: a six-stage cycle and a month-long pilot
how to improve internal communications starts with workflow evidence, audience segments, channel jobs, manager support, employee feedback, and outcome measures.
An internal communications repair begins with a decision employees need to make, not with a new channel or a larger volume of messages. Follow that decision through the information people receive, the action they take, and the route they have for questions. Then use the branches below to choose whether to investigate, repair, test, or measure.
If you cannot name the employee decision, observe before changing anything
Choose one recurring employee decision and observe how people get the information they need to act. Record where the route slows or fails, including late information, missed messages, confusing language, access problems, and responses that go nowhere.
Compare what happens for employees in different circumstances, such as new hires, shift employees, remote managers, and people using assistive technology. Note searches, permission errors, duplicate instructions, missing owners, and repeated questions. These observations can sharpen corporate communications questions about audience, approvals, and responsibility.
| Stage | Decision to make | Evidence to retain |
|---|---|---|
| Choose | Which employee decision and action matter? | Error, delay, service, safety, or support data |
| Observe | How do employees encounter the information? | Searches, questions, interviews, tickets, and task results |
| Diagnose | Where do ownership, access, meaning, or workflow fail? | Failures by employee group |
| Design | What source, message, channel, manager, and feedback route are needed? | Prototype and decision record |
| Test | Does the proposed route work in routine and failure conditions? | Access, understanding, action, and exception results |
| Learn | What should change next? | Owner, date, result, and review point |
Six-Stage Improvement Cycle
- Choosedecision, audience action, consequence
- Observefollow current employee journey
- Diagnoseownership, access, meaning, workflow failures
- Designsource, message, channel, manager, feedback
- Testroutine and failure scenarios
- Learncompare baseline, assign changes
After observation, separate a process gap from a writing problem before proposing a remedy. A communications strategy checklist can help frame that distinction. Use the six stages as a repeatable path: choose, observe, diagnose, design, test, and learn, rather than treating a single message as the whole system.
- Rule of thumb: Follow one employee task until you can point to the exact place where progress stops.
If instructions conflict, establish ownership and the current source
When employees find competing instructions or cannot tell what is current, settle responsibility for the information before rewriting it. Identify who owns the underlying fact, who can approve a change, and how an employee can recognize the current version.
Create one current source page, state the required employee action directly, and retire stale or conflicting messages. Brief managers on what they can say, what remains uncertain, and where to escalate questions. Label corrections and share feedback themes with the owner response. For language likely to face close scrutiny, use hostile-read writing as a separate check.
- Rule of thumb: If the current source or accountable owner is unclear, repair that handoff before sending reminders.
If some employees cannot receive or answer, test access and listening routes
When a message reaches some employees but not others, check whether the channel works for frontline, remote, and accessibility needs. Offer a usable way to receive the information and a practical route to ask questions or report a problem.
The UK Health and Safety Executive communication guidance can prompt a check on relying too heavily on one method and on whether listening routes exist. Compare the channel with WCAG guidance when employees need accessible digital content, and review communication formats before deciding how to present the information and response options.
Do not treat low readership as proof that employees are indifferent. Check relevance, timing, accessibility, findability, and whether people can use the device through which the information arrives. Repeated questions can also mean that a message repeats an earlier decision without making the next action clearer.
- Rule of thumb: Keep a channel only if the intended employees can receive the message, understand the action, and respond.
If one repair can be isolated, run a month-long pilot
Choose one message type and two affected employee groups so the proposed change can be compared with a clear starting point. Before launch, record access, understanding, action, repeated questions, manager effort, and errors; during the pilot, review results weekly against that baseline.
The related four-week corporate communications cycle addresses a wider organizational process; keep this test tied to one observed employee communication failure. At the end of the month, retain the change only if it reduces that documented problem without creating a privacy, access, workload, or records failure.
A case-study comparison can help identify what a test should preserve, while messaging practices offer a further perspective on clarity. Separate early operational signals from claims about trust, behavior, retention, or business outcomes, which need longer observation and careful attribution.
| Pilot point | What to decide |
|---|---|
| Before launch | Record the baseline across the six measures |
| Each week | Review the new source, channel, manager briefing, and feedback route |
| At the end | Keep the change only if the documented issue improves without a listed failure |
- Rule of thumb: Test a small change against recorded evidence, not against the appeal of a new approach.
If the proposed fix requires a tool, verify the capability gap first
Before considering a platform, determine whether the observed failure comes from a missing capability or from unclear ownership and workflow. A purchase is worth assessing only when the audit identifies a capability gap and a controlled trial shows that the proposed fit addresses it.
Check who controls the source, who can change permissions, how records are handled, and whether the proposed workflow has a named owner. Consider security, data control, and ownership costs as part of the decision, rather than treating the tool as a substitute for a working handoff.
- Rule of thumb: Do not buy until a documented capability gap survives a controlled trial and the relevant controls have been reviewed.
If the results are mixed, decide what the evidence can support
When a pilot produces uneven results, return to the observed failure instead of automatically adding more content. Check whether employees found the source, understood the action, completed it, and had a usable response route; then record an owner, a review date, the result, and the next question.
A short test can show whether access and question handling changed, but it cannot by itself establish longer-term trust or business impact. For the next review, keep these reference labels available where they fit the issue: Writing for GOV.UK, public-sector accessibility requirements, National Archives records management, ICO accountability framework, government data quality framework, NCSC supply-chain security, Federal Employee Viewpoint Survey reports, and WCAG guidance.
- Rule of thumb: Treat short-term measures as evidence about access and handling, not proof of lasting impact.
