Logical Reasoning Skillset: Detecting Flaws and Matching Argument Structures

Flaw in the Reasoning

A Flaw in the Reasoning question asks you to diagnose what is wrong with an argument’s logic. The stimulus will present an argument that looks persuasive on the surface, but it makes a move that isn’t justified by the premises. Your job is not to “disagree” with the conclusion or bring in outside facts—you’re identifying the logical gap between what was said (premises) and what was claimed (conclusion).

What it is (and what it isn’t)

A flaw is a predictable kind of mismatch: the author treats weak support as strong support, treats correlation as causation, mistakes what’s necessary for what’s sufficient, assumes a representative sample, uses an ambiguous term as if it were precise, and so on. In LSAT terms, the test is checking whether you can abstract the argument into its logical skeleton and spot the unsupported leap.

What it isn’t: it’s not a question about whether the conclusion is true in the real world. You could have a conclusion that happens to be true, but the argument is still flawed because it didn’t prove it. Likewise, you can have an argument with a false conclusion that is logically valid if the premises (hypothetically) guarantee it. Flaw questions live in the space between premises and conclusion.

Why it matters

Flaw detection is central to Logical Reasoning because many other question types are basically “flaw questions in disguise.” For example:

  • Strengthen/Weaken questions often hinge on the same underlying gap.
  • Necessary Assumption questions ask you to find something the argument must assume to avoid a fatal flaw.
  • Parallel Flaw questions explicitly ask you to match the flawed pattern.

If you can quickly articulate what the author did, you get faster and more accurate across the section.

How it works: a reliable process

When you see a flaw question, treat it like a mini-diagnosis.

  1. Find the conclusion first. Use indicator words (“therefore,” “thus,” “so,” “hence”) but don’t rely on them exclusively—sometimes the conclusion is just the most “opinionated” claim.
  2. List the premises as support. Ask: what facts/reasons are offered?
  3. Describe the gap in your own words. A good prephrase is abstract: “They assumed that because X happened with Y, X caused Y.”
  4. Name the flaw category if it helps—but don’t force it. Categorizing can speed you up, but the LSAT rewards accurate description, not fancy labels.
  5. Match the answer choice to your description. Correct answers typically restate the flaw in general terms. Wrong answers often:
    • attack a premise that was never assumed,
    • bring in something outside the argument,
    • sound “critical” but don’t match the exact logical mistake.

Common flaw families (the ones that show up constantly)

Below are recurring flaw patterns, phrased the way the LSAT tends to test them.

1) Causation errors

The argument treats correlation or sequence as causation, ignores alternative causes, reverses cause and effect, or assumes a cause will produce an effect in all contexts.

Typical gap: “X happened after Y, so Y caused X.” / “X and Y vary together, so X causes Y.”

2) Sampling and representation

The argument draws a broad conclusion about a population from an unrepresentative sample, too small a sample, or a biased survey.

Typical gap: “This group I observed is like everyone.”

3) Necessary vs. sufficient (conditional reasoning mistakes)

The argument treats something that is required as though it guarantees the outcome, or treats something that guarantees the outcome as though it’s required.

Typical gap: “A is necessary for B, so A is enough for B.” (Or vice versa.)

4) Equivocation (shifting meanings)

A key word changes meaning mid-argument—often subtly (e.g., “theory” in the scientific vs. casual sense; “free” as in freedom vs. no cost).

Typical gap: “Because the word is the same, the idea is the same.”

5) Part–whole and whole–part errors

The author assumes what’s true of a part is true of the whole, or what’s true of the whole must be true of each part.

Typical gap: “Each component is good, so the system is good.” / “The system is good, so each component is good.”

6) Comparison and analogy problems

The argument relies on a comparison but doesn’t establish that the two things are similar in the relevant way.

Typical gap: “A and B share some features, so they will share the feature I care about.”

7) “Only two options” (false dilemma)

The author treats two choices as exhaustive when there are more.

Typical gap: “Either A or B. Not A, so B.” (But C exists.)

Worked example (Flaw)

Stimulus:

The city installed new streetlights last year. Since then, nighttime car accidents have decreased. Therefore, the new streetlights caused the decrease in nighttime accidents.

Step 1: Conclusion: The streetlights caused the decrease.

Step 2: Premise: Accidents decreased after installation.

Step 3: Gap: The author assumes that because the decrease followed the installation, the installation caused it—ignoring other possible causes (e.g., better enforcement, weather changes, fewer drivers).

Correct flaw description (what an answer choice would say):

  • It assumes that because one event followed another, the first event caused the second.
  • It fails to consider alternative explanations.

Common trap answers:

  • “It assumes streetlights are always effective” (too strong; the argument doesn’t claim “always”).
  • “It ignores the possibility that streetlights have negative effects” (irrelevant to the claim about accidents decreasing).
Exam Focus
  • Typical question patterns:
    • “The argument’s reasoning is most vulnerable to criticism on the grounds that…”
    • “The reasoning is flawed because the argument…”
    • “Which of the following most accurately describes the flaw…?”
  • Common mistakes:
    • Treating the task as fact-checking (“But accidents could have decreased anyway!”) rather than identifying the logical leap.
    • Picking an answer that criticizes something true about the world but not something the argument did.
    • Missing the conclusion and therefore misidentifying what needs to be supported.

Parallel Reasoning

Parallel Reasoning questions ask you to find an answer choice whose argument has the same logical structure as the stimulus argument. The topic can change completely—what matters is the pattern of support.

What it is

A parallel reasoning match is like matching a blueprint, not matching the paint color. Two arguments are parallel when their reasoning follows the same form, such as:

  • “All A are B. C is an A. Therefore C is a B.”
  • “Most A are B. D is a B. Therefore D is an A.” (note: this is a different form and is typically flawed)
  • “If A then B. Not B. Therefore not A.”

The LSAT often hides the structure in everyday language, so the skill is translating prose into a clean skeleton.

Why it matters

Parallel reasoning tests whether you can:

  • Separate content (what the argument is about) from form (how it reasons).
  • Track quantifiers (all/most/some/none), negations, and conditional logic.
  • Notice when an argument is valid vs. invalid—because if the stimulus is invalid, the correct parallel will repeat that same invalid move.

This matters beyond this question type because it strengthens your general ability to “see” arguments quickly.

How it works: matching the skeleton

A practical method:

  1. Identify conclusion and premises in the stimulus.
  2. Abstract the structure by replacing key terms with placeholders (A, B, C) or short labels.
  3. Note key logical features:
    • Is it conditional (“if,” “only if,” “unless”)?
    • Is it quantified (“all,” “most,” “some”)?
    • Does it use a comparison, analogy, or elimination of alternatives?
    • Does it rely on a necessary/sufficient confusion?
  4. Scan answer choices for the same pattern, not the same subject matter.

A helpful analogy: think of the stimulus as a song’s chord progression. The parallel answer is a different song that uses the same progression, even if the melody (topic) differs.

What to pay special attention to

Parallel reasoning questions punish “close enough.” Common near-misses differ in one crucial way.

Quantifiers: all vs. most vs. some
  • All means every member.
  • Most means more than half (not all).
  • Some means at least one.

If the stimulus says “most,” an answer choice that says “all” usually isn’t parallel, even if it feels similar.

Conditional direction and contraposition

Conditional claims are directional. “If A then B” is not the same as “If B then A.” Also, an argument that uses the contrapositive (If A then B; not B; therefore not A) is structurally different from an argument that affirms the consequent (If A then B; B; therefore A).

Negations

Words like “not,” “never,” “no,” “none,” “cannot,” and “fails to” are structural. Missing a negation can flip the entire form.

Worked example (Parallel Reasoning)

Stimulus:

All certified divers have completed a safety course. Lina is a certified diver. Therefore, Lina has completed a safety course.

Step 1: Structure

  • Premise 1: All A are B.
  • Premise 2: C is A.
  • Conclusion: Therefore, C is B.

Step 2: Match to an answer
The correct choice must follow the same “universal rule + instance” pattern.

Correct parallel (one possible answer choice):

All registered voters are eligible to vote in the election. Marco is a registered voter. Therefore, Marco is eligible to vote in the election.

Why it matches: same quantifier (“all”), same movement from category membership to attribute.

Tempting wrong answer (why it’s wrong):

All registered voters are eligible to vote. Marco is eligible to vote. Therefore, Marco is a registered voter.

That reverses the reasoning (it’s the classic “affirming the consequent” form).

Exam Focus
  • Typical question patterns:
    • “Which one of the following arguments is most similar in its reasoning to the argument above?”
    • “Which of the following exhibits a pattern of reasoning most similar…?”
    • “The reasoning in which of the following is most parallel…?”
  • Common mistakes:
    • Matching on topic similarity (“this one is also about rules”) instead of logical form.
    • Ignoring quantifier shifts (most vs. all) or missing a negation.
    • Forgetting that a flawed stimulus requires a flawed parallel, not a “fixed” version.

Parallel Flaw

A Parallel Flaw question is a hybrid: you must (1) identify the flaw in the stimulus and then (2) select the answer choice that makes an analogous flawed move.

What it is

The stimulus argument is flawed in some specific way—often a classic pattern like causation, necessary/sufficient confusion, or an illegitimate generalization. The correct answer choice will contain a different topic but will commit the same type of mistake in the same structural way.

This is harder than plain flaw questions because you have to do two tasks: diagnose and then match.

Why it matters

Parallel flaw questions train a very LSAT-specific kind of abstraction: recognizing that many flawed arguments are essentially the same “machine” producing bad conclusions from certain premise patterns. Once you can name or describe the machine, you can spot it anywhere.

How it works: a two-pass strategy

  1. Diagnose the flaw clearly. Don’t just say “it’s flawed.” Say what it did.
  2. Abstract the move. Use placeholders.
  3. Pre-eliminate answer choices that don’t share key features. For example:
    • If the stimulus is causal, eliminate choices that aren’t causal.
    • If the stimulus uses a survey/sample, eliminate choices that don’t.
    • If the stimulus confuses necessary and sufficient, look for the same confusion.
  4. Confirm the match by aligning parts. A truly parallel flaw will line up premise-to-premise and conclusion-to-conclusion.

Seeing the “flaw blueprint”

It helps to think in templates. Here are a few common parallel-flaw templates:

Flaw templateSkeletonWhat to look for in answers
Correlation/sequence → causationX happened after/with Y, so Y caused XAnother argument inferring causation from timing/correlation
Necessary vs. sufficient confusionA is required for B; A; therefore BTreating a requirement as a guarantee (or vice versa)
Unrepresentative sampleIn group S, many have trait T; therefore population P has TGeneralizing from a narrow or biased group
Equivocation“Term” means one thing in premise, another in conclusionSame word/phrase used with different meanings

Worked example (Parallel Flaw: necessary vs. sufficient)

Stimulus:

To be eligible for the scholarship, applicants must submit two recommendation letters. Priya submitted two recommendation letters, so she must be eligible for the scholarship.

Diagnose the flaw: Submitting two letters is necessary for eligibility, but not sufficient—there may be other requirements (GPA, essay, deadline, etc.). The argument treats a requirement as though it guarantees eligibility.

Abstract skeleton:

  • Premise: If eligible, then submitted-two-letters. (Eligibility → Letters)
  • Premise: Letters.
  • Conclusion: Therefore eligible.

That is the form “If A then B; B; therefore A” (affirming the consequent) dressed up in requirements language.

Correct parallel-flaw answer (one possible):

To enter the secured area, employees must have an ID badge. Carlos has an ID badge, so Carlos must be authorized to enter the secured area.

Why it matches: Having a badge may be required, but it doesn’t guarantee authorization (badge could be expired, stolen, etc.). Same structural mistake.

Common trap: an answer that reverses which condition is necessary.

  • If an answer says “Only authorized employees have badges; Carlos is authorized; therefore Carlos has a badge,” that’s a different structure.
Exam Focus
  • Typical question patterns:
    • “Which of the following is most similar to the flawed reasoning…?”
    • “Which argument contains flawed reasoning most similar…?”
    • “The pattern of flawed reasoning in the argument above is most closely parallel to…”
  • Common mistakes:
    • Picking an answer with the same topic of the flaw (e.g., also about scholarships) rather than the same structure.
    • Matching a “causal-ish” answer to a causal stimulus even though the specific causal error differs (alternative cause vs. reverse causation).
    • Forgetting to align premises and conclusion roles; two arguments can share vocabulary like “must” yet differ logically.

Method of Reasoning

A Method of Reasoning question asks you to describe what the argument does—the author’s reasoning technique and how the pieces function—rather than whether the reasoning is good or bad.

What it is

Instead of saying “this is flawed because…,” method questions ask for a higher-level description such as:

  • “The argument draws a conclusion by applying a general rule to a specific case.”
  • “The argument supports a claim by ruling out alternative explanations.”
  • “The argument responds to an objection and then reasserts the conclusion.”

Many correct answers read like a neutral play-by-play of the argument’s moves.

Why it matters

Method questions force you to understand argument structure precisely:

  • You must recognize roles: which sentence is a premise, which is a conclusion, which is a subsidiary conclusion, which is background.
  • You must track dialectical moves: concession (“although”), counterargument (“some say”), rebuttal (“however”), and intermediate steps.

This is a deep comprehension skill that improves performance on almost every LR question type.

How it works: translating the argument into “moves”

A useful approach is to narrate the argument in simple verbs:

  1. Identify the main conclusion. What is the author trying to prove?
  2. Identify the support. How do the premises relate to the conclusion?
  3. Notice any intermediate conclusion. Sometimes a premise is supported by another premise (“Therefore X. Since X, therefore Y.”).
  4. Look for special moves, such as:
    • Analogy: argues from similarity.
    • Principle application: applies a general principle to a case.
    • Elimination: rules out options to leave one.
    • Causal inference: infers cause.
    • Explaining away: addresses an alternative explanation.
    • Use of evidence: cites a study, statistic, or testimony.
  5. Match the answer choice at the same level of abstraction. The correct answer is usually neither too specific (repeating details) nor too vague (“it gives reasons”).

Common method descriptions the LSAT likes

The following are not “magic phrases,” but they are the kinds of descriptions you’ll see.

  • Applying a general rule to a particular case (classic: “All A are B; C is A; so C is B”).
  • Generalizing from particular cases (often risky if sample issues exist).
  • Arguing by analogy (comparing two situations).
  • Establishing a claim by eliminating alternatives (sometimes explicit “either/or”).
  • Offering evidence that a claim is the best explanation (competing hypotheses).
  • Responding to an objection (acknowledge then rebut).

Worked example (Method of Reasoning)

Stimulus:

Some people claim that the museum should extend its hours because attendance is low. But low attendance is largely due to the exhibit renovation, which limits access to several galleries. Therefore, extending the museum’s hours would not significantly increase attendance.

Step 1: Main conclusion: Extending hours would not significantly increase attendance.

Step 2: Support: Attendance is low due to renovations limiting access.

Step 3: Method description: The argument responds to a proposal (extend hours) that is supported by a stated reason (low attendance), and rejects it by providing an alternative explanation for the low attendance (renovations), implying the proposal wouldn’t address the real cause.

What a correct answer might say:

  • The argument challenges a recommendation by arguing that the problem cited in support of that recommendation has a different cause, so the recommendation would not solve it.

Trap answers (why they’re wrong):

  • “It attacks the character of those who support extending hours” (no ad hominem occurs).
  • “It shows the recommendation is self-contradictory” (no contradiction is identified).
  • “It applies a general principle to a specific case” (no broad rule is invoked).

Method vs. Flaw: how to keep them separate

A common confusion is to treat method questions as if they’re asking “what’s wrong.” But method questions can describe valid or invalid reasoning—your job is just to describe the strategy.

A quick internal check: if an answer choice contains strong evaluative language like “unjustifiably,” “fails to,” “takes for granted,” it’s often a flaw/assumption-style description. Method answers are more often neutral verbs like “supports,” “infers,” “cites,” “responds,” “draws an analogy.” (There are exceptions, but this heuristic helps.)

Exam Focus
  • Typical question patterns:
    • “The argument proceeds by…”
    • “Which of the following most accurately describes the method of reasoning…?”
    • “The reasoning in the argument is that…”
  • Common mistakes:
    • Choosing an answer that accurately describes something true about the topic but not the argument’s logical role relationships.
    • Missing an intermediate conclusion and therefore picking an answer that misstates what supports what.
    • Over-focusing on whether the reasoning is good/bad instead of describing the moves.