Survey Software, Web Survey, Online Surveys, and Enterprise Feedback Management solutions from Vovici

Your email:
   

Welcome to the Listening Post!

Your single source for everything Voice of the Customer (VoC) and Customer Experience (CxP). And, don’t forget you can follow us on twitter @vovici, or come check us out on Facebook and join the Vovici Network on LinkedIn.

 

Current Articles | RSS Feed RSS Feed

Survey Coding: Categorizing Answers to Verbatim Questions

 
graffiti

What do you with all those answers to your open-ended questions? If you are in a hurry, you can read them all, then highlight three or four comments that you find representative of the types of answers you received and present those as typical. For all but the most tactical survey, however, you are going to want to develop and tally categories of common answers.

A coding frame or code book is simply a list of the categories and subcategories that you are tracking (also called nets and sub-nets). For product lists ("Which mascara have you most recently purchased?", "What was the last movie you watched?"), you might begin a coding frame by seeding it with bestselling products. For essay questions, you will develop a coding frame by reviewing the answers themselves. It's become hip to create a word cloud to visualize open ends; this technique, while colorful, is of limited analytical value but it can help you to see commonly used words as you begin drafting your code book.

For some open ends ("What model cell phone do you have?"), you will record one code per answer. For others ("What, if anything, do you like about...?"), multiple codes per answer make sense.

Managing coding across multiple languages can be quite expensive and time consuming. Often, to save time and money, the verbatim comments themselves are not translated but a standard code book is developed for use across all languages, with native speakers coding the verbatim responses in each language.

For the highest quality coding, follow the double blind process and have two analysts independently develop a coding frame and code all the verbatim responses using it. The analysts should then meet to reconcile their results and develop a consensus coding frame with final coded responses. Large firms that do extensive coding continually measure and monitor intercoder agreement (typically called intercoder reliability).

This manual coding process is fine for a few hundred responses but quickly becomes tedious. You can take a random sample of comments and manually code only those. Alternatively, you can automate the task. Systems such as Ascribe from Language Logic can learn from the manually prepared codes and automate subsequent coding. As an input, this application takes the manually-developed coding frame and coded comments and creates routines that can be used to categorize the uncoded comments. Text analytic systems, including those from Attensity and Clarabridge (both partners of Vovici), can be manually configured to provided automated coding.

Coding helps bring order and structure to your hundreds or thousands of open-ended comments.

Comments

Great summary of the coding process. The only thing I would take issue with is when coding responses in multiple languages. We always prefer to translate first, then code in English for better consistency. And when budget allows, manual coding is far superior to automated/text analytics systems.
Posted @ Monday, October 25, 2010 10:19 AM by Glenn Davis
I think the method I describe is the most expensive but the highest quality. I think your method is a good middle ground. At the lower end, I've seen companies use machine translation of verbatims -- something with very low quality. And, of course, I've seen projects where there was no budget left to do any coding of foreign language verbatims at all. 
 
I think you are right about manual coding being superior to automatic coding. Again, it is a question of budget. Thanks for commenting!
Posted @ Tuesday, October 26, 2010 8:14 AM by Jeffrey Henning
Post Comment
Name
 *
Email
 *
Website (optional)
Comment
 *

Allowed tags: <a> link, <b> bold, <i> italics

Latest Posts

Loading
What's New
Don't Be in the 4%
VoC on Twitter
Verint Blog
Verint Blog: Read the Latest from the Verint Systems Blog