---
name: critical-incident-technique
description: Use when asked to gather and analyze detailed accounts of significant events — define/collect/select/code/cluster/interpret — as a qualitative research method focused on specific incidents rather than routine task execution (see task-analysis).
---

# Critical Incident Technique (CIT)

The Critical Incident Technique (CIT) is a qualitative research method
for gathering detailed and specific information about significant events
or incidents that occurred in a particular context — extracting
actionable knowledge from real-life events to inform decision-making,
problem-solving, training, or process improvement. Unlike
[[task-analysis]], which documents how a task is routinely performed,
CIT focuses specifically on notable events — successes, failures, or
turning points — rather than typical, everyday execution.

## General process

1. **Define** — clearly define what constitutes a critical incident
   within the context: a specific job role, task, customer interaction,
   or other relevant domain.
2. **Collect** — gather details of critical incidents from people who
   experienced them, via interviews, surveys, or reports — what
   happened, who was involved, actions taken, and outcomes.
3. **Select** — choose a subset of incidents that are most critical or
   representative: covering a range of outcomes, highlighting different
   aspects of the context, or providing especially rich insight.
4. **Code** — analyze each selected incident and identify themes,
   patterns, or factors emerging from the narratives, tagging relevant
   concepts or categories.
5. **Cluster** — identify commonalities, differences, trends, recurring
   themes, critical behaviors, environmental factors, or decision points
   associated with outcomes, extracting insights and actionable
   knowledge.
6. **Interpret** — draw conclusions from the identified factors,
   patterns, or themes, validated with stakeholders or subject matter
   experts, to inform decision-making, process improvement, or training.

## Why focus on incidents rather than routine execution

Routine task execution often looks similar regardless of who performs
it; the moments that reveal what actually matters — where expertise,
judgment, or process gaps make the real difference — tend to be the
unusual ones: a near-miss, an escalation, an unexpectedly smooth
recovery from a problem. CIT deliberately samples those moments rather
than averaging over routine cases, which is why it's often used
alongside a more routine-focused technique like [[task-analysis]] or
[[cognitive-task-analysis]], not instead of it.

## Common pitfalls

- **Vague criteria for what counts as "critical"** — without a clear
  definition upfront, collected incidents can be inconsistent in scope
  or severity, making coding and clustering harder.
- **Selection bias toward memorable or extreme incidents** — the most
  vivid incidents aren't always the most representative or informative;
  deliberately seek a range of outcomes, not just the most dramatic
  stories.
- **Coding without a clear framework** — ad hoc tagging that changes
  meaning partway through the analysis makes it hard to reliably cluster
  and compare incidents afterward.
- **Skipping stakeholder validation of the interpretation** — drawing
  conclusions purely from the researcher's own reading of the incidents,
  without checking against people close to the context, risks
  misinterpreting what actually happened or why.

## Learn more

- [[task-analysis]] for the routine-execution-focused counterpart CIT complements.
- [[root-cause-analysis]] for a related technique focused specifically on tracing a problem back to its underlying cause.