Customers Feel the Difference, Not the Average

Think about the metrics in your company: most likely, the metrics that you are accountable for and report on are reported as averages.  Am I right?  Perhaps, those metrics are averages and are lagging or leading, depending on the context.  

But, from the customer’s perspective, it is always important to remember this axiom: The Customer Feels the difference in the experience, not the average.  If you stop to really think about it, the concept of an “average experience” doesn’t exist.  Yet, we report on statistical means.  

The distinction, from a mathematical perspective, is simple: it’s about variation.

All processes are subject to some variability.  More common explanations of variability describes variability as either Common-Cause or Special-Cause.  The former is easiest explained as expected variation within a process that is produced by the process itself.  The latter, on the other hand, is variation that is produced by the process but is assignable to some outside force.   From a Queueing Theory perspective, another way to think of variation is by stratifying variation based on predictable and unpredictable.

Below is a Variability Tree, showing Predictable and Unpredictable Variability. This distinction is important because managing either type of variability will be different:

Most systems will show evidence of variability, as explained in the picture above; some will show both types, but typically one type will dominate.

For processes where arrivals are “bursty” or unpredictable, then the tools of Queueing Theory makes sense to apply; but for processes where the arrivals are predictable or seasonal, then it might make sense to apply the tools of Build-Up Diagrams.

Service Variation

I want to distinguish Service Variation for a moment.  Now, take the ATM example above.  Suppose that customer_a is serviced one way on day_1 and customer_a is serviced a different way on day_2.  This type of service variation, felt by the same customer on two different days, can also be said to be “inconsistent”, from the customer’s perspective.  The customer expects consistent service — the service might not be delightful — but at least it’s consistent. There is a difference and increasing consistency is the same thing as saying “reducing service variation”.  

Now, from a marketing-spin, reducing variation does not mean we do not differentiate or segment our market.  We can absolutely still do that and should. But, the way we service our customers ought to be consistent, but we can differentiate and segment.

My friend, Joe, recently posted on how to treat customers better.  Here’s what he said, which reinforces my post today on variation, but his focus is on the more human side:

  1. Make it easy for customers. It seems these days that a customer never knows who to speak with regardless of the nature of their inquiry. It’s imperative that you make it simple for the customer to speak with the proper party depending on their concern. Often it seems that the customer has to speak with different departments in a company to find the answer they want. Eliminate the need for the customer to travel through the cross section of your company to receive proper attention.
  2. Limit who attends to a given customer. It’s unprofessional to pass a customer off to another representative if you’ve already been dealing with them. This makes the customer feel unwanted or that they’re not dealing with the best company. Whoever starts the process with a customer should be the one who finishes it.
  3. Chop down the phone tree. There’s nothing more frustrating for a customer then going to a company’s website and seeing a litany of phone numbers. Invariably the one the customer chooses isn’t going to bring them to the proper department. It can be difficult to figure out how you can narrow down all the different numbers your company may have, but it’s necessary that you make it easier for the customer to contact the right person.
  4. Own up to your mistakes. There is nothing more frustrating for a customer than when you’re just looking for someone to admit they were wrong. If you make a mistake then it’s crucial that you correct the error and admit that you were wrong. This will leave the customer with a good feeling about his or her experience and won’t turn them away from doing business with you in the future.
  5. Humanize your call center. There is often pressure on the people you have answering phones to handle a call in a certain amount of time and to handle a minimum number of calls in a given day. Let your representatives be real human beings and let them attend to a customer’s complaint or issue in a manner that leaves the customer feeling good. Ultimately, this is more important than statistics.

How To Manage Variability

When reducing or eliminating variation is not the answer, then managing it is the next best thing to do.  Below is a simple table that shows the impact of variability on a system.  I built this diagram quickly, but you can modify this table for your particular process; I’ve made it general enough so that you can apply it to your particular situation:

I’m using the term “Inventory” in a generic way here — it can mean people (patients) or actual things.  For example, when the Waiting Room Size is bigger, then output can increase but there’s also an increase in the amount of patients in the room (patients = inventory).  Use this trade-off table as it applies to your process.

It’s About the Customer

It’s important to always remember that it is Variation that people feel, not the average.  Managing the variability in your process takes work and some knowledge of tools that are pragmatic and helpful.  The “average” is an inadequate measure and is not descriptive of what the customer is feeling.  If the customer is to benefit, we must take action against variation through reducing it or eliminating it and then managing it.

+++++

Please find originally-written articles on Queueing Theory below:

For a few articles on Operations, lean and six sigma, please visit the links below:


Short URL: http://bit.ly/FZFo

Share This Post:



  • Digg
  • Twitter
  • Facebook
  • Google Bookmarks
  • del.icio.us
  • StumbleUpon
  • LinkedIn
  • MySpace
  • HackerNews
  • Reddit
  • Live
  • email

2-pizza teams (10)
3 C's (3)
37signals (1)
5S (38)
A3 Report (9)
adoption (7)
agile/software (59)
ajax (4)
amazon (53)
apple (3)
apple iphone (7)
axiom (3)
Aza Raskin (9)
backcountry.com (2)
berlin (1)
bill gates (1)
bill marriott (1)
blog tag (1)
book reviews (4)
bullwhip effect (5)
business (397)
business plans (3)
busm361 (13)
BzzAgent (12)
call center and queueing (11)
car buying (2)
Carbonite (1)
change management (5)
chicago (1)
click fraud (1)
click-to-ship (21)
clocky (2)
colin powell (2)
community (2)
company interviews (18)
company interviews (6)
complexity (32)
costs (8)
culture (7)
customer experience (10)
customer obsession (52)
customer recovery function (1)
customer segmentation (8)
customer service (17)
design thinking (14)
digg (4)
drum-buffer-rope (38)
dublin (1)
dynamic systems (24)
eBay (6)
economics (3)
efficiency (4)
ethnography (29)
family (18)
featuritis (15)
flexibility (1)
forecasting (2)
four performance dimensions (2)
Fun With The 2×2 Matrix (1)
game theory (7)
Gemba (67)
genchi genbutsu (68)
general (135)
germany (1)
google (15)
Gretchen Rubin (1)
heijunka (65)
holidays (1)
hoshin kanri (1)
how to be a human (1)
IDEO (2)
image uploading (1)
interviews (4)
iphone (5)
ishikawa (69)
IT at Toyota (67)
jason fried (1)
just-in-time (4)
kaizen (4)
kanban (46)
law of instinct (1)
Leadership (46)
lean (167)
Lean Consumption Maps (98)
learning curve (1)
licketyship (1)
mark cuban (1)
martin luther king (1)
mary poppendieck (1)
metrics (73)
microsoft (6)
milton friedman (1)
moving average (1)
muda (68)
nba fines (1)
net promoter score (nps) (1)
obeya (39)
Off-Topic (1)
onstar (1)
operations (108)
pageviews (3)
pareto principle (39)
patent (1)
peanut butter manifesto (2)
philosophy (3)
Poka-Yoke (6)
poppendieck (3)
powerpoint sucks (2)
private equity (4)
process measures (6)
product development (20)
productivity (4)
quality (41)
quasimodal design (1)
queueing theory (41)
Raffle (1)
rational choice (2)
regression analysis (18)
respect for people (6)
root cause analysis (60)
sarah+palin (2)
seth godin (1)
simplicity principle (10)
six sigma (128)
snowboarding (2)
social media (3)
spam (1)
statistical process control (46)
strategy (46)
suburban (1)
supply chain (24)
takt time (8)
teaching (2)
team size (9)
technology (104)
the beer distribution game (1)
The Happiness Project (1)
the profit tree (7)
The Visual Factory (11)
theory of constraints (41)
time (2)
timeline (3)
tony+hsieh (11)
toyota (75)
travel (1)
trump bankruptcy (1)
turnaround (5)
twitter (8)
uspto (1)
utah deal flow (2)
variation (69)
venture capital (1)
Visual Management (11)
waste (59)
website traffic (2)
Wing Chun (2)
wisdom of crowds (1)
wisdom teeth (1)
word-of-mouth marketing (18)
yahoo (2)
zappos.com (12)
zero defects (3)

WP Cumulus Flash tag cloud by Roy Tanck and Luke Morton requires Flash Player 9 or better.


If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.

Comments

Nice article – very thoughtful. I posted some thoughts on how to address some of the issues you raise – like first contact call resolution – in a series I wrote on 21st Century Customer Experience.
Enjoy
JT

Author of Smart (Enough) Systems

Thanks for the link!

Your article rings true: customers are individuals and their experiences are personal. Although the aggregate of your company’s performance may be an acceptable average, there are still customers down in the trenches who aren’t completely satisfied.

Leave a comment

(required)

(required)


Additional comments powered by BackType