Menu

Research

Thematic Analysis

A practical qualitative research synthesis method for translating raw interviews and notes into clear evidence-based themes.

How to run thematic analysis to code qualitative data, identify recurring patterns, and produce actionable findings for design and strategy.

4 min read

What it is

Thematic analysis is a UX and method used to identify, analyse, and report or themes within .

It involves reviewing transcripts, notes, or from interviews, , , or field studies to extract recurring ideas and concepts.

The focus is on understanding underlying and meanings, not just counting occurrences.

Key takeaway

The goal is to synthesise complex data into actionable insights that inform design, strategy, or content decisions.

When to use it

Use this method when you need to interpret .

It is most useful when:

you have collected rich qualitative data
you want to understand user behaviours, needs, and motivations
patterns and insights are not immediately obvious
you need to guide design, content, or strategy decisions
you want evidence-based recommendations

It is less useful when:

data is purely quantitative
patterns are obvious without analysis
Thematic analysis is often used alongside affinity mapping and qualitative research methods.

How to run it

Set up properly

Be clear on your , the questions you are answering, and how themes will be recorded and checked. Analysis without a stated question tends to rediscover whatever you already believed.

Prepare and anonymise the before you start. Coding while still cleaning transcripts is how inconsistency creeps in.

Run the method

Thematic analysis is systematic and iterative. The rigour is what separates it from reading the notes and forming an .

  1. Read through everything before coding anything. Familiarity first stops early codes from framing the rest of the .
  2. Generate initial codes close to the , using the participants' language rather than your categories.
  3. Group codes into candidate themes, and expect several to collapse or split as you go.
  4. Review themes against the coded extracts and against the whole set. A theme that only holds for two participants is a finding about two people.
  5. Define and name each theme so it states something, rather than a topic. " breaks at payment" is a theme; "payment" is a folder.

Focus on meaningful rather than surface content. Counting how often a word appears is not analysis, and it is easily mistaken for it.

Capture and make sense of it

The value comes from clear interpretation. After analysis, document:

  • Each theme with the evidence that supports it, including quotes
  • Which questions each theme answers, and which remain open
  • Findings ranked by user impact rather than by how often they came up
  • Contradictory evidence, rather than only the material that fits

Share results in a form that informs design, content or . Analysis that stops at a themes document has done half the work.

Key takeaway

Use this to turn raw data into actionable understanding.

What to look for

Focus on:

Recurrence: patterns that appear across participants or data points
Relevance: themes that relate to research objectives
Insight: what the theme reveals about users or context
Clarity: themes are understandable and clearly defined
Impact: themes that influence design, content, or business decisions

Where it goes wrong

Most issues come from:

If themes are poorly defined, are weak.

Forming conclusions during the first read, before anything is coded
Coding in your categories rather than the participants' language
Naming themes so broadly that they describe everything and commit to nothing
Keeping a theme that only holds for two participants
Reporting the material that fits and quietly dropping what does not

What you get from it

Done properly, this method gives you:

Findings traceable back to the evidence that produced them
Themes that state something rather than label a topic
A clear answer on which research questions remain open
Analysis that holds up when somebody disagrees with the conclusion

Key takeaway

It helps make sense of complex user data.

Get in touch

If this sounds like something you need, we can help you perform thematic analysis on your research data and turn observations into clear, actionable insights for design and strategy.

No guesswork. No assumptions. Just understanding that drives better UX.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is thematic analysis in UX?

It is a method for identifying and analysing patterns or themes within qualitative data.

When should you use thematic analysis?

After collecting qualitative data such as interviews, surveys, or observations.

What can you analyse?

Transcripts, field notes, survey responses, or research observations.

Why code data rather than summarise it?

It reveals underlying patterns, motivations, and insights to guide design and strategy.

Does thematic analysis improve UX?

Yes. It transforms qualitative data into actionable insights for better user experiences.

Quick take

If you want to turn qualitative data into insights, identify themes that reveal what really matters.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer