Getting the team to actually use it
A CRM nobody opens is an expensive spreadsheet with a login. This is a pilot approach, role-by-role training, and four measures that tell you whether it stuck.
Adoption is a different problem from migration. Migration is getting the data in. This is getting people to look at it, and it fails for a reason most training plans do not address.
Why it actually fails
Not enthusiasm, and usually not training. It fails because the old way still works. If the renewal list is in the new system and also in a spreadsheet somebody maintains, people will use the spreadsheet, because it is familiar and it is not wrong.
Double entry is the specific killer. Asked to put something in two places, a busy producer picks one, and it will be the one their colleagues check. Within a month the new system is a half-populated copy that nobody trusts, and the reasonable conclusion everyone draws is that it does not work.
So the first adoption decision is not a training decision. It is deciding which thing stops, and when, and saying it out loud.
Pilot one workflow, not the product
Two weeks, two or three people, one workflow. Renewals is usually the right one: it has a clear start, an obvious outcome, and everybody already agrees it matters.
During the pilot that workflow lives in the new system only. Not "also". If the pilot group is still keeping the old list, you are not testing the system, you are testing their patience.
At the end, one question decides whether to widen it: did the pilot group prefer it? Not whether it worked — whether they would be annoyed to go back. That is the only adoption signal worth anything, and two weeks is enough to get it.
Train by role, not by feature
A feature tour teaches everybody everything and leaves nobody able to do their job. Train each role on the three or four things they do daily.
- Producers: find a client, see what they hold, log what happened, set the next action.
- Service staff: work the renewal list, update a policy, record a client conversation.
- The principal: the four numbers they will be asked about, and where to find them without help.
Thirty minutes each, on their own data, doing a task they had to do anyway. A training session on sample records teaches people that the system is a training exercise.
Four measures that mean something
- Activities logged per person per week. Not logins. Logging in proves nothing; recording a client conversation is the behaviour you want.
- Renewals worked before the last two weeks. The behaviour change you bought.
- Records with an owner. Rising means people are taking responsibility rather than tidying.
- Surviving spreadsheets. Ask, monthly, without consequences. The honest answer tells you more than any dashboard.
Report these as team totals. The moment adoption becomes an individual performance metric, people log activity instead of doing work, and you have bought worse data at the same price.
Pilot it on a real book
The 14-day trial is about the length of the pilot described above, which is not a coincidence. Import one line of business and run its renewals in it for two weeks.
Related: what it costs, organising the book first.