Académique Documents
Professionnel Documents
Culture Documents
Key steps have emerged over years of CRM implementations that tend to separate successes from
failures.
Set the CRM Vision: Clear and Definable Goals and Expectations
An old proverb said that you can go anywhere as long as you start from where you are, not from where
you think or wish you might be.
Leading a CRM effort starts with looking at your company as customers do. How is your customer
relationship management operating now? Top executives should take steps such as answering an ad,
calling your toll-free number for service, placing an order, and signing up to get emails.
In a successful initiative, your entire company will be deepening its ability to see better from the
customer's point of view.
What are your company's value proposition and competitive advantage in their eyes? How can you
improve each of these attributes?
How do your employees answer these questions?
What customer needs can you serve better?
What feedback mechanisms can you set up to measure these perceptions -- both now and after CRM
implementation? You'll need these mechanisms to carefully quantify the business case for your CRM
effort. The feedback you gather will document your eventual progress. It's critical that you develop
objectives that are measurable, and have key performance metrics in place.
As you become customer-centric, look at your competitors the way your customers see them. What are
competitors doing for your customers that the customers like?
Less-successful CRM initiatives, instead of looking from the customer's point of view at the company,
look from the company's point of view at the customer, in an effort to extract more value.
Part of your training needs to focus everyone on the need for accurate, complete data. Emphasize to
employees that great customer data is the key to unlocking customer value. Show each person how they
will benefit. Make everyone aware of how marketing campaigns can be monitored more effectively,
more accurate sales forecasts can come together more quickly, and add-on sales will be easier.
Set clear standards for data quality. Communicate them widely. Make someone the champion of clean
data. Devise a plan for checking and maintaining data to ensure it is accurate and clean.
Unclear metrics
It's critical to review your plan to measure key performance indicators, and ROI. Can your metrics truly
determine the real business value of your effort? The quality of metrics has been a deciding factor in
making or breaking many CRM projects.
Implementation Errors
Inability to link channels
Have you considered ALL customer touchpoints and processes? CRM projects often have focused on
some parts of the customer experience, but ran into trouble when they were unable to link with or serve
well all parts of the customer experience.
People errors
Introducing CRM to hundreds of employees at a time
It's easy to want to do too much, too fast. Get it right first with a small team of employees chosen to
represent a cross-section of your company. Choose an initial project that can make a dramatic difference,
with clear key performance indicators. Strong pilot results will help you avoid the next pitfall:
Process errors
Instead of enhancing new processes, changing the CRM system to fit old processes
To avoid the pain of revision, some companies don't take the opportunity to re-engineer and optimize
their processes. They look to CRM as a patch rather than an opportunity from the ground up to increase
customer satisfaction, revenue, service and overall productivity.
Technology Errors
Customer data is in more places than expected
As implementation gets underway, key data can turn up in salespeople's PDA's, spreadsheets,
handwritten notes, and legacy systems. To avoid surprise integration nightmares, the requirements
gathering stage needs to be careful and thorough.
Different CRM solutions are in place but do not work well together.
Often marketing, sales and service departments already have different types of CRM software, from
different vendors, to track the same customers. As a result, these departments can't share data, and have
redundant support and administration costs.