AI Accountability Just Landed on Your Risk Register

By Martin Bergmann | AI Project Lab | June 2026

PMI published its first Standard for Artificial Intelligence in Portfolio, Program, and Project Management in early 2026. At 297 pages, it is substantive, technology-agnostic by design, and more honest about risk than most AI guidance I have read recently.

Here is my practitioner-level read.

The accountability shift is real:

The standard does not treat AI as a tool that sits outside the PM's responsibility boundary. It places Human-in-the-Loop oversight squarely on the project manager. You are the checkpoint. If AI output is wrong and you acted on it, that is a judgment call you own. For practitioners who have been using AI tools casually, this is a meaningful reframe. Speed and convenience do not transfer accountability elsewhere.

The risk register just got longer:

The standard formally names hallucinations, model drift, algorithmic bias, and overreliance on AI as project-level threats. Not IT threats. Not governance issues to route upward. Project risks, sitting alongside scope creep and resource constraints. Most PMs I talk to are not yet identifying these in their risk registers. The standard is signaling they should be.

Adoption is a PM leadership responsibility:

At the project team level, the standard assigns AI adoption accountability to the project manager. Communicating the value of AI tools, identifying skill gaps, and creating psychological safety to experiment and fail forward. That is the PM's job, not a separate change management workstream.

The honest limitation:

The standard is technology-agnostic by design, which is the responsible choice for a principles-based document. But it means practitioners using specific tools like Microsoft Copilot, ChatGPT, Claude, or other AI applications will not find implementation guidance here. That translation work still falls to us.

Why this matters beyond compliance:

The organizations building AI fluency at the practitioner level right now are building a capability advantage that will compound. The standard gives that work a professional foundation and a shared language.

The question worth sitting with: if your project managers were evaluated against this standard today, where would the gaps be?