What Does Reflexivity Look Like in Practice?

You know the drill. The methodology section needs a paragraph on reflexivity. So you write: "As a mid-career researcher, I acknowledge that my background shapes my interpretation." Maybe you add a line about being an insider or outsider. Job done, right?

Not really.

That kind of positionality statement is better than nothing, but it's not reflexivity. It's a confession. And the difference between the two is the difference between saying you exercised and actually breaking a sweat.

Reflexivity is an active, ongoing practice of interrogating how your values, assumptions, and presence shape every stage of your research. It's uncomfortable, it's iterative, and it never really ends. But it's also the thing that separates rigorous qualitative work from research that readers can't trust.

Here's what it actually looks like in practice.

Why Do Most Researchers Get Reflexivity Wrong?

The most common mistake is treating reflexivity as a box to tick. You write a paragraph about your identity in the methods section, and then you never think about it again. That's not reflexivity. That's a biographical note.

Other common mistakes include writing a general biography without connecting it to specific research decisions, using reflexivity to claim neutrality (the opposite of what it's for), and getting stuck in "cerebral gridlock" where you overthink every minor decision to the point of paralysis.

Good reflexivity is none of these things. It's a practical tool for doing better research, not a performative ritual for satisfying reviewers.

What Does Reflexivity Actually Look Like in Practice?

Here are concrete techniques you can use at each stage of a qualitative project.

During Planning: Set Your Baseline

Before you collect a single piece of data, write down your assumptions. What do you expect to find? What are your hypotheses? What personal experiences or theoretical commitments might steer your attention in one direction over another?

This baseline list is your anchor. Revisit it after each phase of data collection to see how your thinking has evolved. The gap between what you expected and what you found is often where the most interesting insights live.

During Data Collection: Track Your Emotional Responses

Immediately after each interview or observation, write a quick entry in a reflexive journal. What felt comfortable? What felt awkward? Where did you stay quiet when you could have asked a follow-up? What emotions came up?

One researcher we know was studying reproductive decision-making. When an older participant asked when she was having a baby, she laughed and played along rather than saying she didn't want children. Reflecting on that moment later, she realised she had colluded in naturalising a heteronormative narrative. That became a key insight in her write-up about gendered power dynamics in interviews.

The point is not to berate yourself for these moments. The point is to notice them and use them as data.

During Analysis: Write Reflexive Memos

As you code your transcripts, pause regularly to write about why you are interpreting something a certain way. Ask yourself: "Am I emphasising this theme because it aligns with my personal values? Would someone else group these quotes differently?"

A useful trick: use an AI tool like Paideias to generate an alternative reading of a passage. The friction between your interpretation and the AI's can surface assumptions you didn't know you were making. Just don't outsource the interpretation itself. The researcher is the instrument.

During Writing: Connect Identity to Decisions

A strong positionality statement does not just list your demographic characteristics. It shows how specific aspects of your background shaped specific research decisions.

For example: "My past experience as a classroom practitioner drew my attention to how students divided into groups, and made me more sympathetic to the teacher's challenges in managing a busy environment. A researcher without that background might have framed the same observations differently."

That is a concrete link between identity and analysis. It gives readers enough information to evaluate your claims for themselves.

Will Reflexivity Ruin My Objectivity?

This is a common fear among newer qualitative researchers. The answer is no, and the question itself reveals a misunderstanding.

Reflexivity is not about achieving objectivity. It's about embracing your subjectivity transparently. Qualitative research does not pretend to be value-free. The strength of qualitative work lies in its depth and contextual richness, not in its distance from the researcher. Reflexivity is what lets you claim that depth honestly, by showing your readers exactly how you arrived at your interpretations.

Can You Be Too Reflexive?

Yes. Overdoing it leads to what some researchers call "analysis paralysis" or "narcissistic self-indulgence." If every single coding decision comes with a 200-word reflexive memo, you will never finish your analysis.

The goal is to be reflexive enough to catch meaningful blind spots, not reflexive enough to write a memoir. Use critical friends and peer debriefers to help you calibrate. If a peer reads your positionality statement and can't see how it connects to your analysis, you are either over-sharing or under-linking.

How Does This Work With AI-Assisted Analysis?

Good question, because AI tools are changing how we code qualitative data. The key is to use AI as a reflexive prompt, not as a shortcut around reflexivity.

When you use a tool like Paideias to help with coding, you can ask it for an alternative interpretation of a passage. Compare that to your own reading. Where do they differ? What does that difference tell you about your own assumptions?

The goal is friction, not automation. The AI should make you think harder, not let you think less.

But watch out: if you let the AI do all the coding and skip the memos, you lose the reflexive work entirely. Speed is useful. Skipping the hard parts of analysis is not.

FAQ

How long should a positionality statement be?

Usually 150 to 500 words. Short enough that reviewers actually read it, long enough to show a genuine connection between your identity and your research decisions.

Should I write my positionality statement before or after data collection?

Both. Draft it during the proposal phase, then revise it after data collection. Your assumptions will shift, and your statement should reflect that.

Do I need to disclose everything about myself?

No. Only disclose identity factors that are relevant to the research context and the population you are studying. A positionality statement is not a biography.

Is reflexivity only for interview-based research?

No. It applies to any qualitative method: ethnography, focus groups, discourse analysis, content analysis. The specific techniques may differ, but the principle is the same.

Can Paideias help with reflexivity?

Yes. Paideias maintains a full audit trail of your coding decisions, which is the backbone of a strong reflexivity practice. You can trace how your codes evolved, revisit your memos, and generate alternative readings that surface hidden assumptions. It doesn't do the reflexive work for you, but it makes it easier to do well.