Training week for a new CRM usually goes well. Everyone attends, the trainer is patient, and people leave knowing where the main screens are and how to search for a supporter.
Then go-live arrives. Someone sits down to process a cheque with a Gift Aid declaration attached, and it takes twenty minutes and two messages to a colleague.
That is not a training failure. Training shows people how the system works. Being ready means knowing how your job works in it: the twelve steps of your Tuesday income processing, the way your team records a legacy pledge, the report you send to the director every month. Those are different things, and the gap between them is where a lot of early frustration with a new CRM comes from.
The good news is that the gap is very closeable, and most of what closes it costs time rather than money. Here are three habits that make the biggest difference.
1. Give people time in the system before go-live
Most CRM suppliers can provide a test or sandbox environment, a copy of the system where nothing anyone does affects real supporter records. It is not always part of the standard package, so ask early, whether you are moving to Raiser’s Edge NXT, BeaconCRM, thankQ or anything else. It is the single most useful thing you can give your team, as long as they actually get to use it.
Two things make familiarisation time work.
Base it on real tasks, not features. Ask each team for the five things they do most often, and turn them into practice exercises. For example:
- Process a cheque donation with a Gift Aid declaration
- Update a supporter’s mailing preferences after a phone call
- Book a supporter onto an event and record their payment
- Find a supporter’s last three gifts and who thanked them
- Pull the list your team sends out every month
Someone who has done each of these a few times in the test system will be far more confident on day one than someone who watched a trainer do them once.
Put it in the diary. “Have a play when you get a chance” rarely happens, because there is always something more urgent. An hour a week, booked and protected, for the six weeks before go-live, works much better. It also gives managers a clear picture of who is getting on well and who needs more support.
2. Hold regular show-and-tells
A show-and-tell is a short session where the project team shows what has been built so far, using real scenarios rather than a feature tour. Thirty minutes every fortnight is plenty.
They do three useful jobs at once. People see the system taking shape long before training, so it feels familiar rather than new. Problems surface while they are still cheap to fix: if the events team spots that a booking takes six clicks instead of two, it is far easier to change in month three than after go-live. And the project stops feeling like something happening somewhere else to other people.
A few things help them run well:
- Show one real process from start to finish, such as a donation coming in and being thanked, rather than a tour of every screen
- Invite the people who actually do that process, not just their managers
- Write down every question asked, and answer them at the start of the next session
- Keep to time, so people come back
3. Give the answers a home
Every new system generates the same questions, again and again. Where do I record a phone call? Which appeal code does a raffle go to? Why can’t I see the event bookings?
If the answers live in people’s heads or inboxes, every question lands on the same two or three people, usually your database manager and whoever was closest to the project. Agree one shared place for answers instead: a shared folder, a Teams channel, a page on the intranet, whatever your team already uses.
What goes in it matters more than where it is:
- Short how-to notes for your common tasks, written in your organisation’s own words. “How we record a legacy pledge” is more useful than the supplier’s general guide to the gifts screen.
- The questions and answers from your show-and-tells
- A simple list of who to ask about what
Keep it going after go-live. The questions do not stop on day one, and a page that grows with the system becomes the guide your next new starter learns from.
A quick readiness check
A few weeks before go-live, ask each team one question: can you do your five most common tasks in the new system without help?
The answers tell you exactly where to spend the last few weeks. A team that says yes is ready. A team that says “all except two” has a clear, short to-do list. And a team that is not sure yet has told you something useful while there is still time to act on it.
None of this replaces good training. It builds on it, so that the confidence people leave training with is still there when the real work starts.
If you are planning a CRM project and would like help with familiarisation, show-and-tells or writing your own process guides, contact ADA to discuss your CRM project. We work alongside your team to get people confident in the new system, and leave you with materials you can keep using long after go-live.