19. Reflexivity & Positionality in Research
Before you start
- Awareness that all observation is theory-laden and observer-positioned
- Comfort writing in the first person where appropriate
- Willingness to interrogate your own training and assumptions
By the end you'll be able to
- Treat the self as a primary research instrument
- Document positionality and its analytic implications
- Apply a decolonizing approach where appropriate
- Shift from research **on** to research **with**
- Build reflexivity into the project workflow, not the discussion section
The researcher as instrument
In qualitative work, the researcher is the primary research instrument. The researcher's perception, training, intuitions, and discomforts shape what counts as data and what gets interpreted. Acknowledging this isn't humility theater; it's accuracy.
Even in quantitative work, the researcher's choices — what to measure, what to include, what to omit, how to model — shape what the study can find. The instrument is more visible in qual work, but it's present in quant work too.
The transdisciplinary discipline is to treat the instrument as auditable. Document positioning, document analytic decisions, document the reasoning that shaped both.
Positionality beyond demographics
A positionality statement that says "I am a [demographic, demographic, demographic]" and stops is decorative. It tells the reader nothing about how the position shaped the work.
A useful positionality statement names:
- Training — what disciplines and traditions shaped your methodological intuitions?
- History — what professional and personal experiences ground your understanding of the topic?
- Stake — what do you stand to gain or lose from particular findings?
- Distance — what's your social distance from the population studied (insider, outsider, partial-insider)?
- Analytic implications — how do each of these shape what you can see and what you might miss?
The last point is the analytic move. "My clinical training predisposes me to read participant accounts as system failures rather than personal choices" is more useful than "I am a clinician." The first names a predisposition; the second names a category.
Reflexivity as ongoing, not retrospective
A reflexive paragraph in the discussion section is better than nothing. It's worse than reflexivity built into the project workflow.
Practical workflow reflexivity:
- Post-interview memo — 10 minutes after each interview, three prompts: what surprised me? what am I tempted to discount? whose voice would read this differently?
- Weekly reflexive journal — short entries during fieldwork tracking analytic intuitions and discomforts
- Team-level reflexivity meetings — bringing memos to analysis discussions and using them to interrogate emerging interpretations
- Alternative-explanations memos — explicit consideration of competing readings of each major finding
- Versioned positionality — positionality at start vs. end of project; what shifted, what stayed
The artifacts are the rigor. A reflexivity practice without artifacts is hard to audit and easy to skip.
Power and identity in the research process
Reflexivity is incomplete without an analysis of power. Research relationships have power dynamics — between researcher and participant, between academic and community partner, between funder and researched community. These dynamics shape what's said, what's documented, and what becomes findings.
Questions to interrogate explicitly:
- Who has the power to decide what the question is?
- Who has the power to decide what counts as a finding?
- Who controls the data after collection?
- Who benefits from publication?
- Who can refuse the study?
A study that doesn't name these dynamics treats them as natural. Naming them is the precondition for changing them.
Decolonizing methodologies
Linda Tuhiwai Smith's Decolonizing Methodologies and the body of work it has shaped reframes the relationship of researcher to researched community. The core insight: research on colonized and marginalized peoples has historically been extractive, and many of the methodological practices we treat as neutral were developed in that context.
Decolonizing isn't a citation move. Done seriously, it entails:
- Ceding decision rights to the community on key questions
- Restructuring relationships so that the research relationship is ongoing, not transactional
- Refusal as legitimate — communities may decline research, and that refusal is honored
- Reciprocity built into the project structure — paid roles, training, capacity-building, material benefit
- Community sovereignty over data — including the right to withdraw or refuse certain analyses
- Community-controlled dissemination — outputs designed for the community's purposes, not only academic publication
These commitments are structural. A project that cites Smith but operates without these structures is doing rhetorical decolonizing.
Research with, not on
The shift from "research on subjects" to "research with participants" is more than a vocabulary update. It signals a structural shift:
- On implies extraction: the researcher takes from the population to produce a paper.
- With implies partnership: the researcher and the participants produce knowledge together, with mutual obligations.
The vocabulary is easy; the structure is hard. A study that calls participants "co-researchers" without giving them decision authority or compensation is misusing the term.
Practical structural markers of "research with":
- Community partners hold paid roles
- Decision authority is shared on specified questions
- Outputs include community-controlled artifacts
- Project budget allocates resources to the community partner
- Authorship or formal recognition extends to community contributors
A worked positionality example
Original statement: "I am a white woman researcher from a U.S. university studying maternal health in a rural African community."
Reframed statement: "I am a white, U.S.-trained public-health researcher with 12 years of fieldwork in this region, including ongoing collaborations with two community organizations. My disciplinary training in epidemiology predisposes me to read maternal health questions through a clinical-outcomes frame, and to discount accounts that center spiritual or relational explanations of pregnancy outcomes. To mitigate this, the analysis team includes a Tanzanian midwife co-investigator and a community advisory board that holds decision authority on dissemination. The team uses alternative-explanations memos to interrogate readings that align too closely with my clinical training. My stake in the work includes publication and tenure considerations, which are partially mitigated by joint authorship structures and a non-academic deliverable (community-controlled health resource) that's the primary output for the partner organizations."
The reframed version is longer because positionality, when done analytically, is longer.
Bias mitigation through structure
Reflexivity surfaces bias; structure mitigates it. Practical structures:
- Second coders with different positionalities
- Cross-cultural review of interpretations before lock-in
- Member checking as data, not approval
- Triangulation across data sources
- Pre-registered analytic plans for quant components, to limit researcher-degrees-of-freedom
- Devil's advocate roles in team analysis meetings
Bias doesn't disappear. Structure makes it visible and partially mitigated, which is what rigor in this domain looks like.
Closing
The researcher is the primary instrument; document the instrument. Positionality must be analytic, not demographic-only. Reflexivity through workflow artifacts beats reflexivity at write-up. Power dynamics shape every research relationship; name them. Decolonizing methodologies require structural change, not citation. Research with, not on, requires shared decision rights and reciprocity.
Next: systems thinking in data interpretation — feedback loops, emergence, and avoiding reductionist conclusions.
Common mistakes
These are the traps learners hit most often on this topic. Knowing them in advance is half the fix.
Writing a positionality statement that lists demographics and stops
Demographics are a starting point. Real positionality names how your training, history, and current commitments shape what you can see and what you discount. Without that analytic step, the statement is decorative.
Doing reflexivity only at write-up time
Reflexive notes throughout the project (during recruitment, after interviews, while coding) are the actual rigor. A retrospective paragraph is better than nothing but worse than live reflection.
Treating decolonizing as a citation move
Decolonizing methodologies entails ceding decision rights, restructuring relationships, and sometimes refusing research altogether. Citing Smith or Tuhiwai-Smith without changing practice misses the point.
Practice problems
Try each on paper first. Click Show solution only after you've made a real attempt.
- Problem 1Write a positionality statement that names two of your commitments and how each could shape your analysis.
Show solution
A good statement reads as analytic, not confessional. 'My clinical training predisposes me to read participant accounts as health-system failures rather than as personal choices; mitigation is a second coder with policy training who flags my over-extension to structural causes.'
- Problem 2Identify one reflexive practice you'll commit to during a current or upcoming project.
Show solution
Practices that survive deadlines are short and structured. A 10-minute post-interview memo with three prompts ('what surprised me', 'what I am tempted to dismiss', 'who would read this differently') is far more rigorous than a 'I'll reflect when I have time' plan.
Practice quiz
- Question 1The most rigorous reflexive practice happens:
- Reflection 2Name three structural changes a project would make if it took decolonizing methodologies seriously.
Lesson 19 recap
- The researcher is the primary instrument; document it
- Positionality must be analytic, not demographic-only
- Reflexivity throughout > reflexivity at the end
- Decolonizing is structural, not citational
Coming next: Lesson 20 — Systems Thinking in Data Interpretation
- Next: systems thinking in data interpretation
- Feedback loops, emergence, non-linearity
- Mapping complexity to avoid reductionism
Saved in your browser only — no account, no server.