Data Sufficiency: Stop Combining the Statements Too EARLY

Here's a scene I watch play out every single week. A Test Taker reads a Data Sufficiency question, glances at statement (1), glances at statement (2), sees two clues sitting there like a matched pair, and clicks C. Done in 40 seconds. Feels great. Then the review screen says the answer was A, and they stare at it like the test cheated them.

It didn't. They cheated themselves. They combined the statements before they ever squeezed either one on its own.

First, what Data Sufficiency actually asks

Data Sufficiency (DS for short) is one of the two question types in the Quant section, next to Problem Solving. On the GMAT right now, Quant gives you 31 questions in 62 minutes, with both types mixed together. A DS question gives you a question and two statements. Your job is NOT to answer the question. Your job is to decide whether the facts are ENOUGH to answer it. "Sufficient" just means enough to get one answer, and only one.

The five answer choices never change:

• A: Statement (1) ALONE is sufficient, but statement (2) alone is not.
• B: Statement (2) ALONE is sufficient, but statement (1) alone is not.
• C: BOTH statements TOGETHER are sufficient, but NEITHER alone is.
• D: EACH statement ALONE is sufficient.
• E: The statements TOGETHER are still NOT sufficient.

Look hard at C. It says neither statement works by itself. That's a big claim. To pick C honestly, you have to PROVE that (1) fails and PROVE that (2) fails. Most people who pick C have proven nothing. They just felt safe.

Why C feels safe (and why it isn't)

Using both statements feels careful. More info, more safety, right? That's school thinking. In school, the teacher hands you exactly the facts you need and nothing extra. The people who write the GMAT know you think that way. So they build questions where one statement does all the work, then add a second statement that looks like it "finishes the job." It's bait.

Stop reading for a second and think about this: if statement (1) alone is enough, what happens when you add statement (2)? It's STILL enough. Combining never breaks a question that already works. That's exactly why it fools you. The combined version works, C looks right, and you never notice that half of what you used was dead weight.

How to squeeze each statement dry

Here's the routine. It's mechanical on purpose. Mechanical beats clever when the clock is running.

1. Write the question and every rule in it. Integer? Positive? Different numbers? Those little words do a LOT of work, and they apply to both statements.
2. Write AD / BCE at the top of your notes. If (1) works, the answer is A or D. If it doesn't, it's B, C or E. You're cutting choices as you go.
3. Cover statement (2). Literally. Put your hand on the screen if you have to. Work (1) as if (2) doesn't exist.
4. Try to BREAK the statement. Test values and hunt for two different answers. If you can't find two, and the rules box you into one, it's sufficient.
5. Wipe (1) from your brain and do (2) the same way.
6. Only now, if both failed, combine.

5 mistakes that send you to C too early

1. Reading both statements before working either one. Once you've seen (2), it leaks into how you think about (1). You "just know" things you were never told.

   INSTEAD: Cover (2) while you work (1). Physically. Every time, in practice, until it's habit.

2. Skipping the rules in the question. "Integer" and "positive" turn a hopeless statement into a sufficient one. Ignore them and every statement looks weak.

   INSTEAD: Write every rule on your pad before you touch the statements.

3. Counting equations instead of reading the question. "Two unknowns, need two equations" is a school rule, not a GMAT rule. The question might want a combo, a yes or no, or an answer the rules force.

   INSTEAD: Write the exact target. Then ask, "Can THIS statement get me to THAT?"

4. Testing one value and calling it a day. One value proves nothing. It just tells you one answer is possible.

   INSTEAD: Try to break the statement. Hunt for a second answer. If the rules won't let you find one, that's your proof.

5. Working it all in your head. I'll bet your worst DS misses happened when your pad was nearly blank. In-your-head work is exactly where the integer rule gets forgotten and the second value never gets tried.

   INSTEAD: Small notes. AD / BCE at the top. A quick table for values. Ten seconds of writing beats a wrong click.

This isn't just a DS thing. It's the same lazy reflex that makes people grab a formula on combinations before asking whether order matters, or freeze on slope when it's just rise over run. The fix is always the same: slow down for the first ten seconds, write down what you actually have, and make the question prove itself.

What you WANT more

You have to decide what you want MORE: the comfy feeling of clicking C, or the points. Because C isn't the cautious answer. It's an answer that makes TWO claims, and you're responsible for both of them. Pick it when you've earned it, not when you're scared.

Here's your job for today. Pull up every DS question you've answered C on in the last two weeks, right or wrong. Redo each one with statement (2) covered, then with (1) covered, notes on paper, AD / BCE at the top. If you're short on questions, grab some from GMAC's official practice materials. Count how many of your "safe" Cs were really A, B or D. I'll bet the number is BIGGER than you'd like. Good. Now you know exactly what to train.