I like a lot of what you're doing here. You're reviewing every mistake, you're keeping an
error log, and you're treating guessing as a decision rather than a failure. Before you commit to the six weeks, though, I want to push on the premise a bit.
You said the problem isn't conceptual anymore, that you know how to solve the questions but burn too much time on the hard ones. That's the beginning of the diagnosis, not the end of it. When a question takes four or five minutes and you still get there, the cause is usually more specific than "slow." Maybe the concept is understood but not automatic, so you're rebuilding the approach from scratch each time. Maybe you default to a longer method when a cleaner one exists. Maybe you don't recognize what the question is testing until you're two minutes in. Maybe it's nerves. Each of those has a different fix, and only one is really about time management.
So I'd be careful about swapping topical work out for timed sets. You need both, and they do different jobs. Timed sets show you where your time is going and train your decisions under pressure. Topical work rebuilds the approaches that are costing you the minutes. Run them as a loop: take a timed set, find the exact questions that ate the clock, bring those topics back to careful practice until the setup is automatic, then re-time them. Six weeks is enough to run that cycle several times.
On the guessing, you're right that it's a skill. The check that works is asking yourself mid-question whether you have a path. If you're executing, keep going. If you're rereading the same line or reaching for a third approach, guess and move. Never spend four-plus minutes on one question.
For the log, categorize every miss by cause: concept gap, process error, careless execution, trap answer, task error, recognition error, or real timing pressure. One line on what you missed, one line on what you'll do differently, phrased as a trigger and a response. Review it weekly rather than daily, since patterns don't show up in three entries. Log the ones you got right but weren't sure about, and log the pacing events too: three-plus minutes and still missed, or rushed at the end of a section.
Here's the part worth saying plainly: if the log keeps pointing back to the same handful of topics, what you're looking at is content depth, and six weeks is enough to fix that if you name it now instead of in week five.
Keep the structure and keep the log, run the timed work and the topical work together, and judge progress by whether your time on a given topic is dropping while your accuracy holds.
I hope that helps.
Npnaman98
After taking several mocks and reviewing my performance, I realized that my biggest limitation is no longer conceptual understanding but time management. In Quant and Data Insights especially, I often know how to solve the questions but spend too much time on a few difficult ones, leaving myself to rush or guess at the end of the section.Over the next six weeks, my focus is shifting from learning new concepts to improving pacing, decision-making, and consistency. I'm practicing timed sets instead of isolated questions, maintaining an error log to identify recurring patterns, and reviewing every mistake in detail. I'm also working on recognizing when to make an educated guess instead of forcing a solution that consumes valuable time.My goal is to build the discipline required for the actual exam, where strategic decisions matter just as much as problem-solving ability. Hopefully, this approach will help me convert my current performance into a higher GMAT score.