TL;DR
- PMI published what it bills as the world’s first global standard for AI in project work in June 2026: eight principles, five performance domains, covering both using AI in projects and delivering AI projects.
- Most of it is governance scaffolding, and most governance scaffolding ends up in a PMO binder. Standards set a floor, and floors are easy to sign.
- The load-bearing rule: every AI-assisted decision needs a named human who is accountable for it. Applied honestly, that one rule changes how AI gets used on a project.
- The human-in-the-loop language is right, and it will get implemented as a rubber stamp almost everywhere. Oversight only counts if the human in the loop can stop the line.
- Nothing in the document manufactures judgment. It puts in writing where judgment must sit, which is worth having in writing.
- Spend an evening with it, keep the accountability rule, and skip the checklist industry growing up around it.
PMI published what it bills as the world’s first global standard for AI in project work this June. I have spent thirty years on the receiving end of standards, and my first reaction was a yawn. Then I read the thing, mostly out of professional obligation, and found more in it than I expected. Some of it will decorate shelves. One rule in it is worth the whole document.
What the standard says
Eight principles, five performance domains, and a scope that covers two different jobs most conversations blur: using AI inside your project work, and running projects whose deliverable is AI. The distinction alone is worth having, because the risks are not the same and neither is the work.
The principles are strategic value, risk, governance and compliance, people and culture, ethics and professional responsibility, stakeholder engagement, optimization and innovation, and data quality. The domains run from managing stakeholder expectations about AI, through defining scope and designing for quality and reliability, to executing the strategic goals and managing AI risks and uncertainties. Nothing in that list will surprise anyone who has run a project. The surprise is how much of it holds up.
What it gets right
If I had to keep one rule and burn the rest, it would be this: every AI-assisted decision should have a named human who is accountable for it. A person, not a role or a committee. Anyone who has survived a project audit already lives this way, because when the question comes, and it always comes, “the model suggested it” is not an answer anyone accepts. Accountability has always traveled with a name. The standard insists it still does when software writes the first draft.
I also like that it treats human oversight as a value driver rather than a safety brake, and that it says why: models lack judgment, context, and institutional memory. Oversight is where your most senior people spend their attention, and the tool has to earn it.
The stakeholder guidance is the most honest part. It tells you to engage the people who oppose the adoption, not only the enthusiasts, and anyone who has run a rollout knows exactly why. The skeptic whose sign-off you need is the person whose objections you want early, in detail, while answering them is still cheap.
Where it turns into paperwork
Standards describe a floor, and floors are easy to sign. Eight principles fit on one slide, and a PMO can adopt all eight by Friday without changing a single Tuesday. September has already produced a small industry of implementation checklists for this document, and a checklist can satisfy the letter of a principle while changing nothing about how the work gets done.
The rubber stamp is the specific failure mode. The standard wants human-in-the-loop oversight with real intervention triggers and escalation paths. The lazy implementation is a human clicking “reviewed” on everything, which satisfies the audit trail and none of the intent. Real oversight means the human knows what to check, has the authority to stop the line, and occasionally does. If nobody in the loop has ever rejected an AI output, what you have is attendance.
The rule, made operational
Compressed to something you can run on a Monday: every AI output that reaches a decision carries a name. The status report carries a name for its numbers, the risk register for its entries, the plan for the baseline. If you cannot attach a name, the output stays a draft, and drafts do not go to steering committees.
That is also the line we built Akigo! Pulse around. The AI drafts, a person decides, and the tool shows you which is which. A standard cannot supply the judgment. What it can do is say where the judgment must live, and this one says it plainly.
The standard settles where the judgment sits. The AI-for-PMs eBook and video series are about everything on the other side of that line: where AI pays off in a real project week, and how to run it so the calls stay yours. Join the waitlist and you will be first to get them.