Multiple Testing Discipline¶
Control false discoveries when many comparisons, claims, or tests are being tried.
The Diagnostic Story¶
Symptom: A result looks significant, or a pattern looks real, but the search that found it involved dozens of comparisons, subgroups, metrics, or time windows that nobody is counting. The one finding that got presented was selected because it was the most interesting — not because it was pre-specified. Failed comparisons disappear from the record, so the claimed discovery looks far more credible than the actual search process warrants. When someone tries to reproduce it, the pattern is gone.
Pivot: Define the family of related tests or claims being made, track the full search process rather than just the selected result, and choose a decision rule that accounts for how many chances existed for an accidental pattern. Separate exploratory evidence — leads worth investigating — from confirmatory evidence that is ready to justify action.
Resolution: The rate of false discoveries is bounded because the opportunity set that produced any selected finding remains visible and is factored into interpretation. High-stakes action requires confirmation stronger than the initial search result, so the distinction between a lead and a finding is preserved rather than collapsed. The discovery record becomes more credible because null results and failed comparisons are retained alongside the claimed success.
Reach for this when you hear…¶
[clinical research] “We ran thirty-two subgroup analyses and found one that was significant — that's not a finding, that's what chance looks like when you look often enough.”
[A/B testing] “The dashboard shows a green metric and everyone wants to ship, but we've been peeking at this experiment every day for two weeks and we never preregistered a stopping rule.”
[financial audit] “If we flag every anomaly that crosses a threshold after slicing by region, quarter, and account type, we'll bury the real findings in false positives — we need a family-level rule before we start slicing.”
When This Archetype Applies¶
Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.
Diagnostic problem
A system runs, inspects, or informally considers many tests, comparisons, metrics, groups, models, or stories, but reports the most appealing result as though it came from one pre-specified test. The more opportunities there are for a chance pattern, the easier it becomes to mistake noise for evidence.
What this problem means
When many tests are tried, chance has many opportunities to produce an impressive-looking pattern. If the failed, null, or unreported comparisons disappear from view, the remaining selected result looks more surprising than it really is. This is the structural source of p-hacking, metric shopping, subgroup fishing, data dredging, repeated interim looks, and overfitting to validation evidence.
The problem is not simply that people use a p-value, a threshold, or a dashboard. The problem is that the evidentiary context of the selected result is incomplete. A single result is being interpreted without the family of attempts that generated it. Multiple-Testing Discipline restores that missing context.
Show the applicability expression
Applicability expression5 distinct conditions
groundedpartly groundedopen
5 conditions, all required.
5Required in every casenumbered 1–5
These hold no matter which pattern applies.
Many simultaneous tests · grounded
Many hypotheses, outcomes, subgroups, windows, thresholds, features, treatments, or metrics are tested.
The source archetype describes the situation as follows: Many hypotheses, outcomes, subgroups, time windows, thresholds, features, treatments, or metrics are being tested or inspected. The normalized requirement above isolates the load-bearing portion used in this condition set.
Post hoc result selection · grounded
A reported result was selected after examining alternatives rather than pre-specified.
The source archetype describes the situation as follows: A result was selected after looking across several alternatives rather than being specified before the evidence was seen. The normalized requirement above isolates the load-bearing portion used in this condition set.
Reused discovery dataset · grounded
One dataset, dashboard, experiment, audit stream, or corpus supports repeated discovery attempts.
The source archetype describes the situation as follows: The same dataset, dashboard, experiment, audit stream, or corpus is reused for many discovery attempts. The normalized requirement above isolates the load-bearing portion used in this condition set.
Incentivized favorable comparisons · open
Institutional incentives reward whichever comparison appears favorable or significant.
The source archetype describes the situation as follows: Teams have incentives to publish, ship, escalate, or celebrate whichever comparison looks significant or favorable. The normalized requirement above isolates the load-bearing portion used in this condition set.
Researcher degrees of freedom · open
Analysts can keep slicing, filtering, modeling, or reframing until a preferred pattern appears.
The source archetype describes the situation as follows: Different analysts or stakeholders can keep slicing, filtering, modeling, or reframing until a preferred pattern appears. The normalized requirement above isolates the load-bearing portion used in this condition set.
Other requirements and context (2)
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.
Application gate — it governs whether applying the archetype is appropriate or material, rather than defining the structural problem itself.
Supporting contextA finding will trigger expensive action, reputation change, policy change, clinical choice, enforcement, or strategic commitment.
It is especially important when selected findings will guide decisions, reputations, resource allocation, safety action, publication, enforcement, or product launch. In this archetype, the relevant contextual consideration is: A finding will trigger expensive action, reputation change, policy change, clinical choice, enforcement, or strategic commitment. It helps interpret the situation or strengthens the practical case for examining the archetype.
Application gateExploratory search is valuable, but the organization needs a clear boundary between generating leads and confirming claims.
It becomes necessary when exploratory results are about to be presented as confirmed claims or used for consequential action. In this archetype, the relevant application gate is: Exploratory search is valuable, but the organization needs a clear boundary between generating leads and confirming claims. It narrows when choosing or applying the archetype is warranted or decision-relevant.
Coverage
3 of 5 conditions grounded · 2 open.
Mechanisms / Implementations¶
- Bonferroni-Like Correction: Stiffens each test's significance bar in proportion to how many tests share the family, so that clearing it stays hard even after many simultaneous attempts.
- False Discovery Rate Control: Ranks a whole family of results and draws the significance line to hold the expected share of false discoveries below a chosen rate, trading a little purity for far more power.
- Preregistration: Timestamps the hypotheses, primary outcome, and analysis plan before the data exist, so what counts as confirmatory is fixed in advance rather than chosen after.
- Holdout Validation: Seals a slice of the evidence away untouched during all discovery, then judges the selected finding once against that fresh partition.
- Claim Registry: A living ledger of every attempted claim — its status, owner, and follow-up burden — so selective memory can't erase the failed tries that made a discovery look surprising.
- Replication Study: Re-runs the finding from scratch in independent hands to see whether it survives outside the conditions and choices that first produced it.
- Confirmatory Follow-Up: Turns one promising exploratory lead into a single pre-specified confirmatory test, so a pattern found by searching must earn its status on fresh ground.
- Alpha-Spending Plan: Treats the total false-positive budget as a currency spent in pre-planned fractions across repeated interim looks, so peeking at accumulating data never inflates the error rate.
- Metric Hierarchy: Ranks metrics into primary, secondary, and exploratory tiers before the data land, so a disappointing primary can't be quietly swapped for a flattering secondary.
- Multiverse Analysis Report: Runs the analysis across every defensible analytic choice at once and shows the whole spread of results, exposing whether the headline depends on one lucky path.
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 (3)
- Multiple Comparisons Correction: Adjust the thresholds or p-values of a defined family of simultaneous tests so a chosen family-level error criterion remains bounded despite multiplicity.
- Reproducibility & Replicability: Repeatable results.
- Type I & Type II Errors: False positive/negative.
Also references 6 related abstractions
- Confirmation Bias: Favor confirming evidence.
- Hypothesis Testing (Null vs. Alternative): Null vs alternative evaluation.
- Probability: Quantifies uncertainty and likelihoods.
- Statistical Significance (p-Value): Likelihood results are random.
- Threshold: Safe vs harmful levels.
- Uncertainty: Incomplete knowledge.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Familywise Error Control Variant · risk or failure variant · recognized
A stricter variant that tries to avoid even one false positive across a defined family of claims.
False Discovery Rate Variant · risk or failure variant · recognized
A screening-oriented variant that permits many discoveries while controlling the expected share that are false.
Exploratory–Confirmatory Partition Variant · temporal variant · promote to full archetype candidate
A staged variant that explicitly labels idea-generation evidence separately from confirmation evidence.
Claim Registry Variant · governance variant · recognized
A governance variant that controls multiplicity by making attempted claims, status, and follow-up obligations visible across a portfolio.
Editorial Notes¶
Problem Classification¶
Classification: Uncertainty, Evidence & Inference Failure → Experimental Comparison & Hypothesis-Test Design
Problem kernel: multiple unplanned tests inflate chance findings
Rationale: Earliest causal condition: A system runs, inspects, or informally considers many tests, comparisons, metrics, groups, models, or stories, but reports the most appealing result as though it came from one pre-specified test. The more opportunities there are for a chance pattern, the easier it becomes to mistake noise for evidence.
Independent corroboration: The earliest necessary condition in the frozen evidence is: A system runs, inspects, or informally considers many tests, comparisons, metrics, groups, models, or stories, but reports the most appealing result as though it came from one pre-specified test. That is a experimental comparison and hypothesis test design problem because Treatment, control, assignment, blinding, power, and evidence thresholds are insufficiently designed to support the intended comparison.
Review outcome: Independent reviewer agreement; high confidence.