Skip to content
Back to search results

Reflexive Thematic Analysis — Braun & Clarke

Introduced by
Virginia Braun & Victoria Clarke
Year
2006 (seminal paper); explicitly named 'reflexive' from ~2019
Type
Qualitative research method
Family
Thematic Analysis
Font size

What does it do?

Reflexive Thematic Analysis (RTA) is a widely used qualitative method for identifying, analysing, and interpreting patterns of shared meaning — called themes — across a dataset.

Developed by Virginia Braun and Victoria Clarke, it is theoretically flexible, works across epistemological positions, and foregrounds the researcher's active, interpretive role rather than treating themes as features that simply emerge from data. It differs from older 'codebook' approaches by treating the analyst's subjectivity as a resource rather than a source of bias to be suppressed.

The intuition behind the method

Think of RTA as a disciplined process of reading, rereading, and making meaning from qualitative data. Unlike a simple frequency count of words, the researcher actively constructs themes — interpretive claims about what the data reveal about the research question. The 'reflexive' in the name signals that the analyst continuously reflects on how their own perspective, assumptions, and decisions shape the analysis. This is not a weakness to hide; it is an explicit methodological commitment. A good RTA study does not pretend the analyst is invisible; it shows how the analyst's thinking developed across six iterative phases.

History

Virginia Braun and Victoria Clarke published their foundational paper on thematic analysis in Qualitative Research in Psychology in 2006, providing the first step-by-step methodological guide that made the approach accessible across disciplines. This paper became one of the most cited articles in qualitative research. Over the following decade the authors observed widespread misapplication of their method, particularly confusion with codebook approaches and the erroneous assumption that themes 'emerge' from data. In response, from around 2019 they explicitly distinguished 'reflexive thematic analysis' as a named, theoretically grounded approach, emphasising the analyst's interpretive agency and continuous reflexivity as constitutive of the method rather than optional add-ons.

When to use it

RTA is appropriate when the research question asks what patterns of meaning exist in qualitative data — what people think, feel, do, or experience in relation to a topic. It is suitable across disciplines (health, education, psychology, social sciences) and epistemological positions (realist, constructivist, critical). It fits exploratory, descriptive, and interpretive purposes. It requires text data from interviews, focus groups, open-ended survey responses, or documents. RTA is NOT appropriate when the goal is to build a grounded theory (use grounded theory), to describe a single individual's experience in depth (use case study or IPA), or to test hypotheses (use quantitative methods).

Limitations and considerations

  • Findings are context-specific and not statistically generalizable; transferability depends on thick description rather than sampling logic.
  • The quality of analysis depends heavily on the analyst's skill in constructing interpretive — not merely descriptive — themes.
  • Without genuine reflexivity, themes can inadvertently reflect the researcher's preconceptions rather than patterns in participants' accounts.
  • The method does not produce a formal theory or explain causal mechanisms; for theory-building, grounded theory is more appropriate.

Source conditions do not replace independent scientific review or validation by an analysis engine.

Strengths

  • Theoretically and epistemologically flexible — applicable from realist to constructivist and critical frameworks.
  • Does not require a large sample; rich, in-depth data from a smaller number of participants is more valuable than breadth.
  • Transparent about the analyst's role — reflexivity is a methodological strength, not a confound to be minimised.
  • Accessible entry point for qualitative research; the six phases provide a clear procedural scaffold without rigid rules.
  • Well-suited to applied research contexts where the goal is to understand stakeholder perspectives on real-world issues.

Applications

  • Analysing patient interview data to understand experiences of living with a chronic condition or navigating healthcare services.
  • Examining open-ended survey responses to capture employee or student perceptions of an institutional programme.
  • Exploring focus group data on public attitudes toward a social policy, technology, or health behaviour.
  • Investigating interview transcripts on professional identity, occupational stress, or workplace culture.
  • Interpreting social media posts, news articles, or policy documents to understand how a phenomenon is constructed in public discourse.

How it works

How it works

1

The analyst immerses themselves in the dataset by reading and rereading all transcripts or documents, listening to audio if available, and taking initial notes. This phase is not passive; the researcher begins to notice patterns, puzzles, and ideas about what the data might mean in relation to the research question. Active engagement from the first contact with data is essential.

2

Working systematically through the entire dataset, the analyst generates codes — concise labels that capture something analytically interesting about a data extract. Codes are assigned to every relevant piece of data. In RTA, coding is a creative and interpretive act: the analyst decides what is noteworthy and why, producing a rich code set that reflects the research question rather than simply cataloguing everything said.

3

Codes are sorted, grouped, and reorganised to identify potential themes. A theme is not merely a frequently occurring topic; it is a coherent, interpretive claim about a pattern of shared meaning across the dataset. At this stage the analyst works with all coded data extracts and begins to map candidate themes visually — often using thematic maps or affinity diagrams — noting how codes relate to or differ from each other.

4

The analyst tests candidate themes against the full dataset in two rounds. First, the coded extracts within each candidate theme are reviewed to check that they form a coherent picture. Second, each theme is read in relation to the whole dataset to ensure the theme set captures the data adequately. Themes may be merged, split, discarded, or renamed. Reflexive memos document the reasoning behind these decisions.

5

Each retained theme is given a clear name and a detailed definition that captures its scope and focus — what it is about and what it is not about. The analyst identifies the best illustrative data extracts for each theme. The defining work is analytical, not descriptive: each theme should make an interpretive claim, not merely summarise what participants said on a topic.

6

The final report weaves together analytic narrative with selected data extracts to tell a compelling interpretive story about the dataset in relation to the research question. The write-up is not a sequential tour of themes; it argues for the interpretation, shows how evidence supports it, and positions findings in relation to relevant literature. The researcher's reflexive positionality is typically addressed in a methods section or reflexivity statement.

Common pitfalls

  • Treating themes as emerging from the data rather than being constructed by the analyst — this misrepresents the epistemological basis of RTA and leads to under-theorised, descriptive themes.
  • Confusing a theme with a topic — a theme must make an interpretive claim about a shared pattern of meaning, not merely label what participants talked about.
  • Privileging data quantity over quality — counting how many participants mentioned something is not the basis for a theme; interpretive relevance to the research question is.
  • Skipping genuine reflexivity — simply naming one's background in a methods section is not sufficient; the analyst should document throughout the analysis how their perspective shaped coding and theme development.
  • Applying codebook TA logic (fixed, pre-defined codes agreed by multiple coders) and calling it reflexive TA — the two approaches have different epistemological premises and should not be conflated.

Frequently asked questions

How is reflexive thematic analysis different from codebook thematic analysis?

Reflexive TA treats coding as an interpretive act carried out by a single analyst (or small team working collaboratively), with themes constructed fresh from each dataset. Codebook TA pre-specifies a shared code dictionary, often uses inter-rater reliability checks, and aims for replicability across analysts. The two approaches rest on different epistemological premises: reflexive TA is broadly constructivist and foregrounds the analyst's subjectivity; codebook TA tends toward a (post-)positivist ideal of researcher-independent findings.

How many participants or data items do I need?

There is no fixed minimum in reflexive TA. Braun and Clarke argue that sample size should be determined by the research question, data richness, and the depth of analysis sought — not by a universal number. Smaller samples of 6–15 in-depth interviews are common in rich, experiential studies; larger open-ended survey datasets may involve hundreds of responses. The guiding question is whether the dataset provides sufficient breadth and depth to address the research question.

Do I need to use software such as NVivo or ATLAS.ti?

Software is optional. NVivo, ATLAS.ti, or Dedoose can assist with organising, searching, and retrieving coded data, but they do not perform the interpretive work. The intellectual core of RTA — deciding what is meaningful, constructing codes, building themes, and writing reflexive memos — cannot be delegated to software. Many researchers do RTA with word-processing documents, spreadsheets, or printed transcripts and coloured pens.

What makes a good theme in reflexive TA?

A good theme makes a clear interpretive claim about a pattern of shared meaning in the dataset that is relevant to the research question. It is not a simple label for a topic people discussed. It should be internally coherent (the data extracts within it belong together), distinct from other themes, and analytically significant — it says something interesting about the data beyond summarising it.

How is reflexive TA different from grounded theory?

Both are qualitative approaches using iterative coding, but they differ in goal and procedure. Reflexive TA aims to identify patterns of meaning across a dataset in relation to a research question; it does not aim to build a substantive theory. Grounded theory aims to generate a formal theory grounded in data through theoretical sampling, constant comparison, and theoretical saturation. Grounded theory also typically involves concurrent data collection and analysis, whereas RTA usually analyses a complete dataset.

Related methods

Sources

  1. Braun, V., & Clarke, V. (2006). Using thematic analysis in psychology. Qualitative Research in Psychology, 3(2), 77–101.

    Open DOI reference
    Copied.
  2. Braun, V., & Clarke, V. (2019). Reflecting on reflexive thematic analysis. Qualitative Research in Sport, Exercise and Health, 11(4), 589–597.

    Open DOI reference
    Copied.