Hi everyone!I recently finished my GMAT journey, and I wanted to share my experience here because I know how helpful it was for me to read other people's debriefs when I was preparing.
One thing that made my journey particularly frustrating was a problem I know a lot of GMAT aspirants face: my mock scores were consistently much higher than my actual score. I went from a 625 to a 695 in 19 days, and the biggest change wasn't actually in what I knew. It was in how I approached the test.
Hopefully, some of this is useful for anyone who feels that their preparation is better than what their test-day performance shows.
My first attempt
I initially decided to self-study for the GMAT while working full-time, putting in around 2–3 hours every day. After about two months of preparation, I took my first attempt and scored 625.
The result was difficult to process because my mocks before the exam had consistently been 700+. I knew my conceptual preparation wasn't the biggest problem, but I couldn't understand why I wasn't able to replicate my mock performance on test day.
I've always been an overthinker, and the adaptive nature of the GMAT created a lot of anxiety for me.
During my first attempt, I put enormous pressure on getting the first few questions right. I spent almost five minutes on my very first question, even though it was a question I was technically capable of solving. I simply couldn't get myself to answer it confidently.
After the exam, I went through my score report and thought about what had actually happened.
My concepts were reasonably solid. My test-taking strategy and execution were not matching my level of preparation.
That was when I decided I needed help.
Understanding Where I Was Going Wrong
I came across Piyush from GMATWhiz through his strategy videos and student interviews on GMATClub during my preparation. What stood out to me was that his approach went beyond teaching concepts. He seemed to understand the test really well and focus on how to actually take the GMAT, including strategy, decision-making, timing, and mindset.
After my first attempt, I decided to work with him.
When we started working together, he was able to quickly dissect my approach and point out a few mental habits and execution issues that I was completely unaware of. One of the most useful parts of the process was taking live mocks with Piyush observing my approach and then analyzing not just my answers, but how I was thinking and managing the test.
That helped uncover several things I hadn't noticed on my own.
What I realized about my timing
One of the biggest examples was my approach to Quant timing.
I had convinced myself that I needed to solve every Quant question in under two minutes, particularly during the first half of the section. If I crossed the two-minute mark, I would immediately feel that I was falling behind.
But when Piyush looked at my timing data more closely, he pointed out something I had completely overlooked. I was focusing too much on whether I was getting the test "right" rather than simply focusing on the question in front of me. From there, the pressure kept building, and it became very difficult to settle back into the test.
He made me understand that I was actually very capable of managing the second half of the Quant section within the available time. That meant I could afford to spend 3–3.5 minutes on some of the earlier questions without putting my entire section at risk. That was a huge realization for me. I had been treating two minutes as a hard rule, when my own performance data was showing me that I didn't need to.
It made me realize that trying to save time isn't always the same as managing time well. Sometimes, giving yourself a few extra seconds with a calm mind can lead to a much better decision than rushing through a question just to stay under an arbitrary time limit.
Learning to deal with the adaptive GMAT
A big part of this was the way I viewed the adaptive nature of the test.
Before my first attempt, I had built up this idea in my head that every question, particularly the early ones, was extremely high stakes. So if I wasn't immediately sure about an answer, I would start second-guessing myself.
During the live mocks, I realized how much this was affecting my actual decision-making.
In one instance, I felt that I had spent 3+ minutes on the first question and had almost frozen. When we reviewed it, I had actually spent around 1 minute 40 seconds solving the question and another 40 seconds overthinking it.
Those 40 seconds felt much longer because I was anxious and had lost structure in my thinking.
I could have simply looked at the timer and made a decision based on the actual time rather than what I felt the time was.
That was another important lesson for me: I didn't need to treat every question as a make-or-break moment.
I needed to make good decisions consistently and trust myself enough to move on.
I started focusing on:
- Trusting my initial reasoning instead of constantly second-guessing myself
- Looking at the timer objectively rather than relying on how much time I felt had passed
- Accepting that some hard questions may require more time to pause and strategize before solving
- Accepting that I didn't need to solve every question at the same pace
- Spending that extra time when a question deserved it instead of rushing and planning to come back later
- Focusing on the question in front of me rather than worrying about where my score was heading
- Prioritizing accuracy over trying to finish as quickly as possible
A few other things I worked on
There were also some more specific areas where my approach needed refinement.
For Data Sufficiency (DS), I was approaching questions too much like regular Math/Problem Solving questions and doing more calculations than necessary. I worked on using the logical structure of DS more effectively and reducing unnecessary math.
My timing strategy for Data Insights section was also flawed. I was putting a lot of pressure on myself to solve all 20 questions. That often caused me to rush and, at times, I wasn't even reading questions carefully enough.
I had to shift from thinking "I need to finish all the questions" to "I need to solve the question in front of me properly." That change helped me prioritize accuracy instead of trying to force a particular pace. I realized I didn't necessarily need to rush through every question just to finish all 20.
I also learned to be more comfortable using the calculator when it was actually useful rather than avoiding it unnecessarily.
And when I felt the pressure building, I learned that taking 30 seconds to a minute to pause, breathe, and reset was much more useful than continuing to rush while my mind was somewhere else.
The goal wasn't to eliminate pressure completely. It was to stop pressure from controlling my decisions.
One thing I kept reminding myself during this process was: Trust yourself. Be confident.
I also started seeing the GMAT differently. I didn't need to make every question perfect. I needed to make good decisions consistently.
For someone like me, these changes were much more important than learning another 100 concepts.
The second attempt
I retook the GMAT just 19 days after my first attempt and scored 695.
The 70-point improvement was obviously a huge relief.
But what stood out to me even more was looking at my section performance and seeing that I had gotten the first 10 questions of every section correct.
Those were exactly the questions I had been most afraid of after my first attempt.
The beginning of the test had been such a major source of anxiety for me, and now I had managed to get through the first 10 questions of every section correctly.
For me, that was the clearest indication that my approach to the test had changed.
The concepts hadn't changed dramatically in those 19 days.
My execution had.
And honestly, I couldn't have been happier to see that.
My Biggest TakeawayIf your mock scores are consistently higher than your actual GMAT score, don't automatically assume that you need to study more.Look at how you're taking the test.
In my case, my conceptual preparation was reasonably strong. The bigger problems were anxiety, rushing, second-guessing, and not understanding how to manage my time based on my actual strengths.
Once I understood the root causes, I could work on the right things instead of simply putting in more hours.
The live mocks were particularly helpful because these weren't things I would necessarily have identified just by looking at my final score. Having someone observe my approach while I was actually taking the test made it much easier to see the connection between my thoughts, decisions, timing, and accuracy.
I genuinely attribute that change in approach to the support I received from GMATWhiz and Piyush. He was honest about my mistakes, helped me identify patterns I couldn't see myself, and gave me the confidence to trust my preparation. If you're in a similar situation, I'd suggest looking beyond your score and asking yourself:
Is my preparation the problem, or is my execution not allowing my preparation to show?
For me, learning the difference made all the difference.
Good luck to everyone preparing! I hope this helps someone who is currently stuck between their mock scores and their actual performance. Sometimes the issue isn't that you need to study more; you may just need to understand what is getting in the way of the preparation you already have.