Getting staff to adopt new tools

People adopt what helps them

Owners often describe low adoption as a training problem. Usually it is a value problem. If a new tool saves the owner a report on Fridays but adds three clicks to every job for the dispatcher, the dispatcher will find a way around it. Nobody is being difficult. They are protecting the part of the day they are judged on.

So begin by asking who benefits. For each tool, name the people who will use it daily and write one sentence about what gets easier for each of them. If you cannot write that sentence for a role, expect that role to resist, and either change the setup or accept that you need a different way to get the benefit.

A good test is to ask two or three staff, before you buy: if this worked perfectly, what would you stop doing? Their answers tell you whether the tool solves a pain they feel. If the answers are vague, pick a different problem first.

Design for the busiest user

Set up every tool for the person with the least time and the most interruptions: the front desk coordinator at a busy dental office, the dispatcher during a heat wave, the paralegal the week before trial. If it works for them, it will work for everyone.

In practice that means fewer required fields, sensible defaults, saved views that show only what each role needs, and mobile access for anyone who works in the field. It also means connecting the tool to where people already work. A reminder that appears in Outlook or Microsoft Teams gets acted on. One that lives in a separate dashboard often does not.

Watch someone use the tool for ten minutes before launch. You will see the hesitation, the extra click and the field they skip. Fixing those small things is usually worth more than any amount of training.

Defaults matter more than most people expect. If the most common job type, service or matter template is preselected, staff save a decision every time. Ask the vendor how to set defaults by role, and revisit them after the first month based on what people actually choose.

Make the new way the easy way

People follow the path of least effort. If the old spreadsheet, the paper sign-in sheet or the personal Gmail templates are still available and faster, they will win. Once the new tool is working, retire the old route on a set date. Make shared spreadsheets read-only, remove old templates from the shared drive, and stop accepting requests through the old channel.

Pair that with visible wins. When the new intake form means a client file is complete on day one instead of day five, tell the team. When AI-drafted meeting notes save a financial adviser half an hour after every review, ask them to share how they use it. Specific stories from colleagues persuade far better than announcements from management.

Coach, do not lecture

Avoid long feature tours. Most people use a small fraction of any software, and showing them everything makes it feel harder than it is. Teach the routine first and the exceptions later.

Managers set the tone. If a partner or owner keeps emailing requests instead of using the new system, everyone notices. Ask leaders to use the tool visibly from the first day, and to redirect requests that arrive the old way, politely and every time.

• Short sessions on real tasks, no longer than 30 minutes.
• A one-page guide per role, with screenshots of the three things they do most.
• An internal champion in each team who has had extra practice.
• Office hours in the first two weeks where anyone can bring a problem.
• A second session after two or three weeks, when people know what confuses them.
• New hires trained on the new tool from day one, with no mention of the old way.

Use data without making people feel watched

Most business software shows basic usage: who logged in, how many records were created, which steps were completed. Use these numbers to find friction, not to rank people. If one team logs far fewer jobs in the system than another, ask what is getting in the way before assuming anyone is refusing.

Pick three signals and review them weekly for the first two months. For example: share of new enquiries logged in the CRM, share of jobs closed out on the mobile app the same day, and number of documents still arriving by email instead of through the portal. Share the trend with the team. Improvement is motivating when people can see it.

Pair the usage numbers with the workflow results you care about, such as turnaround time or error rate. High usage with no improvement in results means the tool is being used but the process around it needs work.

Handle AI tools with extra care

AI tools bring worries that ordinary software does not. Some staff fear the tool is there to replace them. Others worry about being blamed for its mistakes, or are unsure what data they are allowed to put into it. Address these directly. Explain what the tool is for, which tasks stay with people, and that a person reviews anything that goes to a client.

Write a short AI usage policy before rollout: approved tools, what data may and may not be entered, and who to ask when unsure. Regulated firms should involve counsel, since law, health, tax and financial advice each carry their own rules. Then give people permission to experiment within those limits. Adoption grows fastest when staff discover their own uses and share them.

When to stop pushing

Sometimes low adoption is the right signal. If people have been trained, the old path is gone, and they still work around the tool, the tool may not fit the work. Ask directly, listen, and be willing to change the configuration or the product. Forcing a poor fit wastes more time than switching.

Set a review point at 60 or 90 days with clear criteria: usage above an agreed level and the workflow measure improving. If neither has happened, decide deliberately whether to fix, replace or cancel. Cancelling a subscription nobody uses is a perfectly good outcome, and it frees budget for something that will help. InTheory builds this review into the last month of every engagement, because adoption is the part that decides whether the work paid off.