Save A Penny, Lose a Customer

It’s amazing to me that organizations and people still miss the basic premise that underlies any successful business and that is good customer service.

Indeed all the innovation and technology in the world will not make up for the common business sense in putting the customer first.

Whatever happened to the customer is always right?

One of the most frustrating customer experiences is often associated with how companies routinely mishandle customer calls. We all know the shtick all too well by now:

  • The phone rings off the hook in the customer call center—why isn’t anyone answering?
  • If the phone is answered, very likely, the call is handled by automated call telephony—and you end up in a maze of instructions and options from which quite frankly, you may never return.
  • If you are so fortunate as to actually get to a real-live customer service representative, they won’t identify themselves—except with a first name--or provide a direct contact number to reach them should you get disconnected or need to follow up with them.
  • If you can identify who you are actually dealing with, you may quickly realize that you are talking to someone who is likely resident in another hemisphere and you may be unable to understand or effectively communicate with the company representative on the other end of the line (whose primary language is not your own).
  • If you are able to actually communicate with each other—what did you say?—you are likely to hear all sorts of gobbley-gook policies and excuses for why they can’t resolve your service request, need or complaint.
  • If you argue, raise your voice in frustration or ask to speak to a supervisor, you are likely to get “accidently” disconnected and you go back to go and cannot collect $200.
  • If you manage to get to a supervisor, the supervisor may throw you a bone and give you a partial win or more likely will stand firm and tell you to “talk to the hand, cause the face ain’t home.”
  • If you threaten to take your business elsewhere, you will have to place a call to another customer call center and start from step one all over again.

This is NOT a customer-centric enterprise architecture for an organization—it is almost the furthest thing from it aside from going out and actually paying customers to go use a competitor’s products or services instead of their own. This customer service-NOT approach is the death of our national competitiveness and represents the end of life for an organization and any individual employing it.

The Wall Street Journal, 24 March 2009, has a review on a book titled “Your Call Is (not that) Important to Us” by Emily Yellin who hits this right on the head.

“It is one of the most maddening ordeals of modern life. You are having problems with a product or service, and so (fool that you are) you call a customer help number, only to be greeted by a cheerfully inept or robotically indifferent voice at the end of the line.”

So why do organizations behave in this self-defeating, anti-customer fashion?

It’s called pinching pennies. Or penny wise and dollar foolish.

“Companies naturally try to keep costs down, sometimes rating the performance of their harried call-center workers by the number of calls they log, not by how well they resolve callers’ complaints…or companies move their help desks to countries where costs are low but accents are impenetrable. Or they switch to computer systems that leave already unhappy customer shouting their responses at an unresponsive machine.”

This is emblematic of the short-term focus on quarterly profits and share price at the expense of the customer satisfaction, service, and long term retention goals. The result: piss-poor customer service!

That’s why as enterprise architects, we need to ALWAYS start, end and follow every point in between with the customer needs. So in terms of EA what can we do to improve service delivery?

  • Focus on organizational performance goals and put customer satisfaction and retention at the top of those goals.
  • Align technology solutions and investments to deliver on the customer experience.
  • Don’t automate the customer out of the equation by removing genuine listening, empathy, and problem resolution.
  • Add a human-capital perspective to enterprise architecture frameworks to focus on best practices, targets, and transition plans to manage both the humans that work in the organization and to satisfy the human beings who are our customers. Human-to-Human interface!

Generally speaking, technology is known as an enabler for efficiency and effectiveness. Let it be first and foremost a means to better customer experiences. That is what is going to keep them coming back for more or heading to the exits.

Why We Miss the Planning Mark

We’ve all been there asking why we missed the signs while others saw them head-on and benefited in some way. This happens with financial investments (e.g. I should’ve sold before this recent meltdown like my good buddy did), business opportunities (e.g. I should’ve opened up a chain of coffee stores like Starbucks before Howard Shultz got to it), military strategy (e.g. we should’ve seen the attacks on Pearl Harbor and 9-11 coming and been better prepared to try and stop them) and other numerous “should’ve” moments—and no I’m not talking about that” I should’ve had a V8!”

Why do we miss the signs and misread information?

Obviously, these are important questions for IT leaders, enterprise architects and IT governance pros who are often managing or developing plans for large and complex IT budgets. And where the soundness of decisions on IT investments can mean technological superiority, market leadership and profitability or failed IT projects and sinking organizational prospects.

An article in MIT Sloan Management Review, Winter 2009, provides some interesting perspective on this.

“Organizations get blindsided not so much because decision makers aren’t seeing signals, but because they jump to the most convenient or plausible conclusion, rather than fully considering other interpretations.”

Poor decision makers hone in on simple or what seems like obvious answers, because it’s easier in the short-term than perhaps working through all the facts, options, and alternative points of view to reach more precise conclusions.

Additionally, “both individual and organizational biases prevent…signals from getting through” that would aid decision making.

How do these biases happen?

SUBJECTIVITY: We subjectively listen almost exclusively to our own prejudiced selves and distort any conflicting information. The net effect is that we do not fully appreciate other possible perspectives or ways of looking at problems. We do this through:

  • Filtering—We selectively perceive what we want to and block out anything that doesn’t fit what we want to or expect to see. For example, we may ignore negative information about an IT investment that we are looking to acquire.
  • Distortions—Information that manages to get through our mental and emotional filters, may get rationalized away or otherwise misinterpreted. For example, we might “shift blame for a mistake we made to someone else.”
  • Bolstering—Not only do we filter and distort information, but we may actually look for information to support our subjective view. For example, “we might disproportionately talk to people who already agree with us.”

GROUPTHINK: “a type of thought exhibited by group members who try to minimize conflict and reach consensus without critically testing, analyzing, and evaluating ideas.” (Wikipedia)

“In principle, groups should be better than individuals at detecting changes and responding to them. But often they are not, especially if the team in not managed well, under pressure, and careful not to rock the boat.”

Interestingly enough, many IT investment review boards, which theoretically should be helping to ensure sound IT investments, end up instead as prime examples of groupthink on steroids.

Concluding thoughts:

If we are going to make better IT decisions in the organization then we need to be honest with ourselves and with others. With ourselves, we need to acknowledge the temptation to take the simple, easy answer that is overwhelmingly directed by personal biases and instead opt for more information from all sources to get a clearer picture of reality.

Secondly, we need to be aware that domineering and politically powerful people in our organizations and on our governance boards may knowingly or inadvertently drown out debate and squash important alternate points of view.

If we do not fairly and adequately vet important decisions, then we will end up costing the enterprise dearly in terms of bad investments, failed IT projects, and talented but underutilized employees leaving for organizations where different perspectives are valued and decisions are honestly and more comprehensively vetted for the betterment of the organization.

If we shut our ears and close our eyes to other people’s important input, then we will miss the planning mark.

What It Means to Get Madoff-ed

"Saying he was 'deeply sorry and ashamed,' Bernard Madoff pleaded guilty Thursday to pulling off perhaps the biggest swindle in Wall Street history and was immediately led off to jail in handcuffs to the delight of his seething victims. Madoff, 70, could get up to 150 years in prison when he is sentenced in June." -Associated Press

In enterprise architecture, defining data terms and usage is very important. So everyone is talking the same language!

Well with Bernie Madoff's plea of guilt to all 11 charges against him today involving a $50 billion Ponzi scheme (named after another financial crook), I believe are witnessing the birth of a new word in the English lexicon.

Here on in, Madoff will mean:

-verb
to swindle, cheat, defraud, deceive.

-noun
a person who swindles, cheats, defrauds, and deceives.

Congratulations Bernie, you lousy Madoff!

Another way to think of this new word...
he MADe OFF with a lot of people's hard-earned money.

We Need A Grand Vision—Let It Be Smart!

We can build systems that are stand-alone and require lots of hands-on monitoring, care, and feeding or we can create systems that are smart—they are self-monitoring providing on-going feedback, and often self-healing and they help ensure higher levels of productivity and up-time.

According to the Wall Street Journal, 17 February 2009, smart technology is about making systems that are “intelligent and improve productivity in the long run…they [makes use of] the latest advances in sensors, wireless communications and computing power, all tied together by the Internet.”

As we pour hundreds of billions of dollars of recovery funds into fixing our aging national infrastructure for roads, bridges, and the energy grid—let’s NOT just fix the potholes and reinforce the concrete girders and have more of the same. RATHER, let’s use the opportunity to leap forward and build a “smarter,” more cost–effective, and modernized infrastructure that takes us, as nation, to the next playing-level in the global competitive marketplace.”

- Smart transportation—the “best way to fight congestion is intelligent transportation systems, such as roadside sensors to measure traffic and synchronize traffic lights to control the flow of vehicles…real time information about road conditions, traffic jams and other events.” Next up is predictive technology to tell where jams happen before they actually occur and “roadways that control vehicles and make ‘driving’ unnecessary.”

- Smart grid—this would provide for “advanced electronic meters that send a steady stream of information back to the utility” to determine power outages or damage and reroute power around trouble areas. It also provides for consumer portals that show energy consumption of major appliances, calculate energy bills under different usage scenarios and allow consumers to moderate usage patterns. Additionally, a smart grid would be able to load balance energy from different sources to compensate for peaks and valleys in usage of alternative energy sources like solar and wind.

- Smart bridges—this will provide “continuous electronic monitoring of bridges structures using a network of sensors at critical points.” And there are 600,000 bridges in the U.S. As with other smart technologies, it can help predict problems before they occur or are “apparent to a human inspector…this can make the difference between a major disaster, a costly retrofit or a minor retrofit.”

Smart technology can be applied to just about everything we do. IBM for example, talks about Smart Planet and applying sensors to our networks to monitor computer and electronic systems across the spectrum of human activity.

Building this next level of intelligence into our systems is good for human safety, a green environment, productivity, and cost-efficiency.

In the absence of recovery spending on a grand vision such as a cure for cancer or colonization of Mars, at the VERY least, when it comes to our national infrastructure, let’s spend with a vision of creating something better—“Smarter”--for tomorrow than what we have today.