All frameworks and cheat sheets

Framework

What a qualitative codebook records

The five columns every code needs in a thematic analysis codebook

Framework listing the five columns of a qualitative codebook: code name, definition, inclusion criteria, exclusion criteria and an example excerpt.
If a code is missing its exclusion criteria or its example quote, a second coder will read it differently.
Download PNGRead the full guide

A qualitative codebook is the rulebook behind your coding, so a second analyst can code new data the same way you did. These are the five columns every code needs at a minimum. Use them as the header row of your own codebook spreadsheet, and add parent theme, coder notes and revision dates once the project grows.

Where this appears

What's in this framework

  1. Code name: A short label of 1 to 4 words.
  2. Definition: A precise sentence on what the code captures.
  3. Inclusion criteria: Signals in the data that should get this code.
  4. Exclusion criteria: Look-alike signals that should not get it.
  5. Example excerpt: A real quote that shows the code in use.

Use this image

Free to use in your docs, decks and posts under CC BY 4.0, as long as you credit Koji with a link to this page. To embed it, paste this into your page:

html
<a href="https://www.koji.so/visuals/qualitative-codebook-five-columns"><img src="https://www.koji.so/visuals/qualitative-codebook-five-columns/qualitative-codebook-five-columns.png" alt="Framework listing the five columns of a qualitative codebook: code name, definition, inclusion criteria, exclusion criteria and an example excerpt." width="1200" height="699" /></a>
<p>Source: <a href="https://www.koji.so/visuals/qualitative-codebook-five-columns">What a qualitative codebook records</a>, Koji</p>

Related

Table of Cohen's kappa thresholds for inter-coder agreement, from poor below 0.40 to almost perfect above 0.80, with what to do at each level.

How to read Cohen's kappa for coding

Process showing six phases for building a qualitative codebook: immersion, open coding, define and consolidate, pilot, reach agreement and apply at scale.

How to build a qualitative codebook

Framework of the four forces of progress in Jobs to Be Done: push of the situation, pull of the new solution, anxiety of the new and habit of the present.

The four forces of progress in JTBD