Qualitative Coding Codebook

Template Overview

Rigorous qualitative research—whether employing Grounded Theory, Interpretative Phenomenological Analysis (IPA), or Reflexive Thematic Analysis—requires a standardized, transparent codebook. The Qualitative Coding Codebook template provides academic and UX researchers with an auditable schema to document inductive and deductive code families, operational definitions, boundary conditions, and verbatim transcript excerpts.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Qualitative Codebook: [Study Title / Research Question]"
date: [YYYY-MM-DD]
primary_coder: "[[Lead Researcher]]"
secondary_coder: "[[Inter-coder Reliability Partner]]"
methodological_framework: "[Grounded Theory / Thematic Analysis / IPA]"
current_iteration: "[v1.0 Initial Open Coding / v2.0 Axial Coding]"
tags: [qualitative-research, codebook, thematic-analysis, grounded-theory, coding]
---

# Qualitative Coding Codebook — [Study Title]

## 1. Study Framework & Coding Strategy
- **Central Phenomenological Question:** How do knowledge workers experience cognitive friction when migrating from cloud-first to local-first software tools?
- **Coding Methodology:** Hybrid approach utilizing deductive codes (from Cognitive Load Theory) and inductive open codes (emerging from interview transcripts).
- **Inter-Coder Agreement Target:** Cohen's Kappa κ ≥ 0.80 across a 20% sampled transcript subset.

## 2. Master Codebook Taxonomy Matrix
| Code Identifier | Code Label | Parent Category / Theme | Operational Definition | When to Apply (Inclusion) | When NOT to Apply (Exclusion) | Exemplar Transcript Quote |
|---|---|---|---|---|---|---|
| `COG-FRIC` | Cognitive Friction | Cognitive Load | User experiences mental stall or uncertainty during task execution | User explicitly mentions confusion, pauses, or expresses frustration with interface flow | Simple mechanical typos or expected learning curve exploration | "I had to stop and stare at the screen for two minutes trying to understand where my files went." (P-03, Line 45) |
| `DAT-SOV` | Data Sovereignty | Privacy & Control | User articulates need to own and control raw data files | Mentions of air-gapping, fear of cloud provider lock-in, or desire for local storage | General preference for desktop apps purely based on speed | "If an app requires me to log into their server just to read my thoughts, I refuse to use it." (P-07, Line 112) |
| `SYS-PERF` | Perceived Latency | Performance | User notices time lag between voice input and transcription rendering | Explicit remarks comparing local inference speed against cloud APIs | Network downtime or general internet ISP issues | "The local model started generating text before I even finished speaking my sentence." (P-11, Line 89) |

## 3. Axial Coding & Thematic Families
- **Theme 1: The Sovereignty Paradox:** Users desire complete local autonomy yet struggle with manual backup configurations.
- **Theme 2: Trust through Observability:** Transparent on-device processing builds immediate psychological safety that glossy cloud privacy policies fail to achieve.
- **Theme 3: Markdown Portability as Insurance:** Plaintext files represent an enduring intellectual hedge against vendor bankruptcy.

## 4. Coding Discrepancies & Reflexivity Log
- **Discrepancy (Transcript 4):** Disagreement on whether 'offline usage during flight' belongs to `DAT-SOV` (Data Sovereignty) or `MOB-WORK` (Mobile Ergonomics).
- **Resolution:** Established rule: if motivation cites file security, code as `DAT-SOV`; if convenience, code as `MOB-WORK`.

## 5. Next Steps for Manuscript Analysis
- [ ] Calculate inter-coder reliability Kappa score across coded sample.
- [ ] Export frequency tables and co-occurrence matrices for findings chapter.
- [ ] Archive codebook version in OSF research repository.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Qualitative Codebook: Local AI Adoption in Legal Practice"
date: 2026-10-09
primary_coder: "[[Dr. Samantha Wei]]"
secondary_coder: "[[Marcus Vance]]"
methodological_framework: "Reflexive Thematic Analysis (Braun & Clarke)"
current_iteration: "v2.1 Axial Coding"
tags: [qualitative-research, codebook, thematic-analysis, grounded-theory, coding]
---

# Qualitative Coding Codebook — Local AI Adoption in Legal Practice

## 1. Study Framework & Coding Strategy
- **Research Question:** How do corporate litigation attorneys navigate ethical compliance and attorney-client privilege when adopting AI speech tools?
- **Inter-Coder Reliability:** Reached Cohen's Kappa κ = 0.86 across 5 sampled partner interviews.

## 2. Master Codebook Taxonomy Matrix
| Code ID | Code Label | Operational Definition | Inclusion Criteria | Exemplar Quote |
|---|---|---|---|---|
| `ETH-PRIV` | Privilege Safeguarding | Actions taken to shield confidential client disclosures | References to ethical sanctions, disbarment risks, or court protective orders | "Under our state bar guidelines, feeding deposition audio to a commercial cloud server could waive privilege." (Partner A, L78) |
| `SUB-AUD` | Subpoena Immunity | Awareness that air-gapped files cannot be secretly accessed | Stating that local disk files require formal warrant rather than silent subpoena | "If data isn't sitting on AWS, third parties cannot subpoena our transcripts without serving us directly." (Partner C, L142) |
| `TOOL-FRIC`| Enterprise IT Hurdles | Difficulties installing local binaries on restricted corporate machines | IT administrator blocks, MDM restrictions, or corporate firewalls | "Our security team blocked all cloud bots, so local desktop apps were the only approved avenue." (Partner E, L205) |

## 3. Key Thematic Insights
- Attorneys perceive cloud transcription as an ethical liability rather than a modern convenience.
- On-device inference is treated as an active compliance defensive moat that satisfies strict judicial standards.

## 4. Next Steps
- [ ] Finalize code co-occurrence matrix in research draft.
- [ ] Submit manuscript to Harvard Journal of Law & Technology.

When to Use and When to Avoid

When to Use

• Use during qualitative doctoral dissertations, academic research papers, or user research thematic analyses.
• Use when multiple researchers code interview transcripts to ensure inter-rater reliability and consistency.
• Use to establish transparent audit trails for qualitative peer review scrutiny.

When to Avoid

• Avoid using for pure quantitative statistical data analysis or numerical survey scoring.
• Avoid using for informal scratchpad summaries without structured methodology.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Review the qualitative codebook definitions and exemplar quotes:
1. Identify any conceptual overlaps or ambiguous boundaries between listed codes.
2. Formulate explicit inclusion and exclusion guardrails to resolve identified boundary overlaps.
3. Suggest a thematic umbrella structure linking individual codes into overarching research findings.
Output in structured Markdown.

Your data remains securely on your Mac with zero cloud exposure.