Collaborative CRM 3
Collaborative CRM 3
Collaborative CRM 3
Bryan Foss
is an experienced CRM and board advisor. He worked with IBM for many years and now provides independent advice for many
large organisations on systems implementation and related change issues.
Merlin Stone
is a leading author and advisor on CRM programme management and implementation. He is Professor of Marketing at Bristol
Business School and a Director of Nowell Stone Ltd. and The Database Group.
Yuksel Ekinci
is a Reader in Marketing at Business School in Oxford Brookes University. He specialised in customer satisfaction measurement,
quantitative data analysis and user satisfaction with CRM systems.
Abstract Although customer relationship management (CRM) has been one of the
fastest growing businesses of the new millennium, critics point to the high failure rate of
the CRM projects as evidenced by commercial market studies. The purpose of the study
is to investigate success and failures of CRM system implementations. We found that the
scope, size, complexity and duration of the CRM projects seem to vary quite significantly
across firms. Poor planning, lack of clear objectives and not recognising the need for
business change are the key reasons for CRM failures.
Journal of Database Marketing & Customer Strategy Management (2008) 15, 68–78. doi:10.1057/dbm.2008.5;
published online 9 June 2008
68 Database Marketing & Customer Strategy Management Vol. 15, 2, 68–78 © 2008 Palgrave Macmillan Ltd 1741-2439 $30.00
www.palgrave-journals.com/dbm
What makes for CRM system success — or failure?
© 2008 Palgrave Macmillan Ltd 1741-2439 $30.00 Vol. 15, 2, 68–78 Database Marketing & Customer Strategy Management 69
Foss, Stone and Ekinci
70 Database Marketing & Customer Strategy Management Vol. 15, 2, 68–78 © 2008 Palgrave Macmillan Ltd 1741-2439 $30.00
What makes for CRM system success — or failure?
CRM initiatives ranged from technological 40 responses, showing the accuracy of our
implementation problems to a lack of targeting and the responsiveness of our
organisational integration and customer contacts. We asked them a few open-ended
orientation.14 Jain et al.15 state that most questions. The following section presents
such failures are attributed to poor design, our findings.
planning and measurement of CRM
projects. They comment that capturing the FINDINGS
wrong customer information, unclear goals, Different industries and users have different
inappropriate selection and use of priorities and varying amounts of funding
technology, inability to integrate people and to invest in CRM. Companies with very
processes and use of misleading metrics tight profit margins or limited funds tend to
or improper measurement approaches are the partner where they can (eg shared loyalty
major barriers in implementing and schemes, outsourced database management
managing CRM projects. According to and call centres) and to use small ‘pay as
Kale,16 the seven deadly sins for you go’ development stages, while keeping a
unsatisfactory CRM outcome are: (1) consistent vision and objective in mind.
viewing the CRM initiative as a technology Many of the largest scale projects were in
initiative; (2) lack of customer-centric vision; the financial services industry in the early
(3) insufficient appreciation of customer years of this century. Banks, insurers and
lifetime value; (4) inadequate support from others usually used packages such as Siebel
top management; (5) underestimating the and Chordiant at the heart of their project,
importance of change management; (6) but some developed their own systems.
failing to re-engineer business processes; and These companies were moving — or had
(7) underestimating the difficulties involved already moved — from managing customers
in data mining and data integration. He states mainly in the branch or direct mail, to
that most executives are not even aware of managing them in the contact centre and
these issues, even though they could spell over the web. Here, it is arguable that the
disaster for their careers and for the company. main reason for the investment was to cut
Others argue CRM failures are heavily the cost of managing customers, and to
influenced by the firm’s lack of ability to enable the company to move into new
integrate CRM technologies into its product markets very quickly (eg from
functional processes.17,18 banking to insurance or vice versa). At the
same time, telecommunications companies
RESEARCH METHOD AND SAMPLE were investing in large CRM projects.
We approached about 90 of our contacts Some did it as a ‘Big Bang’ replacement for
we considered had direct and personal an existing system which was focused
experience of CRM developments and entirely on subscriber management,
deployments in the last ten years. They including billing. Their new systems enabled
included supplier-side contacts, with them to manage churn and up/cross-sell
knowledge of many client projects, but also much better. In telecommunications,
client-side contacts personally involved in particularly in mobile telephony and now
one or more CRM projects during that broadband, reducing churn is a critical target,
period. Some of the latter had moved jobs while increasing customer value by up-sell
and so experienced more than one CRM and cross-sell is the ‘cream on the cake’.
implementation — particularly as they are Many of these companies have sustained
likely to have been hired across from one their CRM systems focus over time,
company to another because of their although these investments may or may not
valuable experience. We received nearly be considered part of a long-term CRM
© 2008 Palgrave Macmillan Ltd 1741-2439 $30.00 Vol. 15, 2, 68–78 Database Marketing & Customer Strategy Management 71
Foss, Stone and Ekinci
72 Database Marketing & Customer Strategy Management Vol. 15, 2, 68–78 © 2008 Palgrave Macmillan Ltd 1741-2439 $30.00
What makes for CRM system success — or failure?
— case management and workflow So, when someone talks about ‘their CRM
management; project’, they could mean any or all of the
— collections and debt management; above. Each function usually demands a big
— outsourcing and work load balancing. additional development, customisation
and/or integration effort, depending upon
Integrated regulatory compliance the choice of software.
© 2008 Palgrave Macmillan Ltd 1741-2439 $30.00 Vol. 15, 2, 68–78 Database Marketing & Customer Strategy Management 73
Foss, Stone and Ekinci
successfully developed even if there are slips The waterfall model is a sequential process
in other parts of the programme. for developing software in which
Many companies reduce risk by staging development flows steadily step by step, like
the development of any particular a series of small waterfalls, through
functionality or group of functionalities, so requirements analysis, design, development
that benefits begin to be delivered early on, and integration, testing, implementation and
and continue to be developed from maintenance. Although there are many
deployment experience. This also reduces arguments about the pros and cons of
the political risk of such programmes. For following this model, it seems that large-
this reason, many suppliers of CRM systems scale projects that use this approach tend to
and consultancy have created CRM have a high risk of failure, longer time to
programme planning and deployment benefit and are also less adaptable to
methodologies that support accelerated early continuous learning during the
development stages. At the heart of such development and deployment process. As a
methodologies must be a strong CRM result the development effort invested in
programme planning methodology that is some functions may be wasted. The
understood by senior management as being waterfall model is associated with another
the central focus of their governance for systems development idea — that of Big
their CRM improvement efforts. The figure Design Up Front, in which system design is
below, from Customer Essential, illustrates agreed early on in the project so that the
such an approach. systems development effort can focus
The risk of a Big Bang approach is that consistently on the required design. Of
all the requirements for development course, there is no perfect model for
changes are gathered at the beginning of systems development. Indeed, the waterfall
the project and applied in one continuous method is often criticised because in the
development period, before ‘waterfall’ testing real world requirements do change, as
takes place and subsequently deployment. systems frequently need design changes
74 Database Marketing & Customer Strategy Management Vol. 15, 2, 68–78 © 2008 Palgrave Macmillan Ltd 1741-2439 $30.00
What makes for CRM system success — or failure?
before their development is finished. As a This speed was usually achieved because the
result it is usually not possible to have CRM programme was defined as
smooth, step-by-step progress from design development of a single function (eg
to implementation. Instead, an iterative marketing campaign management), with
approach often proves much more effective some integration to existing systems and
at delivering appropriate business value in data sources (even though this might
stages and reducing programme risk. We effectively be the first stage of a
believe that companies which think hard multi-stage CRM programme). In other
about the options for their CRM cases, it was achieved because the
programme phasing and systems programme consisted of minimal
development methodology and consider customisation of an existing CRM package
them as related aspects of the same task are with very limited integration with existing
more likely to get the CRM systems they systems or data sources.
want. Projects that took between two and four
years involved multi-function developments.
These are the majority of what we would
‘OUT OF THE BOX’ OR
call ‘comprehensive’ CRM programmes.
CUSTOMISED?
However, when we analysed the responses
The appropriateness of the software chosen
we received, we saw signs that these
to implement a particular functionality is
programmes are now being completed a
also important. Some packages are suitable
year or so more quickly than they used to
for implementation ‘out of the box’,
be. We think this is because of the
provided that the company is prepared to
increased maturity of CRM software and
change how it works to fit with what the
the wider availability of CRM services,
software designers conceived. Others require
skills and proven development
significant customisation or development.
methodologies.
Of equal importance is the choice of
Projects that took five or six years appear
systems integrator (unless the work is
to be, on the one hand, very large projects
done in-house). Systems integrators with
or where investments are deliberately
good track records of success (and this
stretched out over a long period, or on the
covers not just development, including
other what are known as ‘troubled’ projects,
experience with integrating the particular
which run well over time and budget
software products chosen, but also
compared to initial investment estimates.
implementation and subsequent support)
When analysing recent primary and
are more likely to deliver a successful
secondary research we found that CRM
outcome than those with questionable
projects and programmes grouped by
records in this area.
duration time as follows:
© 2008 Palgrave Macmillan Ltd 1741-2439 $30.00 Vol. 15, 2, 68–78 Database Marketing & Customer Strategy Management 75
Foss, Stone and Ekinci
Five, six or seven years: These were managers often return to management for
often very large-scale programmes (eg IBM approval of more time and budget, as
and Citigroup global rollouts), while many overruns become recognised, but at each
were ongoing incremental programmes request the confidence of management in
(eg Lloyds TSB customer insight project achieving an on time, on budget and full
or BP forecourts project). Some projects benefit deployment is reduced. If delays and
in this category would have been classed as overruns continue, management confidence
‘troubled projects’ at some time, where a is lost and the programme is cut severely to
major redefinition and reset would have been focus on minimal deliverables. Such
required at some stage. programmes may be gradually rebuilt over
time, with additional budget, as confidence
In addition to the above timescales, we also
in the programme returns.
identified programmes that had no specific
During the period of delay and recovery
scope or end date. This is not because they
user departments often suffer budget freezes
were poorly planned, but rather because the
until the programme starts to deliver again,
company is on a long ‘CRM journey’ and
as the programme was probably put in place
committed to making a series of
to provide for the primary needs of the
improvements to its CRM capability as
user department. Even where requested
changes take place in its distribution
budgets are related to new investment areas
channel strategy, customer base, competition
not covered by the programme they may
and the like, as customer management
still be held back until the programme
technology changes, and as the company
makes a little progress. During this time
learns what works and as their customer
the business can be seriously affected
learn to be responsive (or not!) to the new
by the delay. In 2007 a loans company
customer management approach.
collapsed from the costs of continual
parallel running of an old and new system
WHAT HAPPENS WHEN THINGS for a few years after the new system
GO WRONG deployment went continually over time and
A significant finding from this research and budget.
our own experience is that many issues The additional costs and lost benefits are
remain unrecognised for far too long after not only those of the programme but can be
they are first identified. While this can be much wider. Business benefits are often
the result of misunderstanding or a delayed or lost (eg customers not retained,
deliberate cover-up, it seems in most cases cross-sell not achieved, new business areas or
insufficient assurance enables the severity propositions not launched, new markets not
and impact of issues to remain undiscovered entered). In one case a company almost
by the programme for far too long. By the completely withdrew from a profitable B2B
time issues become recognised it is often marketplace where the executives determined
too late to address them with tactical and that there was insufficient capacity to operate
immediate corrections, as a result the there while recovering from a CRM
programme is often proven to be over time ‘troubled project’ in their priority B2C
and budget and the downstream programme business. In some situations projects are
can only be rescheduled. Unless the delivery completely scrapped and financially written
contract with external suppliers protects the off, usually following a tough assessment of
budget, rectifying any issues will take the progress by the board. Future programmes in
programme costs beyond the spending plan, such businesses usually receive far more risk
forcing later deliverables to be cut unless management attention at all stages from
more money is available. Programme justification to deployment.
76 Database Marketing & Customer Strategy Management Vol. 15, 2, 68–78 © 2008 Palgrave Macmillan Ltd 1741-2439 $30.00
What makes for CRM system success — or failure?
© 2008 Palgrave Macmillan Ltd 1741-2439 $30.00 Vol. 15, 2, 68–78 Database Marketing & Customer Strategy Management 77
Foss, Stone and Ekinci
orientation, relationship marketing, and resource- management effectiveness in service sector’, Journal
advantage theory’, International Journal of Management of Services Research, Vol. 7, No. 1, pp. 37–58.
Reviews, Vol. 2, No. 1, pp. 17–34. 16 Kale, S. H. (2004) ‘CRM failure and the seven
12 Payne, A. and Frow, P. (2006) ‘Customer relationship deadly sins’, Marketing Management, Vol.
management: From strategy to implementation’, 13(September/October), pp. 42–46.
Journal of Marketing Management, Vol. 22, pp. 135–168. 17 Erffmeyer, R. C. and Johnson, D. A. (2001) ‘An
13 Day, G. (2000) ‘Capabilities for forging customer exploratory study of sales force automation practices:
relationships’, Report No. 00–118, Marketing Expectations and realities’, Journal of Personal Selling
Science Institute, Cambridge, MA. and Sales Management, Vol. 21, No. 2, pp. 167–175.
14 Maselli, J. (2001) ‘People problems’, InformationWeek, 18 Speier, C. and Venkatesh, V. (2002) ‘The hidden
9 July, pp. 35–42. minefields in the adoption of sales force automation
15 Jain, R., Jain, S. and Dhar, U. (2007) ‘CUREL: A technologies’, Journal of Marketing, Vol. 66, No. 3,
scale for measuring customer relationship pp. 98–112.
78 Database Marketing & Customer Strategy Management Vol. 15, 2, 68–78 © 2008 Palgrave Macmillan Ltd 1741-2439 $30.00