Abbott and Costello are probably my favorite comedy double act of all time. Strike that, they are my favorite comedy of all time. I used to watch them every Sunday morning at 11am growing up. Within that context, easily my favorite routine, possibly their most famous is their baseball routine; Who's on First. The general premise behind the exchange has Costello, a peanut vendor named Sebastion Dinwiddle, talking to Abbott who is Dexter Broadhurt, the manager of the mythical St. Louis Wolves. However, before Costello can get behind the plate, Abbott wants to make sure he knows everyone's name on the team...
Fast forward 30 odd years, and the new double act seems to be Customer Relationship Management (CRM) and Customer Experience - you can add the 'Management' part if you are so inclined. It seems that every conversation that starts with CRM these days, ends with Customer Experience. But they are strange bedfellows, because one is an Inside-out view of the world and the other is an Outside-in view. Similar to Abbott and Costello, all we want to know 'everyone's name on the team'. It sometimes feels like the definitions conversation many have had during the past 3 years or longer. Also, the whole 'relationship' bit is quite contentious.
Every conversation about CRM should consider customer jobs to be done (JTBD, thanks Mark Walton-Hayfield for that thought), thus there is an experience happening, in some way shape or form... But, not every experience needs to consider CRM (I touch on this in a post written last year). This is hardly a new conversation, when I began thinking about this, I reached out to my trust network and Paul G came back with the following from CRM at the Speed of Light's very first edition which came out January 2001 and is on page xvii of the introduction. Paul noted that this was "LITERALLY the first time I EVER talked about a definition of CRM in any way at all":
"Okay, enough of this. So, you ask, what is CRM? What is the purpose of this book on CRM technology and the Internet? The more substantial definition of CRM is being left to Chapter 1. However, I'll throw in a short, distilled, filtered definition (120 proof) of CRM to begin to satisfy your terminological blood lust. CRM is a complete system that (1) provides a means and method to enhance the experience of the individual customers so that they will remain customers for life...."
(Paul mentioned to me that he has some thoughts that he will be sharing directly in about a month's time)
Cause and Effect
CRM can drive customer experience, but customer experience cannot drive CRM. Customer Relationship can be impacted by the experiences had with the company (Thanks Scott Rogers for that thought) That said, lessons learned and listening to voice of the customer can impact what data is stored and how to act, of course. CRM is an enabling strategy and technology, used by people inside the organization. Where CRM gets a bad rap is when people believe that CRM and SFA (Sales Force Automation) are the same thing. 'I don't know, third base'. They are not the same thing, SFA is an inward focused, manage the pipeline, manage sales process, manage money and very often does not do much to provide external value. Customer Experience is an SFA afterthought, it just is!
How about Social CRM, does that get us closer? Customer Experience and Social CRM are not the same thing, either (again, my blog from last year). I am not going down the path of definitions, been there, done that. Social CRM is about a specific response, by companies because customers now want to have a say in the boundaries of the customer / company conversation. Social CRM takes into consideration how, when and where a company engages in the conversation will impact the experience of the customer. Interestingly, many examples of customer service done right could be called service experience, customer experience or Social CRM, take your pick, there are supporting arguments for any of the above. I also believe that the word Social is over used and more often than not people actually mean digital, topic for another day.
What about Design?
Proper customer experience design should focus (at least in part) on what good CRM tells you to do. For example, if you are using CRM to manage complaints, the customer data should specify the type of response, the channel of the response and the timing of the response due to the customer. This is not customer experience, is it? A few of the larger analyst firms have so closely linked CRM and customer experience that a conversation about one cannot really be had without the other. Well, that is not totally true, people talking about customer experience do not seem to jump into a CRM conversation, but those talking about CRM quickly jump into a customer experience conversation, hmmm....
Something I have said a few times, you can manage data and you can manage process. Not so sure you can manage customers and I am confident that you cannot manage experiences. We can simply do our best to manage what we would like the experience to be, we can design it and pay attention to detail, it is what the customer perceives it to be - period. How does, or should CRM play into the design process? For example, where does automation fit in, is automation a bad word? It sounds impersonal. But as Esteban Kolsky shared, people simply want the right answer and they want it now:
"For the first time in more than 15 years, automation through multiple channels is growing and the satisfaction scores are rising steadily. People are liking what they get, for the most part, and companies are improving how they do things. In the early 2000s, purchasing a ticket by phone using United's telephone network would take over one hour and involve an innumerable number of steps; today it can be done in 5-10 minutes in far fewer and easier steps (mostly thanks to speech recognition)."
Just remember, if you want to know 'Why' - He is the left fielder... The answer is 'Because', the center fielder.