Posts Tagged ‘knowledge’

The tyranny of the dashboard

Wednesday, December 2nd, 2009

722346_speedingI frankly am beginning to feel that I’m shouting into a void here. Companies are spending more time and money equipping the CEO and team with information, while starving the thousands of ground-level employees who, frankly, can have more impact on the company’s success simply through their day-to-day actions.

One ray of hope: an article in the December Harvard Business Review (co-authored by Fred Reichheld, the creator of the Net Promoter Score – a simple metric that somehow captures the complexity of customer perception) entitled, “Closing The Customer Feedback Loop.”

As opposed to the conventional wisdom of gathering masses of data and trying to detect high-level patterns in them, Reichheld and his coauthors talk about getting more granular – gathering information at the customer transaction level, creating small rollups of the data, and sharing them where they can do the most good – with the front-line employees and first-level management who directly impact the customer experience.

I agree with their prescriptions, but it still leaves the problem of what to tell upper management. Is there anything wrong with high-level management dashboards? Well, yes. Something of the danger in this is described in today’s WSJ article on Simpson’s Paradox (”When Combined Data Reveal the Flaw of Averages“). The first example cited: while today’s overall unemployment rate is lower than the 1982 level, unemployment at each educational level is higher. (The overall rate is lower because there are more people at higher educational levels, which have lower unemployment, than there were in 1982.) The article states: “Compared with a similarly educated worker in 1983, ‘the worker today has higher unemployment at every educational level.’”

There’s always something lost in summarization. In the case of Simpson’s Paradox, the result of the loss is a flawed conclusion, or at minimum missing a greater point of the story. Overall unemployment today is lower than 1982, but people today have been hit harder than their 1982 counterparts.

Dashboards distort reality as well. Executives rely on machines crunching millions or billions of numbers to present them an easily readable story of what is happening in their businesses. Yet the farther the statistics are distanced from the on-the-ground reality, the more likely they are to lie.

What can be done? Let’s get back to “Closing the Customer Feedback Loop.” On-the-ground data gathering and interpretation by those close to it makes all the sense in the world. But in communicating with upper management, there needs to be less sharing of numbers, and more sharing of individual stories. You can’t get any more granular than that. You can read a vibrant story in a minute or two. And stories fall into patterns–something more subtle and nuanced than statistics–that help senior management understand what’s going on. And human experiences are more understandable than the simplest dashboard.

There are tools to do help you gather and use stories. Rakontu, an open-source story-sharing platform, is one. Enterprise 2.0 tools such as blogs would also work for this purpose. So what’s stopping us? Or am I still shouting into the void?

(Photo by awegedebe via stock.xchng)

Related posts:
GE uses “net promoter score” – one of my earliest posts!
On Rakontu
Time to listen to front-line employees
How B2B customers talk
“Enterprise 2.0″ review
Technology is great, and so is avoiding the acorns

For review & comment: a method for gathering-using customer intelligence from your front-line staff (part 2)

Thursday, March 5th, 2009

Part 1 of this series can be found here.

Recapping from yesterday: companies need to listen carefully to their customers, and while new means like blogs, Twitter, etc., are promising sources of customer feedback, the truth is that the vast majority of customers don’t (and maybe won’t) use these tools. There is a source to tap the knowledge in these other, silent customers–the front-line support staff. Retail clerks, bank tellers, etc., have person-to-person contact with customers every day. If customers have opinions, they hear them. The following diagram describes how their intelligence could be captured and used to improve companies’ understanding of their customers.

(Steps 1 & 2 were covered in yesterday’s post.)

Step 3: Periodically, a group analyzes the archive of blog posts, comments, etc., pulls out important excerpts and creates summary data based on the content of the posts. The data is compiled and prepared for analysis by a cross functional team in Step 4, below.

Step 4: The team evaluates the excerpts and the graphs to detect broad patterns that can inspire action. By way of example, a retailer who is trying to understand buyers’ temperaments more deeply in this economic crisis might examine a set of blog posts from before the crisis and compare the topics/findings with a set of posts from the last month or two. This will illustrate patterns in how buyers are reacting to the crisis, such as by substituting one good for another, saying different things to clerks, etc.

To perhaps make this concept more concrete, there was an article in the WSJ yesterday (”From Attitude to Gratitude“) talking about how people are treating their investment advisors since the crisis hit. This quote from the article could have been one of the blog posts I envision here:

“I’m not getting complaints,” Mr. Hirsch (an investment advisor at Credit Suisse) said. “People aren’t asking, ‘What did you do to my portfolio?’ They’re asking, ‘What do we do from here?’”

One quote isn’t a pattern, but imagine there were several dozen stories like this from Credit Suisse’s advisory team. From this insight, management could devise approaches to give the clients the kind of advice they’re asking for, building loyalty that could last beyond the end of the crisis.

That’s what customers are really talking about. And knowing it means you can act on it.

And that’s what I’m talking about.

(Acknowledgement to Shawn Callahan, from whom I first heard the possible uses of blog posting and RSS for collecting and using distributed knowledge. Here’s a white paper Shawn wrote on the topic.)

For review & comment: a method for gathering-using customer intelligence from your front-line staff (part 1)

Wednesday, March 4th, 2009

[Part 2 of this series can be found here.]

I touched on this topic six months ago, but I think it’s worthy of some amplification.

Companies need to listen carefully to their customers, and while new means like blogs, Twitter, etc., are promising sources of customer feedback, the truth is that the vast majority of customers don’t (and maybe won’t) use these tools.

Other sources for customer insight include call-center recordings, customer-service chats, etc. [A white paper on using call-center recordings is available here: Gathering-Using Customer Stories.]

This still leaves a lot of customers–those who don’t contact the company–unheard.

There is a source for this type of insight–the front-line support staff. Retail clerks, bank tellers, etc., have person-to-person contact with customers every day. If customers have opinions, they hear them. The following diagram describes how their intelligence could be captured and used to improve companies’ understanding of their customers.

[This is a very preliminary draft, and I welcome comments, critique, suggestions, etc. It may end up to be a dumb idea or unworkable for some reason. I think, though, that it's worthy of serious consideration and thought.]

Step 1 is the front-line teams blogging on a daily basis about their experiences. The prompt for these blogs is a very simple, general question: “What was the most interesting thing that happened today?” Rather than ask them to sign onto a computer and type their blog post in, it’s gathered via phone. What’s easier than leaving a 1-2 minute message on the phone? The poster also supplies a title for the post.

The phone messages would be auto-transcribed using a service like SpinVox or Dial2Do and automatically posted to an internal blog.

In step 2, the blog posts are distributed via RSS to a wide range of readers within the company–customer service, marketing, management, etc. This group scans the post titles on their RSS readers, read any that caught their eye, and comment on, share and/or rate the posts that were most interesting to them. This process will quickly separate the interesting information from the noise (and we should expect a lot of noise).

In addition to sharing their thoughts, the blog readers can propose improvement projects based on the what they learn through reading the blogs.

(We’ll continue this post tomorrow.)

(Acknowledgement to Shawn Callahan, from whom I first heard the possible uses of blog posting and RSS for collecting and using distributed knowledge. Here’s a white paper Shawn wrote on the topic.)