Why is your GMAT score stuck? Because there is no learning in your learning rituals

You’re doing everything you’re supposed to do. You solve problems, review your mistakes, and diligently record them in an error log. Yet your score is stuck.

Why?

It’s not about the effort; it is that effort isn’t leading to learning.

And it is only through learning that improvement happens.

Let’s look inside your error log. What does it say?

“I misread the question.”

“I missed a constraint.”

“I made a calculation error.”

“I made a bad assumption.”

It’s a library of mistakes. And a library’s purpose is to catalogue the past, not build a better future.

To truly improve, you must stop being a librarian of your errors and become an engineer of your thinking process. A librarian maintains records; an engineer diagnoses a failure and redesigns the system to solve the problem.

This might sound abstract, so let me share a recent conversation with a student that illustrates this shift perfectly.

A Story of a Flawed Takeaway

My student was working on an Inference question. The question was:

First-time computer buyers typically buy cheaper, low-profit models. Repeat buyers, who are replacing their old machines, buy more powerful, high-profit models. Last year, the company’s profits were substantially higher than the previous year, even though the total number of computers sold remained the same.

Option: Last year, the number of computers bought by repeat buyers was greater than the number bought by first-time buyers.

My student’s mistake was that he marked this option as correct.

During our review, he was eventually able to see the flaw by creating a case with numbers. He realized that if first-time buyers initially made up a huge majority of the sales (say, 90 out of 100), their numbers could drop (to 70) and the repeat buyers’ numbers could rise (from 10 to 30), causing profits to soar while still leaving first-time buyers in the majority.

He understood his error. Now came the most important part. I asked him, “So, what’s your takeaway?”

He thought for a moment and said:

“I made an assumption, but I did not validate it. My takeaway is that I need to validate my assumptions.”

This is where most students stop. But this is where the real work begins. An engineer doesn’t accept the first diagnosis without testing it.

“Okay,” I said. “Let me ask you something. When you were solving the question, were you even aware that you were making an assumption?”

He paused. “No,” he admitted. “It just seemed like the logical answer.”

“Then how will your takeaway help you?” I asked. “If I came to you while you were solving the question and asked you to validate your assumption, would you have gotten this question correct?”

“No.”

A light bulb went on. He saw that his takeaway, while well-intentioned, was completely useless. It relied on a state of mind—an awareness—that he simply didn’t possess during the problem-solving process.

Engineering a Better Takeaway

So, what is a useful takeaway? It’s a new piece of knowledge or a change in your process. Something that prevents the mistake from happening again.

In this case, the actionable takeaway, the engineering fix, for this student can be:

“When a value is increasing, I must consider its starting point. A group that is small, even after a significant increase, can still remain small compared to a much larger group.”

It’s a piece of knowledge he can now use to analyze any problem involving shifting proportions, whether it’s about profits, percentages, or demographics. This is something that can help him avoid the same mistake.

How to Stress-Test Your Own Takeaways

This brings us to the core of the issue. The reason most error logs are useless is that students never sincerely try to follow their own takeaways. They intuitively know that advice like “I will be more careful” can’t truly be followed, so they just write it down and move on.

It’s a ritual of learning, not the real thing.

From now on, before you write down any takeaway, you must stress-test it with one simple, powerful question:

“How, specifically, would this takeaway have changed my actions in the moment when I didn’t know I was making a mistake?”

If you can’t answer that question with a concrete action or a specific piece of knowledge you would have applied, your takeaway is useless. Throw it out and dig deeper.

Applying This to Your GMAT Prep

• Audit your log. Are your last ten takeaways vague intentions (“read carefully”) or actionable insights?
• Conduct a post-mortem. For each error, have a conversation with yourself like I had with my student. Recreate your state of mind. Ask why you didn’t see the trap. The answer to “why” will lead you to the source of your problem.
• Commit to the fix. Pick a few new, useful takeaways and apply them with 100% discipline for the next two days. See how this changes your approach and the results.

Stop being a passive librarian of your failures. Be the active engineer of your success. I believe that is the only path to the improvement you’ve been working so hard for.