Prepare people for changed work

A useful handover makes staff confident about the work, not just familiar with a new button. Your team needs to know what the automation handles, what still requires judgement and where to turn when an item behaves differently. Prepare people around their actual responsibilities, including cover for absence and the staff who use the process only occasionally.

01 Start with the task that changes

Write down the manual process before teaching the automated one. Identify where staff previously checked information, decided what to do or corrected a mistake. Some of those checks may move; others must remain. If nobody explains the difference, staff may repeat work unnecessarily or assume a check has happened when it has not.

Microsoft Forms is a familiar example of structured data collection. A submitted form may begin a workflow, but submission is not the same as approval. Training should show which fields are required, what a confirmation means and what happens to an incomplete request. Use fictional training entries rather than customer information.

Distinguish routine users from operational leads. Routine users need to recognise a successful outcome and report an exception. Operational leads need to inspect the queue, understand pause controls and organise recovery. Neither group needs every detail of the implementation.

02 Put instructions where work happens

Microsoft Teams provides conversations and shared working spaces. It can be a useful route to instructions or an exception discussion, but an important runbook should not depend on finding an old chat message. Give it a stable location and make the link easy to reach from the working channel.

SharePoint is used for document libraries, lists and collaborative information. A handover library can hold the current procedure alongside a change record. Explain which document is authoritative and who can edit it; several similarly named copies make a stressful interruption harder to manage.

Google Workspace brings tools such as Google Drive and Google Docs into collaborative work. If those are already familiar to staff, a maintained document may be more usable than a separate documentation system. Check that the instructions remain accessible to the relevant roles rather than living solely in a consultant’s account.

03 Rehearse ordinary work and exceptions

Walk through a normal item. Ask the user to describe what they expect before the workflow runs, then compare the result.
Introduce an incomplete input. Show whether the system rejects it, holds it for review or routes it to a person.
Practise a duplicate. Establish how staff identify an item already processed and avoid creating a second record.
Explain a pause. Use a controlled training setting to demonstrate who may stop the workflow and how unfinished work is recorded.
Repeat without coaching. Let staff follow the written procedure and note where they need help.

Keep the rehearsal separate from live customer work. A screen recording can support later reference, but it cannot establish that a learner can make the necessary decision. Use questions about the task rather than asking whether everyone understood the demonstration.

04 Give different roles usable guidance

Trello is known for organising work with boards, lists and cards. Where a business already uses it, a handover task board can make outstanding training actions visible. A completed card should point to evidence, such as a reviewed instruction or a recorded rehearsal outcome, rather than merely saying “training done”.

Keep task instructions short enough to consult during work. Put technical explanations in a separate runbook and link between them. Use meaningful headings, text descriptions alongside screenshots and terminology that matches the interface staff actually see. Instructions should not depend only on colour or on remembering a particular presenter.

Allow staff to raise concerns about changed workload. Automation can remove copying while adding exception checks or approval duties. Discuss those changes explicitly so a manager can allocate time and responsibility rather than leaving invisible work with the most helpful person.

05 Accept readiness through observable work

Readiness means the relevant roles can complete the expected task, recognise an exception and locate help. Ask a backup colleague to do the same: a workflow is fragile if only one person understands it. Record gaps as handover actions with an owner, not as vague future improvements.

Make refresher training part of onboarding and significant process changes. If the workflow later gains a new approval step, update the task instructions at the same time. Training and documentation should describe the same version of the work.

For processes affecting legal duties, financial decisions or safety, have an appropriately qualified professional review the relevant controls. Staff confidence is important, but it is not a substitute for specialist judgement.