Skip to main content
v2026.11,986 entries · CC-BY 4.0

Thematic Analysis: A Step-by-Step Guide to Braun and Clarke’s Six Phases

How thematic analysis works: the six-phase Braun and Clarke framework, the three schools of thematic analysis (coding reliability, codebook, reflexive), inductive vs. deductive coding, and how to report it in a methods section.

Written and maintained by CASRAI Editorial Board

Published · Last updated

On this page

Thematic analysis is a method for developing patterns of meaning (themes) across a qualitative dataset to answer a research question. Braun and Clarke’s six-phase version is the most cited; they now call their own approach reflexive thematic analysis, one of three clusters alongside coding reliability and codebook approaches.

Thematic analysis is a method for identifying, analyzing, and reporting patterns (themes) within qualitative data — interview transcripts, focus-group discussions, open-ended survey responses, field notes, or documents. It is one of the most widely used qualitative analysis methods across psychology, health research, education, social science, and increasingly business and UX research, largely because it is flexible enough to work with almost any qualitative dataset and any theoretical framework, rather than being tied to a single epistemological position the way grounded theory or phenomenology are. To apply it to data that already exists rather than newly collected interviews, see secondary data analysis explained.

The method’s dominant modern reference point is Virginia Braun and Victoria Clarke’s 2006 paper “Using Thematic Analysis in Psychology” (Qualitative Research in Psychology, 3(2), 77–101), which set out a six-phase process that has since become the standard citation across disciplines far beyond psychology. Braun and Clarke have since revised and clarified their own approach substantially — most notably in a 2019 paper distinguishing their method, which they now call reflexive thematic analysis, from other approaches that also go by the name “thematic analysis.” Understanding that distinction matters more than most guides to the topic acknowledge, because conflating the different schools is one of the most common methodological errors reviewers flag in qualitative manuscripts.

What Are the Six Steps of Braun and Clarke’s Thematic Analysis?

Braun and Clarke’s 2006 framework has six phases: (1) familiarization with the data, (2) generating initial codes, (3) searching for themes, (4) reviewing themes, (5) defining and naming themes, and (6) producing the report. The phases are recursive rather than strictly linear, so researchers move back and forth between them as understanding develops. Each phase is described in detail below; for a hands-on walkthrough see the step-by-step Braun and Clarke guide.

The revised phase names

The authors now use updated names for the phases. On their own website they describe analysis as “typically a recursive process, with movement back and forth between different phases”, and present the phases as tools rather than rigid rules.

Phase 2006 name Current name
1 Familiarization with the data Familiarising yourself with the dataset
2 Generating initial codes Coding
3 Searching for themes Generating initial themes
4 Reviewing themes Developing and reviewing themes
5 Defining and naming themes Refining, defining and naming themes
6 Producing the report Writing up

What Counts as a “Theme”?

A theme in thematic analysis is not simply a topic that came up repeatedly, or a summary of everything participants said about a subject. Braun and Clarke are explicit that a theme should capture a coherent and meaningful pattern relative to the research question — something the researcher has actively constructed through interpretation, not passively discovered lying in the data waiting to be counted. This is the single most common conceptual error in student and early-career thematic analysis: treating themes as pre-existing labels for domains of content (“participants talked about family,” “participants talked about work”) rather than as analytic claims about what is going on across the dataset in relation to the question being asked.

When to Use Thematic Analysis (and When Not To)

Thematic analysis is a good fit when the goal is to understand patterns of meaning across a dataset without committing to a specific theoretical apparatus for generating that understanding. It is less suited to research questions that require a different, more specialized analytic logic:

  • Grounded theory is the better choice when the goal is to generate a novel theoretical model or explanatory framework from the data itself, with its own iterative sampling and theoretical-saturation logic. See CASRAI’s grounded theory entry for how the two methods differ in aim and process.
  • Discourse analysis is the better choice when the research question is about how language itself constructs meaning, identity, or power relations — the focus is on language-in-use, not on identifying patterns of meaning across a dataset. See CASRAI’s guide on how to conduct a discourse analysis.
  • Narrative analysis is the better choice when the unit of analysis is the story itself — its structure, sequence, and how it is told — rather than themes extracted across multiple participants’ accounts. See CASRAI’s guide on narrative analysis as a qualitative research method.
  • Content analysis (particularly quantitative content analysis) is the better choice when the goal is to systematically count the frequency of pre-defined categories across a large body of text, rather than to interpret patterns of meaning.

Thematic analysis is compatible with almost any research paradigm — positivist, interpretivist, or critical — because it is a method, not a methodology tied to a single set of ontological/epistemological commitments. See CASRAI’s research paradigm guide for how that distinction plays out in a methodology section.

See also Photovoice — Photovoice is a participatory method in which participants photograph their own lived experience and discuss the images using the SHOWeD framework, producing image-plus-caption data for thematic analysis.

The Three Schools of Thematic Analysis

Thematic analysis is best understood as an umbrella term for a family of approaches. Braun and Clarke’s own pages describe three clusters, and naming the one actually used is good methodological practice in a methods section. The data table below this guide compares the three on codebook, coders and the status of themes.

  • Coding reliability thematic analysis uses a structured codebook, multiple independent coders and an agreement measure such as Cohen’s kappa. Themes are treated as inputs that are developed early, and the project is oriented towards discovering what the data contain.
  • Codebook thematic analysis (which includes template analysis, framework analysis and matrix analysis) also uses a structured codebook, but works within a broadly qualitative philosophy and does not centre on reliability scores.
  • Reflexive thematic analysis, the authors’ own approach, uses flexible, organic coding. Themes are analytic outputs built from codes through the researcher’s engagement with the data, so reflexivity (see the reflexivity statement template) and the coherence of the analysis are the quality markers rather than coder agreement.

These are not interchangeable labels for the same procedure. A manuscript that reports “thematic analysis” without specifying which of the three it used, or that reports inter-rater reliability scores while citing Braun and Clarke’s reflexive approach (which does not advocate inter-rater reliability), is presenting an internally inconsistent methods section — a pattern peer reviewers in qualitative research increasingly flag.

Braun and Clarke’s Six-Phase Framework

The original 2006 framework, still the most commonly cited structure regardless of which of the three schools a researcher ultimately follows, sets out six phases. Braun and Clarke are explicit that the process is recursive, not strictly linear — researchers move back and forth between phases rather than completing each one once and moving on permanently.

  1. Familiarization with the data. Repeated, active reading of the full dataset (transcribing recordings personally, where feasible, is itself considered part of familiarization, not just a preparatory step) while noting initial ideas.
  2. Generating initial codes. Systematically coding interesting features of the data across the entire dataset, collating data extracts relevant to each code. Coding at this stage (see the worked example of coding interview data) should be comprehensive and inclusive rather than pre-filtered to what looks obviously relevant.
  3. Searching for themes. Collating codes into candidate themes, gathering all data extracts relevant to each candidate theme. This is where a mass of codes starts to be organized into a smaller number of broader patterns.
  4. Reviewing themes. Checking candidate themes against the coded extracts (do the extracts actually support the theme, and is the theme internally coherent?) and against the entire dataset (does the developing thematic map accurately represent the whole dataset, not just the extracts already coded?). Themes are commonly split, merged, or discarded at this stage.
  5. Defining and naming themes. Refining the specifics of each theme, identifying the “essence” of what each theme is about, and generating clear, concise names and definitions for each.
  6. Producing the report. Selecting vivid, compelling data extracts, relating the analysis back to the research question and existing literature, and writing up a coherent account — not just a list of themes with illustrative quotes attached.

Orientations: Inductive–Deductive, Semantic–Latent, Realist–Constructionist

Braun and Clarke describe the main analytic choices as continua rather than binary options: inductive to deductive, semantic to latent, and critical realist to constructionist. What matters, in their words, is that the analysis is theoretically congruent and consistent: the stated assumptions, the way data were collected, the coding approach and the claims in the write-up should fit one another. The two sections that follow explain the first two continua.

Inductive vs. Deductive Thematic Analysis

Thematic analysis can be conducted inductively (data-driven, where codes and themes emerge from the content of the data itself, with minimal reference to pre-existing theory) or deductively (theory-driven, where the analysis is guided by an existing theoretical framework, coding the data against categories derived from that framework). Many real analyses combine both: a largely inductive first pass supplemented by deductive coding against a specific theoretical concept the study is testing or extending. Whichever approach is used, it should be stated explicitly in the methods section, since it materially affects how the resulting themes should be interpreted.

Semantic vs. Latent Themes

A related distinction is between semantic (explicit) and latent (interpretive) themes. Semantic thematic analysis identifies themes within the explicit, surface meaning of what participants said, without looking for anything beyond what was directly stated. Latent thematic analysis goes further, examining the underlying ideas, assumptions, and ideologies that are theorized to shape or inform the semantic content — this level of analysis typically involves more interpretive work and is closer to a constructionist than a purely descriptive analytic stance. As with the inductive/deductive choice, most published studies sit somewhere on a continuum rather than at a pure endpoint, and stating where on that spectrum the analysis sits is part of a transparent methods section.

Software for Thematic Analysis

Qualitative data analysis software does not perform thematic analysis automatically — the interpretive work of generating and reviewing themes remains the researcher’s, not the software’s — but it substantially eases the mechanics of coding a large dataset: tagging extracts, retrieving all data linked to a given code, building and reorganizing a codebook, and keeping an audit trail of how codes evolved into themes. The most commonly used tools are NVivo, ATLAS.ti, MAXQDA, and the lighter-weight Delve, alongside manual approaches (color-coding printed transcripts, spreadsheet-based coding) that remain entirely valid for smaller datasets. See CASRAI’s NVivo guide for a detailed look at how one of the major platforms supports the coding-to-theme workflow described above.

Using software does not make an analysis coding-reliability or codebook TA. According to Braun and Clarke’s FAQ, software is not incompatible with reflexive TA per se; what matters is how a generated codebook is used, as a listing of codes from which to begin clustering rather than a fixed scheme applied to the data. See also the guides on NVivo with Braun and Clarke’s approach and coding in ATLAS.ti, and the entry on AI in qualitative coding.

How Many Participants and How Many Themes?

Braun and Clarke give indicative, not mandatory, guidance in their FAQ. For a small project they suggest roughly 6–10 rich interviews, for a medium project 10–20, and for a large project 30 or more. They say five interviews are “probably not” enough. For the number of themes, 2–6 themes including subthemes is “about right” for a single article, an undergraduate project, an Honours or Masters dissertation or a single doctoral analytic chapter. These are guides to be justified against your question and data, not rules. For fuller treatment of sample size reasoning see data saturation and information power.

Saturation and Reflexive Thematic Analysis

In “To saturate or not to saturate?” (Qualitative Research in Sport, Exercise and Health, 13(2), published online 26 December 2019, doi 10.1080/2159676X.2019.1704846), Braun and Clarke argue that saturation, understood as information redundancy or no new codes or themes appearing, fits the discovery-oriented project of coding reliability TA but not reflexive TA. In reflexive TA meaning is built through interpretation, so decisions about how much data to analyse are situated and subjective rather than triggered by a threshold. Alternatives that have been proposed include information power and theoretical sufficiency.

Inter-Rater Reliability: Why Reflexive TA Does Not Use It

According to the authors’ FAQ, inter-rater reliability assumes that meaning is fixed in the data, whereas in reflexive TA coding “bears the mark of the researcher(s)”. Agreement scores show that coders have been trained to code the same way, not that the coding is accurate, and coding cannot be right or wrong, only weaker or stronger. Sharing coding with an experienced supervisor or colleague for reflection is encouraged instead. If your study does use multiple independent coders and agreement statistics, you are doing coding reliability TA and should say so.

Quality Checklist: Braun and Clarke’s Twenty Questions

Braun and Clarke’s article “One size fits all? What counts as quality practice in (reflexive) thematic analysis?” (Qualitative Research in Psychology, 18(3), 328–352, doi 10.1080/14780887.2020.1769238) sets out common problems and twenty questions in two blocks.

  • Adequate choice and explanation of methods and methodology (questions 1–13): why TA was chosen, which type, how it fits the theory, data collection and aims, whether it was enacted consistently, whether problematic assumptions are present, whether the researcher’s own perspectives are stated, whether procedures are described as actually done, and whether concepts and procedures are confused.
  • A well-developed and justified analysis (questions 14–20): whether it is clear where the themes are, whether topic summaries are presented instead of fully realised themes, whether contextual information is presented as a theme, whether outcomes are actionable in applied research, whether there are conceptual clashes, whether the analysis is weak or unconvincing, and whether statements about generalisability are problematic.

Is a topic summary a theme?

No. A topic summary collects everything said about a subject, whereas a fully realised theme is an analytic claim built around a central idea. This is the test the checklist applies.

Reporting Guidelines

Braun and Clarke’s quality pages point to the Reflexive Thematic Analysis Reporting Guidelines (RTARG) and the Big Q Qualitative Reporting Guidelines (BQQRG), which are designed as a reflexive tool rather than a checklist. They also critique the use of checklists such as COREQ for reflexive work.

Common Mistakes in Thematic Analysis

  • Themes as topic summaries, not analytic claims. The single most common issue: presenting “domain summaries” (everything said about a given subject) as though they were themes, rather than identifying a coherent pattern of meaning across the data.
  • Not specifying which school of thematic analysis was used. Citing Braun and Clarke’s six phases while also reporting inter-rater reliability statistics mixes reflexive TA with coding reliability TA in a way that blurs two different approaches.
  • Coding too narrowly, too early. Filtering out data that doesn’t look immediately “interesting” during initial coding, rather than coding inclusively across the full dataset and letting theme development do the narrowing later.
  • Treating theme prevalence as the main quality marker. A theme’s value comes from what it captures about the research question, not from how many participants mentioned it or how many times it was coded — a theme voiced by a minority of participants can still be analytically important.
  • Insufficient reviewing. Skipping phase four (reviewing themes against both the coded extracts and the full dataset) and moving straight from initial candidate themes to a final write-up, which risks a thematic map that doesn’t actually represent the dataset as a whole.

Reporting Thematic Analysis in a Manuscript

A methods section reporting thematic analysis should specify, at minimum: which of the three schools (coding reliability, codebook, or reflexive) was followed and why; whether coding was inductive, deductive, or a combination; whether the analysis operated at a semantic or latent level; who conducted the coding (a single researcher, or multiple coders, and if multiple, how disagreements were resolved — noting that this question does not apply the same way under a reflexive-TA approach, which does not treat coder disagreement as an error to be reconciled); and how many phases of Braun and Clarke’s framework, or an equivalent process, were followed. Reporting a bare citation to Braun and Clarke (2006) with no further detail is increasingly treated by reviewers as under-specified, given how much the field’s own understanding of what “thematic analysis” means has diversified since that original paper.

Frequently Asked Questions

Is thematic analysis qualitative or quantitative?

Thematic analysis is a qualitative method. It works with non-numerical data (text, transcripts, open-ended responses) and produces an interpretive account of patterns of meaning, not statistical output. Some coding-reliability variants do report reliability statistics (like Cohen’s kappa) as a supplementary quality check, but the core analytic work stays qualitative.

What’s the difference between thematic analysis and content analysis?

Content analysis, especially in its quantitative form, typically involves systematically counting the frequency of pre-defined categories across text. Thematic analysis is more interpretive: themes are constructed through engagement with the data’s meaning rather than counted from a pre-set coding frame, though codebook thematic analysis sits closer to content analysis on this spectrum than reflexive thematic analysis does.

How many themes should a thematic analysis have?

There is no fixed number and theme count is not a quality marker. The authors regard 2–6 themes including subthemes as about right for a single article, undergraduate project, Honours or Masters dissertation or single doctoral analytic chapter.

Is five interviews enough for a thematic analysis?

The authors say five interviews are “probably not” enough, and suggest roughly 6–10 rich interviews for a small project, 10–20 for a medium project and 30 or more for a large one, as indicative guidance only.

What is the difference between coding reliability, codebook and reflexive TA?

Coding reliability TA uses a structured codebook with multiple independent coders and agreement statistics; codebook TA uses a structured codebook without centring reliability scores; reflexive TA uses flexible, organic coding and treats themes as outputs of the researcher’s interpretation.

Do I need a second coder for reflexive TA?

No. Reflexive TA does not advocate inter-rater reliability; sharing coding with an experienced supervisor for reflection is encouraged instead.

Can I use NVivo for reflexive thematic analysis?

Yes, according to the authors software is not incompatible per se. The issue is whether a generated codebook is used as a list to start clustering or as a fixed scheme applied to the data.

Does thematic analysis need data saturation?

Not in reflexive TA. Braun and Clarke argue saturation fits coding reliability TA better, and that sample decisions in reflexive TA are situated and subjective.

What are the revised names of the six phases?

Familiarising yourself with the dataset; Coding; Generating initial themes; Developing and reviewing themes; Refining, defining and naming themes; Writing up.

Do you need special software to do thematic analysis?

No. Software such as NVivo, ATLAS.ti, MAXQDA, or Delve makes coding a large dataset more manageable and auditable, but thematic analysis was originally developed and is still routinely conducted with manual methods (highlighting transcripts, index cards, spreadsheets) for smaller datasets.

What sample size does thematic analysis need?

There is no universal minimum. Use the indicative ranges above, justify the number against the richness of each data item and the scope of your claim, and avoid applying saturation as a blanket stopping rule in reflexive TA.

Sources

  • Braun, V. & Clarke, V. (2006). Using thematic analysis in psychology. Qualitative Research in Psychology, 3(2), 77–101. https://doi.org/10.1191/1478088706qp063oa
  • Thematic analysis FAQs (Braun and Clarke): https://www.thematicanalysis.net/faqs/
  • Understanding TA (Braun and Clarke): https://www.thematicanalysis.net/understanding-ta/
  • Doing reflexive TA (Braun and Clarke): https://www.thematicanalysis.net/doing-reflexive-ta/
  • Quality in TA (Braun and Clarke): https://www.thematicanalysis.net/quality-in-ta/
  • Braun, V. & Clarke, V. (2019). To saturate or not to saturate? doi 10.1080/2159676X.2019.1704846
  • Braun, V. & Clarke, V. (2021). One size fits all? What counts as quality practice in (reflexive) thematic analysis? doi 10.1080/14780887.2020.1769238; question list at https://study.sagepub.com/node/172745

Data: Three clusters of thematic analysis compared: codebook, reliability and theme treatment

Compares the three clusters of thematic analysis (coding reliability, codebook, reflexive) on how each treats the codebook, coders, agreement statistics and themes, compiled from the method developers' published FAQ and orientation pages.

Three clusters of thematic analysis compared: codebook, reliability and theme treatment
ClusterCodebookIndependent coders and agreement statisticsStatus of themes
Coding reliability TAStructured codebookMultiple independent coders; agreement measured with statistics such as Cohen's KappaInputs developed early
Codebook TA (template, framework, matrix analysis)Structured codebookNot centred on reliability scoresAnalytic inputs; often topic summaries
Reflexive TANo fixed codebook; flexible, organic codingInter-rater reliability not advocated; sharing coding with an experienced supervisor encouraged for reflectionAnalytic outputs built from codes through researcher engagement

Sources

Compiled by CASRAI from the sources above. Free to reuse under CC BY 4.0 with attribution.

Follow CASRAI

Research-administration guidance, standards updates and independent tool reviews.

Ask CASRAI · free to try

Ask about Thematic Analysis: A Step-by-Step Guide to Braun and Clarke’s Six Phases

2 free questions a day, no account.

An AI assistant for research: funder rules, compliance, methods and publishing. It links the sources behind its answers and labels answers that come from a web search.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays open to read, with no account and no card.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →