Qualitative Data Analysis A Methods Sourcebook

Working With Qualitative Data Analysis: A Methods Sourcebook

The book isn't a single method. It's a reference you pull off the shelf when you realize your interview transcripts are drowning and you don't have a system for getting them out. Joris van Beeumen organized it by technique, not by theory, which means you flip to the section that matches what you're actually trying to do. Thematic analysis, grounded theory coding, conversation analysis, discourse analysis, narrative analysis, framework analysis, content analysis, qualitative content modeling — each gets its own chapter with steps, examples, and references. I use it as a decision map more than a instruction manual. The first time I opened it, I was stuck on a project with 47 semi-structured interviews and no coherent way to move from raw text to findings. I spent a morning scanning the table of contents, found the framework analysis chapter, and followed the five-stage structure it laid out. It didn't solve everything. It gave me enough structure to stop spinning. Each chapter walks through a specific approach to making sense of non-numerical data. The techniques range from the broadly used thematic and framework methods to more specialized ones like conversation analysis and qualitative content modeling. The value is in the comparisons — seeing how one method's coding rules differ from another's helps you pick the right tool instead of guessing. The chapters include worked examples, which is useful when you're tired and just need to see the mechanics before you start.

Here's what that looks like in practice. You have a set of interviews about patient experiences in a clinic. You could do thematic analysis, where you code for recurring ideas. Or framework analysis, where you start with a preconceived matrix and fill it in. Or grounded theory, where you let categories emerge without forcing them into a pre-existing structure. The book lays out the differences so you can choose based on your research question, not because someone online said it's the most popular method.

How to actually use it on a real project

Start by writing down what you're trying to answer. Then match that question to the method that fits. The book helps with the matching. Once you pick a method, follow its steps exactly for the first round of coding. Don't improvise early. You'll regret it when you have to go back and re-code thirty transcripts. I once used thematic analysis on a dataset where the initial codes kept collapsing into each other. The problem was my codebook was too broad. I went back to the framework analysis chapter instead, built a thematic index first, and applied it to a subset of the data. That cut my total coding time roughly in half compared to starting over with a fresh thematic approach. It wasn't faster because the method was better. It was faster because I had structure before I started wading into the full dataset.

Common mistakes people make with this sourcebook

The biggest one is treating it like a textbook you read cover to cover. It's not. It's a reference. Read the chapters relevant to your method, skip the rest, and come back when you hit a problem. Another mistake is ignoring the limitations sections. Every method has constraints, and the book is honest about them. Framework analysis, for example, requires a pre-set analytical framework. If your project doesn't have one, you'll spend more time building it than you save on coding. Grounded theory requires constant comparison and theoretical sampling, which means you can't just code everything at once and expect clean results. A less obvious pitfall is mixing methods mid-project without adjusting your documentation. I've seen analysts switch from thematic to content analysis after two rounds of coding. The code definitions change between methods, and your audit trail becomes impossible to follow. If you switch methods, redo your codebook from scratch and note the change explicitly. Reviewers and your future self will thank you.

What it doesn't cover well

The book focuses on established Western qualitative traditions. If you're working with Indigenous methodologies, participatory action research, or decolonial approaches, you'll need additional sources. The coverage of software workflows is also minimal. It mentions Nvivo and Atlas.ti but doesn't walk through them. If you need step-by-step instructions for your tool, look elsewhere. The book is stronger on the thinking than the clicking.

Where to get it

You can find it through SAGE Publications, major academic book retailers, and library networks. The ISBN is 978-1-4462-7553-8 for the second edition. If you're affiliated with a university, check your library's e-book platform first. The print version runs around £45 to £55 depending on the retailer.

When to reach for it

Use it when you have qualitative data and need to choose a method, not when you already know your method and just want validation. It's strongest at the design stage, when you're deciding whether thematic analysis, framework analysis, or grounded theory is the right fit. It's less useful once you're deep into coding and running into edge cases — that's when you need forums, method papers, and sometimes just experience. But for getting started, it's one of the more practical references available.