The AI-Powered Enterprise. Seth Earley

and blade to allow for effortless cutting and chopping, and instructions on how to best care for the knives (wipe with a clean damp cloth and never put them in a dishwasher or toss them into the sink with dishes and silverware).

      At each stage of the process of buying the knives, my customer experience was seamless and easy. Very little got in the way of my becoming a satisfied customer. I like these knives. My wife likes them, too. And I like the company that sold them to me—unlike the retailer who drove me nuts returning $12 worth of granite cleaner, or the bank that tried to sell me on a financing offer I’d already taken them up on.

       CUSTOMER EXPERIENCE SUCCESS DOESN’T HAPPEN BY ACCIDENT

      Customer experience (CX) is hard to get right and easy to get wrong. It’s not a question of will: everyone wants to be good to the customer (except maybe Ryanair). It’s not even a question of investment. It’s a question of the proper integration of technology. A well-designed customer experience accounts for the customer’s needs and all possible events the customer may experience (as the Kamikoto knife ads and delivery did). It allows for the possibility that things can go wrong and delivers an acceptable experience accounting for those cases (as the granite cleaner retailer didn’t). And it leverages all the knowledge that the company has about an individual, even if it’s held in different information systems (as the bank’s system obviously didn’t).

      Customer experience is the sum total of all of the experiences related to your brand. It starts with the first marketing impression; expands with the customer’s increasingly detailed understanding of the features, benefits, price points, style, and other selection considerations; and continues through the actual purchase, acquisition, usage, maintenance, and post-purchase relationship.

      During this lifecycle, in which prospects become first-time customers, then repeat customers, and then loyal brand advocates, they will have a series of interactions online and off-line. They may talk to friends or colleagues, conduct research, look for recommendations and online reviews, talk to customer service reps and salespeople, visit stores, test products, and investigate competitive products. In this process they also experience a range of emotions: they may become confused on a website or by instructions, read conflicting reviews, become excited by the prospect of purchase, become disappointed, get frustrated, feel happy about getting a good deal, or become angry about not getting a better deal. They may experience regret at missing an opportunity, or buyer’s remorse after making a purchase. They may be delighted by an unexpected level of customer service or attention to their needs, or they might be freaked out by overly personal service that feels intrusive. All of these emotions, interactions, perceptions, and events are part of the customer experience.

      For CX design to work right, the brand must avert countless opportunities to fumble the sale by using comprehensive planning and immaculately consistent messaging that eliminates all potential friction. AI can help, but if the supporting processes and systems are not solidly aligned and integrated, no AI can enable a friction-free experience.

      There are now many more dimensions to a successful engagement strategy than there were before people went online, including social media, content marketing, cross-channel customer experience, big data, and analytics. We’ll touch on digital marketing as well, because much of the data used to power these experiences comes from new marketing technologies. (We’ll explain the role of the digital marketer in more detail in the next chapter.)

      In this chapter, we’ll explore how problems can get in the way of a systematic approach to customer experience and describe the eventual solution: the high-fidelity journey map and the plan for applying it to your technology. The result is a technique for applying the ontology to customer experience in your marketing technology stack and making more thoughtful decisions about technology. We will show you how to use the customer journey to make marketing technology plans, blueprints, and investments.

      Let’s get started by looking at the fundamental challenge: how can you move quickly and personalize experience at the vast scale that’s necessary in the enterprise?

       Ontology Enables Agility and Scalability to Coexist

      Enterprises interacting with customers pursue two conflicting goals: agility and scalability. The newly integrated worlds of customer experience and marketing demand the ability to react and respond quickly and efficiently across departments, tools, platforms, and business functions. They also require organizations to globally manage a significantly larger volume of personalized and localized content than ever before. The customer experience emerges from this, since it is the sum total of all interactions: with marketing, with sales, with customer service, and throughout the organization.

      The first goal is agility—or more specifically, agile execution. Agility is crucial as the pace of business and markets accelerate. Organizations must keep up with changing priorities, strategies, and execution challenges. What is working and what isn’t? Where are resources focused? What do market research and customer data tell us, and how should organizations respond, adapt, and evolve? What tools are most appropriate to solve engagement problems?

      The second goal is scalability. Enterprises must be able to scale sophisticated and nuanced marketing, product, and service initiatives across platforms and channels, and operate them efficiently to support customers at every stage. This goal conflicts with agility in that it typically entails coordination of many tasks and processes that cannot be completed quickly.

      How can you harmonize these two goals? The correct governance structure combined with consistent organizing structures provided by the ontology is the key. A fully integrated, holistic, cross-department execution perspective is most effective with digital technologies based on a consistent architecture—and managed with reference to the ontology. Agility is based on reacting and adapting. Scaling requires consistency and standardization. It is only through the use of an ontology that the two goals are no longer at odds with each other.

       Complexity and the Customer Experience

      As more customers transact most or all of their business online, organizations are forced to stitch together a seamless customer experience from what in many cases is a series of disparate systems.

      For example, we once conducted a customer experience project for a financial firm using more than 50 platforms for managing customer investments. Customers could conduct some transactions predominantly online. For more complex investment redemptions, changes in beneficiary, or transactions with tax implications, the customer needed to call and speak with a customer service representative. Of these tasks, some required transfers to specialists for callbacks, and others required the call center agent to interact with a back-office transfer agent. In extreme cases, the transfer agent required support from a special “hotline” of top-tier specialists who had even greater levels of training, expertise, and system access.

      Imagine the customer experience this generated: beginning a process online, running into a roadblock, searching for help, sending an email request, calling in, being transferred, getting placed on hold, leaving messages, calling back, having to provide basic identifying information repeatedly, and so on. Rather than a smooth paved highway, that journey was filled with bumps, detours, and side ramps that slowed the process, increased support and transaction costs, and damaged the customer relationship. Each step and task could require a different department, system, process, technology, cost center, or procedure. So much for a smooth, seamless journey. Disconnected internal systems and processes destroyed it.

      This type of poor experience will likely result in customer ill will, higher support costs, missed opportunities, and lost business.

       Reducing the Customer’s Cognitive Load

      We have all been transferred from department to department and have had to repeat account information and security questions. We have all dealt with confusing and maddeningly unhelpful call trees (press 1 to be annoyed, press 2 to be really annoyed, press 3 to be really, really, annoyed . . .) while yelling “Operator!” and frantically pressing “0”. Some of us have even tried to return granite cleaner and wasted fruitless hours on the task.

      In theory, the customer experience