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.

Version

v1 · 2026-08-24 · History

Solution archetype #

330

Problem family

Uncertainty, Evidence & Inference Failure

Problem subfamily

Explanatory Hypothesis, Pattern & Case Reasoning

When This Archetype Applies

Complete catalog groundingAt least one sufficient condition set is fully represented by existing primes or domain-specific abstractions.

Diagnostic problem

A case that belongs within a working account's comparison scope behaves contrary to the account and remains unexplained by explanations that fit ordinary cases.

What this problem means

A theory, model, rule, typology, evaluation, or empirical pattern predicts one thing across a set of cases, but one or more cases behave differently. The difference may reveal a boundary condition, omitted variable, hidden mechanism, or classification error, yet ordinary workflows often either discard the case as noise, celebrate it as an anecdote, or force it into the old pattern.

Applicability expression3 distinct conditions

Unexpected focal caseandComparable in-scope caseandTypical explanation failure

Algebraic1∧2∧3

groundedpartly groundedopen

3 conditions, all required.

3Required in every casenumbered 1–3

These hold no matter which pattern applies.

1

Unexpected focal case · grounded

A case violates an expected outcome, pathway, classification, trend, benchmark, or association. more

primeNegative Case Analysis— Deliberately hunt the cases that would overturn your account, then revise or scope it.

and — also required

2

Comparable in-scope case · grounded

The case appears to belong in the same comparison universe as ordinary cases rather than being obviously out of scope. more

primeNegative Case Analysis— Deliberately hunt the cases that would overturn your account, then revise or scope it.

and — also required

3

Typical explanation failure · grounded

Existing explanations describe typical cases but struggle to explain the focal case. more

primeNegative Case Analysis— Deliberately hunt the cases that would overturn your account, then revise or scope it.

Other requirements and context (5)

Why these sit outside the expression

Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.

Solution feasibility — it describes whether the intervention can work, not whether the diagnostic problem exists.

Goal — a goal states an intended outcome or evaluation criterion, not a pre-existing situation that independently summons the archetype.

• Supporting contextThe deviation has practical, theoretical, ethical, safety, or explanatory importance beyond curiosity.

• Solution feasibilityThere is enough case-level evidence to reconstruct sequence, context, actors, constraints, or mechanism rather than only label the case anomalous. more

• GoalA research, diagnostic, evaluation, or operational process needs to learn from exceptions without overfitting to them.

• Supporting contextStakeholders disagree about whether the case is a measurement artifact, isolated exception, evidence of a new subtype, or sign that the theory is wrong.

• Supporting contextA previous comparative analysis produced residuals, unexplained cases, unexpected successes, unexpected failures, or negative cases that were left uninterpreted.

Coverage

3 of 3 conditions grounded.

Read the methodology · Download the trigger-logic data

Common Mechanisms

8 documented mechanisms across 4 implementation forms.

The grouping reflects forms represented among the mechanisms currently documented for this archetype; an absent form is not necessarily an impossible implementation.

Analysis, Modeling & Optimization · 3 mechanisms

• Deviation Residual Table — Displays the predicted or expected pattern against the observed case evidence so the magnitude and type of deviation are explicit.
• Omitted Variable Probe — Searches for variables, mechanisms, constraints, or contextual features absent from the original explanatory frame.
• 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.

Communication, Facilitation & Learning · 1 mechanism

• Boundary Condition Revision Workshop — Uses the deviant case to revise scope conditions, typologies, theory clauses, or decision rules with reviewers or domain experts.

Decision, Gate & Allocation · 1 mechanism

• Deviant Case Selection Protocol — Selects a case that violates an explicitly stated pattern while documenting the universe of comparison and selection rationale.

Representation, Specification & Plan · 3 mechanisms

• Follow-Up Case Sampling Plan — Selects follow-up cases, audits, or monitoring triggers to test whether the revision prompted by a deviant case is isolated, subgroup-specific, or broadly general.
• Matched Case Pairing Matrix — Pairs the focal deviant case with expected-pattern cases that share key background conditions but differ in outcome or mechanism.
• Within-Case Process-Tracing Memo — Documents event sequence, mechanism evidence, actors, constraints, turning points, and rival-process evidence inside the deviant case.

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.

Editorial Notes

Problem Classification

Classification: Uncertainty, Evidence & Inference Failure → Explanatory Hypothesis, Pattern & Case Reasoning

Problem kernel: deviant cases are not used to revise model boundaries

Rationale: Unexpected cases may expose omitted variables or mechanisms, yet the theory treats them as noise instead of evidence against its pattern.

Independent corroboration: The earliest necessary condition in the frozen evidence is: A theory, model, rule, typology, evaluation, or empirical pattern predicts one thing across a set of cases, but one or more cases behave differently. That is a explanatory hypothesis pattern and case reasoning problem because Partial or recurring observations are forced into a favored explanation, analogy, pattern, or universal before alternatives and boundary cases are tested.

Review outcome: Independent reviewer agreement; high confidence.