•   01234 759 800
  •   info@acuigen.com
  •   We are recruiting, click here.
Client Login
AcuigenSalesSite
  • Services
  • CustomServe
  • Pricing
  • Resources
    • Blog
    • Case Studies
    • Discussion Groups
  • About
  • Client Logon
Let's talk

Blog  

 

Blog

Guest Blog

Case Studies

News

Certifications

All

 

Published on 09 April 2020

What’s the difference between Coding and Tagging?

person writing

Adding structure to open ended feedback

When you have any volume of client feedback, a common challenge to resolve is what to do with all the many and varied comments across a series of interviews, so that you can easily remember the themes and what was said, and report on it. 

In-depth interviews are great – the open ended discourse provides a wealth of insight into clients’ needs, perceptions, experiences, the problems they may be facing and the solutions that they need.  However the volume of insight can become overwhelming, and difficult to comprehend, particularly when you are seeking to summarise the common themes across a number of interviews, or you are trying to find that particular quote to emphasise your pitch but you can’t quite remember who said it.  It becomes more complex when the information needs to be recut into different views (e.g. by market, sector, service line, lawyer, etc.).

Borrowing from the market research toolbox, the answer is simple, you need to categorise (or code) important open ended questions into themes and store them in a spreadsheet or database.  The outputs can then easily be summarised and reported on, however, the process can be time-consuming to categorise a large volume of historical client feedback – it’s best to do it frequently.   

What’s the difference between Coding and Tagging?

At Acuigen we use 2 terms ‘Coding’ and ‘Tagging’ to get content organised.  The difference between the 2 similar processes is easy to understand   

  • Coding is the process of reading many responses to the same question, and when you have enough answers you code the answers into groups (or buckets as they are sometimes referred).  For example, if you ask the question “Why did you recommend us” [Question number 1234] you could get 10 or more different reasons in, say 75 interviews - each type of response would be coded to one or more of these buckets (e.g. Great people, Great service, Other).  The rule of thumb is that you will have a random bucket called “Other” containing comments that you can’t simply code, and if the ‘other’ comment list makes up more than 10% of the total responses, then the coding frame (the list of codes/buckets) needs to be recategorised so that the list of others drops below 10%.  Often a verbatim comment will have more than one code associated with a response, and so it’s helpful to make a note on any report “Multiple responses to Question 1234, 75 interviews, 95 coded comments”.

  • Tagging is the term that we use to describe an applied process that uses different information sources or knowledge to add intelligence to an interview.  It’s similar to coding but has a different more commercial purpose.  For example, if you ask the question “Why did you recommend us” and the answer is “John is an excellent lawyer, pivotal to our relationship and the great service we receive” it could be coded as both ’Great people’ and ‘Great service’.  However, if it is also known the John is about to retire, the tagging process would potentially also flag the comment as a ‘Risk’ (can we retain the client after John retires?) or an ‘Opportunity’ (could John could introduce new lawyers to the relationship before his retirement).  A verbatim comment may have one or more tags associated with it.

By using a mixture of coding and tagging it is possible to gain a really good understanding of the meaning of verbatim feedback and the associated commercial intelligence within it, making it easier to present and report upon a series of interviews.

Tips

  • When reporting feedback make it clear to the reader if a question’s code frame can have only one or more than one associated codes

  • Regularly check code frames to ensure that they are up to date, and do not have a catch-all bucket of ‘other’ comments of more than 10%.  If a code frame changes, be prepared to recategorise prior interviews

  • Keep a diary and narrative of when and why code frames were updated or changed

  • Explain to readers the difference between coding and tagging

Continue the discussion

If you’re interested in understanding the process of client feedback to a greater extent or are interested in initiating or scaling up a client feedback programme in your firm, get in touch with our team who be happy to talk further to assist you and to share our experiences. 

Comments (0)Number of views (0)

Author: Anonym

Categories: ROI, Acuigen Blogs, All, Interviewer Support Hub (Old)

Tags: CustomServe, Actionable Feedback, Using Client Feedback, Strategy, Tagging, Insights

Print

Related articles

  • A new way to track themes in our insight conversations?
  • Measuring client loyalty in professional services firms
  • Is your client listening ready to support your next business plan?
  • What's the best way to interview clients to get actionable client feedback?
  • How do you build the business case for client feedback?

More information

Chris Lang

Client Services Director

chris.lang@acuigen.com

+44 (0) 1234 759882

Latest Thinking

Keep up to date with the latest thinking and advice about client feedback.

Sign up for our blogs.

Sign Up

Our Services

See if our services could help your firm with your client feedback

Find out more

Why Acuigen

Better Client Feedback Superb Platform International Certifications Client Stories

Services

Getting Started Scaling Up Corporate Solutions Thought Leadership

Resources

Blog Case Studies Events Discussion Groups  

Pricing

Service Plans

About Us

About Acuigen Vision and Values Leadership Team Quality and Security Careers Contact Us Client Portal  
MRS Company Partner Logo
© Acuigen Ltd, 2010 - 2025 | Terms of Use | Privacy and Cookies | Cookie Settings | Accessibility | Anti-Bribery | Anti-Slavery | AI Policy | Login