Hey [First Name],
I want to start with something nobody says in the PMP study groups:
Passing the exam was the easy part.
Not easy like easy easy. You know what it took. The flashcards at 11pm. The practice exams you failed twice before you passed. The acronyms you still sometimes mouth silently in meetings because they stuck.
But the exam? It had a right answer. It had a scoring rubric. It had an end date.
Real projects don't work that way.
Here's what actually made me a project manager:
It wasn't the PMBOK. It was the Tuesday afternoon when I had to walk into a room full of stakeholders and tell them we were three weeks behind — and I hadn't caused the delay, but I owned the recovery plan anyway.
Nobody teaches you that part. No multiple choice question asks: "Your executive sponsor is visibly disappointed and the team is looking at you. What do you do?"
The answer, by the way, is: you don't flinch. You give them the facts, the options, and a recommendation. You let them decide, but you make it easy for them to decide well. Then you walk out and you execute like you were never rattled.
That's what makes someone a PM. Not the letters after their name.
The real competency gap nobody talks about:
After the PMP, a lot of people wait for the job to get easier. They think the cert signals something — and it does, it signals that you did the work to learn the discipline. But then they sit in their first real project and realize: the frameworks are a foundation, not a formula.
The gap between passing the PMP and actually running projects comes down to a handful of things that you can't study your way to:
1. Delivering bad news before it becomes a crisis.
The instinct is to wait until you're sure. The skill is telling people early, when you're still uncertain, so they have time to respond. PMs who wait until they're certain have already lost a week.
2. Saying no without blowing up a relationship.
Not "let me check with the team." Not "that's interesting, we'll consider it." A clear, kind, non-negotiable no — with a reason — and then moving on. Scope doesn't protect itself.
3. Staying calm when the room isn't.
Every project has a moment where panic is contagious. Someone's going to be the non-anxious presence. That someone should be you. This is 90% posture and 10% having a plan, even if it's a rough one.
4. Knowing when the plan needs to change.
This one trips up a lot of PMs. The plan is a tool. It's not a contract with the universe. The ability to read when you're holding onto a bad plan because you made it — and let it go — is one of the hardest things to learn.
5. Making people feel like this project is worth their time.
Teams don't show up for Gantt charts. They show up when they understand why it matters, when they feel heard, and when someone is making their path forward clear. That's leadership, not project management. But the best PMs don't separate the two.
What I want for you:
Every week, I'm going to write to you about the things that actually move the needle — not the things that show up on the exam.
Some of it will be tactical (resume rewrites, interview prep, how to talk about your projects). Some of it will be honest (the parts of PM work that are hard and under-discussed). Some of it will be directly applicable to wherever you are in your career right now.
You're here because you're building something — a career change, a promotion, a credential that opens a door. I want to help you walk through it ready.
More next week.
— Karissa
P.S. — The post that started this newsletter got 94,000 impressions on LinkedIn. It said: "Passing the PMP doesn't mean you can run a project." If that hit a nerve for you, you're in exactly the right place.