Guides · For students and researchers
How to do thematic analysis in Google Docs
You've done your interviews and typed up the transcripts. Now you need to turn hours of talk into a handful of clear themes. Here's how to do it step by step, using nothing but Google Docs.
What thematic analysis is
Thematic analysis is a way of finding patterns in what people said. You read your interviews closely, label the parts that matter, then group those labels into a few big ideas, called themes, that answer your research question.
The labels are called codes. A code is just a short tag for an idea, like trust in banks or money worries. Labelling quotes this way is called coding. If you've ever highlighted a textbook in different colours for different topics, you already understand the basic idea.
The most widely used approach comes from Virginia Braun and Victoria Clarke, who set out six phases in 2006. Most UK universities teach their method, so it's the one we follow here. Check your module handbook too, because your department may prefer a slightly different version.
Set up your documents
A little setup at the start saves a lot of scrolling later.
- One document per interview, or one document with each interview in its own tab. Google Docs tabs (in the left-hand panel) keep everything in one place.
- Anonymise first. Replace real names with pseudonyms (P1, P2, or invented names) before you start coding. Use
Edit › Find and replacefor each name. - A separate "codebook" document with a simple table: code name, what it means, and an example quote. You'll fill it in as you go.
| Code | What it means | Example quote |
|---|---|---|
| Trust in banks | Talks about trusting or distrusting banks | "I never really trusted them again" |
| Family support | Relies on relatives for money or advice | "My mum lent me the money" |
The six steps, in Google Docs
Get to know your data
Read every transcript at least once without coding anything. Jot first impressions in a notes document: things that surprised you, ideas that keep coming up, and moments that felt important. If you did the interviews yourself, listening back while you read helps.
Code the transcripts
Go through line by line and label anything relevant to your research question. In Google Docs there are two ways to do this:
- Comments: select the words, add a comment (
Ctrl+Alt+M, orCmd+Option+Mon a Mac), and type the code name. Comments keep the code and the quote together, and you can see them all at once with the comments button at the top right. - Highlight colours: pick one colour per code. It's quick and visual, but it gets confusing once you have more than five or six codes.
Use the exact same wording for a code every time, such as "Family support", not "family help" in one place and "relatives" in another. Add every new code to your codebook as you create it.
Tip: you don't need to code every sentence. Code what helps answer your research question, and a sentence can carry more than one code.
Gather your quotes and look for themes
Now pull all the quotes for each code into one place so you can see them side by side. Make a new document with a table (Code, Quote, Participant) and copy each coded quote in. This is the slowest part of doing it by hand, so expect it to take a while.
Then look at the codes together and ask which ones belong together. "Trust in banks" and "Avoiding apps" might both be part of a bigger idea, such as distrust of institutions. Those bigger ideas are your candidate themes.
Review your themes
Check each theme against the quotes underneath it. Do they really fit together? Is there enough evidence? Some themes will merge, some will split, and some will turn out to be too thin to keep. That's normal and a sign you're doing it properly.
Define and name your themes
Write two or three sentences explaining what each theme is about, and give it a clear name that says something, such as "Family as a financial safety net" rather than just "Family".
Write it up
Write a section for each theme in your findings chapter, with your best quotes as evidence. Your table of quotes from step 3 also makes a good appendix, because it shows your examiner how you got from the data to the themes.
Doing this for a whole dissertation?
Steps 2 and 3 are where the hours go: coding, then copying every quote into a table. Themely is a Google Docs add-on that does that part for you. Highlight a quote and click a code, and Themely collects every quote under its theme across all your interviews, then builds a findings report and quote table for your appendix.
See how Themely worksFree for 3 interviews.
Common mistakes
- Themes that are just your interview questions. If you asked about "family" and your theme is called "Family", you may be summarising answers, not analysing them. A theme should say something about the pattern.
- Too many codes. Hundreds of tiny codes make step 3 impossible. Start broad and split codes only when you need to.
- Codes that drift. If a code's meaning changes halfway through, go back and recheck the earlier transcripts. Your codebook keeps you honest.
- Quotes without explanation. In your write-up, always say why a quote matters. Don't let it speak for itself.
Questions students ask
Do I need NVivo for thematic analysis?
No. Thematic analysis is a method, not a piece of software. Many students do it with highlighters, Word, or Google Docs. Software like NVivo can help with big projects, but it takes time to learn, and your examiner cares about the quality of your analysis, not the tool. See our guide to free NVivo alternatives.
How many interviews do I need?
It depends on your question and your participants. Our guide on how many interviews you need for a dissertation covers what the research says and how to justify your number.
How many codes should I have?
There's no right number. For a typical undergraduate or master's dissertation with 6 to 12 interviews, somewhere between 15 and 40 codes is common, grouped into 3 to 6 themes. Ask your supervisor what's usual in your subject.
Should I count how often each code appears?
Counts can be a useful check on which ideas come up most, but a theme doesn't have to be the most common thing people said. It has to matter for your research question. If you report counts, explain why.
Can two people code the same transcripts?
Yes. In Google Docs you can share the transcripts and each add comments. Agree on the codebook first, or you'll end up with two different sets of codes for the same ideas.
Further reading
Braun, V. and Clarke, V. (2006) Using thematic analysis in psychology. Qualitative Research in Psychology, 3(2), 77–101.
Braun, V. and Clarke, V. (2022) Thematic Analysis: A Practical Guide. London: SAGE.