I was recently engaged in a job search in the VOC and CX space. Among other tools, I used Google Alerts and Simply Hired saved searches (which emailed me new postings every morning) with keywords to target my search results. One of the observations I made throughout this search was the very misleading job titles that are being used to describe certain positions. I saw postings for jobs with titles such as Director of Customer Experience or Vice President of Customer Experience, which to me would have been golden. Except... these titles were being used to describe positions that oversaw customer service or technical support departments. When did "Vice President of Customer Service" go out of style? Because one of my search keywords/phrases was "Customer Experience," I also happened to spot other Customer Experience titles, like Customer Experience Associate. Companies were using that title to refer to their store associates or sales clerks. That's not really appropriate, either.
I read something yesterday that reminded me of this phenomenon, and it compelled me to tweet about it (see below) and to write about why companies are using these titles now... and incorrectly, at that.
I didn't get any takers on my tweet, but I do believe that using titles like these, in the manner they are being used (as described above), really devalues or discounts the larger, more-encompassing role of a true Vice President of Customer Experience or other roles that are truly about the customer experience (and all that those roles entail). It leads to confusion and lack of clarity.
Take a look at the Customer Experience Lifecycle to the left (click the image to enlarge), and if you get a moment, read my blog post on this topic. You can see that the experience starts long before the service event. Keep in mind, too, that not every customer experience even includes a service event.
There was a great post on the 1to1 Blog about two weeks ago that nicely summed up the differences, to which I remarked: "Amen! Needed to be said!" And here I am, saying it again.
When I tweeted the article, Mark Gunn responded to it by saying:
Have you had to make this distinction to your co-workers, executives, or clients? How do we get organizations to think about these two concepts in a different way? What are your thoughts?