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

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.)

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

Tags: , , , , , ,

  • ameyer32
    John,

    a very interesting idea that actually addresses something I've been thinking about. We have a highly distributed consulting company. How can one easily share ideas and updates between people in different geographic sites? I've thought about creating a blogging policy where everyone would post a max of 150 word update on what happened that is interesting that day, but your suggestion is even better. Have people call in and give an 5 to 10 minute update on things that were interesting or important at their site that day. Put that autotranscribed into a blog and then distributed to everyone else via an RSS feed. That way everyone would have an awareness of what's happening at different sites and if you're going to visit a site, there is a history that can be read so one is savvy with what is happening with that site. Comments made to the post would also allow junior consultants to get feedback from consultants who have been around longer.

    Much more efficient and easily accessible than email.

    Have you tried doing this or are you thinking of trying? If you do, let me know, it would be an interesting experiment and it would be helpful to compare notes with someone else.

    Andy
  • Andy, what you have been thinking of is precisely the idea. Getting input
    from everyone, and allowing everyone to review and comment. Scanning RSS
    feeds is really efficient at poring through large amounts of info, and
    comments etc. add to the conversation. [One of the inspirations was Gary
    Hamel's book "The Future of Management," where he asserted that companies
    needed to be much better at tapping the capabilities of every single
    employee.]

    I haven't tried out this concept yet, but have proposed it a couple of
    times. In most cases, the companies saw value, but were inhibited about
    letting the lower-level folks blog. Fear of internet use, I believe.
    Short-sighted as well.

    A couple of thoughts. I really don't know how much it would cost to
    autotranscribe on a mass basis. I've used Spinvox to auto-post and it worked
    pretty well, though I needed to do some minor corrections. Licensing it for
    large-scale use is something they are very interested in (they've approached
    me about it), but I just don't know what the dollars would be.

    Second, I'd say that 5-10 minutes might be too long to give people. That
    will yield a lot of text, perhaps too much for readers to wade through. I
    did a number of auto-transcribed posts, and 2 minutes was enough to get a
    good story across. Plus, as Twitter has shown, there's value in forcing
    brevity on folks.

    Finally, I think there's great value in giving posters very general
    instructions, as you say. "Interesting or important" will yield more
    diverse, interesting and useful input, I believe, than tighter constraints
    on what to write about.

    If it's something you think you might want to try, I'd love to participate,
    as a test case of the idea...

    Regards, John
  • ameyer32
    John,

    we wouldn't have a huge group of people (my company isn't that large). But as we grow, it would be an interesting way to capture corporate experience and review it. That is more what interest me.

    When I was studying Industrial Engineering, we spent quite a bit of time talking about Peter Senge's "The Learning Organization". One of the real challenges was, how do you capture corporate learning? This offers a way to do that.

    I'm probably going to experiment doing this myself first. I like your idea of answering "What's interesting?" Maybe I'll also pretend I'm Jean Luc Picard entering my Captains Log.

    If I were hit by a bus and a co-worker had to take over, what would I want them to know?

    Have you talked to Rich Maltzman (the Scope Crepe blogger) about this? He's done quite a bit to encourage more blogging of what different people are doing. He might well be interested. I'll send him with links to your posts.
  • John,
    I think this idea is just great. I'm wrting a blog about retail in Spain. (...stays mainly in the plain - I had to say this joke!) If you don't mind I will write about this idea and see if I get any feedbak. I'm also member in a professional net - www.retailers.es, and there I might find some company ready to try this out or even start out an open space for responses from any customer-facing rep, not as a company but as professional. Have you thought about tweeting the answers to "what's interesting"? It would be 140 character messages with no place for innecessary info. But the best thing might be blogging, even written because everyone has a PC in the store. Please let us know how is it going if you start doing it with Andy. Good luck!
  • Hi, Sashka, thanks for your comment and your very interesting ideas. Using Twitter is a fascinating suggestion, though I'm not sure there's enough meat in a Tweet (sorry) to show patterns. I've done some experiments collecting Twitter stories about products, and you can discern positives/negatives, but not much more than that. With respect to blogging, an important aspect is assigning a memorable title to a post. This can help those who are monitoring the posts on RSS quickly find ones of interest. That's one way to think of the Twitter model--in addition to writing a brief post, compose a 140-character title.

    I am eager to see if you get any response to your post. I'll be watching (but my Spanish proficiency is non-existent, so I won't understand much of what's said).

    John Caddell

    Original Message
    ----------------
    Subject: [caddellinsightgroupblog] Re: For review & comment: a method for gathering-using customer intelligence from your front-line staff (part 2)
blog comments powered by Disqus