{"slug":"critical-incident-technique-qualitative-research-2026","title":"Critical Incident Technique: Steps, Guide & Example","description":"The critical incident technique (Flanagan, 1954) explained: five steps, an interview guide with probes, a worked example, and the nine ECIT credibility checks.","keywords":"critical incident technique, critical incident technique qualitative research, CIT interview, enhanced critical incident technique, ECIT, Flanagan 1954, critical incident interview guide, qualitative interview methods","date":"2026-10-27","author":"Qualitati Research Team","category":"Qualitative Methods","readTime":"10 min read","content":"<div class=\"short-answer\"><p><strong>Short answer:</strong> The critical incident technique (CIT) is a qualitative research method, introduced by John Flanagan in 1954, that collects participants' accounts of specific events that clearly helped or hindered an outcome. Researchers then extract each incident, sort the incidents into inductive categories, and report how often each category appears. It suits questions about what makes a practice succeed or fail.</p></div>\n\n<p><em>Last updated: October 27, 2026</em></p>\n\n<p>The critical incident technique is one of the oldest structured interview methods in qualitative research, and it is still widely used in counselling psychology, nursing, education, service marketing and UX research. Its appeal is simple: people are poor at describing what they \"usually\" do, but they can describe one concrete event in detail. This guide walks through Flanagan's five steps, gives a ready-to-use CIT interview guide with probes, shows a short worked example, and lists the credibility checks reviewers now expect.</p>\n\n<h2>Key takeaways</h2>\n<ul>\n<li>CIT asks for <strong>specific incidents</strong>, not opinions or habits: what happened, what the person did, and what resulted.</li>\n<li>Flanagan's five steps are: define the aim, set plans and criteria, collect data, analyze, and report.</li>\n<li>A study is sized by <strong>incidents and categories</strong>, and you stop when new incidents add no new categories (exhaustiveness).</li>\n<li>The enhanced version (ECIT) adds wish-list items and nine credibility checks.</li>\n<li>CIT over-samples memorable, extreme events, so pair it with observation or diaries if routine behavior matters.</li>\n</ul>\n\n<h2>What is the critical incident technique?</h2>\n\n<p>Flanagan described the method in <a href=\"https://doi.org/10.1037/h0061470\" target=\"_blank\" rel=\"noopener noreferrer\">The critical incident technique (Psychological Bulletin, 1954)</a> as a set of procedures for collecting direct observations of human behavior that have critical significance for a defined aim. It grew out of the U.S. Army Air Forces Aviation Psychology Program in World War II, where it was used to identify the behaviors that separated effective from ineffective performance.</p>\n\n<p>An <strong>incident</strong> is any observable activity complete enough to let you draw inferences about the person doing it. It is <strong>critical</strong> when its purpose is clear to the observer and its consequences are definite enough that there is little doubt about its effect. In modern practice, most CIT studies replace expert observation with participants' own retrospective accounts, collected in interviews or open-ended questionnaires.</p>\n\n<p>Fifty years on, <a href=\"https://doi.org/10.1177/1468794105056924\" target=\"_blank\" rel=\"noopener noreferrer\">Butterfield, Borgen, Amundson and Maglio (2005, Qualitative Research)</a> reviewed how the method had moved from task analysis toward exploring psychological constructs and experiences. They also warned that its flexibility had produced inconsistent terminology and studies that drift from Flanagan's analysis steps.</p>\n\n<h2>When should you use the critical incident technique?</h2>\n\n<p>Use CIT when your research question is about <em>what helps or hinders</em> a specific outcome, and when the people involved have recent, first-hand experience of that outcome. It fits well when the topic is hard to discuss in the abstract but easy to illustrate with a story.</p>\n\n<table>\n<thead>\n<tr><th>Your question looks like…</th><th>Best-fit method</th><th>Why</th></tr>\n</thead>\n<tbody>\n<tr><td>What helps or hinders X? What makes X succeed or fail?</td><td>Critical incident technique</td><td>Concrete events map directly to helping and hindering factors.</td></tr>\n<tr><td>How do people experience or make sense of X?</td><td>Semi-structured interview with thematic analysis or IPA</td><td>Meaning matters more than event-level causes.</td></tr>\n<tr><td>Why do people prefer one option over another?</td><td>Laddering interview</td><td>Links attributes to consequences and values.</td></tr>\n<tr><td>What do people do routinely, day to day?</td><td>Diary study or observation</td><td>CIT misses the ordinary; diaries capture it in the moment.</td></tr>\n<tr><td>What triggered a purchase or a switch?</td><td>Jobs-to-be-done interview</td><td>Timeline of one decision, with push and pull forces.</td></tr>\n</tbody>\n</table>\n\n<p>In service research, <a href=\"https://doi.org/10.1177/1094670504266138\" target=\"_blank\" rel=\"noopener noreferrer\">Gremler (2004, Journal of Service Research)</a> reviewed how CIT had been applied to satisfying and dissatisfying service encounters. The same review is a good model for reporting standards, because it criticizes studies that omit how incidents were classified and checked.</p>\n\n<h2>The five steps of a CIT study</h2>\n\n<h3>1. Define the general aim</h3>\n<p>Write one sentence that states what the activity is for, in terms that participants and experts would agree on. Example: \"The aim of doctoral supervision is to help a student become an independent researcher.\" Every incident will be judged against this aim, so a vague aim produces vague incidents.</p>\n\n<h3>2. Set plans, specifications and criteria</h3>\n<p>Decide who can report incidents (people with direct experience), what counts as an incident, which situations are in scope, and how recent the event must be. Many studies limit recall to the past 6 to 12 months to reduce memory distortion. Write these rules down before the first interview; they become your inclusion criteria for extraction.</p>\n\n<h3>3. Collect the incidents</h3>\n<p>Interviews give the richest incidents; open-ended questionnaires reach more people but often return thinner accounts. A <a href=\"https://www.frontiersin.org/journals/psychology/articles/10.3389/fpsyg.2025.1646782/full\" target=\"_blank\" rel=\"noopener noreferrer\">December 2025 methods article in Frontiers in Psychology (Petiot et al.)</a> compared both and recommends following written incidents with an interview that walks through each one in chronological order. Record and transcribe every interview.</p>\n\n<h3>4. Analyze the incidents</h3>\n<p>Analysis has three moves. First, choose a <strong>frame of reference</strong> based on how the results will be used. Second, extract incidents from transcripts and group similar ones into inductively formed categories. Third, decide the level of specificity: categories broad enough to be useful, narrow enough to be distinct. Butterfield et al. (2009) cite Borgen and Amundson's rule that a category should be supported by at least 25% of participants to stand on its own.</p>\n\n<h3>5. Report the findings</h3>\n<p>Report each category with a definition, example incidents, the number of incidents, and the participation rate. State the limits of the frame of reference and how credibility was checked.</p>\n\n<h2>A CIT interview guide you can copy</h2>\n\n<p>This guide follows the structure used in the enhanced critical incident technique: context first, then helping incidents, hindering incidents, and a wish list. Ask for one incident at a time and probe until you have the three elements Flanagan needs: the situation, the action, and the outcome.</p>\n\n<ol>\n<li><strong>Context:</strong> \"Tell me briefly about your role and how long you have been doing it.\" \"Overall, how well is [the activity] going for you right now?\"</li>\n<li><strong>Helping incident:</strong> \"Think of a specific time in the last six months when something clearly helped you [reach the aim]. What happened?\"</li>\n<li><strong>Probes:</strong> \"What led up to it?\" \"Who was involved?\" \"What exactly did you or they do?\" \"What was the result?\" \"How did it help?\"</li>\n<li><strong>Repeat:</strong> \"Can you think of another time something helped?\" Continue until the participant runs out.</li>\n<li><strong>Hindering incident:</strong> \"Now think of a specific time something made it harder. What happened?\" Use the same probes.</li>\n<li><strong>Wish list:</strong> \"Is there anything that wasn't there that would have helped?\"</li>\n<li><strong>Close:</strong> \"Is there anything important about this that we haven't covered?\"</li>\n</ol>\n\n<p>Nielsen Norman Group's <a href=\"https://www.nngroup.com/articles/critical-incident-technique/\" target=\"_blank\" rel=\"noopener noreferrer\">guide to CIT in UX research (Rosala, 2020)</a> adds two practical cautions: ask for a <em>critical</em> incident rather than \"the last time,\" and pilot the wording, because small changes in phrasing change which events people recall. For a structured approach to piloting, see our <a href=\"/blog/how-to-pilot-test-ai-interview-guide-2026\">guide to pilot-testing an interview guide</a>.</p>\n\n<h2>A worked example (illustrative)</h2>\n\n<p>The example below is invented to show the mechanics; it is not real data. Suppose a research lab studies what helps or hinders first-year PhD students in working with their supervisors, and interviews 15 students.</p>\n\n<table>\n<thead>\n<tr><th>Step</th><th>What the researcher produces</th></tr>\n</thead>\n<tbody>\n<tr><td>Raw incident</td><td>\"Two weeks before my first progress review, my supervisor blocked an hour, read my draft line by line and told me which section to cut. I went in with a clear argument and passed.\"</td></tr>\n<tr><td>Extraction</td><td>Situation: upcoming review. Action: supervisor gave dedicated, specific feedback. Outcome: clearer argument, passed review. Type: helping.</td></tr>\n<tr><td>Category</td><td>\"Timely, specific feedback on written work\"</td></tr>\n<tr><td>Report line</td><td>Category name, definition, number of incidents, participation rate (e.g., 9 of 15 participants, 60%), and one or two representative quotes.</td></tr>\n</tbody>\n</table>\n\n<p>The researcher logs, after each interview, how many new categories appeared. When several consecutive interviews add none, the category scheme is exhaustive. In the <a href=\"https://cjc-rcc.ucalgary.ca/article/view/58863\" target=\"_blank\" rel=\"noopener noreferrer\">Butterfield et al. (2009) ECIT study</a>, no new categories emerged from the sixth through the twentieth interview.</p>\n\n<h2>Original asset: the CIT Rigor Checklist</h2>\n\n<p>We built this checklist from the nine credibility checks in Butterfield, Borgen, Maglio and Amundson (2009, Canadian Journal of Counselling). Use it in your methods section or ethics application.</p>\n\n<table>\n<thead>\n<tr><th>#</th><th>Credibility check</th><th>What to do</th><th>Evidence to report</th></tr>\n</thead>\n<tbody>\n<tr><td>1</td><td>Audio-recording interviews</td><td>Record and work from recordings or transcripts.</td><td>Recording and transcription procedure</td></tr>\n<tr><td>2</td><td>Interview fidelity</td><td>An expert in CIT reviews a sample of interviews against the guide.</td><td>Who checked, how many, and feedback given</td></tr>\n<tr><td>3</td><td>Independent extraction</td><td>A second person extracts incidents from about 25% of transcripts.</td><td>Agreement rate and how differences were resolved</td></tr>\n<tr><td>4</td><td>Exhaustiveness</td><td>Log new categories per interview.</td><td>Interview number after which no new categories appeared</td></tr>\n<tr><td>5</td><td>Participation rates</td><td>Count participants per category.</td><td>Rate per category, with the 25% threshold</td></tr>\n<tr><td>6</td><td>Independent placement</td><td>A judge places 25% of incidents into your categories.</td><td>Match rate (80% or better is the usual guideline)</td></tr>\n<tr><td>7</td><td>Participant cross-checking</td><td>A second contact where participants review their incidents and categories.</td><td>Number of participants reached and changes made</td></tr>\n<tr><td>8</td><td>Expert opinions</td><td>Two or more domain experts review the final categories.</td><td>Who reviewed and what they questioned</td></tr>\n<tr><td>9</td><td>Theoretical agreement</td><td>State your assumptions and compare categories with the literature.</td><td>Which categories are supported, novel, or contradicted</td></tr>\n</tbody>\n</table>\n\n<p>For checks 3 and 6, our guide to <a href=\"/blog/intercoder-reliability-ai-qualitative-coding-2026\">intercoder reliability</a> explains percent agreement, Cohen's kappa and when each is appropriate. For check 7, see <a href=\"/blog/what-is-member-checking-qualitative-research-2026\">member checking</a>.</p>\n\n<h2>Where Qualitati fits</h2>\n\n<p>Qualitati is a European, budget-friendly qualitative research platform for universities and research companies, with GDPR and data privacy as central priorities. It does not have a CIT-specific mode, but it covers the parts of a CIT study that take the most time:</p>\n<ul>\n<li><strong>Collecting incidents at scale:</strong> the <a href=\"/ai-interviewer\">AI Interviewer</a> runs your CIT guide as a text or voice interview in 10 languages and asks follow-up questions, so participants can report incidents asynchronously.</li>\n<li><strong>Categorizing incidents:</strong> the <a href=\"/qda-workspace\">QDA Workspace</a> supports inductive and deductive coding and codebook generation, which you can use to draft incident categories and then refine them yourself.</li>\n<li><strong>Cross-study synthesis:</strong> <a href=\"/themelens\">ThemeLens</a> runs thematic analysis across up to 100 transcripts with participant-anchored quotes, which helps when you compare categories across sites or groups.</li>\n</ul>\n<p>Keep extraction decisions, category definitions and the credibility checks with the research team. AI output is a draft for human review, not a substitute for the independent coder in checks 3 and 6.</p>\n\n<h2>Limitations and methodological concerns</h2>\n<ul>\n<li><strong>Recall bias:</strong> people remember dramatic events better than routine ones, and reconstruct details. Limit the recall window and ask for specifics.</li>\n<li><strong>Extreme-event skew:</strong> CIT over-represents the memorable. Combine it with a <a href=\"/blog/how-to-run-diary-study-ai-2026\">diary study</a> or observation when ordinary practice matters.</li>\n<li><strong>Self-presentation:</strong> participants may cast themselves well in helping incidents and others poorly in hindering ones.</li>\n<li><strong>Category subjectivity:</strong> categories are researcher-built. The credibility checks exist because two analysts can group the same incidents differently.</li>\n<li><strong>AI moderation risks:</strong> an AI moderator may accept a general opinion as an \"incident.\" Read early transcripts and tighten the guide. This methodological guidance should be reviewed by your supervisor or ethics board for your context.</li>\n</ul>\n\n<h2>Who this is for, and when not to use it</h2>\n<p><strong>Use CIT</strong> if you are a PhD student, lab or research company studying what helps or hinders a defined practice: supervision, onboarding, service recovery, clinical handovers, software adoption. <strong>Do not use it</strong> when you need to understand lived experience in depth (choose IPA or narrative analysis), when participants lack first-hand experience, or when the behavior is too routine for anyone to remember specific instances.</p>\n\n<h2>Bottom line</h2>\n<p>The critical incident technique turns vague questions about \"what works\" into a set of concrete, countable events. Its strength comes from discipline: a clear aim, specific incidents, careful extraction, and documented credibility checks. Done that way, it gives qualitative research a level of auditability that reviewers recognize.</p>\n\n<h2>FAQ</h2>\n\n<h3>What is the critical incident technique in simple terms?</h3>\n<p>It is a way of interviewing (or surveying) people about specific, memorable events that clearly helped or hindered an outcome, then sorting those events into categories. Instead of asking what people usually think, you ask what actually happened in one concrete situation, what they did, and what resulted.</p>\n\n<h3>How many participants does a critical incident study need?</h3>\n<p>CIT studies are sized by incidents, not people. Flanagan's rule is to keep collecting until new incidents stop producing new categories (exhaustiveness). In the Butterfield et al. (2009) example, no new categories emerged after the fifth of twenty interviews. Plan for more, and log new categories per interview so you can show when you stopped.</p>\n\n<h3>Is the critical incident technique qualitative or quantitative?</h3>\n<p>It is usually treated as a qualitative method today, but it was designed to produce counts. Incidents are categorized inductively, and categories are then reported with frequencies and participation rates (the share of participants who mentioned each category). Many studies report both.</p>\n\n<h3>What is the difference between CIT and the enhanced critical incident technique (ECIT)?</h3>\n<p>ECIT, described by Butterfield, Borgen, Maglio and Amundson (2009), keeps Flanagan's five steps but adds wish-list items (what would have helped), contextual questions, and nine credibility checks such as independent extraction, participant cross-checking and expert review of the categories.</p>\n\n<h3>Can AI-moderated interviews be used for CIT?</h3>\n<p>Yes, for data collection, if the interview guide asks for one specific incident at a time and the moderator probes for context, actions and outcome. Pilot the guide, read the transcripts, and keep incident extraction and categorization under human control with an independent second coder.</p>\n\n<h2>Conclusion</h2>\n<p>If your question is about what helps or hinders an outcome, the critical incident technique is a proven, well-documented choice. Define the aim, ask for one incident at a time, log exhaustiveness, and report the credibility checks. When you are ready to collect incidents, you can <a href=\"/register\">start free with 30 monthly credits</a>, no credit card required, or <a href=\"/pricing\">view transparent pricing</a>. For the analysis stage, our <a href=\"/blog/thematic-analysis-guide\">thematic analysis guide</a> and <a href=\"/blog/qualitative-codebook-template-2026\">codebook template</a> pair well with CIT categories.</p>\n\n<script type=\"application/ld+json\">\n{\n  \"@context\": \"https://schema.org\",\n  \"@type\": \"Article\",\n  \"headline\": \"Critical Incident Technique: Steps, Guide & Example\",\n  \"description\": \"The critical incident technique (Flanagan, 1954) explained: five steps, an interview guide with probes, a worked example, and the nine ECIT credibility checks.\",\n  \"datePublished\": \"2026-10-27\",\n  \"dateModified\": \"2026-10-27\",\n  \"inLanguage\": \"en\",\n  \"author\": {\n    \"@type\": \"Organization\",\n    \"name\": \"Qualitati Research Team\"\n  },\n  \"publisher\": {\n    \"@type\": \"Organization\",\n    \"name\": \"Qualitati\",\n    \"url\": \"https://qualitati.com\"\n  },\n  \"mainEntityOfPage\": \"https://qualitati.com/blog/critical-incident-technique-qualitative-research-2026\"\n}\n</script>\n<script type=\"application/ld+json\">\n{\n  \"@context\": \"https://schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What is the critical incident technique in simple terms?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"It is a way of interviewing (or surveying) people about specific, memorable events that clearly helped or hindered an outcome, then sorting those events into categories. Instead of asking what people usually think, you ask what actually happened in one concrete situation, what they did, and what resulted.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How many participants does a critical incident study need?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"CIT studies are sized by incidents, not people. Flanagan's rule is to keep collecting until new incidents stop producing new categories (exhaustiveness). In the Butterfield et al. (2009) example, no new categories emerged after the fifth of twenty interviews. Plan for more, and log new categories per interview so you can show when you stopped.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Is the critical incident technique qualitative or quantitative?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"It is usually treated as a qualitative method today, but it was designed to produce counts. Incidents are categorized inductively, and categories are then reported with frequencies and participation rates (the share of participants who mentioned each category). Many studies report both.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What is the difference between CIT and the enhanced critical incident technique (ECIT)?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"ECIT, described by Butterfield, Borgen, Maglio and Amundson (2009), keeps Flanagan's five steps but adds wish-list items (what would have helped), contextual questions, and nine credibility checks such as independent extraction, participant cross-checking and expert review of the categories.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Can AI-moderated interviews be used for CIT?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Yes, for data collection, if the interview guide asks for one specific incident at a time and the moderator probes for context, actions and outcome. Pilot the guide, read the transcripts, and keep incident extraction and categorization under human control with an independent second coder.\"\n      }\n    }\n  ]\n}\n</script>","related":[{"slug":"longitudinal-qualitative-research-guide-2026","title":"Longitudinal Qualitative Research: Designs & Analysis","description":"Longitudinal qualitative research explained: designs, wave spacing, attrition, trajectory vs recurrent cross-sectional analysis, and a wave-planning matrix.","category":"Qualitative Methods","date":"2026-10-19","readTime":"13 min read","author":"Qualitati Research Team"},{"slug":"interpretative-phenomenological-analysis-guide-2026","title":"Interpretative Phenomenological Analysis (IPA): 7 Steps","description":"What is interpretative phenomenological analysis? IPA steps in 2022 terms (PETs, GETs), sample size, a worked example, and a quality checklist for theses.","category":"Qualitative Methods","date":"2026-09-29","readTime":"11 min read","author":"Qualitati Research Team"},{"slug":"qualitative-research-questions-examples-2026","title":"Qualitative Research Questions: Examples by Design","description":"Qualitative research questions examples for phenomenology, grounded theory, case study and narrative designs, plus how many to ask and a free fit checklist.","category":"Qualitative Methods","date":"2026-09-23","readTime":"10 min read","author":"Qualitati Research Team"}]}