Archive

Archive for the ‘Customer Experience’ Category

There is a Big Difference Between Can’t and Won’t

July 18, 2013 3 comments

A series of recent experiences on the customer side shed light on what I believe is a growing problem, possibly made worse by the public nature of communications – or possibly just poor grammar.

Cannot or Can’t is an expression of inability or incapacity – “I can’t take the garbage out”

Will not, or Won’t is also deliberate choice not to act – “I won’t take the garbage out”

For those of you with kids, those phrases are really quite different if they are used in response to “hey, would you please take out the garbage”. My reaction would be (has been?) very different in each case. Yes, I realize that some kids will use improper grammar and use one, and actually mean the other, so please look beyond that point.

When someone in customer service says “I cannot help you”, I believe that what they often mean is that they won’t help you.  However, if those words are used, while they might be honest, they might incite a much stronger reaction. Think offering a hotel voucher due to a delayed flight, or a refund for a poor experience or some other scenario. Read between the lines of ‘ I could help, but I am choosing not to help, so I won’t’ – yeah, probably not going to fly.

The unfortunate use of “Can’t” is when a subordinate is acting as a face for a more senior person or larger organization. Is this an act of proper deflection, a way to defuse the situation? “My boss says I can’t” Which is a proxy for, my boss can, but won’t and I will get in trouble if I let you talk to him (this exact scenario happened to me last week).

This may simply be a game of semantics, but it is a bit more complicated when the social web becomes involved. I cannot think of many more examples, or maybe I simply won’t try 🙂

Thoughts?

 

Advertisements

Rethinking the Customer Journey

Funny thing about customers, they do not seem to follow a Map.

In the good old days, if you wanted to plot a course, you needed a map; a physical piece of paper with roads, highways, streets and avenues written in different colors, big fonts and a picture of a compass near the corner. Unfolding a map was easy, closing it back up the same way was really hard.

When you traveled to a new city, you needed a new map. When you visited that same city again four years later, you needed a new map again (because the previous map was carefully put in a spot you would not lose it — it is still there).

When traveling with the family, the course was carefully plotted; stop here, visit there, spend the night … right about … here! Somehow it became a journey an adventure, more than just a trip.

If you commute to work every morning, you do not need a map, well, not usually. The route is the same each day, unless there is traffic, then the commute becomes an adventure, with plan B and C close at hand. There are highs — a hidden restaurant or rainbow out the window, and lows — traffic, construction, a snowstorm. Some things can be predicted, some cannot.

Customer Journeys are not Static

A funny thing about customers, they do not often follow a map. The customer relationship with their vendor or service provider, from first touch, to purchase and support is a journey. Some portions can be predicted, some are hard to predict. Even if you had all the correct data, personal information and preferences, what would you do? Is it possible to manage the customer journey?

Each customer has a unique channel preference, web search, community, social media, talking to friends, talking on the phone, sending an email or browsing through the store. Some like one of the above, some like all of the above. Do you plot their course, push them in a certain direction? It might be easier for you, but is it easier for them?

We as individuals like to be treated as, well, individuals! Today, we live our lives in a high gear, always running and fighting against the clock, time never seems to be our friend. We hate to read long emails, but we like blogs (why is that?). Listening to telemarketing calls is annoying and we skip commercial ads by time shifting. When we go out to the store talking with shop staff is not a priority.

So, if we feel that way as individuals, why do we assume in our professional role that things will be different? Why don’t we follow the basic “don’t do to others what you don’t want done to you”?

Planning the Journey Versus Adapting to Course Correction?

With volumes of data available to you, telling you and your team exactly where customers went, how long they stayed on a page, what they searched for, giving insights into likes and dislikes, the question should be, “what are you planning to do?” [with all this data]. The information collected through all the touch-points with all the customers and all the transactions that they have with you must be leveraged to get into one point of personalizing the experience and get the most out of the relationship. This, however, is not managing the journey, nor the experience.

This is simply trying to make each journey, each experience along the way better and more meaningful.

In the past and unfortunately in the present the CMO and CIO do not quite understand each other. It is a bit like the CIO is building the roads and the CMO are building the attractions. What good is one without the other?

CMO and CIO should be close partners, friends, allies and peers. They should both work together to get the personalization of brands and the to leverage the experience of their customers. They can only achieve that by combining the communication channels with the right information at the right point in time — this is called context integration. The communication should be tailored to each customer, based on all the information that the brand collected about each customer. And the information should be stored and worked in every experience that the brand has with its customer.

It is not about managing the experience or controlling the journey. It is about understanding your customers and the roads they like to travel. Brands can only be successful in the future if they adopt new strategies to provide value along the journey at each step and enhance the experience for their customers and they can only achieved that, by listening, learning, engaging and understanding.

This post was written with the help of Jorge Teixeira da Silva, Head of BI at DRI, has over 20 years of experience working in CRM and BI. Jorge spent time at TMN, Portugal’s largest mobile operator. Jorge adds a layer of analytics to several projects, directly via BI and also embedded in CRM and BPM based projects. It is reposted from a submission to CMSWire

Context Integration, the Future of System to System Interactions

April 22, 2013 1 comment

Context integration is the future of system to system interaction. By prioritizing relevance, customer needs and jobs-to-be-done, context is the reason to operationalize big data.

Definition: Context integration is the instantaneous combination of information and process integrated at a point in time, location, to the right person, on the right channel and on the right device.

During the past 20+ years, the way in which system and/or application integrations have been conceptualized has not really changed all that much. Sure, it is possible that I am being overly simplistic, but up until now, there have been only two types of integrations process and data. Yes, the protocols have changed, APIs, REST, SOAP – pick the acronym, and designs changes (spoke and hub, point-to-point, bus,etc.,..). However, what is often assumed is that a person will make the determination as to why a particular data element is on a screen, or not. Now, there is too much data, too much information it is time to refine the process.

Data Integration

Data movement in one direction is the easiest (not always easy, mind you) type of integration. Yes, there are nuances, but overlooking these nuances puts the complexity on the low end of the spectrum. One directional data integrations are typically read-only (or a copy). For example, taking data out of an operational system and putting it into a reporting system (I am not talking about transforms just yet). If you desire the data more quickly, say real-time, slide the complexity to the right a bit. Want to be able to write/update and have this reflected in the source system; bidirectional, slide the scale bunch more to the right.

Action item: we need to progress from data integration to information integration, there is too much data, people need information.

Process Integration

Process integration often require detailed use cases, user scenarios and can often be quite complicated. Process integration is best described by old school triggers. Something happens in system A, but the users on System B need to be both alerted, they need to do something and hey need to know what to do. Too often, this type of integration ‘channel jumps’ and the recipient receives an email, text or page in order to go take some action, in some other core system. These types of integrations take place in everything from sales, to support, operations and marketing, as well as everything in between.

Similar to the data integration conversation, when it is one direction and the originating system does not need to be notified upon completion, complexity is reduced. Now, if there are multiple process flows in the secondary system, and each is complex and the originating system needs to be aware at each stage (think credit check, for example), slide the complexity scale a bit to the right some more.

Action item: We need to move beyond the task list of things to do, to being told what to do, how to do it and when to do – why? only if asked.

What does Context Integration Look Like?

As stated above, context integration is information plus process, it is real-time, but may or may not be bidirectional. What I mean is that communication is bidirectional, but it might not be operating on the same data. Delivering the right information to the right person at the right time is hard, just start by sliding the scale way way to the right. For starters, there is now a third system involved within each integration scenario, the analytics engine. Breaking it down further:

  • Information equates to ‘what’,
  • Process equates to ‘where’ and ‘how’;
  • Context equates to ‘why’, as-in ‘why is this important to me, now’?

In order to accomplish this feat, we need more insight. We need to spend a bit of time translating data into information, processes into specific tasks and actions and help the user to understand why something is displayed or being done. In a very real way, right time information may also be considered to be proactive, as expectations are low in this area, but changing rapidly.

The two primary systems and their users need intelligence, something that has been done by humans, until now. The possibilities are awesome, the complexity enormous, the risks, very real. The intelligence comes from the aggregation of social data, combined with filtering, analysis and direct (ie predictive) insights. The salesperson wants more than just new information, he/she wants the question they forgot to ask – don’t only tell me something new, suggest what I should do.

The following are just some quick ideas, there are so many more and if you would be willing to add your own, I would appreciate it!

Example – Sales

  • Data – The CRM (SFA) application has a copy of purchase and/or case history, maybe event data, purchase history and company financial information

  • Process – The Marketing Automation System responds to a visit by a lead to landing page a task is created to make a call or send an email

  • Context – The intelligence platform creates a set of tasks, based up information from Linkedin (say through InsideView integration) that certain people are active on Linkedin and have changed jobs, company purchase history and trends are used to suggest tone of message and 3 independent tasks are created. If the CRM system notes the user is accessing information on an iPhone, the tasks are delayed a few hours, as the emails and tasks are better done on a larger screen. Tasks and reminders are created and scheduled.

Example – Service (Customer Support)

  • Data – The Contact Center has account service history, household purchase history, number of claims displayed on the screen (or a couple clicks away).

  • Process – Add to the above, notifications of device recalls, health alerts, community posts, credit checks, invoice verification, payment verification, (think billing and finance).

  • Context – In financial services, think fraud alert. For example a user social check-in in New York and credit card use in Paris. In travel, make agents aware of weather or flight delays, tell client new flights are booked. Help systems should be product and location aware as well as being proactive.

Example – Customer (Me)

(There are too many customer examples to count, feel free to add your own)

  • Data – Give me access to my account information through a portal or smart device

  • Process – Notify me of potential fraud, account balance issues, credit issues, ask and wait for response. If an application is incomplete, point me to the place to complete it. If a doctor or hospital is too busy ask me if I want to reschedule.

  • Context – Notify me of weather on my travel route, give me options: car; a new route, plane; a special number or email address, finance; tell me my bank account is low before the rent check is due. Tell me to watch out for an issue, before I have it – the customer side of proactive support.

The Evolution of Customer Community

Community: a group of people sharing common characteristics, common history or common social, economic, or political interests, often located in close physical proximity to other members; interactions are usually face-to-face. 1

Online Community: Same as above, with two big caveats, the proximity is virtual and interactions are digital. The small caveat is that online the commonality among members might not be as significant, but are just as real (like shared product, service or technical interest).

It is not New, but it is Different

What should be evident is that the idea of a community is not a new concept. What is new, however, is the transition from physical proximity to virtual proximity. In the purest of context, virtual communities began about as quickly as the Internet itself, predating the Web or fancy graphical interfaces. Virtual communities progressed from bulletin boards to forums and now we have something even better. What we have now are enhanced graphical capabilities and multiple device support; the user experience is better. One problem remains; integrating communities with the rest of the business. Too often, communities are sets of isolated conversations lost in the vastness of the web.

           Communities should be used to bridge the gap from social media conversation to digital interactions with a purpose? Today many organization are trying to figure out how to leverage social conversations and these new connections to deliver a better customer experience. Customer communities are great way to accomplish this goal. As much as we would like to do it, taking  the online conversations people are having about your company in Facebook and Twitter and dumping them into a CRM system just does not provide a whole lot of value. As you have learned with forums, your customers really do want to connect with you and while the basics have not changed, customers expect more as does your business.

But. In order to really leverage the benefits from social, you have to bring together people, processes, and technology necessary to listen, guide, and engage your customers in the digital world. That means paying attention, understanding who your customers are, and providing them with relevant information for the appropriate stage in the customer lifecycle. In that way, you can truly leverage the capabilities of social media to deliver the kinds of customer experiences that will keep them bringing their business back again and again.

Communities provide a smart way to build engagement in a way that provides your customers with navigable issue resolution, as well as to provide feedback and insights to you and your team.

A customer community allows you to collect and analyze data, derive insights about your customers that will then allow you to provide them with relevant, appropriate information at key points along the journey. Today’s forums, or customer communities, can be strongly linked to social networks in order to maximize insight, streamline campaigns, and drive organizational shift to bring your company into the social age. But we’re getting ahead of ourselves.

(This post is written as we announce our recent work in building a bridge between SugarCRM and Get Satisfaction)

Experience Innovation

March 11, 2013 5 comments

Moore observed, nearly a half century ago, that the power of computational devices would double every 18 months (based on how many components could be squeezed onto an integrated circuit). Therefore, it is not much of a leap to suggest that the functional capabilities and ability to advance productivity based upon these devices would follow suit. For the most part, this has been the case. Now 50 years in, the simple question is: ‘is innovation still about squeezing more components into a device, or capabilities into a piece of software?’ Or, is it time to refocus? Maybe we need to think about making the devices and systems we have work better and more strongly consider the experience of the person using it.

I am completely willing to be wrong here, but I would need some convincing. I am not so bold as to suggest something at the level of Clay Christensen’s disruptive innovation. I am not talking about new markets. What I am suggesting is something more along the lines of rethinking sustainable innovation; the ability to evolve what we have already. To accomplish this, I am of the opinion that it is time to start focusing on experience innovation, and take a step back from the sole focus on product innovation. It is no longer about how much computational power we can squeeze into a device, or how many widgets we can display on a screen. This type of innovation will continue, but there is more.

“The experience space is conceptually distinct from that of the product space, which is the conventional focus of innovation. In the experience space, the individual consumer is central, and an event triggers a co-creation experience. The events have a context in space and time, and the involvement of the individual influences that experience. The personal meaning derived from the co-creation experience is what determines the value to the individual.”

C.K. Prahalad & Venkatram Ramaswamy, MIT Sloan Management Review, SUMMER 2003 VOL.44 NO.4 The New Frontier of Experience Innovation

I am not sure what is more interesting, the content itself or the fact that it was written nearly 10 years ago.  It might suggest that I am on to something, or simply that I found a few bits to support my thinking. The concepts are extremely relevant, even more at this point in time as companies struggle to differentiate themselves on increasingly commoditized products and dare I say services as well. In fairness, differentiation on services still has some legs and is more closely aligned to experience innovation.

The way I see it, is that the objective is to create what Prahalad and Ramaswamy refer to as an experience environment. Though it is still important to differentiate between the digital interaction experiences and the much more vast customer experience. This is especially true in instances where the greater experience contains elements that are far removed from communications, think heli-skiing or windsurfing, versus checking-in via Foursquare.

It is Time to Mature from Just Product Innovation

If one follows the breadcrumbs a bit, there is a fun example that can be found from a 2008 InfoWorld article. It simply highlights that too often software – the front end of the user experience – simply works to leverage hardware advances in a way that is often lazy and unfortunate:

“[Microsoft] Vista and Office 2007 on today’s [2008] state-of-the-art hardware delivers throughput that’s still only 22 percent slower than Windows XP and Office 2003 on the previous generation of state-of-the-art hardware. In other words, the hardware gets faster, the code base gets fatter, and the user experience, as measured in terms of application response times and overall execution throughput, remains relatively intact.”

Many of us have spent time reading, writing or analyzing product roadmaps. These directory type documents or PowerPoint presentations are filled with features and functions. Sometimes, the ones that are well written will include a section on exactly why a feature is included, beyond simply that a Magic Quadrant requires it. For those who have been lucky enough to write these documents, we all know the debates between internal factions of what needs to be built first and why. These debates will continue to happen, but I would ask that the conversation mature a bit.

As Prahalad & Ramaswamy so eloquently state it:

The ability to imagine and combine technological capabilities to facilitate experiences will be a key success factor in experience innovation, regardless of industry.

In order to make progress, what is needed are programs that focus on the customer perspective. We need to consider the user experience as we build devices and design software systems. We need to focus on their experience, not just our profits. We need an environment that includes both organizational capabilities in technology and communications driving the capability to interact collaboratively internally as well as with customers, partners through community. These interactions, in order to be meaningful, need to have proper context.  When we have this in place, then we will better be able to understand what customers want and need and deliver products and experiences that do make a difference.

Your thoughts?

Maybe We are Using the Wrong Words to Describe Collaboration

February 12, 2013 Leave a comment

When we attempt to describe something we are often judge based upon the words we use. Choose certain words and we are considered buzzword compliant or worse, SEO compliant. Choose the wrong words and we are considered out of touch, old school or not ‘cool’. On the other side of the coin, if we try to consider new ideas, or think forward a bit we might be considered too academic or a purist without a strong sense to technological or cultural limitations. What then is the right balance? How do we effectively communicate and at the same time be sure to be heard and found?

Specifically, say or write the words “Social Business”, “Enterprise 2.0” or even “collaboration”, “innovation”, “co-creation” or “design thinking” and many people roll their eyes. “Oh, great another buzzword fest”. I suppose we can still possibly save “innovation”, just a hope. But, aside from that, the rest are too often fodder for power point presentations, executive motivational speeches and fancy conference track titles. That said, the core concepts are very important and we should not allow the hype cycle to get in the way of what we need to get done. The question is, when we write or present these topics, who are we talking to, who is the audience? Are we trying to convince the senior executive or the people in the field, boots on the ground?

I am not going to start throwing around generational monikers (X, Y, Z, C) in an attempt to further confuse. If the goal is to be creative and build something new (as in product, service or concept) and we are trying to describe the value of doing that to people of many ages, backgrounds and job roles, maybe we need a new way to communicate the message. Everyone understands the ideas of teamwork, creativity, working together. When we enter the corporate world is it required to change the names and labels? The following may  not work for everyone, but I believe there is a crowd who might just appreciate the effort.

Remix and Mashup

Say the word Remix to most people under 40 (even some older, but not as many) and the mental image – or mental sound bite –  is clear. A remix is a song that has been edited to sound different from the original. The remixed version might have changed the tempo or pitch, made the song shorter or longer. There is more to it than that, but that is the basic idea. A Mashup is similar in concept, but includes more than one song or instrumental from one song overlaying on the vocals from another. In the digital word, a mashup is a combination of different media, pre-existing creative, all put together. The ideas are similar and well understood, add creativity and originality to someone else’s original work.

(One area I am not going to cover is the legal parts. One, because I am not qualified and Two because I am talking specifically to internal collaborative efforts, ie, one company owns the original works, so it is all kosher.)

Now that I just stated that I am going to ignore the legal issues, the example I am going to use and the basis for the use of Remix is HitRecord. This is a public place to do this and illustrated the example very well. Again, for the sake of discussion, all creative are assigned to HitRecord, thus, no legal issues. The whole idea of working with anyone else internally at your company is to meet a business goal. It might be a new product, a project, a problem or something else – all towards a common goal. We could take a manufacturing / assembly line approach; you do your part, taken from someone who did theirs and hand it off to someone else. Yes, but thinking linear will only get you so far.

We need to Help Everyone to be…

Adaptable, resourceful and make it easy to change. In the world where many grew up (parents and grandparents) people went to work for big companies and stayed there 30 or 40 years. Those days are gone, but nor forgotten. The way I believe that Remix and Mashup can fit into the modern work culture is to allow creativity and fresh ideas to permeate the atmosphere of an organization. In the future, a person’s career will involve many employers, as well as periods of self-employment as part of an ecosystem. Of the modern company is going to survive, it will need to become more like an ecosystem. This approach will give people the opportunity to follow their interests, even as they change over time. The person working for you yesterday, with you tomorrow may be your boss tomorrow. You might one day call this a career Remix, or Mashup, I am not sure. You will take what you know, change the speed, tempo, add a new song or two and dance another day.

Helping means communicating in a language that is understandable, in and on channels where everyone is comfortable – or least willing to learn to adapt. Give permission to others to take your ideas and run with them – Remix them and add their own creativity. When someone helps someone else to learn something or to see it from a new perspective, this may be referred to as mentoring. Mentoring is age independent, anyone can teach, anyone can learn (ie, there is no such thing as ‘reverse’ mentoring). The goal, as a mentor, teacher, friend, peer, co-worker is to help others and help help yourself –

Enjoy the Remix

Enterprise Customer Experience, A Convergence

January 22, 2013 5 comments

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.