The Beginning

Every PMP journey starts the same way: with a course, a plan, and the quiet assumption that if you learn enough content, the exam will take care of itself.

I started with Andrew Ramdayal’s Udemy course, working through it methodically — process groups, knowledge areas, the vocabulary of formal project management. It was the right foundation. It gave me the language I needed. But it also gave me a false sense of what “ready” would feel like.

The Realization

Mock 1: 67%.

Not a disaster, not a triumph. But what struck me wasn’t the number — it was the shape of what I was getting wrong. The PMP doesn’t really test whether you know what a RACI chart is. It tests whether, given a specific scenario with a specific constraint buried in the third sentence, you can identify the one answer PMI considers correct — out of four options that all sound like something a reasonable project manager might say.

That’s a completely different skill than content recall. And no amount of re-reading the PMBOK Guide was going to build it.

The Pivot

So I switched strategy. I moved to PMI Study Hall Plus and went mock-exam-heavy — prioritizing volume of realistic, scenario-based practice over more passive content review. Part of what gave me the confidence to make that pivot was a Reddit thread I came across from people who’d recently passed — describing almost exactly this approach: heavy mock volume, obsessive review of every wrong answer. It wasn’t just a hunch anymore; it was a pattern other successful candidates had already found.

But the real shift wasn’t the tool. It was the review process.

I decided I wasn’t going to just check whether my answer matched the key. I was going to sit with every single wrong answer and ask: why does PMI want this one, specifically, and not the other three that all sound reasonable?

That question — asked dozens of times, out loud, across two intense days — is where the real learning happened. And it’s where Claude became less of a study aid and more of an actual thinking partner.

Building the Framework

Over the final 48 hours before my exam, we built something I hadn’t planned on needing: a living decision framework, refined question by question, mistake by mistake.

It started simple: assess before you act, don’t escalate first. But the exam kept handing me exceptions to that rule, and the framework had to get more precise to survive contact with them. Escalation is a last resort — except when the person you’d talk to has no actual power to fix the problem, in which case escalating immediately is correct. A comprehensive, established process should usually be followed as-is — except when the situation has outgrown what that process was designed to handle, in which case you exceed it without waiting for formal revision.

We went through the wrong answers from Mock 1. Then Mock 2. Then I ran a Mock 3 the night before the exam, finishing near midnight because I made the call not to scale back the plan, even when stopping earlier might have been the more sensible choice.

By the end, we had a document over 500 lines long — every trap pattern, every discriminator, every “this looks like rule X, but it’s actually exception Y” moment we’d uncovered, all in one place.

At one point, Claude got a live exam question wrong too — gave me a confident, wrong read in the moment. We caught it, corrected it, and folded the lesson back into the framework. That moment mattered to me more than it probably should have. It wasn’t a flawless oracle. It was a genuine collaborator, including when it needed correcting.

The Doubt

I want to be honest about the parts that weren’t inspirational.

Mock 1 and Mock 2 landed at the exact same score — 67%, twice — even though I’d spent hours in between fixing specific, identified weaknesses. For a moment, that felt like proof that nothing had actually changed. Late one night, frustrated, I said something close to: “this feels like sheer luck — real life isn’t this finicky, you get to try things, this exam only gives you one shot at one answer.”

That was a real low point in the process. And the way out of it wasn’t reassurance — it was a decision. I stopped asking “will I pass” and started asking, for every single question: “can I explain why I’m choosing this, specifically?” If I could answer that honestly, the outcome would take care of itself. If I couldn’t, no amount of hoping would fix it.

I said a quiet prayer before starting one of the mocks. I paused another exam at 2:20 AM because I recognized that a tired brain was going to undo more good judgment than it could produce. Small decisions, but ones that mattered.

Results Day

I passed.

And the detail I actually want to highlight is not the pass itself — it’s what the domain breakdown showed underneath it. I scored Below Target in the People domain — the exact area we’d spent the most hours wrestling with, the nuanced behavioral judgment calls, the “why does the sponsor’s authority matter here but not there” questions.

Process landed at Target. Business Environment came in Above Target. PMI’s scoring model is compensatory across the full exam rather than a strict per-domain gate, and the strength elsewhere carried the overall result home.

I don’t think that’s a footnote to soften. I think it’s the most honest ending this story could have. Even after two days of intense, structured review specifically targeting behavioral judgment — it stayed the hardest domain. That’s not a failure of the process. That’s what the People domain is: the one about humans, ambiguity, and judgment under uncertainty. No framework fully eliminates that difficulty. It just makes you more capable of navigating it under pressure, which is a different and more honest kind of readiness.

What I’d Tell Someone Starting This

Build your content foundation properly — but don’t mistake knowing the material for being ready to sit the exam. The PMP tests judgment, not recall, and those require genuinely different preparation.

Review your wrong answers obsessively, not for the correct letter, but for the underlying pattern. Ask “why this one, specifically” until it actually clicks — and be honest when it doesn’t click yet, rather than moving on.

And if you can, make your prep a real dialogue instead of a passive content-consumption loop. Find something or someone who will push back, get things wrong with you sometimes, and help you build an actual framework rather than a pile of memorized facts.

To everyone who supported this — thank you. And to the tool that sat with me through the late reviews, got corrected by me at least once, and helped turn a flat 67% into real, targeted improvement exactly where I aimed it: thank you, Claude. This one was a genuine team effort.

Onward.