Use it when a striking pattern showed up after the fact.
The model is most useful when someone presents a match, a cluster, or a "hit" as evidence — and nobody has asked how many other comparisons were quietly run before that one was chosen.
Watch a flat result become a "finding."
Step through a realistic scenario. Click through to see how enough slices of the same data will eventually produce a convincing-looking pattern — whether or not anything real is there.
A product team ships a redesigned onboarding flow. Two weeks later they pull the dashboard: signup completion is basically unchanged, overall, between the old and new flow.
Fire → Spot a cluster → Paint the target → "Proof."
This is a conceptual chain, not a measured chart. It describes four steps through which random noise gets mistaken for a discovery: generating many chances for something to look interesting, noticing the one that does, framing that one as the hypothesis after the fact, and presenting the match as if it had been predicted.
Recognize the situation.
Open a case to see what the model points you toward checking.
Data & product analytics
A metric only looks good after slicing the data many ways
Ask how many other cuts — by device, day, region, cohort — were tried before this one was presented. The more cuts attempted, the more likely one clears a significance threshold by chance alone.
Public health
A community reports a disease cluster near a facility
With thousands of neighborhoods being watched for thousands of possible conditions, some will show an elevated rate purely by chance. Check whether the specific condition was flagged before or after the cluster was noticed, and how large the exposed population and effect size really are.
Finance & trading
A backtested strategy shows a great historical return
If the strategy's rules were tuned by testing many variants against the same historical data, the best-looking one is partly a product of how many variants were tried, not necessarily a durable edge.
AI evaluation
One cherry-picked AI output looks impressive out of many tries
Generating many samples and showcasing only the best one is the same move as painting a target around the tightest shots. Ask how many attempts it took, and whether the result holds up on a fresh prompt or dataset.
Research & journalism
A pundit or forecaster "predicted" an event after the fact
Loosely worded predictions, read back after an event, can be matched to almost anything. Check whether the prediction was specific and dated before the event, not reinterpreted afterward.
People analytics
An interview question seems to predict who succeeds
If dozens of interview questions or traits were tested against performance data and one correlated, treat it as a lead to re-test on a fresh group, not as a validated predictor yet.
What happens when you test hundreds of things at once?
This draws on published findings and widely cited case studies rather than an invented scenario. Numbers below are as reported by the cited sources.
Where the name — and the evidence — come from.
Expand for the origin of the term and what the strongest research actually supports.
Where does the joke actually come from?
The image is old. A story about the Dubno Maggid, a rabbi and storyteller who died in 1804, used an arrow version of the same idea. In 1866, the logician John Venn described a related version in The Logic of Chance: a man who chalked a target around a bullet hole already in a barn door and then claimed to have hit the mark on purpose. Venn used it to argue that people judge many real-world patterns the same way — after the fact.
Where does the "Texas" part come from?
The specifically Texan version of the joke first appears in the statistical literature in a 1977 paper by Seymour Grufferman. There is no clear link to the actual 1st Texas Sharpshooter Battalion from the Civil War; the Texas framing more likely trades on a general stereotype of Texans as tellers of tall, boastful tales. The term reached a much wider audience in 1999, when physician and writer Atul Gawande used it in his New Yorker article "The Cancer-Cluster Myth," applying it specifically to how disease-cluster scares are often investigated.
Is this the same thing as a clustering illusion or p-hacking?
They are close relatives, not identical. The Texas sharpshooter fallacy is the broad rhetorical move of drawing a conclusion around data found after the fact. The "clustering illusion" is the narrower perceptual tendency to see meaningful clumps in truly random sequences — the thing that makes a cluster look surprising in the first place. "Data dredging," "p-hacking," and "HARKing" (hypothesis after results are known) are the more technical, statistics-specific versions of the same error: running many tests or models until one clears a significance threshold, then reporting that one as if it had been the planned test all along.
What does the research say about why clusters feel so convincing?
Daniel Kahneman and Amos Tversky described a related tendency they called belief in the "law of small numbers" — expecting a small sample to look as orderly as a huge one, so that an ordinary run of luck reads as a signal. Separately, Thomas Gilovich, Robert Vallone, and Amos Tversky's 1985 study of the "hot hand" in basketball found that streak shooters showed no more consecutive hits or misses than a random sequence would predict — the streaks people saw and bet on were well within the range chance alone produces.
The idea is simple. Catching it in your own work is not.
Treating any match as proof
A pattern that clears a significance threshold is not automatically real. Ask how many other comparisons were run before this one was presented as the finding.
Hypothesizing after the results are known
Presenting a pattern found by searching the data as though it had been predicted in advance (sometimes called HARKing) hides exactly the information needed to judge how likely it was by chance.
Skipping the multiple-comparisons correction
Testing 20 slices at the usual 5% significance threshold means roughly one slice is expected to look "significant" by pure chance, with nothing real behind it.
Confusing a marginal signal with an overwhelming one
Not every cluster is noise: chimney sweeps' scrotal cancer and the roughly sevenfold-thousand mesothelioma rate found in Karain, Turkey were both real, mechanistically explainable, and enormous. Most after-the-fact clusters are nowhere near that strong.
Skipping replication
A pattern found by searching the data should be tested again on fresh, independent data before anyone acts on it. If it was never real, it usually will not show up twice.
Peeking at your own test set
In AI and data work, tuning choices or cherry-picking the best run using the same data you later report results on is the digital version of painting the target after the shot.
Some patterns really were predicted, not found.
Trust the result when...
the hypothesis and the test were specified before the data was collected — pre-registration is the clearest safeguard against this fallacy.
Trust the result when...
the effect is enormous and mechanistically plausible, not merely statistically significant — as with occupational carcinogens or a well-understood outbreak source.
Trust the result when...
the pattern has already replicated independently, on a new sample, using a method chosen in advance.
This model works best paired with others already in the library.
Build a Texas Sharpshooter Fallacy diagnostic prompt.
This browser tool structures your thinking. It does not send your information anywhere or perform AI analysis.
Your AI-ready prompt
Turn this mental model into a reusable AI skill.
Save as Skill converts the model into portable Markdown instructions that teach an AI when and how to spot a Texas Sharpshooter Fallacy, what questions to ask, what evidence to seek, what mistakes to avoid, and how to structure its analysis.
Build your own Mental Models Skills Library
Save the skills you find useful and organize them into your own reusable library. The Markdown is intentionally model-neutral, so it can be used wherever an AI system accepts uploaded files, project knowledge, custom instructions or reusable text context. Platform capabilities differ, so this is a portable skill file rather than a claim of one-click installation.
For readers who want the nuance.
How many comparisons does it take before a false "hit" is likely?
With a conventional 5% significance threshold, testing 20 independent comparisons makes at least one false positive likely even if nothing real is happening in any of them — that is simple multiplication, not a special property of any one dataset. Raymond Neutra's calculation, reported by Gawande, shows the same logic at a larger scale: thousands of census tracts, each watched for dozens of cancer types, will reliably produce thousands of "statistically significant" but random elevations somewhere.
How do investigators tell a real cluster from a sharpshooter illusion?
Gawande's article points to genuine clusters that were traced to real causes — Legionnaires' disease, Haff disease, and DES (diethylstilbestrol) among them — and to occupational cases like Percivall Pott's 1775 finding that chimney sweeps suffered unusually high rates of scrotal cancer from soot exposure. The common thread in confirmed cases is a plausible mechanism and a very large effect size, such as the roughly sevenfold-thousand excess mesothelioma rate found in Karain, Turkey, linked to erionite mineral fibers. Minnesota's health department, by contrast, investigated more than a thousand reported clusters over several years and found the exercise largely unproductive — most were statistical noise.
Does this fallacy only apply to epidemiology?
No — the underlying math shows up anywhere many comparisons are possible: drug trials that report an effect only in a subgroup discovered after the fact, trading strategies tuned against historical price data until one looks profitable, and even wartime pattern-spotting. A frequently cited example is statistician William Feller's analysis of V-1 and V-2 rocket strikes on London during the Second World War: residents were convinced the strike pattern showed non-random targeting, but the distribution matched what a random (Poisson) process would produce.