Gumshoe · Method reference

Critical incident technique

Ask people to recount specific memorable moments, good or bad, to surface what truly drives success and failure.

Conceptual illustration of critical incident technique.
Effort
Medium
Participants
Needed
Remote friendly
Yes
Evidence / output
Direct user

What it is

A structured interview method that collects detailed accounts of specific, memorable events (critical incidents) a person experienced, focusing on what happened, what they did, and why it mattered, to identify factors that lead to effective or ineffective outcomes.

When to use it

During Immerse and early Synthesize, when you need concrete, grounded evidence of what helps or hinders users rather than generalized opinions.

Why (value)

Memorable incidents carry outsized signal. Anchoring to real events reduces rationalization and recall bias, and surfaces the specific moments and conditions that determine satisfaction or breakdown.

How to run it

  1. Define the activity or outcome you care about and what counts as an incident.
  2. Recruit people with direct, recent experience of that activity.
  3. Ask them to recall a specific time it went notably well, and a time it went notably poorly.
  4. Probe for detail: context, their actions, what others did, the result, and why it stuck with them.
  5. Collect enough incidents across participants to see patterns.
  6. Categorize incidents and extract the factors that drive good and bad outcomes.

Inputs and outputs

  • Inputs: Access to people with relevant firsthand experience, an interview guide, a clear definition of the activity.
  • Outputs: A categorized set of incidents and a list of success and failure factors with illustrative quotes.

Time and effort

Medium. Interviews run 30-60 minutes each; you need enough participants to reach saturation, plus synthesis time to categorize incidents.

Evidence and limitations

Yields direct-user, retrospective evidence of specific past events. It is strong on vivid, high-impact moments but biased toward the memorable and the recent; it does not quantify frequency, and self-reported accounts can omit routine-but-important factors. Pair with observation or analytics to balance recall bias. See Evidence and limitations.

Tips and pitfalls

  • Anchor every account to a specific event (“tell me about the last time…”), not general opinion.
  • Collect both positive and negative incidents; failure-only sampling distorts the picture.
  • Probe for the user’s actual behavior and context, not what they think they should have done.
  • Keep categorizing until new incidents stop adding new factors.

Variations

Positive-only or negative-only incident collection, in-the-moment capture via diary studies, group debriefs after a shared event (e.g., post-incident retrospectives).

Need help planning research or facilitating this method?

Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.

Discuss your project with Gumshoe Explore Gumshoe services

Sources and further reading

Explore related methods

  • Stakeholder interviews — Interview the people who own, fund, or are affected by the work to surface goals, constraints, and risks early.
  • Journey mapping — Visualize a person's end-to-end experience across steps, emotions, and touchpoints to find pain and opportunity.
  • Diary studies — Have participants self-report their experiences over days or weeks to capture behavior as it unfolds.

A general practice reference. This page does not establish that a method was used on a particular client project or that an outcome was measured.