Reflexivity in thematic analysis: what it means and how to write it

What reflexivity means in reflexive TA

In quantitative research, a researcher's perspective is treated as a threat to validity, something to control for or train out through inter-rater agreement. Braun and Clarke build reflexive TA on the opposite premise. Themes are not sitting in the data waiting to be discovered; they are built by a researcher who brings a standpoint, a discipline, and a set of assumptions to every coding decision. That standpoint is a resource you use, not a contaminant you apologise for. Our Braun & Clarke thematic analysis guide covers where this fits among the six phases; this guide stays on the reflexivity itself.

Braun and Clarke made the point directly in their 2019 reflection on the method's uptake, pushing back on studies that claimed reflexive TA while still describing coding as a mechanical, researcher-free process. Reflexivity, in their framework, is not an optional add-on. It is part of what makes the analysis reflexive TA rather than a looser, undertheorised version of coding.

Why “themes emerged” is the tell

Watch for this phrase in your own draft: “three themes emerged from the data.” It sounds neutral, even modest. To an examiner trained in reflexive TA, it signals the opposite of reflexivity: a claim that the themes surfaced on their own, independent of any decision you made. You didn't let themes emerge. You read the transcripts through a particular lens, coded selectively, decided which candidate themes earned their place, and named them in your own words. Write it that way: “I constructed three themes,” or “three themes were developed from the coded data,” and be ready to say why those three and not five.

Two kinds of reflexivity, not one

Linda Finlay's widely cited work on reflexive practice draws out several variants, but two matter most for a thematic analysis write-up. Personal reflexivity is about you: your background, prior experience with the topic, and why you care about the question. Epistemological reflexivity is about your method: how the assumptions built into your approach (what counts as data, what counts as a theme, semantic or latent coding) shaped what you were able to find.

A statement that covers only the personal side (“as a former nurse, I have direct experience of this setting”) reads as biography, not reflexivity. Pair it with the epistemological side, how that background influenced a specific coding or theming decision, and it starts doing the analytic work an examiner is looking for.

How to actually write it

A workable positionality statement usually does three things in order: states your relationship to the topic, names at least one assumption or piece of prior experience that could shape your reading, and ties that directly to a decision you made in the analysis — a code you almost missed, a theme you nearly merged with another, a choice to read semantically rather than latently. The third part is the one most drafts skip, and it is the part that separates reflexivity from disclosure.

Most methods chapters place this in a dedicated subsection — often titled “Researcher positionality” or “Reflexivity” — inside the methodology chapter. Strong write-ups also return to it briefly in the discussion, noting where the researcher's standpoint plausibly shaped a specific finding, rather than treating reflexivity as something you declare once and never revisit.

A worked example

Weak: “As the researcher, I acknowledge that my own views may have introduced some bias into the analysis. I tried to remain as objective as possible throughout.”

This apologises for a standpoint without describing it, and “objective” is precisely the goal reflexive TA sets aside.

Stronger: “I completed this study as a final-year student who had spent two summers volunteering on the ward where the interviews took place. That familiarity helped me read past surface politeness in participants' answers — I recognised guarded phrasing I had heard used the same way by staff before. It also meant I initially read one code, ‘we just get on with it,’ as straightforward resilience. On a second pass, I recognised it as the same deflection I had used myself when asked about difficult shifts, and reread the surrounding data with that in mind, which led me to reframe the theme as reluctant coping rather than resilience.”

Notice the second version names a real background, ties it to a specific code, and shows the analysis changing because of it. That is what an examiner is checking for.

Where these statements usually go wrong

• Treating it as an apology. Reflexivity isn't a confession that your analysis is compromised. It's an account of how your perspective shaped a legitimate interpretation.
• Writing it once, at the front, and forgetting it. If your positionality never resurfaces near your findings, it reads as a box you ticked rather than a stance you held throughout.
• Staying generic. “I tried to be aware of my biases” describes every researcher who has ever lived. Name the specific experience and the specific decision it touched.

Where the analysis tool fits — and where it doesn't

Reflexivity is the one part of this process that has to stay yours; no tool can write an honest account of your own standpoint. What the thematic analysis tool on this site can do is take the grinding first pass, coding line by line and clustering codes into candidate themes using the Braun & Clarke framework, off your plate, so the hours you get back go toward the reflexive thinking above instead. Once you have a structured draft of codes and themes, our worked dissertation example shows how that draft turns into methodology and findings chapters, positionality statement included. First three studies are free, no signup.

References

• Braun, V. and Clarke, V. (2006). Using thematic analysis in psychology. Qualitative Research in Psychology, 3(2), pp.77–101. doi:10.1191/1478088706qp063oa
• Braun, V. and Clarke, V. (2019). Reflecting on reflexive thematic analysis. Qualitative Research in Sport, Exercise and Health, 11(4), pp.589–597. doi:10.1080/2159676X.2019.1628806
• Finlay, L. (2002). Negotiating the swamp: the opportunity and challenge of reflexivity in research practice. Qualitative Research, 2(2), pp.209–230. doi:10.1177/146879410200200205