StrategyQuantitative · Verbal · Data Insights
Timing problem or knowledge problem?
Taking too long does not automatically mean you have a timing problem.
Time can be the visible symptom of weak recall, poor translation, an inefficient route, repeated checking, or uncertainty about when to leave. Training speed before identifying the cause often makes errors faster.
Start with the accuracy-time matrix
Wrong timed, wrong untimed
The issue is probably not the clock. Investigate concept knowledge, representation, constraints, and reasoning.
Correct untimed, slow timed
You may know the concept but lack recognition or route fluency. Compare how long it takes to identify the structure versus execute it.
Correct and fast in isolated practice, weak late in a section
The issue may be pacing allocation, fatigue, or over-investment earlier.
Accurate but consistently slow
Audit for unnecessary calculation, repeated rereading, and failure to use answer choices or estimation where valid.
Run a relaxed-time retest
Take a small set you have not seen. Record:
- time to understand the target
- time to choose a method
- time to execute
- time to verify
Then repeat the same concept with a reasonable time boundary.
The phase that expands tells you more than the total time.
Example
A machine produces 240 units in 6 hours. How many units does it produce in 90 minutes?
A direct route is:
- rate = 40 units/hour
- 90 minutes = 1.5 hours
- output = 60
A student may reach 60 correctly but spend four minutes converting every value into minutes, writing a full proportion, and checking it twice.
The concept is present. The bottleneck is representation and route choice—often Premature Calculation—not arithmetic speed.
Check the first minute
After roughly the first meaningful reading interval, ask:
- Can I state the target?
- Can I name the governing relationship?
- Do I have a viable representation?
If not, rereading the same way is unlikely to help. Reset the representation once. If uncertainty does not fall, make an educated guess and preserve time.
Do not confuse confidence with progress
Spending another minute can feel productive because you have already spent two. That is sunk-cost reasoning.
Continue only if you can identify what the next step will resolve. Otherwise the extra minute may have lower value than using it on a reachable question later.
An appliance store sold a total of 50 washing machines, each of which was either a Model X washing machine or a Model Y washing machine. Each Model X sold for $x and each Model Y sold for $y. The average (arithmetic mean) selling price of the 50 washing machines was $200. How many of the 50 washing machines were Model X washing machines? (1) The Model X washing machines sold for $25 less than the Model Y washing machines. (2) Either x=180 or y=180.
Answer: C
Let n be the number of Model X machines. Total revenue is 50×200=10,000. Statement (1) gives x=y−25, so revenue = n(y−25)+(50−n)y = 50y−25n. This leaves both y and n variable, so (1) is not sufficient. Statement (2) says one of the two prices is 180 but does not fix the other, so (2) alone is not sufficient. Combining, test the two cases from (2). If x=180, then y=205, and 50(205)−25n=10,000 gives n=10. If y=180, then x=155, and 50(180)−25n=10,000 gives n=−40, which is impossible. Thus n=10 is uniquely determined.
Original GMAT-style question written for Premiergrad and checked by an independent blind solve. Not an official GMAT question.
What Lumen looks for
Lumen reads the answer you chose, not just whether it was wrong. On a question like this it separates three things that all look identical in a score: a concept you have not met, a reasoning step that went sideways, and a correct method pointed at the wrong target. Those need three different next weeks, and only the third one is fixed by re-reading the topic.
A single answer is weak evidence and Lumen says so. It becomes a diagnosis when the same shape shows up across several questions — which is the part a page like this cannot do for you.
Match the intervention to the diagnosis
- Concept gap: rebuild the concept, then use direct-to-disguised practice.
- Recognition gap: mixed practice with explicit post-question classification.
- Route gap: compare two valid solutions and rehearse selection cues.
- Execution gap: short timed sets with one targeted checkpoint.
- Pacing gap: section-level blocks and planned abandonment rules.
- Fatigue gap: realistic blocks, breaks, sleep, and sequence analysis.
Related resources: Premature Calculation, When to Guess and Move On, Why Your GMAT Score Keeps Plateauing, and the Practice Collections.
Use a free diagnostic set to compare your accuracy and decision time across question types.
Diagnose my timing →
Related
-
Strategy
Why Careless Errors Aren’t Really Careless
“Careless” describes how a mistake feels after you see it. It does not explain what produced it.
If untimed accuracy is fine, read this next.
-
Strategy
How to Review a Wrong GMAT Question
Review is not complete when the explanation makes sense.
The review step that produces the evidence.
-
Practice
Hard GMAT Data Sufficiency Questions
Hard Data Sufficiency is rarely hard because the arithmetic is long. It is hard because several cases remain possible…
Where over-solving costs the most time.
You have the method — now get the evidence
A framework is worth more with your own attempts in front of it. A short diagnostic produces the evidence this page tells you how to read.
Run a short diagnostic Everything on this page stays free and open — no account needed to read it or to attempt the questions above.