The launch announcement was sent to everyone. On Monday, people still use the old form because the message never said when the new route became mandatory or what to do with work already open. A project change communication plan should connect each audience with a specific action, the information needed and a feedback route.
APM's communication principle recommends understanding recipients and reviewing effectiveness. The action card below turns that general idea into a small-team working tool. Sending a message is evidence of distribution, not necessarily understanding or adoption.
Photo by Vitaly Gariev on Unsplash.
Start with what must change for the recipient
Separate audiences by task and decision, not simply by department. The requester may need a new form. The receiving coordinator may need to assess it. The manager may need to authorise an exception.
State what remains unchanged only where it prevents genuine confusion. A long list of unaffected details can bury the one action the person needs to take.
Build an action-message card
For each audience, record:
Required action and effective date.
Current authoritative instruction or working link.
Treatment of existing work during transition.
Sender with relevant authority.
Timing, channel and any acknowledgement needed.
Question route and response owner.
Observable check that the audience can act.
Use language people recognise from their work. If “transition to the future-state platform” means submit new requests through a particular form from a particular date, say that.
A hypothetical announcement correction
A team replaces its request form. The original message says the new form is now available. Some people interpret that as an optional trial while the receiving team stops checking the old inbox.
The revised message specifies which requests use the new route, the effective date and who handles items already sent to the old inbox. The owner confirms that the destination is ready and that the transition rule has an accepted owner.
The improved wording cannot compensate for a broken form or an unstaffed queue. Communication and operational preparation must agree.
Sequence messages with actual readiness
Do not announce an action before users have the required access and instructions. Equally, do not wait until the final day if people need time to change a planned task or obtain approval.
Give important audiences an opportunity to ask questions before the action becomes necessary. In a small team, that might be a short walkthrough rather than a campaign of polished announcements.
Check the response and adapt
Ask a representative recipient to explain the next action and where they would go when unsure. After transition, inspect misrouted work and repeated questions. Those signals can reveal missing information or an unclear rule, not simply people failing to read.
Keep the current instruction easy to locate and withdraw obsolete working links through the approved route. The small-team planning guide connects communication to delivery dates. For the connected task, read Project-to-Operations Handover: What the Receiving Team Needs. If announcements are going out but behaviour remains confused, discuss your project requirements.
