Why your team won't use the new tool, and what to change instead
Your team won't use the new tool when the new step costs them more than it gives them, so they keep the old spreadsheet. Pushing harder breeds workarounds. Put the step inside the tool they already work in, make it the default, close the old path, and name one person to watch whether it's used.
You bought the tool, set it up and told everyone to use it. A few weeks later the CRM is half empty, the project board is out of date, and the real numbers are in a spreadsheet one person keeps on the side. Every tool you try ends up the same way.
Keeping a system up to date feels like extra work to the people who have to do it. Reps and account managers fall back to a private sheet, because it is faster and nobody checks it.
What usually gets tried, and why it does not hold
The common moves are a mandate, more training, a champion on the team, or a switch to a different tool. A mandate gets compliance while someone is watching and a workaround the rest of the time. Training teaches people where the buttons are, but they already knew that. A champion carries the load until they get busy. A new tool brings the same extra step in a new place, so the same thing happens a few months later.
Why it happens
Think about what the new tool asks of the person using it. They finish a call, then they have to open another screen, retype what they already know and choose from fields they don't care about. The person who gains from that is somebody else, usually you or the person reading the report. The person doing the work pays the cost and gets nothing back, so they find a quicker way around it. Push harder and the workarounds get quieter, not rarer.
The reverse is also true. A new way spreads when it fits how people already work and gives something back to the person doing it. The systems thinker Donella Meadows called the pushback "policy resistance": people pulling toward their own goals make a pushed process bend around them. Everett Rogers, who studied how new ideas spread, found that fit with existing habits, which he called "compatibility", decides whether people take something up.
Signs you can notice in your own business
- The old spreadsheet is still open next to the new tool, and people trust it more.
- The new tool is full on the days before a meeting and empty the rest of the time.
- Someone is asked to "update the CRM" at the end of the week, and the entries read like they were typed from memory.
- Two people give different answers about the same client, and each points at a different place.
- The tool's reports look tidy, but nobody on the team has used one to make a decision.
What the fix looks like running as a system
The step moves to where people already are. When an email arrives or a form is filled in, the CRM record fills itself from it. When a deal changes stage, the update posts to the chat channel the team already reads. Nobody retypes anything, because the person doing the work never has to open the new tool to feed it.
Two rules finish the job. The new way is the default, so the record exists without anyone choosing to create it. And the old path is closed: the side spreadsheet stops being the place where the real answer lives, because the answer is already somewhere easier. When both are in place, there is nothing left to work around.
In the first weeks, one named person watches whether it is being used. They look at whether records fill in and whether the old sheet has gone quiet. When something is skipped, the step gets fixed, and the team gets no extra reminder.
What stays with you
- Choosing which tool is the home for each kind of information, and saying so plainly.
- Naming the person who watches it in the first weeks and has the authority to change the step.
- Closing the old path once the new one works, so the two never run side by side for long.
- Deciding what a person should still write in their own words, such as the read on a client after a hard call.
The system behind this: the step sits inside the tool your team already works in, the record fills itself, the new way is the default, and one named person watches whether it is used.
Questions
Why does my team ignore the CRM we paid for?
Because keeping it up to date costs them time and gives them nothing back. The person typing is rarely the person who reads the report. Make the record fill itself from the email or form, and the reason to avoid it goes away.
Will more training fix it?
Rarely. People usually know how to use the tool already. They skip it because the extra step is not worth their time. Training helps only after the step has been made lighter.
Should I mandate it?
A mandate gets entries while someone is watching and workarounds the rest of the time. It works better as the last step, after the new way is the easy default and the old path is closed.
Related
- CRM hygieneCRM hygiene is keeping CRM records accurate, complete and free of duplicates. Why it decays, what it breaks, and how a system keeps it as a routine.
- Call notes to CRM: why every call lands in a different shapeCall notes land in the CRM in a different shape each time. Pull every call into the same fields with a next step and a date, checked by whoever ran it.
- When two tools disagree about a client, which one winsWhen two tools disagree about a client, pick one owner tool for each field, let changes go one way from it, and send edits made elsewhere back to the owner.
- Build it, hire for it, or install a system: a one-page decisionDecide whether to build it yourself, hire a person or set up a system by the kind of work it is, with a one-page memo to fill in for your own business.
- Where AI belongs in a revenue systemWhich steps from lead to revenue go to AI, which run on plain rules, and which stay with a person. The hard rule: the AI never invents a price.
- Should I hire an operations coordinator or install a system?What an operations coordinator costs a year, set against building a system: where each one fails, and which to pick first when your agency is growing.