LSAT
Reasoning Pattern4 min read

How to Spot Weak Analogy on the LSAT

When Weak Analogy appears in your diagnostics, it is pointing at a specific reasoning move in the stimulus or in a flaw answer choice. The reasoning depends on a comparison where the relevant similarity is not established. The goal is not to memorize a label; it is to notice the move before an answer choice makes it feel normal.

What This Reasoning Pattern Means

The reasoning depends on a comparison where the relevant similarity is not established.

In plain English, Weak Analogy means the argument is making a move that needs more support than it has. Sometimes the tag describes the stimulus itself; on flaw questions, it can also describe a wrong answer that misidentifies the flaw. Either way, the value is in seeing the move, not reciting the name.

Example

Here is the pattern in a simplified LSAT-style setup. The topic will change, but the underlying move is the part you want to recognize.

Example

Setup: A reservation system reduced crowding at a small museum.

Flawed move: Therefore, the same system will reduce crowding at a major airport.

Why it matters: That is a Weak Analogy unless the argument shows the museum and airport are similar in the relevant way.

Why It Feels Tempting

The argument depends on a comparison without showing that the compared things match in the relevant way.

LSAT wrong answers are rarely random. They borrow real language from the stimulus, point at a nearby issue, or describe something that would matter in a different version of the question. That is why this pattern can feel reasonable in the moment even when it does not survive a strict check against the task.

How To Spot It

Use these checks before committing to the answer. The point is to make the suspicious move visible while you still have time to compare choices.

  • Find analogies, precedents, or similar cases.
  • Ask which similarity matters for the conclusion.

How To Beat It

Do not treat the label as something to memorize. Treat it as a cue for what to check next.

During review, identify the conclusion, the evidence, and the move that is supposed to connect them. Then say what the argument would need to make that move legitimate. This is the difference between recognizing a flaw label and actually seeing the flaw happen.

  • Do not accept surface similarity as logical similarity.
  • Strengtheners usually add the relevant shared feature; weakeners show a relevant difference.

How To Review It In Your Diagnostics

If this pattern is showing up in your diagnostics, start with a small set of missed questions rather than trying to overhaul your whole approach. Look at the answer you picked, write down the feature that made it tempting, and then compare that feature to the reason the credited answer works.

Over time, the percentage matters less than the reaction it trains: pause, name the move, and force the answer back through the exact question stem.

Quick Check

Are these things similar in the way that matters?