I think what you’re describing is a very common issue, especially when moving into DI. The problem may not actually be “reading speed” as much as
deciding what deserves attention while reading.
One thing that helped me was separating
comprehension from processing. You don't need to understand every sentence or connect every piece of information immediately. First, identify the structure of the question.
For MSR/DI, I’d use this quick checklist:
- Read the question/task first. What exactly am I being asked to find?
- Identify the relevant variables. Which dates, categories, people, numbers, or conditions could affect the answer?
- Scan the tabs/data only for those variables.
- Write a tiny mental summary of the relationship you need to establish.
- Solve. Don't try to build a complete mental model of the entire passage.
Your CCC example is a good illustration. The sentence about Friday determines the assignment/fee, but that doesn't necessarily mean Friday is something you need to compare. The question itself should determine which dates matter. That's an important habit:
don't let information in the passage create a task that the question never asked you to perform.For post-question analysis, I would avoid spending 20–30 minutes simply rereading the official explanation. Instead, record five things:
- What was the question asking?
- What information actually mattered?
- What information did I incorrectly treat as relevant?
- Where exactly did my reasoning go off track?
- What rule/trigger should I recognize next time?
For the seabird/cat example, I think the bigger lesson is the wording rather than the mathematics. Words such as
“likely,” “most,” “only,” “three times as likely,” “if,” “during more years,” etc. should immediately make you slow down and translate the statement into something simpler.
For example:
Quote:
Cat population increases → seabird decrease becomes 3× as likely.
That's different from:
Quote:
Cat population increases → seabird population decreases.
And “most years” is a completely different claim from “more years.”
I would actually recommend keeping a small
GMAT wording error log. Every time you miss a question because of language, write the exact phrase and what you incorrectly interpreted it as. After 20–30 questions, you'll probably start seeing the same traps repeatedly.
One other thing:
don't try to reduce your time by forcing yourself to read faster. Initially, aim to make your first read more purposeful. Speed usually comes afterward because you stop rereading.
A useful rule for practice could be:
Read → Identify task → Identify relevant information → Solve → Analyze the error.And during review, ask yourself:
Quote:
“If I saw this exact question again tomorrow, what would I notice within the first 20 seconds that I failed to notice today?”
That answer is probably more valuable than simply knowing why the official answer is correct.
Finally, don't judge your progress solely by the 3:51 average. Your 6:38 on the CCC question is useful data. If you can determine that 2–3 minutes of that time came from unnecessary orientation/re-reading, you've identified a specific skill to train rather than simply concluding that you're “slow.”
Your structured approach from KarishmaB is already a good foundation. I’d focus next on
relevance filtering and wording precision, because those seem to be the two bottlenecks behind the timing issue you're describing.