Making the case for internal CRM adoption (page 2 of 2)

As Sealing Devices got ready to adopt new CRM software, I personally met with every key manager and formed a committee to decide which features were most important to us. Just because a feature exists does not mean it is applicable to your businesses.

Unless you make the effort to understand which features and modules are actually useful to your various teams, you may end up with a costly excess of data and functionality.

Don't Saddle Non-Technical People with Technical Duties
Many salespeople I consulted worried that the new CRM system would force them to spend more time behind a computer, rather than behind the wheel of a car, visiting potential customers. It was critical that they understood the software was being installed so they could spend more time away from their computers.

To that end, I made sure to limit as much as possible the amount of "heavy lifting" they were responsible for. Most notably, I took on the major task of converting data from the old system into the new one. Granted, this would have been easier to delegate in small doses across the sales team. But had I done so, it would have only reinforced their early impressions of the new system as a "burden."

Train Early -- and Continuously
Selling people on the idea of a CRM system is one thing, but eventually you need to make sure the entire staff knows how to take advantage of their new tools. Conducting comprehensive training sessions just before you go live can be a fool's game. We began training a full six months prior to the upgrade.

Once a week, I would meet with employees and walk them through a single, specific feature of the software. (that's all - just a single feature.) The only additional request I made was that each staff member practice using the new software for a half hour or so every day.

Indeed, it was a gradual process, but by the time we went live, everyone knew exactly how to add a customer name, how to edit an old contact, and how to identify what features of the new software were most critical to their jobs.

But the training does not stop with the basics. We've continued to train over the past few years, getting progressively more advanced with each session. It's the difference between being knowing your CRM system and mastering it.
Don't "Dabble Your Feet in the Water"
This is what I call the "Big Bang" approach to adopting CRM. There is always a risk with any major software overhaul.

But I would caution companies against taking the "incremental" approach. We found there were great benefits to an integrated implementation, in which all the different software applications are launched at once. The alternative - maintaining a mix of new and old systems - is far more expensive and challenging.

It also creates psychological barriers, if employees have old and familiar software to fall back on. They are far more likely to appreciate the power of the new software if they are given access to all its features at the same time.

Today, I can say with confidence that every user at our company is not only happy with our CRM system but sees it as an integral part of their success. Reaching this point was a tough climb, involving a sometimes exhausting campaign of persuasion, patience and training. But when you spend the energy to ensure that your staff - and not just management - is fully "on board," the payoff to your business is huge.