I was strong at Quant but stuck below 700. The section that unlocked it was the one I had been neglecting: Data Insights.Here is the one thing this debrief is about: I could not break 700 until I fixed Data Insights, and once I did, everything else fell into place. My first attempt was a 625, with DI at a 75, the 47th percentile. My third was a 705, with DI at an 86, the 99th. Same person, same strong Quant. The only real difference was that I finally learned to solve DI with a method instead of on instinct. Everything below is how that happened.
Why my first attempt fell apartThe problem was invisible to me. Walking out of my first exam I thought DI had gone fine, so a 75 made no sense until I saw what I had been doing: reading each question, then hunting back and forth through the data for an answer, with no fixed process and no eye on the small conditions that decide a question. I was fast but undisciplined, and on DI that quietly bleeds points you never realise you lost. Naming that, that my issue was approach and not knowledge, is what let me fix it.
The DI method that changed the scoreWhat actually moved DI was learning a fixed sequence for each question type instead of improvising. Two concrete changes did most of the work. First, in Data Sufficiency I stopped mechanically writing out all five options and striking them off one at a time. The course taught me to eliminate in groups instead: the moment I confirm that one statement settles the question, I can rule out several answer choices together rather than checking each on its own, which cuts real time on every DS question. Second, on multi-source reasoning I stopped jumping between the questions and the passage. I now read the passage section by section first and note where each piece of information lives, so when a question comes I go straight to the right place instead of re-reading everything. That is the HOW behind the numbers: my hard-question accuracy in multi-source reasoning went from 56 percent to 73, and in table analysis from 63 percent to 80, with my time on table analysis dropping from 2 minutes 48 seconds to just 2 minutes 6. (Attaching files for the same).
Learning when to walk away from a questionThe second half of DI is time discipline, and my fix here was a rule, not a feeling. I used to sink minutes into a hard question to prove I could crack it. Now, the moment a question crosses a couple of minutes with no clear path, I mark it, leave it, and move on, because on DI you are barely penalised for missing one hard question but heavily penalised for letting it swallow the time of three others. Applying that rule, rather than trusting my ego in the moment, is what kept my whole section on the clock.
Quant: protecting a strength, not rebuilding itQuant was never my problem, so the work here was surgical too. The mistakes that separate a Q87 from a Q90 are behavioural, not conceptual, mainly forgetting a stated condition, like a value having to be an integer, after solving. My mechanism was simple: write the condition at the top of the question the instant I read it, before solving. And because I already scored Q90 in practice, the PACE engine let me test out of concepts I knew and jump straight to hard cementing quizzes and mocks, so the hours I saved went to Verbal, where I actually needed them, instead of re-covering Quant I had mastered.
A quick word on VerbalVerbal is my weakest area, so I will keep this short, but I owe Payal ma'am a genuine thank you. The specific fix her Critical Reasoning course gave me was to stop selecting an answer that merely matched the conclusion and instead anchor it to the premise and reasoning, which is where the traps hide. That one change took me from around a 78 to a steady 82, and at these margins those few points are the difference between a 705 and slipping back.
How I made improvements actually stickThe engine behind all of this was the Scholaranium sectional mocks paired with a mandatory
error log. The mocks gave me new questions every time, close to the real exam, so repeating a question type kept driving my time per question down rather than rewarding memory. The
error log is what turned practice into improvement: every wrong answer got tagged with why it went wrong, and when the same reason kept reappearing, I could not pretend it was bad luck, I had to fix the actual habit. Seeing the pattern is the HOW behind steady improvement instead of random ups and downs.
What a mentor addedI chose
e-GMAT specifically for the LMP program, because after my 625 I knew I needed someone who could read my
error log and instantly spot what I could not. My mentor Dhruv did exactly that across a long, on-and-off journey, steadying me when I got carried away after a good score and when I spiralled after a bad one, and even predicting my final Verbal and overall range before the exam. If you have been preparing alone and stalling, that outside eye is worth more than another month of solo effort.
If you are stuck the way I wasIf you are strong at Quant but cannot break 700, look hard at your Data Insights, because that was the exact wall in front of me. It is not about being smarter, it is about having a real method for each question type, the discipline to walk away from a question that is eating your clock, and honest tracking of every mistake. That is what took my DI from a 75 to an 86, and me from a 625 to a 705.
Attachments

Screenshot 2026-08-15 at 9.04.34 AM.png [ 97.96 KiB | Viewed 249 times ]

Screenshot 2026-08-15 at 9.02.28 AM.png [ 71.12 KiB | Viewed 244 times ]

Screenshot 2026-08-15 at 9.02.19 AM.png [ 72.28 KiB | Viewed 245 times ]