Thematic analysis: a step-by-step guide for students

Thematic analysis: a step-by-step guide for students

Your transcripts are open, the assignment deadline is getting closer, and every participant seems to be saying something slightly different. You can see repeated ideas, but turning those ideas into “themes” feels risky: if you group too broadly, the findings sound vague; if you code every line separately, you end up with a spreadsheet nobody can read. Thematic analysis is often introduced as a flexible method, which is true, but that flexibility can leave undergraduate and master’s students wondering what counts as enough evidence, how many themes they need, and how to write findings without simply summarising interviews one by one.

In reflexive thematic analysis, researchers develop patterns of shared meaning through sustained engagement with qualitative data. Braun and Clarke’s six phases guide familiarization, coding, theme development and reporting; researchers revisit earlier work as their interpretation changes. The phases are a framework for inquiry, not a guarantee that following steps produces a sound analysis.

Scope: This guide focuses on reflexive thematic analysis. Coding-reliability and codebook approaches make different assumptions; choose and explain the approach that fits your question rather than combining their procedures without justification. See Braun and Clarke’s explanation of the approaches.

Teaching examples: All participant quotations, datasets and study findings used as examples below are fictional. They demonstrate analytical choices and must not be presented as collected research data.

In this guide

• What is thematic analysis in student research?
• When should you use thematic analysis for an undergraduate or masters paper?
• What are the six Braun and Clarke thematic analysis steps?
• How do you code qualitative data without losing the meaning?
• What does a thematic analysis example look like?
• How do you write up themes in a results or findings section?
• What mistakes do students commonly make when doing thematic analysis?
• How can you check whether your thematic analysis is ready to submit for feedback?

What is thematic analysis in student research?

Thematic analysis refers to related approaches for exploring patterned meaning in qualitative data. This guide uses the reflexive approach, in which the researcher actively develops an interpretation rather than simply retrieving themes that already exist in the material. Explain how this approach fits your question, theoretical assumptions and dataset.

Key terms students need before coding

Code means a short label attached to a meaningful data extract. A code might be close to the participant’s words, such as “feeling watched by managers,” or more interpretive, such as “surveillance pressure.”

Theme means a broader pattern of meaning built from related codes. A theme is not just a topic label. “Social media” is a topic; “social media as a source of comparison pressure” is closer to a theme because it says something about meaning.

Dataset means the full body of material you analyse. In a small undergraduate paper, that might be six interview transcripts. In a graduate seminar paper, it might be 40 open-ended survey responses and a set of organisational documents.

What thematic analysis does and does not do

Thematic analysis helps you move from raw qualitative material to an organised interpretation. It does not count as a shortcut for avoiding method decisions. You still need a research question, a rationale for your data source, and a transparent explanation of how you moved from extracts to themes.

For example, in a psychology paper on first-year students’ experiences of academic stress, thematic analysis could show patterns such as “normalising burnout” or “seeking informal reassurance before formal support.” In a nursing master’s project on medication adherence after discharge, it could identify themes such as “confusion at the transition home” or “family members as unofficial medication managers.”

How thematic analysis differs from simple summary

A simple summary reports what participants said one after another. Thematic analysis compares the whole dataset and asks what repeated meanings appear across cases. That means your findings section should not read like “Participant 1 said..., Participant 2 said..., Participant 3 said....”

A useful test is this: if removing participant names destroys the structure of your analysis, you may still be summarising individuals rather than analysing themes. Themes should organise evidence across the dataset, not merely list responses.

When should you use thematic analysis for an undergraduate or master's paper?

Use thematic analysis when your research question asks about experiences, perceptions, meanings, practices, barriers, motivations, or representations. It fits many undergraduate and master’s qualitative projects because it can be applied to different types of textual data and different theoretical positions. It is less suitable when your project needs statistical testing, causal measurement, or formal theory generation as the main outcome.

Good fits for thematic analysis

Thematic analysis works well when students ask questions such as “How do students describe...?”, “What barriers do participants experience...?”, or “How is a topic represented in documents?” These questions invite patterned interpretation rather than numerical comparison.

In education, a seminar paper might ask: “How do trainee teachers describe the challenge of classroom behaviour management during placement?” Codes might include “fear of losing authority,” “copying mentor routines,” and “avoiding confrontation,” which could later form a theme about “performing confidence before feeling confident.”

In business and management, a capstone project might ask: “How do early-career employees describe hybrid work and professional identity?” The analysis could examine how flexibility, visibility, isolation, and career progression appear across interviews.

When another method may fit better

If your question asks whether one variable predicts another, thematic analysis is probably not the main method. For example, “Does study time predict exam score?” needs a quantitative design, not thematic coding. If you are still choosing between qualitative, quantitative, and theoretical work, a method decision flow can help you compare designs before committing to one approach: Three research method branches: quantitative, qualitative, and theoretical.

Content analysis includes qualitative and quantitative approaches, so the distinction is not simply meaning versus counting. Identify the specific approach, its assumptions and its analytical purpose. Counting code occurrences does not, by itself, establish the importance of a theme in reflexive analysis.

Matching the method to your research question

Your research question should give thematic analysis something meaningful to analyse. “What do nursing students think about simulation training?” is workable but broad. “How do final-year nursing students describe the role of simulation training in building confidence before clinical placement?” gives the analysis a clearer centre.

If your question is still too wide, narrow it before coding. A focused qualitative question makes theme development easier because you know which meanings matter for the paper and which interesting details are outside the scope. For support at that stage, see the Qualitative research question funnel.

What are the six Braun and Clarke thematic analysis steps?

Braun and Clarke thematic analysis is commonly taught as a six-phase process: familiarisation, coding, generating themes, reviewing themes, defining and naming themes, and writing up. The phases are not a mechanical checklist; students often move back and forth as their interpretation improves. Still, the sequence gives you a clear way to show how your findings were developed.

Phase 1: Familiarise yourself with the data

Start by reading the full dataset before making firm decisions about themes. If you conducted interviews, listen to the recordings where possible and compare them with the transcript. Write short analytic notes about repeated ideas, contradictions, emotional tone, and surprising wording.

Do not rush this phase. Many weak analyses fail because the student starts coding after reading only the first transcript. Familiarisation helps you notice patterns across the dataset rather than giving too much weight to the first few responses.

A practical familiarisation routine looks like this:

1. Read each transcript or document once without coding.
2. Write a short memo after each item: “What seems to matter here?”
3. Read the full dataset again and mark passages related to the research question.
4. List repeated words, tensions, metaphors, or examples.
5. Keep a separate note of material that is interesting but outside the scope.

Phase 2: Generate initial codes

Coding means attaching meaningful labels to specific extracts. Codes can be descriptive, such as “lack of feedback,” or interpretive, such as “uncertainty treated as personal failure.” Both can be useful, but your coding should stay connected to the research question.

At this stage, code more than you expect to use. Early coding is exploratory. Later, you can merge, rename, or remove codes that do not help answer the question.

Phase 3: Generate candidate themes

After coding, group related codes into candidate themes. A candidate theme is a possible pattern, not a final finding. Look for codes that seem to share an underlying idea, tension, process, or consequence.

For example, codes such as “checking email late at night,” “fear of missing updates,” and “feeling guilty when offline” might sit under a candidate theme called “availability as a hidden performance expectation.” That theme says more than “communication,” because it interprets the meaning of the pattern.

Phase 4: Review the themes

Reviewing themes means checking whether each theme works against both the coded extracts and the dataset as a whole. Ask whether the extracts inside a theme fit together and whether the theme is clearly different from the others. If two themes overlap too much, merge them or sharpen their boundaries.

This is where many student projects improve sharply. A first theme set often looks tidy but shallow. Reviewing forces you to ask whether your themes explain the data or merely rename your interview questions.

Phase 5: Define and name the themes

Defining a theme means writing a concise explanation of what the theme captures and how it answers the research question. Naming a theme means choosing a title that reflects the analytic point, not just the topic area.

Compare “Support” with “Support depends on being seen as struggling enough.” The second name gives the reader a claim. It suggests a pattern about thresholds, visibility, and help-seeking.

Phase 6: Write up the analysis

The write-up connects themes, extracts, and interpretation. Each theme section should make a claim, present evidence, and explain how that evidence answers the research question. Quoted extracts are not self-explanatory; you need to interpret them.

A good write-up also explains your analytic process in the methodology section. If you are writing a full paper, connect your thematic analysis to your design, sampling, data collection, and limitations. For wider structure, the Methodology chapter stages from design to justification can help you position the analysis within the method section.

How do you code qualitative data without losing the meaning?

Code qualitative data by labelling meaningful extracts while keeping enough context to interpret them accurately. Avoid coding single words in isolation unless the wording itself matters. Good coding balances detail with usability: it preserves relevant detail and context while supporting the analytical question.

Keep extracts attached to context

A code is only useful if you can return to the extract and understand why it was coded. Keep participant ID, transcript location, and surrounding context. If a participant says, “I just stopped asking,” the meaning depends on what they stopped asking for: feedback, medical advice, help from managers, or clarification from lecturers.

Many students use a spreadsheet with columns for source, extract, initial code, notes, and possible theme. Others use qualitative software. The tool matters less than the audit trail: you need to show how raw material became findings.

Use descriptive and interpretive codes

Descriptive codes stay close to the surface meaning. Interpretive codes move toward what the extract suggests. Both have a place in thematic analysis.

In a health sciences project, descriptive codes might capture practical barriers, while interpretive codes explain why those barriers matter. For example, “unclear discharge instructions” describes a problem; “home care begins with uncertainty” moves closer to a theme.

Avoid over-coding and under-coding

Assess coding by its relevance, specificity and engagement with the data, not by the number of labels. Fine-grained coding can be useful. If a broad code hides different meanings, revisit the extracts and consider whether more specific labels help answer the question.

A better approach is to split broad labels into meaningful variations. “Academic stress” might become “stress from unclear expectations,” “stress from comparison with peers,” and “stress from delayed feedback.” Later, these may combine into a theme about “uncertainty turning normal workload into threat.”

Record evolving coding decisions

For reflexive thematic analysis, keep evolving notes about codes, examples and your interpretive decisions. A fixed codebook designed to make independent coders agree belongs to a different approach. Reflexive notes help explain how your thinking changes; they do not certify that one coding is objectively correct.

Revisit earlier data when your interpretation changes and record why you revised a label. If a supervisor or collaborator offers a different reading, use it to examine your assumptions rather than treating agreement scores as a requirement of reflexive analysis.

What does a thematic analysis example look like?

A thematic analysis example usually shows the movement from research question to data extract, code, candidate theme, and final theme. The point is not to display every coded line, but to make your analytic decisions visible. A clear example helps readers see that your themes came from the data and answer the research question.

Example research question and dataset

Imagine a master’s education paper asking: “How do first-generation university students describe their experiences of seeking academic support during the first semester?” The dataset contains eight semi-structured interviews with first-year students. The research question focuses on experiences and meaning, so thematic analysis fits.

A possible set of early codes might include “not knowing who to ask,” “fear of sounding unprepared,” “waiting until crisis,” “using peers as translators,” and “support services feel formal.” These codes point to more than a general topic of “support.” They suggest patterns around belonging, uncertainty, and help-seeking.

From codes to candidate themes

Here is a simplified version of how codes can become themes:

The stronger versions make analytic claims. They tell the reader what pattern was found and why it matters.

A worked mini example

In the fictional example, participant P1 says, “I saw the writing center link, but I thought it was for people who were really failing. I didn’t think my questions counted.”

Initial codes could be “misunderstanding support threshold,” “fear of not qualifying for help,” and “questions seen as illegitimate.” A candidate theme might be “support as a last resort.” After reviewing other extracts, the final theme could become “Students delay help-seeking when support is framed as remedial rather than normal.”

This theme could be supported by several participants, not just one quote. You might then compare it with a second theme, such as “Peers normalise confusion before formal services are used.”

Before and after: theme quality

The table below shows the difference between topic labels and analytic themes:

A theme does not need to sound dramatic. It needs to be specific, evidence-based, and connected to the research question.

How do you write up themes in a results or findings section?

Write up thematic analysis by giving each theme a clear claim, supporting it with selected extracts, and explaining how the evidence answers the research question. Avoid dropping quotations into the text without analysis. The reader should understand both what participants said and what your interpretation adds.

Use a repeatable paragraph structure

A clear theme paragraph often follows this pattern:

1. State the theme claim in one sentence.
2. Explain the pattern across the dataset.
3. Introduce a short extract as evidence.
4. Interpret the extract, focusing on meaning.
5. Link the interpretation back to the research question.

For example, in a business project on hybrid work, you might write: “The theme ‘visibility as career currency’ captures how participants treated office presence as a signal of commitment, even when remote work was officially accepted.” A quote can then show how an employee describes attending the office mainly so managers “remember” them. Your interpretation should explain how flexibility becomes conditional rather than equal.

Balance quotes and analysis

Select extracts for their analytical purpose and preserve enough context to support your interpretation. A longer passage may be needed to convey a tension or sequence; explain the role of the selected evidence in the surrounding narrative.

Check the balance between extracts and analytical narrative across the section. A quotation can sometimes close a paragraph, but its purpose and connection to the argument should be clear. Do not add a formulaic sentence after every extract just to follow a layout rule.

Connect themes to literature without losing your findings

Follow the reporting structure agreed for the assignment. Separate findings and discussion chapters may have different roles; an integrated account can connect the analysis with literature throughout. In either format, show what is supported by your data and distinguish it from claims drawn from published work.

If your project includes a literature review, organise sources by ideas rather than by author. The Thematic source clusters and research gap for a literature review can help you keep literature themes separate from empirical themes while still making them speak to each other.

Explain method choices transparently

Your methods section should state what data you analysed, how coding was conducted, and how themes were reviewed. You do not need to report every code. You do need to give enough detail for a reader to trust the process.

For example: “After repeated reading, relevant extracts were coded line by line. Codes were then grouped into candidate themes and reviewed against the full dataset. Themes were revised where extracts did not share a clear pattern of meaning.” This is concise, but it shows the logic of the analysis.

What mistakes do students commonly make when doing thematic analysis?

Students most often weaken thematic analysis by treating themes as topics, coding without a research question, using quotations as decoration, or claiming that themes “emerged” without explaining analytic decisions. These mistakes are fixable if you return to the link between question, code, theme, and evidence. The goal is not to make the analysis sound more complex, but to make the reasoning clearer.

Mistake 1: Naming themes as single-word topics

1. The mistake: Topic-label themes
   Student example: “Theme 1: Stress. Theme 2: Support. Theme 3: Motivation.”
   Correction: Rename each theme as a claim about meaning. For example: “Students describe stress as uncertainty about hidden expectations,” or “Support is used only after peers confirm the problem is serious enough.”

Single-word themes usually leave the reader asking, “What about stress?” A theme title should point to the pattern you found, not just the area you discussed.

Mistake 2: Coding everything that looks interesting

2. The mistake: Collector’s coding
   Student example: A paper on help-seeking codes “part-time work,” “commuting,” “family pressure,” “library opening hours,” “assessment anxiety,” and “lecturer email tone” with no link to the research question.
   Correction: Keep a separate note for interesting context, but code mainly for extracts that help answer the research question.

Interesting data is not always relevant data. If your paper has a tight word count, every theme must earn its place.

Mistake 3: Treating interview questions as themes

3. The mistake: Copying the interview guide into the findings
   Student example: Interview question: “What barriers did you face?” Theme: “Barriers faced by students.” Interview question: “What support helped?” Theme: “Helpful support.”
   Correction: Use responses across questions to build themes. A better theme might be “Students recognise support only when it is embedded in ordinary teaching routines.”

Interview guides organise data collection, not analysis. If you need help designing questions that generate analysable data, see the Interview guide sequence with probe branches.

Mistake 4: Using quotes without interpretation

4. The mistake: Quote stacking
   Student example: “Participant A said, ‘I felt lost.’ Participant B said, ‘Nobody explained it.’ Participant C said, ‘I was confused.’ This shows students were confused.”
   Correction: Review the balance of extracts and analytical narrative. Explain what kind of confusion appears, what produces it, and how it shapes behaviour.

A list of similar quotes proves repetition, but thematic analysis needs meaning. Ask what the repeated wording suggests about the experience.

Mistake 5: Claiming themes appeared automatically

5. The mistake: Passive emergence language
   Student example: “Three themes emerged from the data: stress, support, and communication.”
   Correction: Write in a way that recognises your analytic role: “The analysis developed three themes that captured how students interpreted support, uncertainty, and communication.”

Themes do not jump out fully formed. You develop them through reading, coding, comparison, and revision.

How can you check whether your thematic analysis is ready to submit for feedback?

Your thematic analysis is ready for feedback when the research question, codes, themes, extracts, and interpretation clearly connect. A reader should be able to see why each theme belongs in the paper and how it was developed from the data. Before sharing a draft, check whether your themes are analytic claims rather than topic headings.

Quality checks for themes

Test each theme by asking: “What does this theme argue?” If you cannot answer without repeating the theme name, the theme may be too vague. A useful theme can usually be expressed as a sentence.

Also check boundaries. If the same extract fits equally well under three different themes, your themes may overlap. Overlap is normal early on, but final themes need clear roles in the argument.

Quality checks for evidence

Assess themes against the coded material and the whole dataset, including relevant variation and tensions. A vivid quotation alone is insufficient grounds for a broad pattern claim. Explain the support for your interpretation without substituting a fixed quotation count for that assessment.

Do not hide conflicting evidence. If most participants describe support as hard to access but one describes it as easy, that difference may refine the theme. For example, the pattern might become “Support feels accessible only when students already know the system.”

Quality checks for write-up

Your findings should not read like a methods diary. The reader does not need to see every step in the coding process. They need a clear final structure, enough process detail to trust it, and enough evidence to assess your claims.

Check whether each theme section opens with a claim, includes evidence, interprets that evidence, and links back to the research question. If a section only says what participants talked about, revise it toward what the talk reveals.

Before you move on: thematic analysis checklist

• My research question asks about experiences, meanings, perceptions, practices, or representations.
• I have read the full dataset before finalising codes.
• My codes are attached to specific extracts, not floating notes.
• I can explain the difference between my codes and my themes.
• Each theme is written as an analytic claim, not a one-word topic.
• My themes are distinct enough that extracts do not fit everywhere.
• Each theme is supported by relevant evidence from the dataset.
• I interpret quotations instead of letting them stand alone.
• My methods section explains how I coded and reviewed themes.
• My findings answer the research question directly.
• I have checked whether any interesting material falls outside the paper’s scope.
• My final theme names are specific enough for a reader to understand the pattern.

Method and quotation guidance

• Braun and Clarke: Doing reflexive thematic analysis — six phases, recursive engagement and writing.
• Braun and Clarke: Frequently asked questions — approach differences, themes and coding.
• Braun and Clarke: Editor and reviewer guide — coherence between the stated approach and the analysis.
• APA Style: Quotations from research participants — participant extracts are not reference-list entries; quotations under 40 words are inline and quotations of 40 words or more are indented blocks.