A new system is announced on Monday. By Friday, half the team still uses the old process, managers are giving different answers and customers are receiving conflicting instructions. The announcement happened; the change did not.
Internal communication should help people move from knowing about a decision to working differently. That requires more than a launch email. It requires clear responsibilities, usable instructions and a reliable way to resolve the questions that appear during implementation.
Explain the operational difference
Describe what changes in an ordinary working day. If enquiries will move from personal WhatsApp accounts into a shared system, explain who records them, who assigns them and where colleagues check the status. “Improving collaboration” is too broad to guide behaviour.
State the reason for the change without exaggerating the problem or blaming staff. Explain what has been decided and where feedback can still influence implementation. Asking for opinions after every decision is closed creates frustration rather than participation.
Also say what remains the same. People may assume that a new approval process changes their authority, reporting line or performance expectations. Resolve those uncertainties explicitly.
Brief managers before the general announcement
Managers need more than early access to the email. Give them the rationale, the practical instructions, the timetable and the questions they should expect. Confirm which issues they can resolve and which require escalation.
Ask them to test the instructions against their team's work. A process that suits the head office may create difficulties for field staff, part-time colleagues or teams with unreliable connectivity. These differences should be discovered before launch day.
Do not leave managers to invent reassuring answers. It is more credible to acknowledge an unresolved detail and promise a dated update than to make a commitment the organisation cannot keep.
Build a short communication sequence
Use separate messages for separate jobs. The initial announcement explains the decision and timing. A practical guide shows the new steps. Training lets people practise. A reminder confirms the changeover date and support arrangements.
For a hypothetical reporting-system rollout, the sequence might be: manager briefing, staff announcement, role-specific demonstrations, a short practice period and then a controlled changeover. The dates depend on the work; the sequence makes the transition understandable.
Avoid sending every document to everybody. Give each role the instructions it needs, while maintaining one source for the full policy and current version. Label documents clearly so an old attachment does not become an alternative procedure.
Make questions part of the process
Provide a named contact or shared channel for questions. Keep a visible question log with the answer, owner and date. Repeated questions usually indicate a missing explanation, not inattentive employees.
Distinguish a communication gap from a design flaw. If staff understand the process but cannot complete it with their access, equipment or workload, another reminder will not solve the problem. Escalate the operational issue.
Give people a way to raise concerns that may be difficult to discuss publicly. Changes can affect responsibilities and confidence, and a large group meeting will not surface every concern.
Measure adoption through the work
Email opens and training attendance show exposure, not implementation. Check whether the new records are complete, approvals follow the intended route and staff can explain the next step without assistance.
Review a small sample of real cases with managers. Identify where work falls back into old habits and why. Update the instructions when the process changes, and retire the old templates.
Close the communication sequence with an honest update: what is working, what has been corrected and where support is still available. A change earns credibility when staff can see that questions lead to practical improvements.
Get help planning and writing your internal communication rollout.




