MDIA5031 Chap.6 Thematic Analysis of Interviews
Thematic Analysis of Interviews
Thematic Analysis of Interviews focuses on read, code, theme and explain. Thematic analysis moves from close reading of transcripts to a defensible account of patterned meaning; Familiarisation comes first: read across the material, note surprises and tensions, and preserve context before attaching labels;
Initial codes should capture something relevant to the question without pretending that every vivid quotation is already a theme; Codes may describe content, action, evaluation, identity, or contradiction; Themes are interpretive claims that organise several pieces of evidence around a central idea;
They are not interview topics, frequency counts, or headings copied from the guide; Review a candidate theme against both its extracts and the full dataset, split it when it contains unrelated ideas, and merge it only when one coherent organising concept remains; Reporting then combines an analytic claim, carefully selected evidence, explanation, and a link back to the question and framework;
What this chapter covers
- 01
Thematic Analysis of Interviews: central decision route
- 02
Read evidence and code boundaries
- 03
Theme decisions and difficult cases
- 04
Explain limits and transparent reporting
- 05
Initial code in the project audit trail
Apply the thematic analysis of interviews decision rule
- +1Use Initial code to identify what the scenario leaves unresolved.
- +1Apply Candidate theme: A developing interpretive pattern organised around a central meaning and tested against the dataset.
- +1Check the conclusion through Thematic coherence and state the remaining limit.
Key terms
- Initial code
- A provisional label attached to material that is relevant to the research question during close reading.
- Candidate theme
- A developing interpretive pattern organised around a central meaning and tested against the dataset.
- Thematic coherence
- The extent to which evidence within a theme supports one organising concept while remaining distinct from other themes.
Thematic Analysis of Interviews FAQ
How should I handle this read problem?
A provisional label attached to material that is relevant to the research question during close reading. Connect that definition to the specific material and state how it changes the available explain claim.
What should happen when theme creates a difficult case?
Return to the extracts and organising concepts; merge only if one coherent claim remains, otherwise redraw the boundary between them; Preserve the thematic analysis of interviews case in the record so the final method can explain that revision.
Why does explain matter here?
A thematic map can expose whether themes explain the research question or merely restate data topics; Draw the relationship among central and supporting themes, test negative or deviant cases, and revise names until they convey an analytic proposition; Select quotations for their evidential role, not because they are dramatic or unusually polished;
How can I review thematic analysis of interviews before submission?
Two candidate themes overlap heavily; How should they be reviewed; Write a theme definition that names its organising insight and specify which codes or extracts do not belong within it;
Assessment move
Thematic analysis moves from close reading of transcripts to a defensible account of patterned meaning; Familiarisation comes first: read across the material, note surprises and tensions, and preserve context before attaching labels;
Initial codes should capture something relevant to the question without pretending that every vivid quotation is already a theme; Codes may describe content, action, evaluation, identity, or contradiction; Themes are interpretive claims that organise several pieces of evidence around a central idea;
They are not interview topics, frequency counts, or headings copied from the guide; Review a candidate theme against both its extracts and the full dataset, split it when it contains unrelated ideas, and merge it only when one coherent organising concept remains;
Reporting then combines an analytic claim, carefully selected evidence, explanation, and a link back to the question and framework; Coding is provisional during early familiarisation; Keep enough transcript context to avoid turning a memorable phrase into a free-floating label, and write analytic notes about tensions as well as repetitions;
When a theme is named, its title should express the organising meaning, not merely repeat the interview topic that prompted the conversation; A thematic map can expose whether themes explain the research question or merely restate data topics;
Draw the relationship among central and supporting themes, test negative or deviant cases, and revise names until they convey an analytic proposition; Select quotations for their evidential role, not because they are dramatic or unusually polished;
Preserve counterexamples during theme review; A case that does not fit may refine a theme, expose a hidden condition or demonstrate that two experiences were prematurely combined under one attractive label; Write a theme definition that names its organising insight and specify which codes or extracts do not belong within it;
A vivid quotation appears once and is declared a theme; What is missing; Code it provisionally, compare it across the dataset, examine context and decide whether it supports a broader patterned meaning; Two candidate themes overlap heavily;
How should they be reviewed; Return to the extracts and organising concepts; merge only if one coherent claim remains, otherwise redraw the boundary between them; Review extracts within their transcript context before naming the organising meaning that links them;
The thematic account must preserve the counterexample that tests the coherence of the organising idea; Thematic Analysis of Interviews decision vocabulary: familiarisation memoing clustering recurrence divergence negative-case refinement centrality coherence saturation interpretation thematisation extract-context candidate-map semantic-pattern latent-meaning theme-boundary deviant-case naming-precision dataset-review