Stop Timing EVERY Question From Day One
Say it's 9:15 on a Tuesday night. The last work email is finally out. You open your first set of Executive Assessment Quant questions and set a timer on your phone: two minutes a question, because you read somewhere that's the pace. You rush. You guess on anything that feels slow. You finish 14 questions with 6 right, and you decide: "I'm too slow."
No. You're not too slow. You're SLOPPY, and you just spent an hour training yourself to be sloppy faster.
I watch people do this every week. Smart, busy professionals who run teams and budgets treat the clock as the first thing to beat. It isn't. Racing the clock from day one doesn't build speed. It builds the habit of skipping steps, and skipped steps are where your points go to die.
What the clock is really telling you
Here are the facts. The Executive Assessment (the EA) is 90 minutes split into three 30-minute sections: Integrated Reasoning with 12 questions, Verbal Reasoning with 14 and Quantitative Reasoning with 14. Each section is scored 0 to 20, and all three count the same toward a total of 100 to 200. You can see the full layout on GMAC's structure page.
Do the math with me. 30 minutes for 14 Quant questions is a little over 2 minutes each. For Integrated Reasoning it's 2.5 minutes each. Now stop and read that word again: EACH. That number is an AVERAGE, not a rule. Some questions take 40 seconds. Some take 3 minutes even when you do them well. An average tells you what the whole section adds up to. It does not tell you how long any single question should take.
When you put a 2 minute timer on every question from the first day, you're asking yourself to hit an average on questions you don't yet know how to solve. So you guess at a method. You work in your head because writing feels slow. You skip checking what the question actually asked. You miss it. Then you do the same thing tomorrow. That's not practice. That's rehearsing a mistake until it feels normal.
I'll bet your misses weren't the hard ones
Go back to the last timed set you did. Look at every question you got wrong. I'll bet MOST of them weren't hard. I'll bet you knew the math, misread a number, forgot a condition or picked an answer before you checked it. Those are 'gettable' questions, and they're the cheapest points on the whole test.
Now the forced choice. What do you want MORE: to feel fast in week one, or to score higher on test day? Speed built on top of a broken method just gets you to the wrong answer sooner.
Think about learning a golf swing. Nobody good learns it by swinging as hard as they can in the first lesson. You go slow. You get the motion right. Then you add speed, and the speed holds up because the motion under it is clean. The EA works the same way. Accuracy is the motion. Speed is what you add after.
Watch what rushing costs you
Here's a Data Sufficiency question, one of the two Quant question types on the EA. In Data Sufficiency you don't solve for a number. You decide whether the information you're given is ENOUGH to answer the question. Do this one with no timer. Take notes on paper. Then check.
The mistakes I see most (and what to do INSTEAD)
Putting a per-question timer on from the first session. You end up judging yourself on a clock you haven't earned the right to race yet.
INSTEAD: Run a stopwatch, but don't race it. Write down the time for each question afterward. Judge the session on two things only: did you get it right, and HOW did you get there.
Working in your head to 'save time.' Every reread of a prompt you didn't write down is time you lose, and every number you carry in your head is a chance to drop it.
INSTEAD: Notes on every question, every time. Integrated Reasoning is full of charts and tables, and one misread number there costs you the same as a Quant miss, because all three sections count the same.
Guessing and moving on in practice. On test day, a smart guess is a tool. In week two, it's a way of hiding what you don't know.
INSTEAD: Finish every practice question, even if it takes 5 minutes. Then, in review, hunt for the faster route.
Reviewing only the wrong answers. A right answer that took 4 minutes is a problem. So is a right answer you got by luck.
INSTEAD: Review the slow ones and the lucky ones too, including the ones in your strongest section.
Doing 'speed drills' on your phone while you wait in line. No paper, no notes, half your attention on the line.
INSTEAD: Read why studying on your phone is mostly fake studying, and save real practice for when you have a pen and 30 quiet minutes.
So when DOES the clock come in?
The clock isn't the enemy. It just has a place in line, and that place isn't first. Build it up in three stages.
- Stage 1: Accuracy. Untimed, stopwatch running in the background. The goal is right answers with clean notes. You move on when your misses are rare and you can name the cause of each one.
- Stage 2: Timed sets, not timed questions. Try 7 Quant questions in 15 minutes. That's the same average as 14 in 30, but now you're free to spend 3 minutes on one and 1 minute on another, which is exactly how the real thing works.
- Stage 3: Full sections. 30 minutes, the real number of questions, test-like conditions. Full 90-minute practice tests go here too, as a way to MEASURE where you are, not as your main training. By the final week, you're sharpening, not learning.
Here's what you'll likely notice in Stage 1: your times start to drop on their own. You never pushed them. They dropped because a clean method with good notes is simply faster than a messy one. That's speed you can trust on test day.
Your move, tonight
Pick 5 Quant questions you haven't seen. Start a stopwatch and turn it face down. Write notes on every question. When you finish, write down the time for each one and whether you got it right. Then take the SLOWEST one and find a faster way to solve it, even if it means testing values or testing the answer choices.
That's one session of real training. Not someday. Tonight.
