Research Governance

Thematic Analysis

Thematic analysis is a qualitative analysis method for identifying, organizing, and interpreting patterns of meaning across a dataset.

Concept facts

Thematic analysis is a qualitative analysis method for identifying, organizing, and interpreting patterns of meaning across a dataset.

Also known as
Theme analysis, qualitative thematic coding, reflexive thematic analysis.
Used in
Interview analysis, focus group analysis, diary studies, field research, usability research synthesis, service evaluation, and program learning.
Interpret with
Codebook, triangulation, research protocol, sampling strategy, data saturation, and research ethics.

Plain-language explanation

Thematic analysis helps a research team move from raw qualitative data to a structured understanding of what people experience, value, misunderstand, fear, avoid, or need. It does not simply count repeated words. It examines patterns of meaning across participant accounts, observation notes, documents, or open-ended responses.

In UX and digital service work, thematic analysis is useful when teams need to understand why users struggle with a service journey, how institutional workflows create friction, or what patterns appear across different stakeholder groups.

Why it matters

Digital service decisions often rely on qualitative evidence: interviews with citizens, field staff, patients, agents, learners, or operational teams. Without a disciplined analysis process, teams may overreact to memorable quotes, senior stakeholder opinions, or isolated incidents.

Thematic analysis helps teams build a clearer evidence base by connecting individual experiences to broader patterns. It supports decisions about service redesign, workflow improvement, content clarity, accessibility, training, and governance.

Use contexts

Thematic analysis is used when:

  • research produces interviews, focus groups, diary entries, observation notes, or open-ended responses
  • a team needs to understand recurring barriers across user groups
  • usability findings need to be synthesized beyond issue lists
  • public-service or development-sector programs need to compare participant experiences across locations
  • institutional teams need to understand why a digital workflow is resisted, bypassed, or misunderstood

Application guidance

A thematic analysis process should define the dataset, clarify the research questions, document coding decisions, and distinguish between descriptive patterns and interpretive themes.

Teams should avoid treating themes as simple topic labels. A theme should explain something meaningful about the user experience, service environment, institutional process, or decision context.

Good thematic analysis usually requires memoing, team discussion, transparent coding decisions, and careful handling of contradictory evidence.

Practical example

A social protection program evaluates a redesigned beneficiary registration system used by local offices, field enumerators, and applicants. The research team interviews applicants who were rejected, staff who handled appeals, and supervisors responsible for verification.

A thematic analysis shows that “application confusion” is not one problem. The data reveal separate themes: uncertainty about eligibility rules, fear of losing benefits after correcting information, staff workarounds for missing identity documents, and distrust caused by unclear rejection messages.

These themes help the program redesign not only the form, but also the applicant guidance, staff training, verification handoffs, and rejection communication process.

Interpretive boundaries

Thematic analysis does not automatically prove how common a problem is across the entire population. It explains patterns of meaning in the studied dataset.

It should not be used as a substitute for statistical measurement, system log analysis, accessibility testing, or operational performance monitoring when those are required.

The quality of thematic analysis depends on sampling, documentation, analyst judgment, and transparency in how themes were developed.

Applied at Userhub

Userhub uses thematic analysis to synthesize qualitative evidence from interviews, usability sessions, service walkthroughs, stakeholder discussions, and field observations.

In institutional and development-sector work, thematic analysis helps connect user experience findings with service logic, staff workflows, operational constraints, and decision-making risks.

See Userhub UX Lab for applied UX research and evaluation context.

Sources and references

Braun, V., & Clarke, V. (2006). Using thematic analysis in psychology. Qualitative Research in Psychology, 3(2), 77–101. https://doi.org/10.1191/1478088706qp063oa

Braun, V., & Clarke, V. (2022). Thematic Analysis: A Practical Guide. SAGE Publications.

Guest, G., MacQueen, K. M., & Namey, E. E. (2012). Applied Thematic Analysis. SAGE Publications.

Nowell, L. S., Norris, J. M., White, D. E., & Moules, N. J. (2017). Thematic analysis: Striving to meet the trustworthiness criteria. International Journal of Qualitative Methods, 16(1). https://doi.org/10.1177/1609406917733847

Cite this entry

APA

Userhub. (2026). Thematic Analysis. UX Reference. https://userhub.com.bd/reference/thematic-analysis/