I used to think coding was clean. Apply a label, sort the data, move on. Then I started actually coding for reflexive thematic analysis.
Suddenly I found myself staring at a phrase like “She seemed more relaxed” and asking: is this a semantic code? Or am I interpreting too much? Is this about child confidence… or am I just hoping it is?
Reflexive thematic analysis invites us to sit with that mess. Braun & Clarke don’t ask for perfect distinctions – they ask us to be reflexive about our role in making meaning.
So I started keeping a “murky codes” list – entries I wasn’t sure about, to revisit later. Some became strong latent themes. Some I dropped. But the point was, I thought through my decisions, rather than pushing uncertainty aside.
Reflexivity isn’t just about the emotional stuff. It’s about being honest when your analysis isn’t clean and knowing that’s not a flaw, it’s the work.