In this video, watch how Ronaldo motivates his teammate to take a penalty. While there is a lot to like in the way Ronaldo goes about it, there is one key thing that stands out for me. Why don’t you through the video, then I’ll share further.
‘If we lose, so be it’
I loved Ronaldo saying that. It completely takes the pressure off. Sometimes when we are too focused on the outcome, performance suffers. Instead he reduced the expectations. There would not be any repercussions. “If we lose, so be it.” He makes the situation psychologically safe.
Your inner talk
Take a moment to reflect on how you motivate yourself before a mock test or the actual exam.
Is your inner talk along the lines of:
- You have to score at least 605.
- You have to score at least 20 points more than your previous mock test.
- On the actual GMAT: You have to score within 20 points of your scores in the mock tests.
If so, it probably is not as convincing as you think. It might be adding too much pressure onto a situation that is already quite heavy with pressure.
So, how about instead you reframe using Ronaldo’s quote:
If you score lower than 605, so be it.
If you score lower than your previous mock test, so be it.
On the actual GMAT: If you score lower even the lowest mock test score, so be it.
Focus on process, not score
The first time you take a mock test, even if you have been preparing for a while, take it without any score expectations.
Now, this doesn’t mean you don’t have a target score for your overall prep. The key is to not let the target score be your focus during the test. There are many aspects such as stamina, concentration over an extended period of time, and regular context switching that you wouldn’t have worked on yet. They might need work. So, without knowing about these things to expect a certain score just because you have been getting certain accuracy in your practice, does not make sense.
The goal during the test should be about process; the score is just the outcome you analyze later.
For example, instead of the score, here are some process-based goals you can use:
Process Goal 1: Nailing your timing checkpoints
What does ‘nailing your timing checkpoints’ even mean? For me, this isn’t about speed. It’s about pacing. It’s my map for the section so I don’t suddenly find myself with 10 minutes left for 10 questions. You can’t time every question perfectly. So I use blocks.
- Let’s take Quant (21 questions, 45 minutes). I recommend you mentally divide it into thirds.
- After 14-15 minutes, you should be at the 8th question.
- After 30-31 minutes, you should be starting Question 15?
- That leaves ~15 minutes for the last 7 questions.
Such milestones can help you track your pacing and course-correct, if needed. e.g.: If I’m on Question 6 at the 15-minute mark, I know I have to move.
When you take a mock, that could be one goal: I’ll even write “8th Q – clock should read 29:__. 15th Q – clock should read 14:__” on my pad. I’ll try to hit those marks. (And if I can’t I’ll later try to analyse why I couldn’t.)
Process Goal 2: Executing your ‘moving-on’ strategy
Can you successfully identify 2-3 questions to guess and move on from? This will allow you to be more in control of your test. Even if you can comfortably answer all the questions within the time limit, leave the hardest-feeling ones for the end. If you anyway struggle with time, your time will be better rewarded on questions that do not feel as hard.
‘Guessing and moving on’ is not a failure, it is a strategic win.
These are just examples of process goals. You could come up with some of your own. e.g. a way to ensure you do not get stuck for too long on a single question.
On your next mock: Ditch the “improvement” pressure
The next time you take a mock test, do not think: Ok I should score at least as much as my last mock test score. Actually, I score see at least a 20-30 point bump, if not more.
While hopefully that happens, this also adds pressure. It is very much possible that you score lower in a subsequent test compared with a previous one. I have seen it happen with my students numerous times.
Instead, based on your analysis after the last test, you should have some key learnings. Revise those before the next test. Recall the key things in terms of the process that you wish to focus on. These could be things that you did not do well last time, or things that did not even consider before.
On the actual GMAT, accept that you may get a score significantly lower than your mock scores
When you are going in to take the actual GMAT, do not think:
- ”I have to score at least a 655 – I scored 645 last time. This attempt’s score should be higher.”
- “I have to score at least a 675. That’s the median score of my target B-school. Anything lower than that would be a failure.”
- Or even: “Ok, my lowest mock test score was 605. I should score at least a 605. Or maybe 10-20 points lower, but certainly not lower than that”
Again, while hopefully your test goes well even beyond your expectations, you’re again adding pressure. The added pressure of the real test, an unfamiliar environment, and various other factors could lead to students scoring lower in their actual test compared with their mock scores or even their past attempts. I have seen a student score 100 points less in their actual test compared to their lowest of the recent mock scores. True story. This could be because the student let one bad question derail the whole section, let one bad section derail the whole test, burn out, just the pressure of the situation, or many other reasons. Hopefully this doesn’t happen to you. But, again creating a stringent target score – based on any factors – could add pressure that does more harm than good.
Tip: If you cannot resist having a target score in mind: Target 100 points less than your average mock scores. Not because I expect you’ll experience such a dip. But because going in with such lowered expectations can actually be very beneficial.
The words you think make a difference. Choose purposefully.