Community
RRITA is a living methodological resource, open to continued refinement by its user community. This space is designed for researchers to ask questions, share adaptations, and contribute to the method's ongoing development.
Curated answers to common questions about RRITA, and a way to get in touch with the people behind it.
Curated Q&A
Understanding RRITA
In what sense is RRITA "rapid"?
"Rapid" refers to workflow efficiency, not speed. By consolidating data generation, reflexive practices, coding, and theme development into one structured instrument, RRITA reduces the administrative friction that typically fragments the analytic process — reclaiming time and mental space for the interpretive work itself. RRITA prescribes no fixed timeline. Rigour and efficiency, in RRITA's logic, are complementary rather than competing.
How is RRITA different from reflexive thematic analysis?
Reflexive thematic analysis (Braun & Clarke, 2021) provides RRITA's interpretivist foundations and approach to theme construction, and RRITA inherits these fully. The difference lies in what RRITA adds and how it organises the process. RRITA introduces three analytic innovations absent from RTA: embedded, situated reflexive practices formalised directly within the analytic instrument; systematic engagement with discordant data and analytic tensions through a dedicated matrix feature; and a versioned analytic trail that renders the full reasoning process visible and auditable. It also provides a structured, stepwise workflow organised around an expand–compress cadence — something RTA deliberately leaves open. RRITA is therefore not a replacement for RTA but a methodological synthesis that makes RTA's depth more accessible and traceable under real-world constraints.
Is RRITA compatible with my epistemological stance?
RRITA is characterised by an interpretivist stance and treats researcher subjectivity as a central analytic resource to be documented and scrutinised rather than bracketed or minimised. Researchers working within constructivist, critical, or interpretive pragmatic paradigms will find it well-aligned. Compatibility with positivist or objectivist frameworks should be carefully assessed prior to adoption, as the method's core logic — particularly its reflexive practices — presupposes that knowledge is contextually and subjectively situated.
Using the matrix
How many matrix versions should I keep, and how do I organise them?
RRITA recommends maintaining one matrix per participant. As analysis proceeds, clearly named versions — Expanded, Compressed, Coded, Themed — are saved as separate tabs within the same spreadsheet file. This tab-based versioning preserves the analytic trail, allows immediate return to earlier interpretive states, and enhances transparency and traceability across participants. The naming convention is flexible; what matters is that the versioning logic is consistent and that no version is overwritten.
What do I do with data that doesn't fit any theme?
Outliers and unclassifiable codes are temporarily assigned to a Miscellaneous group during Step 6 and revisited as themes stabilise. Resist the urge to discard them early — what appears to be noise at one analytic stage often catalyses key insights later. If a code or extract remains unplaceable after themes are finalised, document it in the analytic tensions and discordance column and consider whether it signals a limitation of the thematic structure or a genuinely marginal data point. Either way, the decision and its rationale should be visible in the matrix.
Reflexivity in practice
What do I write in the reflexive anchor if I have no obvious prior connection to the topic?
The absence of an obvious personal connection is itself a reflexive position worth documenting. The reflexive anchor prompts scrutiny of assumptions, values, disciplinary training, and emotional resonances — not only biographical proximity to the topic. A researcher with no prior connection to palliative care, for instance, might document assumptions about illness, death, or caregiving shaped by professional training or cultural background. The anchor also captures methodological positionality: why this paradigm, why these domains, what the researcher hopes or fears to find. There is always something to document; the anchor is not a confessional but a thinking tool.
How do I know if a reflexive pivot is analytically justified?
A reflexive pivot is justified when the interrogation of positionality, tension, or discordance demonstrably redirects or deepens the interpretive trajectory — not merely reflects on it. The test is whether the pivot changes something in the analysis: a theme boundary is redrawn, an interpretation is revised, a code is reconsidered. In the RRITA manuscript example, the researcher's awareness of oscillating between a critical and a positive psychology lens led to prioritising the participant's framing of gratitude as a "gift from nowhere" over an analytic hunch of "rescue from somewhere" — a concrete interpretive consequence. If the pivot produces no analytic consequence, it belongs in the reflexive notes rather than as a formal pivot.
Adapting RRITA
Can RRITA be used with data other than individual interviews?
RRITA is optimised for individual qualitative interviews but may be adapted to other qualitative materials. In the gratitude study, it was applied to participant letters alongside interview data. Its matrix structure may also be adjusted to accommodate deductive and hybrid coding approaches. Adaptation to focus groups, ethnographic data, or digital materials would require additional methodological reflection — particularly regarding how the reflexive anchor handles multiple data sources and how the line of sight between raw data and analytic output is maintained across different material types. Researchers who adapt RRITA to new contexts are encouraged to document and share their adaptations via the Community section.
Can RRITA accommodate team-based analysis?
RRITA was developed primarily for individual analysis, and its reflexive practices — particularly the reflexive anchor — are designed around individual positionality. In team-based settings, the anchor can be adapted to capture each team member's positionality separately, with peer-debrief and critical-friend dialogues broadening interpretive possibilities without seeking consensus. RRITA does not prioritise inter-rater reliability as a quality marker, since interpretivist epistemology approaches divergent readings as analytically generative rather than problematic. Teams are encouraged to treat disagreement as analytic data rather than error.
Teaching and supervision
How do I use RRITA for student supervision?
The versioned matrix trail is RRITA's most powerful supervisory tool. Because every analytic decision — from code selection to reflexive anchor entries to theme warrants — is documented and dated within the matrix, supervisors can follow the student's reasoning step by step, identify where interpretive leaps are unjustified, and engage with the analysis at the level of specific decisions rather than global impressions. The theme warrant in particular makes the student's interpretive reasoning explicit and accountable, providing a concrete basis for feedback. RRITA is also well suited to formative supervision: the matrix can be shared at any stage of the analysis, not only when a draft is complete.
How do I introduce RRITA to students with no prior qualitative experience?
Start with the problem RRITA solves: the tension between wanting to do rigorous qualitative work and working under real constraints. Then introduce the matrix as the central instrument before explaining the steps — students grasp the logic better when they see where everything goes before learning how to populate it. The reflexive anchor is often the most unfamiliar element; frame it early as a thinking tool rather than a confessional, and model it with your own positionality as an example. The gratitude study examples in the manuscript and supplementary materials can be used directly as teaching illustrations.
Get in touch
Share how you've applied RRITA, propose a question for this page, or send a note to the team.