ESTIMATE. The Test WANTS You To.

It's 9:40 on a Tuesday night. You worked a full day. Now you have a Quant drill open, and you are multiplying 38 by 212 by hand on scrap paper. Carry the one. Check it. Then 41 by 198. Carry. Check. Add. Four minutes later you have the exact answer, and you feel good about it.
Here's the problem. The answer choices were about 4,000 apart. You could have had it in 30 seconds.
I watch people do this every week. Smart people. People who run budgets and lead teams. They sit down to the Executive Assessment and suddenly act like it's a high school math final, where every digit must be perfect and showing your work earns partial credit. There is no partial credit. Nobody grades your work. There is only the answer you click and the clock you burned getting there.
The clock is the whole story
The Quantitative Reasoning section gives you 14 questions in 30 minutes. That's a little over 2 minutes per question on average, and some of those questions are wordy. Two question types show up. Problem Solving is a regular math question with five answer choices. Data Sufficiency asks whether the facts you're given are ENOUGH to answer a question, which means you often don't need the final number at all. Quant is scored 0 to 20 and counts exactly as much as Verbal and Integrated Reasoning, per GMAC's official breakdown of the sections and scoring.
So every minute you spend on long multiplication you didn't need is a minute stolen from a question you could have gotten right. Your 'pacing problem' isn't the clock. It's the long route.
And here's the part most people miss. When the answer choices are miles apart, the test is TELLING you something. The people who write these questions pick those choices on purpose. Wide spacing means you don't need precision. Tight spacing means you do. Read the choices like a message, because they are one.
Stop for a second. Which way would you have solved that if you hadn't been told to estimate? Be honest. If you'd have reached for exact multiplication, that's the habit we're breaking today.
The three-second check
Before you touch any math on a Problem Solving question, glance at the choices and ask one question: how far apart are they compared to their size?
- If each choice is way bigger than the one before it (like 60, 115, 175, 365, 570), round HARD. Easy numbers, fast answer.
- If the choices are close together (like 16,100, 16,174, 16,250), estimation will betray you. Do the real math, carefully, on paper.
- If the question literally says "approximately," that's the test waving a flag at you. Take the hint.
This takes three seconds. It saves minutes. It also pairs well with the other shortcuts you should already own, like testing the answers and picking numbers. None of these are tricks for people who can't do math. They're what strategic people do when the clock matters.

5 ways people wreck a good estimate
Doing math before reading the choices. You can't know whether to round until you've seen how far apart the choices are.
INSTEAD: Read the question, then the choices, THEN decide. Every time, until it's automatic.
Rounding everything the same direction. Push every number up and your estimate drifts high. Do it on a multi-step question and you can drift right into the wrong choice.
INSTEAD: Balance it. When you multiply, round one number up and the other down, like we did with 38 and 212.
Estimating in your head. "It's just rounding, I don't need to write it." That's pride talking, and pride is how you lose April's billing.
INSTEAD: Write the rounded numbers and each step on paper. It takes five seconds and kills the silly mistakes.
Estimating when the choices are tight. Rounding is a tool, not a religion. Use it on close choices and you'll be confidently wrong.
INSTEAD: If neighboring choices are close, slow down and do the exact math. Knowing WHEN not to estimate is half the skill.
Stopping one step early. Test writers love putting the halfway number in the choices. It feels right because you just calculated it.
INSTEAD: Before you click, reread what the question actually asks for. Remote employees, or remote SALES employees? One month, or two?

"But I'm not a numbers person"
Good news: estimation is easier than exact math, not harder. You're working with 40s and 200s and halves instead of 38s and 212s and 48%. If you're rusty at math, this is one of the best skills to train first, because it turns ugly numbers into friendly ones.
And if you ARE a numbers person? Then this is for you most of all. Strong math people are often the ones grinding out exact answers out of habit, because they can. Being able to isn't the point. What do you want MORE: the satisfaction of a perfect calculation, or the extra two minutes for the next question?
The Executive Assessment isn't really a math test. It's a thinking test that uses math to measure you. One of the things it's measuring is whether you can tell when precision matters and when it doesn't. You make that call at work every day. Make it here too.
Your assignment for today
Pull 10 Problem Solving questions you've already done. Before you do any math, look only at the answer choices and mark each question ROUND or EXACT. Then redo the ROUND ones using estimates written on paper, and time each one.
I'll bet at least a few of them drop well under a minute. When they do, ask yourself how many minutes you've been leaving on the table. Then go take them back.


