Every LR Question Is a Weaken Question

Every LR Question Is a Weaken Question

I know what you're thinking. There are fourteen question types in LSAT Logical Reasoning. Weaken is just one of them. How can every question be a Weaken question?

Stay with me. Because once you see this, you can't unsee it — and it changes how you approach the entire section.

---

The Weaken Foundation

Let's start with what happens on a Weaken question, because this is the engine that powers everything else.

You read the argument. You simplify it — casual language, like you're explaining it to a friend at a bar. You find the conclusion and the premises. Then you say to yourself, with as much suspicion as you can summon:

"Just because [premise] doesn't mean [conclusion]. Maybe..."

That's JBDM — "Just Because Doesn't Mean." And the moment you say it, you start generating maybes. Alternative explanations. Reasons the conclusion doesn't follow from the premise.

Take a classic: The chocolate ice cream is gone from the freezer, therefore Jennifer ate it. "Just because the ice cream is gone doesn't mean Jennifer ate it. Maybe someone threw it out. Maybe someone fed it to the raccoons." You start silly, you let the snowball roll, and suddenly you're generating real predictions: "Maybe someone else in the house ate it. Maybe Jennifer is lactose intolerant."

On a Weaken question, you take those predictions straight to the answer choices. One of your maybes — or something in the neighborhood of one of your maybes — is the correct answer.

Simple enough. But here's the twist: that same process is the starting point for nearly every other question type. What changes isn't the thinking. It's what you do with the thinking after.

---

Flaw: Weaken + Name It

On a Flaw question, your brain does the exact same work as on a Weaken question. JBDM. Snowball. Generate maybes. Build umbrellas. The argument is bad for the exact same reasons it's bad on a Weaken question.

The twist? Instead of finding an answer choice that is a weakener, you find one that describes the weakness.

Think of it like this: on a Weaken question, you punch the argument. On a Flaw question, you describe where you'd punch.

He's wearing a blue shirt, therefore blue must be his favorite color. Your maybes are identical to a Weaken question — maybe it was a gift, maybe it was the first shirt he grabbed, maybe his employer requires it. But the correct answer on a Flaw question doesn't say "the shirt was a gift." It says something like: "The argument fails to consider that wearing a particular color does not establish it as a preference."

Same gap. Same thinking. Different packaging.

If you can weaken an argument, you can name the flaw. It's the same skill with a rephrasing layer on top.

---

Strengthen: Weaken + Reverse It

Here's one that surprises students: the fastest route to strengthening an argument is to weaken it first.

I'm serious. Start by finding the gap — JBDM, snowball, generate your maybes, the whole process. Identify all the reasons the conclusion doesn't follow. Then reverse those weakeners to the extreme.

I'm about to drive without my glasses, therefore I'm going to crash.

Weaken it first: Maybe I'm wearing contacts. Maybe it's a wide, empty street. Maybe it's a self-driving car.

Now flip each weakener into a strengthener: I'm definitely not wearing contacts. The street is narrow and packed with cars. The car has no autopilot. Suddenly the argument that driving without glasses leads to a crash is much stronger.

There are two flavors of strengthening — direct (adding evidence that supports the conclusion) and alternative (eliminating competing explanations). But both start from the same place: first you see the gap, then you close it. You can't close a gap you haven't identified, and identifying the gap is exactly what weakening teaches you to do.

The Weaken process gives you the map. Strengthening is just walking the map in the opposite direction.

---

Necessary Assumption: Weaken + Negate It

Necessary Assumption questions ask: What must the author be assuming for this argument to work at all?

That sounds completely different from weakening. But watch what happens when you approach it through the Weaken lens.

Take the driving example again: I'm driving without my glasses, therefore I'm going to crash.

Weaken it: Maybe I'm wearing contacts. Maybe my glasses are only for reading. Maybe the car drives itself.

Now here's the elegant twist: negate each weakener, and you get a necessary assumption.

If "maybe I'm wearing contacts" weakens the argument, then the author must be assuming I'm not wearing contacts. If "maybe it's a self-driving car" weakens it, the author must be assuming it's not a self-driving car.

Think about it — if the author genuinely believed any of your major weakeners were true, they never would have made the argument in the first place. So every weakener you generate is, when negated, something the author must be taking for granted.

Weaken first. Negate second. You've found the necessary assumption.

This is why students who master weakening find assumption questions surprisingly natural. The skill isn't different — it's the same skill viewed from the other side of the glass.

---

Evaluate: Weaken + Test Both Directions

Evaluate questions are the rarest "Do" type, and they throw students off because the answer choices are phrased as questions, not statements. But they're secretly one of the most straightforward question types once you see the Weaken connection.

Start the same way: JBDM, snowball, generate maybes, build umbrellas. You now have a sense of the argument's vulnerabilities.

Then apply the Yes-No Test to each answer choice. The correct answer, when answered one way, strengthens the argument — and when answered the other way, weakens it. Both directions must matter.

But here's what makes this a Weaken question in disguise: you need to understand the gap first. You need to know what would weaken the argument and what would strengthen it. And you already know how to find both of those things — because strengthening is just reversed weakening.

The Weaken process gives you the foundation. The Yes-No Test is just checking both sides of it.

---

Paradox: Weaken + "Therefore This Is Weird"

Paradox questions look nothing like Weaken questions on the surface. There's no argument to attack — just an info set with two facts that seem incompatible. Sophie hates purple. Sophie is wearing a purple shirt. You're asked to explain it.

But here's a trick that converts any paradox into a weaken-style problem: append "therefore this is weird" to the stimulus.

Sophie hates purple and she's wearing a purple shirt, therefore this is weird.

Now you have an argument. And you can JBDM it: "Just because Sophie hates purple and is wearing a purple shirt doesn't mean it's weird. Maybe her college colors are purple and she's showing school pride. Maybe her employer requires it. Maybe it was a gift from her grandma and she doesn't want to hurt her feelings."

Each of those maybes doesn't just weaken the "weirdness" — it resolves the paradox. By weakening the claim that the situation is strange, you're explaining why it actually makes perfect sense. The two processes produce the exact same answers.

You can also think of it from the other direction: generate maybes using "What's Strange?" and snowballing directly. Either way, the underlying muscle — seeing the gap and generating alternatives — is the Weaken muscle.

---

The Pattern

Let's step back and see the full picture:

Six question types. One foundational process. The only thing that changes is what you do with your predictions after you've generated them.

---

What About the Other Eight Types?

Fair question. Conclusion, Role, Method, Inference, Principle, Parallel, Agree/Disagree, and Sufficient Assumption operate somewhat differently — some don't even involve arguments. But the Weaken mentality still shows up in subtle ways.

Sufficient Assumption shares DNA with Necessary Assumption. While NA asks what the author must assume (soft, defensive), SA asks what would make the argument airtight (strong, constructive). Both require you to identify the gap between premises and conclusion — the same gap-finding skill that Weaken develops.

Inference and Principle questions use info sets rather than arguments, so there's no argument to weaken. But the critical thinking muscle — refusing to let facts carry more weight than they deserve, checking whether a claim actually follows from the evidence — is the "just because doesn't mean" instinct applied to answer choices. When an inference answer tries to stretch "some" into "most," your Weaken-trained brain catches it: "Just because Dan likes six types of candy doesn't mean he likes most candy."

The Weaken process isn't a trick for six question types. It's a way of thinking that makes you better at all fourteen.

---

Why This Changes Your Study Strategy

Here's the practical payoff.

If every question type is a Weaken question with a twist, then mastering Weaken is the single highest-leverage skill in Logical Reasoning. Every hour you spend getting better at JBDM, snowballing, and generating predictions doesn't just improve your Weaken performance. It directly improves your Flaw, Strengthen, NA, Evaluate, and Paradox performance too.

This is why our curriculum teaches Weaken first — and teaches it deeply, across eleven lessons — before introducing any other question type. When students arrive at Flaw questions, they don't learn a new approach from scratch. They learn a twist on something they already know. When they hit Strengthen, same thing. Necessary Assumption? Same thing.

Instead of fourteen separate strategies fighting for space in your head, you have one core process and a handful of small adjustments. Less to memorize. More to understand. And understanding beats memorization on the LSAT every single time.

---

The Electrician Analogy

I like to think of it like being an electrician. Someone calls you to fix their fan. What's the first thing you do? You figure out what's wrong with it. You diagnose the problem before you attempt a repair.

That diagnosis — finding what's wrong with the argument, identifying the gap — is weakening. Every other question type is a different kind of repair, but they all require the same diagnosis first:

• Weaken: Point out what's wrong (diagnosis IS the answer)
• Flaw: Describe what's wrong in technical language
• Strengthen: Fix what's wrong
• Necessary Assumption: Identify what must be true for nothing to be wrong
• Evaluate: Determine what information would tell you whether something is wrong
• Paradox: Explain why nothing is actually wrong

Same diagnosis. Different next step.

---

One Last Thing

If this reframes how you think about LR, good. But don't let it stay abstract. The next time you sit down with a practice section, try this: on every single question — Flaw, Strengthen, NA, Evaluate, Paradox — start by weakening the argument first. JBDM it. Snowball your maybes. Build your umbrellas. Then apply the twist for whatever question type you're looking at.

You'll be shocked at how much smoother the section feels when you're running one process instead of six. The twists become almost automatic. And the question types that used to feel like completely different animals start looking like variations on a theme — because that's exactly what they are.

Every LR question is a Weaken question. The only question is: what's the twist?