Inductive vs. deductive coding, explained
Coding is the heart of thematic analysis, and there are two broad ways to do it: let codes emerge from the data (inductive) or apply a predefined framework (deductive). Your methods section needs to say which you did and why — choosing well shapes everything downstream.
Inductive coding (data-driven)
In inductive coding, you start with no preconceived categories and derive codes directly from what the data says. It's the usual choice for exploratory questions and for synthesising findings across studies, because it surfaces patterns you didn't know to look for. The trade-off is consistency: without a fixed scheme, codes can proliferate and drift between coders — which is why examiners ask how you kept coding systematic.
Deductive coding (framework-driven)
In deductive coding, you bring a codebook — a predefined set of codes from prior research or theory — and tag the data against it. It's fast, consistent, and comparable across datasets, which suits theory-testing designs and replication studies. The risk is tunnel vision: a fixed framework can miss anything it wasn't designed to catch, so reviewers expect you to note findings that didn't fit the codebook.
Most real analysis is hybrid
Finish your thematic analysis on time — with total ease, without sacrificing academic rigour. The thematic analysis tool codes your data inductively with linked verbatim quotes, giving you a rigorous first pass you can refine against your research framework.