Are 200 customer stories more useful than 2,000,000 data points?

I’m wrestling with this question right now. I’ve completed several projects that involved collecting, reviewing and working with collections of customer stories to help companies in telesales, market positioning and strategic planning. When I talk to larger companies, inevitably they point to an industrial-strength IT platform they’ve installed that collects & interprets thousands or millions of interactions. “See what we’re doing?” they say. “We are looking at millions of data points. So there’s nothing more you can do for us.”

My discussions with these companies won’t go anywhere if I can’t demonstrate to them that there is a distinct difference between the data mining they’re doing today and this more hand-crafted approach I’m proposing.

So I’m laying out some important distinctions between story work and data mining.

1) My approach (and others’) is rooted in customer narratives, not in numbers.

2) With the narrative-based approach, an essential aspect is human immersion in the individual customer stories. This means a real person reading transcripts, listening to recordings, etc., to experience as fully as possible what’s going on in the moment. In customer encounters, hesitations, stammers, changes, long pauses, laughs, interruptions are not noise–they are part of the story. Removing these is at least sterilizing and at worst misleading. [Even rudimentary, supposedly machine-readable stories such as Tweets can be easily misinterpreted.]

3) This human interactor helps catalyze* or identify unusual or possibly interesting patterns, acting as a naive observer (or customer proxy), outside the company. Excerpts that may illustrate patterns are excerpted and used in sensemaking described below. [Sensemaking, in a somewhat different context, is discussed in this Sloan Business Review article.] Data items related to the stories are also collected and the interactor creates graphical representations of the data, some of which are potentially interesting and insightful.

4) The catalyzed information is reviewed and assessed by groups of people inside the company, rather than individuals scanning dashboards and using that data to reinforce their preconceptions. The groups use techniques designed to foster evidence-based collective sensemaking, rather than simply to confirm/refute preexisting hypotheses. The techniques encourage the groups to develop alternate interpretations of the data, an important advantage over numerical data analysis in evaluating customer service, sales, product satisfaction, which have complex aspects that defy reduction to simple dashboard figures.

But what about the limitations of all this human intervention? Isn’t 200 stories too small a data set to a company with millions or tens of millions of customers? My answer, surprisingly, came from a CFO friend. “Gosh,” he said, “after 200 stories, I don’t think you’d find much of anything new.” I agree. If the scope and key questions are defined clearly enough, a sample of a hundred or two hundred can blanket the problem and provide patterns that would equally apply to the remainder of the customer base.

*I first heard the term catalysys used by Cynthia Kurtz to describe this process.

Share and Enjoy:
  • Print
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Blogplay

Tags: , , , ,

  • http://caddellinsightgroup.com/blog2/2009/04/dealing-with-what-customers-tell-you-online/ Customers Are Talking » Blog Archive » Dealing with what customers tell you online

    [...] Customers Are Talking A discussion of how to listen to, make sense of, and act on customer feedback, however it’s given « Are 200 customer stories more useful than 2,000,000 data points? [...]

  • http://fredzimny.wordpress.com/2009/04/10/are-200-customer-stories-more-useful-than-2000000-data-points/ Are 200 customer stories more useful than 2,000,000 data points? « Fredzimny’s CCCCC Blog

    [...] Are 200 customer stories more useful than 2,000,000 data points? Posted on April 10, 2009 by fredzimny Written by John Caddell and found at http://caddellinsightgroup.com/blog2/2009/04/are-200-customer-stories-more-useful-than-2000000-data-... [...]

  • MorganB

    The problem is not normally the availability of data but that the data can be converted into something worthwhile. With something like customer feedback the language used is not going to be the same every time let alone consistent with the language the company likes to use.

    Getting back to the original context of the statement is almost impossible to do with 2,000,000 pieces of data. But it can be used to reinforce the conclusions that were gleaned from the smaller contextual analysis.

  • http://caddellinsightgroup.com jmcaddell

    Morgan, I agree that the 2000000 data points are useful to reinforce conclusions reached by working with narratives. The inverse is also useful–dashboards can highlight questions that can be investigated using story methods.

    For example, in a telemarketing project I worked on, close rate was a significant metric. Leadership wanted to know why close rates were stuck at a certain level. We sorted through sales call recordings (the stories) & helped them determine half a dozen reasons why the close rate was what it was. Knowing those reasons enabled them to design interventions addressing each reason.

    In other words, dashboards are good at telling you what's going on. For customer issues, stories are good at telling you the reasons behind the “what.”.

  • http://blog.threestarleadership.com Wally Bock

    Great post, John. Stories are the way that human beings have stored, remembered, and made sense of complex information since we've been human beings. You don't sit around the campfire and share data points. You tell stories, even if the campfire is digital.

    I use stories in the form of “reader personas” to get at who I'm writing for in an article or on a web site. Data-rich descriptions can't come close.

    I use “web use vignettes” to describe what we want to happen when a visitor comes to a client site. Detailed feature sets and maps can't come close.

    Close to what? To the richness and nuance that stories provide.

    But data points can help you supplement and sharpen your stories. The combination is more potent than either alone.

blog comments powered by Disqus