A change plan for people who already have a full-time job

The change plan says staff will complete training before launch. Their manager's plan says they will deliver the same workload as usual. Neither plan explains which work will move to make room for the other.

That conflict deserves attention before the communications campaign. People can understand a change and still lack the time, access or confidence to adopt it. A credible change plan treats learning and transition as work the organisation has chosen to fund.

Put time on the manager's agenda

Start with the tasks people will do differently. Estimate the time needed to learn, practise and recover from early mistakes, then discuss the assumption with the managers responsible for the work. Avoid presenting training as a minor obligation that staff can fit around everything else.

For a fictional scheduling-system replacement, coordinators might need practice with recurring bookings and cancellations, while occasional users only need to request a slot. Giving everyone the same long session wastes some people's time and leaves others underprepared.

Managers should decide how that time becomes available. They might stagger attendance, defer lower-priority work or arrange temporary coverage. Those choices have costs. Hiding them does not make the change cheaper; it makes the workload less honest.

Check timing against the organisation's calendar. A technically convenient release can coincide with a busy reporting period or leave cycle. If the date cannot move, reduce the scope or increase support explicitly. Do not depend on goodwill as the only transition resource.

This connects to leading a team out of firefighting. A new process introduced without capacity can become another stream of interruptions for the same people already struggling to finish planned work.

Teach the task people will perform

Training should follow the job rather than the product menu. Let participants complete representative tasks with safe data and receive feedback. Watching a presenter complete a clean example is useful preparation, but it does not show whether someone can handle an ordinary exception alone.

Create short guidance at the point of need. A coordinator dealing with a cancelled recurring booking should not have to search a recording for the relevant two minutes. Keep instructions specific enough to act on and give each item an owner who will update it when the process changes.

Explain the business rule behind the interaction where judgement is required. If users understand why an approval is needed, they can recognise when a request is unusual. Memorising where to click is less helpful when the screen changes or the expected approver is away.

Practice needs a forgiving environment. Tell staff which actions are simulated and which have real consequences. Do not ask them to experiment with live notifications or confidential records just because a separate practice space was omitted from the plan.

Offer more than one route to learning where needs differ. A written guide, accessible demonstration or short supported practice may be appropriate. Ask what prevents participation rather than assuming non-attendance means resistance.

Design the first week of support

The first week should have named support arrangements and a clear route for problems. Staff need to know whether to use the normal service desk, contact a local helper or report a process question to the business owner. Avoid a collection of overlapping chat groups with no triage owner.

Local champions can be useful, but give them bounded responsibilities. A willing colleague should not become the permanent unpaid support model. Set aside time, describe which questions they can answer and give them a route to escalate faults without personally investigating everything.

Collect the issues that repeat. A question asked several times may indicate unclear guidance, poor design or a business rule nobody has settled. Fixing the underlying issue can be more useful than sending another reminder to read the instructions.

Plan for people who miss the initial transition. New starters, staff returning from leave and people whose role changes will need the same essentials later. A one-off launch event cannot carry ongoing capability.

Keep the old route only for a stated reason and duration. Parallel processes may support continuity, but they can also leave staff uncertain about where the official record lives. Tell people which route to use, how exceptions are reconciled and who can approve continued use of the alternative.

Ask whether people can do the work

An attendance record shows participation in training. It does not establish independent task completion. Check a small set of relevant tasks after launch, with particular attention to roles that had limited practice or different working conditions.

Ask managers about workload and workarounds. Listen for quiet signs of difficulty: one person doing everyone else's requests, a spreadsheet that remains essential or staff postponing tasks until a helper is available. These are operating signals, not grounds to blame the user.

Use that feedback to change the transition plan. Extend targeted support where the need is clear, simplify the process where possible and stop communications that are no longer useful. Be specific about who still needs help and with what task.

A good change plan eventually becomes ordinary onboarding, current guidance and a manageable support route. The launch team can step back because capability exists in the service, rather than because a calendar says the communication phase is complete.