What Should Be in a Qualitative Codebook?
A qualitative codebook should make coding decisions inspectable. The strongest ones define each code, show when to use it, and record how it changed.
6 min read
Thematic analysis, coding strategies, and making sense of qualitative data.
A qualitative codebook should make coding decisions inspectable. The strongest ones define each code, show when to use it, and record how it changed.
6 min read
Most applied projects land between 30 and 70 codes, and past 100 a consolidation pass is usually overdue. The real test, though, is whether you can still tell your codes apart. Here are the warning signs of codebook bloat and how to merge, nest, and prune without losing nuance.
5 min read
Codes that get counted need demonstrated agreement. Interpretive codes need documented judgement. A working rule for when intercoder reliability matters — and when it's theatre.
3 min read
You have heard the pitch: AI can code your transcripts, find your themes, and deliver your findings in minutes. It sounds too good to be true, and in some ways it is. But the real…
4 min read
Thirty transcripts, one deadline, and patterns you know are in there somewhere. Paideias finds them in minutes, so you can spend your time on the analysis that actually counts.
3 min read
Participants don't answer your questions, they tell you stories — and every story has structure worth analysing. Paideias' AI-assisted coding helps you track both content and structure across your whole dataset, so nothing gets lost in the retelling.
2 min read
Discourse analysis asks you to notice the phrase repeated four times, the metaphor that reframes an entire interview. Paideias' AI-assisted coding surfaces those patterns across your whole dataset, not just the transcript you happen to remember.
2 min read