Start here.
Plan the change around the work each person needs to finish. Explain what is changing, let staff practise ordinary tasks and exceptions, and start with a manageable group. Give them a named contact for help, investigate workarounds, and agree what needs to be working before you invite the rest of the team.
- Explain the change in responsibilities as well as the buttons people will use.
- Make room in the working day for practice, questions and corrections.
- Treat a return to the old spreadsheet as something to investigate before deciding that staff simply need more training.
What will change in each person’s day?
Imagine a business replacing a shared list of customer requests with an app. An office colleague records the request, another person takes responsibility for it, and a manager checks anything that remains unresolved. This is an invented planning example.
Walk through the job with the people doing it today. Ask what they write down, whom they tell and how they know someone has taken over. Then describe the same job in the proposed app. A screen demonstration alone will not settle who is responsible for the next step.
Be clear about what stops, what continues and what is changing later. If the app becomes the place to assign requests, managers need to know where to look instead of asking for a separate list. Decide how staff will handle any work outside the first trial.
Include people who cover absences, work different shifts or receive the handoff at the end. Ask them which parts of the plan would be difficult during an ordinary working day. Leave time to resolve those questions before announcing the change as settled.
What should people practise before using it for real work?
Choose a small set of tasks for each role. In our example, the office colleague could record a request, correct a detail and find out who has taken it. The person doing the work could accept it, add an update and pass it back when information is missing.
Use made-up records in an agreed practice area so a learning exercise does not send a customer message or change a real job. Ask the supplier to explain what is safe to try and to show how mistakes can be corrected.
Let staff try the tasks themselves after a short introduction. Notice where they ask for help or use wording differently from the app. Give them a useful prompt sheet for the task, including what a completed result looks like and where to ask a question.
Practise an awkward case as well as a tidy one. Who handles a request assigned to someone who is away? What happens when a customer phones with a correction? Use the answers to improve the instructions, the working arrangement or the app itself.
How can you start with a manageable group?
Choose a limited part of the work for the first trial and include the people needed to finish it. A group of enthusiastic volunteers may be helpful, but also consider who will reveal the practical difficulties: someone covering reception, someone working away from a desk or the person receiving the final handoff.
Tell the group what you are trying to learn and how long the initial trial will run before review. Give them time to practise and a named contact who can help during the hours they use the app.
Agree where work is recorded and what people do if they cannot finish in the app. If a temporary workaround is needed, name who will keep track of it and who will bring the result back into the agreed record. Avoid leaving each person to invent a different fallback.
Keep customer service in the plan. Decide who will step in if a member of staff needs help while a customer is waiting. Your business contact can answer process questions, while the supplier investigates faults through the agreed support route.
What if people keep going back to the old way?
Ask someone to show you the moment they left the app and explain what they needed to finish. A return to a spreadsheet might reflect a missing capability, an unclear responsibility, a reporting request or a task they have not yet learned.
Respond to the reason you find. Another demonstration will not resolve a missing business rule, and a new feature will not explain who is meant to pick up an unassigned request. Check the evidence with the person doing the work before choosing a response.
The following table uses hypothetical situations from our customer-request example. It suggests questions to investigate, not diagnoses of your staff or proof that a particular change will solve the problem.
Keep the trial group informed about what you have changed and what is still open. If a workaround must continue for a while, explain its boundary and who is responsible for reviewing it.
| What you notice | What to ask | Possible next step to discuss |
|---|---|---|
| A request is recorded in both places | Who still needs the old list, and for what decision? | Agree where the current record lives and change the remaining handoff |
| Someone asks a colleague to update the app | Can they find the task and are they allowed to do it? | Check the task, access and instructions with them |
| An unusual request stays outside the app | What information or step is missing? | Agree how the exception will be handled and whether the app needs a change |
| A manager requests a separate progress sheet | Which unanswered question is that sheet meant to answer? | Review the manager’s task rather than requiring duplicate entry by default |
When should the rest of the team start using it?
Agree the conditions before expanding. Can the first group finish the chosen jobs, including a correction or handoff? Are there unresolved problems that would make ordinary work difficult? Is help available to the next group when they need it?
Review completed work and the effort around it. A sign-in count tells you people opened the app; it does not tell you whether a request reached the right person or whether someone recreated the result in another file.
Decide whether to expand, repeat the trial with changes or pause. Record the remaining problems, their owners and the next review point. Tell staff why you made that decision so they know which arrangements still apply.
As more people join, keep the task instructions current and make practice available to staff who missed the first sessions. Include the app in how a new colleague learns the job. The aim is for the team to understand and complete its work, with a clear way to get help when something is unfamiliar.
Write a short introduction plan with your team.
Use the work people already understand as the starting point. Make sure your software partner and the staff helping with the first trial know what they are responsible for.
- The first job
- Name the task people will start doing in the app and what counts as finished.
- The first group
- Include the roles, working patterns and cover arrangements needed to try that task properly.
- The help available
- Name the business contact, supplier contact and agreed way to report a problem.
- The next decision
- Set a review point and the conditions for expanding, adjusting or pausing the trial.
Planning something with a similar workflow?
Discuss your project with usA couple of common questions.
Should everyone switch to the new app on the same day?
Start with the work people share. If several people share the same work, a gradual introduction needs clear boundaries about who is using which process and where the current record lives. Choose the approach your team can support and practise the handoffs before the switch.
Who should train the team: our manager or the developer?
Agree the parts each person covers. The supplier can explain the software and investigate faults; your business needs to explain its responsibilities and decisions. Staff should know whom to ask for either kind of help, and the people providing that help need time allocated for it.