Nowadays, professionals that often talk to customers as part of their job (e.g. UX Research, founder, Customer Success) can do so virtually and at scale using popular tools like Zoom or Google Meet.
However, these individuals and their companies are now facing huge volumes of raw data coming from these video calls. How should they uncover, save, and share meaningful insights in this sea of noisy data?
The answer to this question is to use tags.
Tags enable customer-centric organizations to quickly and easily access key insights from their customer conversations. This gives them a better understanding of their customer’s pain points and aspirations.
Moreover, tags that stem from a coherent taxonomy help companies answer critical research questions. Being able to answer these questions help companies become more customer-centric and deliver the right solutions for their customers .
In this article we will cover the following points related to tagging:
A taxonomy is a way to classify information that falls under a given topic. This enables companies to group information that is related under the same category. Therefore, a taxonomy represents the vocabulary used by customer-centric organizations to name and organize crucial information.
A taxonomy encompasses multiple tags that are related. While a taxonomy represents a higher level of abstraction, tags on the other hand are the manifestation of a grouping when applied to an observation.
These elements are core components of what we refer to as a nugget of insight. This term originates from the UX Research world and was coined by Tomer Sharon, who also popularized the concept of Atomic Research.
In Atomic Research, a nugget is the smallest unit of insight from qualitative data that customer-centric organisations can leverage. A nugget is composed of:
For instance, imagine you conducted 3 usability tests over video and have identified these 3 excerpts from their respective transcripts:
What do all these examples have in common? Answer: they are about usability issues.
These 3 excerpts could thus constitute 3 nuggets from the same insight with the tag usability issue. Tagging insights like this makes important information around usability issues easy to organise and of course retrieve for anyone with access to the system where this information is stored. These systems have traditionally been called repositories.
Adopting a well-defined taxonomy together with clear tags yields the following benefits for companies:
Avoiding knowledge silos
Increased life expectancy of customer insights
Related information is easier to retrieve
To build an effective taxonomy, customer-centric companies must be aware of the different ways tags can be created to determine what approach works best for them. Firstly, tags can either be global, which means they could be applied to any material, or project specific. Additionally, tags can be derived either deductively or inductively.
Global tags are used by everyone within the organisation and across projects. The taxonomy around global tags is developed after interviewing multiple stakeholders across different functions within a company to understand what topics they would like to capture insights for.
Examples of global tags could be pain points, usability issues, motivation, etc.
Project specific tags are related to a single project. When working on a given project, there is a lot of information that is unknown ahead of time. Project specific tags therefore are useful because they help identify themes from project-specific conversations.
These tags can be created with more flexibility that global ones. For instance you could define these tags without seeking consensus for the time being. It’s important though that in planning these tags you make sure that some of them are related to the goals of the project. You should also leave some room for tags that highlight unexpected insights.
Examples: applications used to book flights, reason for buying milkshake in the morning, etc.
Inductive tags are created on the go, without advance preparation. They reflect observations they could not have been predicted and planned for ahead of the conversation. For instance, they give a UX Researcher room for manoeuvre so that they can capture surprising yet important information outside the initially defined scope of a research project.
Deductive tags refer to any tags that are created prior to a conversation. Whether these tags are global or project specific, the taxonomy for these is agreed upon with team members and stakeholders to ensure they use a common vocabulary. This common vocabulary provides a consistent way of grouping and retrieving related insights.
We recommend you follow these to get started with defining your taxonomy:
There are multiple ways in which you can define global tags in advance.
Tags derived from Stakeholder Objectives (Questions)
Objectives are things that your stakeholders plan to achieve finding in your repository.
Simply start by talking with your stakeholders to try understand what they would want to get out of the repository. We recommend you conduct private interviews with each stakeholder individually.
A product manager might ask, what features are people requesting? what bugs were they reporting? What suggestions do people have, etc.? You can then extract tag names out of it. Feature requests, suggestions, bugs, etc.
Tags derived from Use cases
Retrieving information can also be based on use cases, workflows, or the journeys a user might make within the app. Accessing insights in such a fashion of course is highly dependent on the type of organization and the project that you are working on.
For instance, in the case of a food delivery app, we could have the following tags based on what stakeholders are trying to find out regarding use cases: ordering due to of lack time, ordering to unwind, ordering as habit, ordering for romantic setup, etc.
Tags derived from Interview questions
These are interview questions derived from an interview guide.
For instance for the question “What are the reasons for installing xyz software ?” you could create the tag reasons for installing xyz software.
In general, it’s a good idea to have tags that are expressive so that it is easy to understand what the content tagged is about without overthinking.
Now that you have a set of predefined tags, it’s time to put it to test.
A dictionary is a place where every tag you create is defined. Tags fall into many groups, some generic and some specific to your project. Granted most of your tags should already be in sync with the vocabulary that is used in your organization, but a dictionary acts as a place for anyone to use as a reference.
You shouldn't be tagging everything. The most important things to tag are
Being able to retrieve valuable insights and acting upon it is what turns businesses into customer-centric organisations that deliver what the customer needs. But in order to have a pulse on these insights it is critical for companies to have a consistent way of grouping related observations.
That’s exactly what tags are for. Customer insights repositories like EnVsion enable you to group every relevant observation using tags and derive insights from these. Tags extend the life-expectancy of these insights, make information quicker to access, and by extension help create ever green company knowledge.
There isn’t a singular way to define tags, but we recommend you speak with stakeholders and colleagues to understand what they want to get out of your conversations. Once this preliminary internal research is finished you should be able to define the original tags for your research.
Remember that your first iteration won’t be perfect. Continuously seek feedback, and keep refining your taxonomy. You are well on your way to catch all the golden nuggets that will help your company ship delightful experiences for your customers.