How to Test a Popular Claim Without Replacing It With Another Myth

A good fact-check begins with a smaller sentence

Popular claims tend to arrive in polished, portable form. They are easy to remember, easy to repeat, and often too broad to test as written. “Lightning never strikes the same place twice” is a neat example: it sounds like a statement about weather, but it is also used as a comforting metaphor for rare misfortune. Those are different claims. One can be examined with observations of lightning; the other expresses a hope about life.

Before searching for proof, translate the sentence into a prediction. If the claim is literal, it predicts that no location ever receives a second lightning strike. One documented location struck more than once is enough to refute that absolute. If the claim instead means that a particular unlikely event will not recur in one person’s life, the weather cannot settle the matter. The wording has changed the subject.

This first move—clarifying what a claim actually says—is the quiet craft behind serious myth-busting. It keeps a check from becoming a performance in which one side announces “true” or “false” and the other side is expected to applaud. The aim is narrower and more useful: identify the prediction, find evidence that could test it, and state what that evidence can and cannot establish.

Step one: separate the literal claim from the metaphor

Language travels between literal and figurative meanings all the time. “The sun rises” is a practical description of what an observer sees, though Earth’s rotation explains the apparent motion. “Lightning never strikes twice” can be a figure of speech meaning that a rare setback is unlikely to repeat. Neither usage is automatically a problem. Trouble begins when a metaphor is treated as a scientific rule—or when a scientific correction is presented as if it had disproved the emotional idea behind the metaphor.

Write down the claim in the form you intend to test. A useful testable version might be: No lightning flash has ever struck the same physical structure twice. That is much more specific than the familiar saying. It identifies the event (a lightning strike), the target (a physical structure), and a criterion for repetition (the same structure). It also makes clear what evidence would count: reliable records showing multiple strikes to a single structure.

Definitions matter. Does “same place” mean the same building, the same point on a roof, or the same patch of ground? A lightning channel can branch, and a structure is not a mathematical point. In a rigorous test, the definition should match the scale of the claim. For an everyday saying, a repeated strike on the same tall building plainly counts. For a scientific study of strike locations, researchers may need precise spatial measurements and a stated tolerance.

When a claim uses words such as “never,” “always,” “everyone,” or “impossible,” pause. Absolutes are vulnerable to a single counterexample, but only if the example meets the claim’s definition. “This has happened at least once” and “this happens often” are also not interchangeable. A fact-check should not turn one into the other.

Step two: look for a clean test

A strong test is one that could, in principle, prove the claim wrong. For the lightning saying, a repeat strike on a named structure is a direct counterexample. The Empire State Building in New York City is a particularly vivid case: the building’s public information describes it as being struck repeatedly, commonly cited at around 20 to 25 strikes per year. That makes “lightning never strikes the same place twice” untenable as a literal statement about structures.

The example is striking because it is ordinary in one important sense: tall structures can be hit repeatedly. Lightning is not choosing a building because it remembers a previous visit. Electrical conditions, storm development, and the geometry of the surroundings shape where discharges occur. A tall, exposed structure offers a likely point of attachment in its local environment. The building’s repeated strikes are therefore not a loophole in the saying; they expose the problem with its literal wording.

For claims that are not so easily tested, ask what observation would change your mind. If no possible evidence could count against a claim, it may be a matter of belief, a value judgment, or a claim framed too vaguely to evaluate—not an empirical statement with a straightforward fact-check. That distinction is not an insult. It simply keeps different kinds of questions in their proper lanes.

Useful tests can take different forms. A historical claim may be checked against dated documents, material evidence, and the context in which a source was produced. A technology claim might be tested against a stated benchmark, version number, or reproducible procedure. A health claim may require controlled studies and careful attention to population, dose, and outcome. The method changes with the subject; the discipline of specifying the prediction does not.

Step three: match the evidence to the claim

Not all evidence answers the same question. A photograph of lightning hitting a building can show that a strike occurred, but it may not establish how many strikes that building receives in a year. A building’s annual strike estimate can speak to frequency, but it does not prove that every tall structure is struck repeatedly. The question should determine the evidence, rather than the other way around.

For the familiar saying, one well-documented repeat strike is sufficient to defeat the absolute “never.” To describe how common repeat strikes are, however, a broader record is needed. To explain why the same structure is hit, one needs an account of lightning physics and local conditions. These are three different conclusions, and each calls for a different level of support.

It helps to sort evidence into a rough hierarchy, while remembering that no source is automatically perfect:

• Direct records: Instrument measurements, official logs, or documented observations tied to a defined place and time.
• Expert and institutional explanations: Material from organizations with relevant technical expertise, such as the U.S. National Weather Service, interpreted in context.
• Careful secondary accounts: Reporting or reference works that identify their sources and distinguish established findings from uncertainty.
• Anecdotes and repetition: Personal recollections, viral posts, and familiar sayings, which may point toward a question but rarely settle it alone.

This is not a rule that official information must always be right or that a witness must always be wrong. It is a prompt to inspect how a source knows what it says. Does it show its method? Is the information current? Does the author have relevant expertise? Can the underlying observation be checked independently? A credible fact-check makes that chain visible instead of relying on a confident tone.

Step four: read the source, not just the search result

A headline or search snippet is a doorway, not a source. Open the page and look for the actual statement, its date, and its qualifications. A number may describe one year, a long-term average, a particular structure, or an estimate repeated without a clear method. Those distinctions are small on the screen and large in meaning.

For lightning information, the U.S. National Weather Service provides public material on lightning safety and behavior. The Empire State Building’s own published facts offer a site-specific account of strikes on the building. These sources answer related but not identical questions: one explains the hazard broadly; the other describes a famous structure. Read them for what they establish, and avoid borrowing a figure from one context to make a broader claim it was never meant to support.

Check dates, too. A building may undergo renovations; a measurement system may change; an article may be updated. When a source reports a number, ask whether it is a direct count, an estimate, or a commonly repeated figure. If the method is not described, say so. “The building reports roughly this many” is more transparent than presenting an approximate figure as a laboratory measurement.

One practical habit is to follow citations backward. If an article attributes a number to an institution, visit the institution’s page. If the institution cites a study, inspect the study’s abstract or methods where available. Each step can reveal whether a claim has been simplified accurately—or whether a citation has become decorative through repeated copying.

Step five: distinguish a counterexample from a whole explanation

One repeat strike is enough to show that lightning can strike the same structure twice. It is not enough to calculate the global probability of a repeat strike, describe lightning risk in every location, or explain every mechanism that guides a discharge. This is the difference between refuting an absolute and building a complete account.

That distinction is central to honest myth-busting. A myth-buster can be technically correct and still leave readers with a distorted impression by stretching the evidence. If the claim says “never,” a single counterexample settles the literal question. If the claim is “how often,” the answer needs a frequency estimate and a clearly defined population. If it asks “why,” a list of examples is not a causal explanation.

For the lightning example, the careful conclusion is modest: the saying is false if read literally as a claim that a place or structure cannot be struck twice. Tall structures, including the Empire State Building, are struck repeatedly. The frequency for a particular building depends on what is counted and over what period; the fact of repetition does not mean every building faces identical conditions.

Precision does not weaken a conclusion. It gives the conclusion edges that fit the evidence. “Repeated strikes are documented” is a strong statement. “Lightning will strike any particular building every year” is not supported by that example and should not be smuggled in as a dramatic flourish.

Step six: treat anecdotes with care

An anecdote can be true and still be poor evidence for a general rule. Someone may remember one lightning strike near their home and infer that the neighborhood is uniquely dangerous. Another person may live for decades without witnessing a direct strike and conclude that repeat strikes are impossible. Both experiences can be sincere; neither represents a systematic record of lightning behavior.

Anecdotes are valuable as leads. They can suggest what to investigate, identify a local observation, or reveal how people interpret an event. The mistake is asking them to do work they cannot do—such as establish a rate across thousands of storms or prove that something never happens. For that, broader observations and defined methods matter.

Online repetition creates a related trap. A claim repeated across many websites may appear to have many independent sources, when all of them trace back to one unsourced sentence. This is sometimes called citation laundering: repetition gives an assertion the costume of corroboration. Look for independent records, not just multiple copies of the same phrasing.

Step seven: give the claim a fair verdict

Binary labels can be useful, but they should not flatten nuance. A verdict might say “false as a literal statement,” followed by the evidence and the limits of the finding. It might say “misleading” where a sentence contains a kernel of truth but implies more than the evidence supports. It might say “unverified” when the available sources cannot establish the claim. The label should describe the evidence, not reward a preferred side.

For this saying, “false as a literal claim” is more exact than simply “false.” The expression remains understandable as a metaphor about improbable events. That figurative use does not make the weather claim true, and the weather correction does not erase the metaphor’s social meaning. Holding both facts at once is a sign of clear reading, not fence-sitting.

Good verdicts also disclose uncertainty. If a number is approximate, call it approximate. If a study measures one group rather than the whole population, name the group. If sources disagree, explain what differs: dates, definitions, methods, or interpretation. A polished answer is not one that hides the seams; it is one that shows readers which seams matter.

A compact checklist for evaluating a popular claim

Use this sequence when a claim feels familiar enough to repeat without thinking:

1. Quote it accurately. Keep the original wording, including qualifiers such as “often,” “can,” or “never.”
2. Define its key terms. Decide what counts as the event, the place, and a repeat occurrence.
3. State the prediction. Write down what should be observed if the claim is true.
4. Ask what could disprove it. If nothing could, clarify whether it is a value judgment, metaphor, or unfalsifiable assertion.
5. Find evidence suited to the question. A counterexample can refute an absolute; a rate needs broader data.
6. Check the source trail. Read the original material, examine its date and method, and look for independent corroboration.
7. Keep the conclusion proportional. Say exactly what the evidence establishes—and no more.
8. Separate literal and figurative meaning. Correct the factual statement without pretending that language has only one use.

The checklist is deliberately plain. Critical thinking is not a special mood reserved for political arguments or dramatic scientific disputes. It is a set of repeatable habits: clarify, test, compare, and qualify. Those habits work on a weather saying, a historical anecdote, a product claim, or a viral assertion about technology.

Why this method travels beyond lightning

In science, the method helps distinguish a proposed mechanism from evidence that it occurs. In technology, it turns vague promises—“faster,” “safer,” “unbreakable”—into questions about benchmarks, threat models, and operating conditions. In history, it encourages readers to check whether a quotation has a reliable source and whether a later retelling has altered its context. In culture, it helps separate a statistical claim from a stereotype or a memorable story.

Take “this device is unhackable.” The word “unhackable” is an absolute, much like “never.” A useful evaluation would define the device and software version, specify the kind of attacker and the available time or access, and look for independent security testing. A single successful exploit can refute an absolute claim about that version, but it does not prove every version is insecure. The structure of the test is the same as the lightning example; the expertise and evidence are different.

Or consider a historical statement that a famous event happened “exactly as everyone remembers.” The evaluator must identify the particular detail, locate contemporary records, ask who produced them and when, and compare them with later accounts. Memory, like an anecdote about storms, may provide a starting point. It does not substitute for source criticism.

The point is not to become suspicious of every sentence. It is to reserve confidence for claims that have earned it. A good explainer should leave the reader not only with an answer, but with a small, portable method for judging the next claim that arrives dressed as common knowledge.

The answer, stated plainly

Lightning can strike the same place more than once. The Empire State Building’s repeated strikes—often reported at roughly 20 to 25 per year—make the familiar saying false if it is read as a literal rule about physical locations. The phrase still works as a metaphor for hoping that an unlikely misfortune will not recur; that is a different proposition, and meteorological records cannot settle it.

That modest conclusion is the model to carry forward. Test what a claim predicts, not what its rhythm suggests. Prefer evidence that directly addresses the question. Do not let one counterexample balloon into a universal explanation, and do not let a metaphor masquerade as a scientific fact. The sharpest myth-busting is not the loudest verdict. It is the one that leaves the reader with a clearer sentence than the one they arrived with.