A few weeks back I had an agent reconciling a vendor list. It ran clean. No error, no crash, output looked right. Then I noticed it had merged two suppliers that share a parent company into a single row, which would have thrown off every spend rollup downstream by a real number.
I stopped it and fixed it by hand. Not because anything alerted me. Because I'd been burned by that exact shape before, and the burn taught me something a tutorial never did.
I'm telling you this because on July 9 the PMP changes, and the change points straight at that moment.
What changed in the exam
For the first time, the PMP makes AI mandatory content instead of an elective. The Business Environment domain goes from 8% of the exam to 26%. PMBOK 8 becomes the base. Fees climb in August.
The largest project-management body on earth just put it in writing: AI fluency is core PM competency now, not a specialty track. If you've been treating "PM + AI" as a buzzword, the institution that certifies the role just disagreed with you.
I think that's the right move. It's also where it gets interesting for anyone who actually ships work through agents.
Certified is not practiced
A multiple-choice exam can certify that you know what an agentic workflow is. It can check that you'll pick the textbook answer about AI risk, define non-determinism, name the correct oversight principle.
That's awareness, and awareness is worth certifying.
What it can't reach is the reflex that runs real work. The exam can't certify that you've handed live stakes to an agent, watched it drift, and built the instinct for when it can act versus when you take over. You don't recall that instinct. You earn it, and the only way to earn it is to need it.
I learned the vendor-merge thing from the run where I caught it too late.
What AI fluency looks like in the editor, not the exam
Let me put it in do-this terms. Here's the practiced version, and none of it is a question you can bubble in.
You scope the agent's slice like a statement of work. Not "improve onboarding." Bounded edges, in and out defined before it touches anything:
task: reconcile vendor list for Q2
in_scope:
- dedupe exact-match names
out_of_scope:
- merging distinct legal entities # <- the line that would have saved me
acceptance:
- row count change is human-reviewed before rollup runs
You know the override moment. This one I'd put first. You only learn the veto by having needed it.
You read the output for what it didn't do, not just whether what's there is correct. The skipped supplier, the untouched edge case.
You design the work so a human can actually check it. If the only way to verify is to redo the whole thing, the slice was wrong.
You size the blast radius before deploy. How wrong can this go, who feels it, answered up front the way you'd treat a change to a live service.
Five reps. All earned. Zero on the exam.
Why this is a level-up, not a layoff
The panic read of this is backwards. The credential catching up doesn't shrink the role, it raises the floor. When the institution names AI fluency as baseline, the person who's practiced it instead of read about it becomes the scarce one. Certified-and-practiced is a much smaller set than certified.
So I wouldn't study the new section and stop. I'd go get the reps it's gesturing at. Hand something real to an agent this week, let it run a little past comfortable, and watch the moment your hand goes for the keyboard. That moment is the competency. It never shows up on a scorecard.
For those of you shipping work through agents already: what's the moment that taught you to override, and could a test have taught it instead?
Tags: #projectmanagement
Top comments (0)