How to Check Where an Analogy Misleads Readers

First identify what the analogy is doing

An analogy can serve as an explanation, an illustration, or part of an argument. These jobs are related but not interchangeable. “A project plan is a map” may help a reader picture a plan as a guide. If the writer adds, “so it will show every obstacle in advance,” the comparison now carries an argumentative load: it is being used to support a claim about what the plan can predict.

Write the conclusion in plain language without the image. Then ask what the analogy is supposed to establish. Is it meant to explain a process, suggest a possibility, or persuade the reader that a conclusion is likely? In an analogical argument, known similarities between a source and a target are used to support a further similarity; that conclusion is supported to some degree, not guaranteed. The Stanford Encyclopedia of Philosophy’s account of analogical reasoning describes this as ampliative reasoning: the inference can extend what is known without making the conclusion certain.

That distinction gives you a useful editing test: if the analogy only illustrates a point, label its limits so the illustration is not mistaken for evidence. If it supports a conclusion, test the inference itself. Evidence in the source domain—a familiar case—does not automatically establish that the target case works the same way.

Map relationships, not just matching objects

List the source (the familiar comparison) and target (the subject you want the reader to understand) side by side. Under each, record only the features that matter to your point. Then draw the relationship between them: who or what acts, what changes, what enables the change, and what result follows.

For a hypothetical workshop example, suppose a writer says: “Planning a workshop is like preparing a picnic: choose a date, gather what you need, and people can enjoy the day.” The mapping may look like this:

Source: a picnic; target: a workshop.

Shared relationship: a person plans ahead, assembles resources, and hosts an event for others.

Proposed inference: planning ahead will help the workshop run smoothly.

Possible limit: a workshop may depend on a sequence of activities, equipment, or participant coordination that the picnic comparison does not represent.

The point is not to count resemblances. “Both involve people” adds little unless it connects to the conclusion. The SEP article distinguishes features that correspond between two domains from the within-domain relationship that links those features to an inferred result. Its evaluation discussion emphasizes making that connection explicit and checking whether a critical difference blocks it. In practice, ask: in the familiar case, what makes the outcome follow from the shared features? Is that same connection present in the target?

If you cannot explain the link in a plain sentence—“Because X causes or enables Y in both cases”—the analogy may be relying on a visual resemblance or familiar feeling instead of a relevant relationship. That is a cue to narrow the claim or find another basis for it.

Find disanalogies that could change the inference

A disanalogy is a relevant difference between the source and target. Differences matter when they affect the feature you are trying to transfer. The Internet Encyclopedia of Philosophy’s discussion of analogy uses examples to show why similarities must relate to the feature being inferred: shared details may be numerous yet unhelpful if they do not bear on the conclusion. It also notes that identifying a causal connection can matter when the inference concerns a result such as reliability.

Use a “same except” question: if the target differs in this way, would the conclusion still be reasonable? For the workshop and picnic comparison, weather may affect either event, but that shared vulnerability does not show that their logistics match. A workshop’s timed sequence could make a late equipment delivery more consequential than a late picnic item. If the claim is only “both benefit from preparation,” the difference may not defeat it. If the claim is “a picnic checklist is enough to ensure a smooth workshop,” the difference bears directly on the claim.

Separate three categories in your notes:

Relevant similarities: features connected to the conclusion, such as advance preparation when arguing that a schedule helps keep sessions on time.

Relevant disanalogies: differences that may break that connection, such as the workshop requiring a sequence of activities that the picnic plan does not address.

Unknowns: features you do not know about either case. Unknowns are not proof against the analogy, but they limit how confidently it can carry the argument.

The SEP’s overview lists ignorance about the compared domains, the strength of the conclusion, and the relevance of similarities and differences among considerations that can affect an analogy’s plausibility. It also cautions that these general guidelines can be too vague on their own. So do not turn them into a points system: one critical disanalogy can matter more than several surface similarities.

Stress-test the comparison before readers do

Try three quick checks before you keep an analogy in a persuasive passage.

1. Extend it. Ask what else would follow if the comparison were taken literally or consistently. If a project plan is a map, does that mean an unlisted obstacle cannot exist? If the answer exposes an implication you do not mean, specify which feature of the map you are comparing and which you are not.

2. Swap the cases. Would the same reasoning work if the familiar case were replaced with another that shares the feature you cited but leads to a conclusion you would reject? If so, the shared feature may be too broad to support your point. This is a diagnostic prompt, not a stand-alone refutation.

3. State the missing bridge. Complete the sentence: “The shared relationship supports my conclusion because…” If you need an unstated general rule to make the argument work, state it and ask whether you have reason to accept it. The Oklahoma State University-hosted chapter on inductive reasoning illustrates how pointing out disanalogies can challenge an argument, and how extending a comparison can expose the limits of the feature being transferred.

These checks are editing tools, not formal proof tests. A clever counterexample can show that an analogy is too broad, but it does not automatically show that the writer’s narrower point is false. Revisit the stated conclusion and judge the counterexample against that exact scope.

Repair the analogy or replace it

If the comparison still helps after checking it, revise it to fit what it can reasonably show. Narrow the claim, name the relevant relationship, and add a boundary sentence. For instance: “Like preparing a picnic, planning a workshop involves choosing a date and gathering supplies. The comparison is useful for basic preparation; a workshop may also need a timed agenda and assigned roles.” This version uses the analogy to orient the reader without suggesting that the two events have identical demands.

If the analogy is doing too much work, keep it as a brief illustration and support the conclusion separately with reasons or evidence appropriate to the claim. If the comparison’s central relationship does not transfer, replace it. A concrete description of the target may be clearer than a strained comparison.

Before publishing a draft, read the analogy once without its vivid wording and ask whether the remaining reasoning holds. Then restore the image and check that readers can see both the intended connection and its boundary. The goal is not to make two unlike things identical; it is to help the comparison illuminate one relevant relationship without quietly carrying across features the argument has not earned.

Keep exploring this topic