Customer Experience is the superset of sensations, emotions and perceptions felt by your customers before, during and after product or service use. Enterprise Customer Experience represents the people, internal processes and technology required to listen, guide and engage your customers in the digital world; all towards creating better and enhanced experiences. Designing positive experiences begins with understanding needs and wants. Seems logical right? How else can you understand what your customer’s wants and needs, if you do not listen first?
The very next part is to prove that you are listening, if actions do not result, then it is not really listening at all. Yes, in this day and age, you do need to provide proof. For, example, if you do not plan to take any actions based on what you hear, are you really listening? That said, there are many ways to show that you are listening. The first is transparency, allowing people to see inside the organization where they can witness what you are doing, often at their bequest. The second, more interesting way is to specifically give people what they are looking for, as in information, service or a product enhancement.
To customers, being open means more than simply looking through the window, but being able to walk through the front door and participate. An engaging conversation is one where all voices are heard and respected and no one is simply listening, waiting to talk. In order to improve customer experience, you, your team and the whole organization needs to convert the listening to information that can be used to collaborate, co-create and engage at a personal level with your customers. This will take analyzing the data, providing relevant, consistent content, where and when your customers want it, need it and are expecting it.
It is time to move beyond what needs to be done and why it needs to be done. Some parts of your organization are more advanced than others, some are ready and some are not. The starting point should be clear. What is less clear is exactly HOW to progress in a uniform fashion from understanding what needs to be done, to actually doing it. It is time to progress from departmental Social Media initiatives to organizational digital communication programs. These programs should have defined and coordinated objectives. As the team and understanding of the technology mature, Social CRM is next logical step, with both business and technical integration and a digitally aware customer data model. Internally, CRM will have certain objectives, but it is time to add customer centricity, directed individual engagement and customer collaboration to those objectives. Finally, the end-game, Enterprise Customer Experience. Just my name for it, I suppose, but it seems to fit.
I put together a few slides where I tried to visualize some of my thoughts. The copy is taken from a white paper we just released as well. If you would like a copy of the white paper, please just send me an email mitch.lieberman – at – dri-global.com and I am happy to forward it along.
Social Media Initiatives are too often:
- Departmental and Uncoordinated,
- Loosely defined and with soft qualitative objectives,
- Lacking strong guidance that aligns with corporate vision
- Have little or no Governance or Oversight
- Driven by metrics with unproven value (like, follow, +)
Now to progress from disjointed efforts to coordinated and structured efforts,
Social Communication Programs that are characterized by:
- Multiple, linked digital initiatives,
- Defined and Coordinated goals (across departments),
- Agreed to processes for Content,
- Modestly Mature Governance,
- Data Capture and Burgeoning Analytics,
- Tighter agility to act upon lessons learned.
It takes maturation of the organization to make this progression. It is important to not that up until now the discussion is much less about technology than it is about people and process. Once the organization has matured, it is then possible to reach enhanced customer experience through Social CRM by further integrating more baseline technology, carefully and methodically.
Social CRM sets the course for creating better Customer Experiences, through:
- Coordinated Customer Facing Communication Programs,
- Both Technical and Business Level Integration,
- Advanced Analytics that Improve Customer Insights,
- Mature, Modern, Customer Data Model,
- Personal, Customer level Interactions and Engagement.
Now things start to get very interesting. Just when everyone was comfortable with the buzzwords, we are now ready to dump the term ‘Social’. The team realizes that social is a characteristic of people. The term is dispensed with and for the purposes of Customer Experience, the CRM platform is now in charge of the digital data and used for specific purposes.
It is time to execute CRM, across the Enterprise:
- Data, information and knowledge is universally accessible,
- Content and digital assets are consistent and shared,
- Back-office to front-office Collaboration creates efficiency,
- Customer facing processes are repeatable and embedded,
- Community and Customer Collaboration are part of the platform.
Finally, it is time to complete the
Enterprise Customer Experience vision:
- Customer centricity is a reality,
- Directed engagement at the level of the individual
- Analytics are predictive,
- Customer expectations are understood and met,
- Communications are conversational and collaborative,
- The organization is highly collaborative,
- Organizational culture is mature and ready.
Complexity is not the same as complicated. To some, it might be semantics, but I do not think so. The difference might just explain:
- Why organizational silos still exist and will continue to exist,
- Why customer journey’s (and experiences) are fragmented
The difference is this: Complicated speaks to the number of elements within a system, Complex speaks to the dependence, more specifically, the interdependence between two elements or among many elements of a system.
Taken from “Complex Adaptive Systems” by John H. Miller and Scott E. Page:
“Complexity is a deep property of a system, whereas complication is not. A complex system dies when an element is removed, but complicated ones continue to live on, albeit slightly compromised.”
So What, you might say. I am creating a nuance where one does not exist, making the whole topic, well, more complex… Let me try and explain. There is child’s game that we used to play (there are few of them that fit this description actually) where in each turn the player needs to take out one block hoping that the tower does not collapse. If it collapses, you lose. In the beginning, the blocks represent a complicated system, the removal of one element does not alter the integrity of the whole. As the game progresses however, the dependence between the elements increases until the removal of an element causes the whole thing to fall down. The system progressed from complicated to complex.
Well, let’s think this from a customer journeys and customer experiences perspective. Organizations provide dozens of touch-points for their customers; in-person, phone, email, Web, Social (Facebook, Twitter, Community…) and many more. The customer experience correlates to their journey with each touch-point adding some facet to the overall experience. This could be deemed a complicated ecosystem of touch-points, take one away and the system keeps working, though not as well as it did before. Here is the problem, if you create dependencies between and among the touch-points there is a risk of the whole thing collapsing if one falls down. For example, if you use a link shortener (say bit.ly) embedded in an email newsletter that points to a YouTube video, how many failure points exist and which are in your direct control after you hit ‘send’?
What about the next generation of business, a Social Business. I myself have written and talked about breaking down the silos, collaborate with others within your organization, different departments and all that good stuff. But wait, did we just alter the risk factor? Did it get better or worse. Once the silos are broken down, and their is a dependence created, there is risk, right? A manager from another department could reassign a resource or customer service is now dependent on engineering to answer a question. As organizations become less complicated, do they become more complex? What do the dependencies now created do to the greater organization, the goals and the strategy. This is not a rhetorical question, I would like some help. I have written about both collaboration and coordination, with the later more important in this context.
What does it mean
It means simply that the interconnection points (the lines on most diagrams) are the complex things and the ones that are most important. If one of the lines is workflow, that needs careful planning and attention. If one of the lines is communication between two people, two departments or two pieces of technology make sure you understand exactly what dependencies have been created between the two elements. On the one hand, you might tightened a gap, made things more efficient, on the other hand, you might have created a risk, a single point of failure. From my vantage point, businesses have always been complicated, now they are really complex.
Please share your thoughts, thanks!
- There is a Big Difference Between Can’t and Won’t
- Stop Thinking in Two Dimensions
- No Beginning, No Middle and No End
- Rethinking the Customer Journey
- The Simplest Thing I Ever Had to Write
- Context Integration, the Future of System to System Interactions
- The Evolution of Customer Community
- The Fine Line Between Personalization and Creepy
- Experience Innovation
- Maybe We are Using the Wrong Words to Describe Collaboration
- Data, Customer Service, Reputations and Big Brands try.harrys.com/lp-welcome-bac… @Gillette and @harrys 4 hours ago
- @wimrampen uh oh, definition time :-) 1 day ago
- @dirkjandokman not assured yet :-) Design of the conversation is design of the experience, the bot is the tech part. Cc @wimrampen 1 day ago
- @dirkjandokman by definition a Chatbot is tech. If you want it not to be, then it is a ChatHuman 1 day ago
- @dirkjandokman process and design should be independent from point or type of interaction, whenever possible 1 day ago
- An error has occurred; the feed is probably down. Try again later.