Can You Solve This Customer Interaction Puzzle?
Q: What Is The Cause Of This Customer Interaction Turning Out As It Turned Out?
Do you have an avid interest in designing-conducting research, eliciting-capturing requirements, listening to the voice of the customer, or designing customer experiences? If you have this interest then I invite you to help me solve the following customer experience puzzle:
Last week, while on an average holiday shopping trip, my mother and I decided to stop by Starbucks to get a quick snack…..
When we got up to the counter, my mother placed our simple order, at which point she asked for a “tall” cup of two percent white milk. This is how the conversation played out:
“Mocha,” said the barista.
“No. Milk,” my mother repeated.
“No. Two percent white milk.”
….. I attempted to withhold my personal thoughts. Milk. You know, that white stuff you pour in the coffee? Yes, well, we want an entire cup full of that. Minus the coffee, of course.
Our barista proceeded to ask if we’d like the milk steamed, but we opted for cold. (They steamed it anyway.) Eventually, we managed to get our order straightened out, but not without a few stifled giggles.
I ask you to put your intellect and expertise into action. Please consider the situation and give an answer to the following question: What is the cause of the mismatch between the customer’s request for “milk” and how Starbucks responded to the customer’s request?
Why it is worth spending time on this puzzle? Because we are grappling with that which lies at the heart of making sense of the customer’s voice and sound experience design. It is also the reason that so many systems, including CRM systems, disappoint customers even though the designers are convinced that they have listened to the customer and designed the system to meet the customers needs-requirements.
What Explanations-Interpretations Have Been Put Forth To Date?
To date, I have come across two ways of explaining-interpreting that which occurred between the customer and the Starbucks staff. Allow me to share these with you.
The author of the story (Anna Papachristos) explains this breakdown in communication (and the resulting experience) as follows:
I’m not sure what was more baffling–the fact that no one in the coffee shop listened, or that they’ve become blissfully unaware of the basics. I understand that Starbucks stands as a status symbol more than anything, but have we really distanced ourselves from the simple things in life that badly? This barista’s mistake may have been the result of a random miscommunication, but her confusion was nothing short of hilarious.
Don Peppers in his post (How To Deal With Customer Variability) sees the same situation in terms of variable customer needs-behaviour coming up against standardised processes and operations:
Starbucks, like the roadside diner and any other business, tries to maintain quality and control costs by standardizing processes and operations. Routine tasks, if they can’t be automated, are at least handled in the same way by every employee.
But customers are all different. They want different things – different sizes of products, different delivery dates, different specifications for services, and so forth.
Variability like this is something Frei and Morriss call “customer chaos,” and they suggest it can be managed in two basic ways: either by eliminating it, or by accommodating it. If you choose to eliminate variability, you will generate more efficiency. If you choose to accommodate it, you will generate better service.
My Take On This Interaction?
p>I do not find myself in agreement with the author (Anna Papachristos). Nor do I find myself in agreement with Don Peppers. I propose to share my answer to this customer interaction puzzle in a follow up post – hopefully after some/many of you have put forward your answers by commenting.
Posted on January 22, 2014, in Case Studies, Customer Experience, Customer Service and tagged "milk", communication, customer experience, customer interaction, customer service, customer variability, Starbucks. Bookmark the permalink. 5 Comments.