Process / pipelineOrganizational BehaviorOrganizational behavior / job and task analysisPipeline

Critical Incident Technique

Also known as: CIT, Flanagan Critical Incident Technique, Critical Incidents Method, Critical Incident Analysis

OriginatorJohn C. FlanaganYear1954Sources1Related methods7

The critical incident technique (CIT) is a qualitative procedure for studying human behavior by collecting and classifying detailed accounts of specific incidents in which behavior was especially effective or ineffective in achieving an aim. John Flanagan introduced it in his landmark 1954 Psychological Bulletin article, drawing on his work selecting and classifying aircrew in World War II, where vague trait descriptions had proved useless and concrete behavioral accounts proved decisive. Rather than asking people for opinions or generalities, CIT asks observers to recount what actually happened, what the person did, and why it mattered, then builds a framework of behavioral requirements inductively from those accounts. The technique gave applied psychology a rigorous, replicable way to derive job requirements, performance criteria, and training content from real behavior. It remains a foundational method underlying job analysis, behaviorally anchored rating scales, and competency modeling. Its hallmark is grounding abstract requirements in observable, situated action.

Key highlights

  • Grounds abstract requirements in concrete, observable behavior drawn from real incidents rather than opinions or traits.
  • Produces categories inductively from the data, yielding a framework that reflects the activity as actually performed.
  • Is flexible and economical, adaptable across jobs, services, and settings via interviews, questionnaires, or observation.
  • Feeds directly into practical tools such as performance criteria, training content, and behaviorally anchored rating scales.

Intuition

This section is available to Pro members. Upgrade to Pro

How it works

This section is available to Pro members. Upgrade to Pro

When to use it

Use the critical incident technique when you need to understand what distinguishes effective from ineffective behavior in a role or activity and you want that understanding grounded in real, observable action rather than opinion or theory. It is well suited to job and task analysis, deriving performance criteria, designing behaviorally anchored rating scales, building competency models, and studying service encounters or safety events where concrete incidents are memorable and consequential. It is less appropriate when the phenomenon does not break naturally into discrete incidents, when knowledgeable observers are unavailable or incidents cannot be recalled accurately, or when the goal is to estimate prevalence or test a causal hypothesis, since CIT describes and classifies behavior rather than quantifying or experimentally testing it.

Strengths & limitations

Strengths
  • Grounds abstract requirements in concrete, observable behavior drawn from real incidents rather than opinions or traits.
  • Produces categories inductively from the data, yielding a framework that reflects the activity as actually performed.
  • Is flexible and economical, adaptable across jobs, services, and settings via interviews, questionnaires, or observation.
  • Feeds directly into practical tools such as performance criteria, training content, and behaviorally anchored rating scales.
Limitations
  • Relies on recall of incidents, which is subject to memory bias, salience effects, and selective reporting.
  • The categorization step requires judgment and is the most subjective and least replicable part of the procedure.
  • It captures extreme, critical incidents and may neglect routine but important everyday behavior.
  • It describes and classifies behavior but does not by itself establish prevalence, weighting, or causal effects.

Common pitfalls

This section is available to Pro members. Upgrade to Pro

Applications

This section is available to Pro members. Upgrade to Pro

Frequently asked

What exactly makes an incident 'critical'?

An incident is critical when it makes a clear, significant difference, positive or negative, to the stated aim of the activity. Flanagan's definition has two parts: the incident must be a specific, observable piece of human activity complete enough to permit inferences about the person, and it must matter to the objective, either contributing to it or detracting from it. A routine action that has little bearing on success or failure is not critical. This is why defining the general aim first is essential, because criticality is judged relative to that aim, and it is what keeps the method focused on behavior that actually distinguishes effective from ineffective performance.

How many incidents do I need to collect?

Flanagan tied the number to category saturation rather than a fixed count: you keep collecting until additional incidents stop producing new behavioral categories. The number needed therefore depends on the complexity of the activity. Simple, narrow activities may saturate after a few dozen incidents, while complex jobs can require many hundreds or even thousands. A practical check is to monitor how many new categories each batch of incidents adds; when that approaches zero, the behavioral framework is reasonably complete. Reporting how saturation was judged is an important part of demonstrating the rigor of a CIT study.

Is the critical incident technique qualitative or quantitative?

It is fundamentally a qualitative method, since its core activity is eliciting and inductively classifying rich, behavioral accounts of incidents. However, it has a quantitative side: once incidents are categorized, researchers can count how many fall into each category and use those frequencies to indicate which behaviors recur. This counting should be interpreted cautiously, because incidents are sampled by salience and memorability rather than by representativeness, so category frequencies reflect what observers found striking rather than the true base rate of behaviors. Used carefully, CIT bridges qualitative depth and a modest, descriptive quantification of behavioral categories.

Sources

  1. 1.
    Flanagan, J. C. (1954). The critical incident technique. Psychological Bulletin, 51(4), 327-358.

You have read it. What now?

Cite this page

ScholarGate. (2026, June 23). Critical Incident Technique. ScholarGate. https://scholargate.app/organizational-behavior/critical-incident-technique