Deviant Case Analysis

When a case violates what the comparison set led you to expect, analyze the violation as evidence for theory refinement rather than dismissing it as noise or treating it as a story by itself.

Common Mechanisms

• Boundary Condition Revision Workshop
• Deviant Case Selection Protocol
• Deviation Residual Table
• Follow-Up Case Sampling Plan
• Matched Case Pairing Matrix
• Omitted Variable Probe
• Rival Explanation Elimination Table — Lays every candidate explanation for an outcome side by side and rules each out by the evidence it would predict but the cases do not show.
• Within-Case Process-Tracing Memo

Compression statement

A comparative-method archetype that turns anomalous, negative, discordant, or outlier cases into disciplined learning objects. It begins with an explicit expected pattern and case universe, verifies that the apparent deviation is real, anchors the focal case against matched or contrast cases, traces within-case mechanisms, tests rival explanations, and converts the result into bounded theory revision: new variable, new subtype, boundary condition, scope restriction, causal-mechanism refinement, or follow-up sampling plan.

Canonical formula: theory_gain = verified_deviation + matched_comparison + within_case_trace + rival_explanation_test - measurement_artifact - anecdotal_overgeneralization

Related Abstractions

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (1)

• Comparative Method: Systematically juxtaposing selected cases so that their similarities and differences do the causal-inference work that controlled experiments cannot.

Also references 22 related abstractions

• Abstraction: Focus on core elements.
• Black Swan (High-Impact, Low-Probability Events): High-impact unexpected events.
• Boundary: Defines system limits.
• Causality: Cause-effect relationships.
• Classification: Sorting entities into discrete categories by explicit rules, turning unbounded variation into a finite, reusable map for downstream reasoning and action.
• Confirmation Bias: Favor confirming evidence.
• Counterfactual Reasoning: Hypothetical alternatives.
• Deductive Reasoning: General to specific conclusions.
• Feedback: Outputs influence inputs.
• Hypothesis Testing (Null vs. Alternative): Null vs alternative evaluation.

▸ Show 12 more

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Negative Case Validation · subtype · candidate

Uses cases that contradict an expected claim to validate, qualify, or revise the claim.

• Distinct from parent: The parent includes negative-case validation but also covers unexpected successes, unexpected failures, omitted variables, subtype discovery, and boundary-condition refinement.
• Use when: The main question is whether a claim survives known contrary cases; Contradictory cases must be integrated into validation rather than ignored.
• Typical domains: comparative sociology, policy evaluation, clinical diagnosis
• Common mechanisms: rival explanation elimination table, followup case sampling plan

Deviant Success Case Analysis · subtype · recognized

Explains cases that succeed despite conditions under which failure was expected.

• Distinct from parent: The parent covers all deviations; this variant centers unexpectedly favorable outcomes.
• Use when: A case performs unexpectedly well relative to matched peers; The analysis aims to identify transferable enabling conditions or overlooked mechanisms.
• Typical domains: organizational resilience, education improvement, public health
• Common mechanisms: matched case pairing matrix, within case process tracing memo

Deviant Failure Case Analysis · subtype · recognized

Explains cases that fail despite conditions under which success was expected.

• Distinct from parent: The parent includes positive, negative, and mixed deviations; this variant centers predicted-success failures.
• Use when: A case underperforms relative to an expected successful pattern; The analysis must uncover hidden fragility, omitted constraints, or implementation breakdowns.
• Typical domains: implementation science, safety analysis, program evaluation
• Common mechanisms: omitted variable probe, rival explanation elimination table

Boundary Condition Discovery · subtype · candidate

Uses deviant cases to specify where a theory, model, or rule stops applying.

• Distinct from parent: The parent may produce several revision types; this variant specializes in scope limitation.
• Use when: The main value of the deviant case is clarifying scope conditions; The original theory still works in many cases but fails under identifiable contextual limits.
• Typical domains: model validation, comparative history, policy transfer
• Common mechanisms: boundary condition revision workshop, followup case sampling plan

Omitted Variable Recovery · subtype · candidate

Uses a deviant case to discover variables, mechanisms, constraints, or interactions missing from the original explanation.

• Distinct from parent: The parent can produce multiple theory revisions; this variant foregrounds variable recovery.
• Use when: The deviant case appears explainable only by a factor absent from the original model; Matched comparison can isolate a candidate omitted factor.
• Typical domains: epidemiology, economics, operational incident analysis
• Common mechanisms: omitted variable probe, matched case pairing matrix

Near names: Negative Case Analysis, Outlier Case Analysis, Anomalous Case Analysis.