Study guide

Method of Reasoning Questions

LSAT Logical Reasoning Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Current LSAT Logical Reasoning Format and Section Strategy

Current LSAT Format LR Section Timing And Volume Argument Core: Premise, Conclusion, Gap Question Stem Triage Wrong Answer Patterns

2 Argument Foundations for Logical Reasoning

Conclusion, Premise, and Background Assumptions and Gaps Conditional Logic and Contrapositives Quantifiers, Causation, and Analogy Translating Dense Stimuli

3 Core Logical Reasoning Question Types

Necessary Assumption Questions Sufficient Assumption Questions Flaw Questions Strengthen Questions Weaken Questions Evaluate Questions

4 Inference, Method, Role, and Conclusion Questions

Must-Be-True Questions Most Strongly Supported Questions Method of Reasoning Questions Role of Statement Questions Main Conclusion Questions Point at Issue Questions

5 Formal Logic, Principle, and Parallel Reasoning

Parallel Reasoning Parallel Flaw Principle Identify Principle Apply Except and Cannot-Be-True Comparative Two-Speaker Stimuli

6 Pacing, Review, and Final Logical Reasoning Drills

Pacing, Skip-Return, and Flagging Blind Review and Error Log Method Mixed-Section Stamina and Score Stability Final-Week Review Plan Test-Day LR Execution

Method of Reasoning Questions

Key Takeaways Explain This Topic AI

Method questions ask how the argument proceeds as a whole, not whether the reasoning is good.

The credited answer should neutrally describe the main argumentative move using the same logical force as the stimulus.

Common methods include applying a rule, drawing an analogy, offering a counterexample, eliminating alternatives, and responding to an objection.

Do not choose a flaw description unless the stem specifically asks for a flaw or the method is explicitly a flawed move.

Last updated: June 2026

Describe The Move

A Method of Reasoning question asks how the argument proceeds. The answer is a structural description, not a verdict. You are not primarily deciding whether the argument is persuasive. You are identifying the author's main move from support to conclusion.

This aligns with LSAC's stated LR skills, including recognizing parts of arguments, reasoning by analogy, recognizing reasoning patterns, and determining how evidence affects an argument. Method questions test whether you can see the architecture without being distracted by subject matter.

Stem Signals

  • Stem language Task
  • proceeds by describe the reasoning path
  • method of argument identify the main argumentative move
  • reasoning in the argument name the structure, not the topic
  • technique used describe how the author supports the claim

Read the stimulus for role and sequence. What claim is the destination? What evidence, principle, example, comparison, or objection gets the author there?

Neutral, Not Evaluative

Many wrong answers are too judgmental. If the author applies a general rule to a specific case, the method may be rule application even if the rule itself is questionable. A flaw answer saying the author fails to consider exceptions may be tempting, but it does not describe the main method unless the stem asks for vulnerability.

Neutral does not mean vague. The answer should still be exact. Describing an argument as citing evidence is often too broad. Better answers specify whether the author uses a counterexample, analogy, statistical comparison, conditional rule, expert report, causal mechanism, or elimination of alternatives.

High-Frequency Methods

  • Method What it looks like Watch for
  • Applies principle general rule plus specific case rule direction
  • Draws analogy case A supports claim about case B relevant similarity
  • Gives counterexample one case disproves a general claim universal target
  • Eliminates alternatives rejects rival explanations whether all needed alternatives are addressed
  • Cites mechanism explains how cause could produce effect mechanism versus evidence
  • Responds to objection grants or denies a criticism concession structure
  • Uses conditional chain if-then links reach conclusion valid direction

Your answer should match the dominant move. Some arguments include several pieces, but the credited answer usually captures the central support pattern.

Method Versus Flaw

Flaw asks what is wrong. Method asks what is done. The same stimulus can support both kinds of questions, but the answer style changes.

If an argument says a tutoring program caused score gains because scores rose after the program began, a flaw answer may say it infers causation from temporal sequence. A method answer may say it uses a before-after comparison to support a causal conclusion. The first criticizes; the second describes.

Do not smuggle criticism into a method answer unless the answer remains structurally accurate. An answer can say the author dismisses an objection by labeling it irrelevant if that is what happened. But a choice saying the author unfairly dismisses the objection adds a judgment that may exceed the task.

Method Versus Role

Method is whole-argument. Role is local statement function. If the stem asks about the argument's method, zoom out. If it asks about a specific claim or phrase, zoom in.

For method, compress the stimulus into a verb phrase: applies a rule, rejects an analogy, cites a counterexample, infers a cause, distinguishes a case, explains a discrepancy, or derives a conditional consequence. Then match answer choices to that phrase.

Work From The Conclusion Backward

A reliable process is to find the conclusion first. Then ask what kind of support reaches it. If the conclusion is a recommendation and the support is a moral rule, the method may be applying a normative principle. If the conclusion rejects a general claim because one instance violates it, the method is counterexample.

If two speakers appear, identify whether the second speaker attacks a premise, offers an alternative explanation, challenges relevance, or accepts part of the first view while rejecting the conclusion.

Answer-Choice Filters

Does the answer describe the whole argument rather than one detail?

Does it preserve whether the author argues for, against, or conditionally?

Does it match the type of support actually used?

Does it avoid adding motives or evidence not present?

Does it use the right force, such as proves, suggests, questions, or illustrates?

The force filter is important. If the author says evidence suggests a policy may help, an answer saying the author proves the policy will solve the problem may be too strong.

Efficient Review

After a missed method question, write the argument in one sentence beginning The author... For example: The author concedes a cost objection, then argues that a separate legal requirement makes the objection irrelevant. This habit trains structural reading.

If an answer describes only tone or subject matter, treat it as incomplete unless it also captures the reasoning move.

Then compare your sentence to the credited answer. If your sentence is right but you missed the answer, the problem is answer translation. If your sentence is wrong, the problem is stimulus mapping.

On current LR, method questions can be fast because they often require no gap attack. The payoff comes from staying disciplined: describe the move, preserve scope, avoid judging unless asked, and ignore subject matter that does not affect structure.