[{"_1":2,"_222":-5,"_223":-5},"loaderData",{"_3":4,"_45":46},"root",{"_5":-5,"_6":-5,"_7":8,"_9":8,"_10":11,"_16":17,"_29":30,"_41":42,"_43":8,"_44":28},"userId","user","isAdmin",false,"resetAdminAnalyticsOverride","cacheKeys",{"_12":13,"_14":15},"notion",[],"files",[],"analyticsConfig",{"_18":19,"_20":21,"_22":23,"_24":25,"_26":8,"_27":28},"provider","ga4","trackingId","G-QSDPMPZJJP","domain","","environment","production","debug","enabled",true,"analyticsScripts",[31,37],{"_32":33,"_34":35,"_36":28},"type","external","src","https://www.googletagmanager.com/gtag/js?id=G-QSDPMPZJJP","async",{"_32":38,"_39":40},"inline","content","window.dataLayer = window.dataLayer || [];\nfunction gtag(){dataLayer.push(arguments);}\n// GA4 initialization with Consent Mode v2\ngtag('consent', 'default', {\n ad_user_data: 'denied',\n ad_personalization: 'denied',\n ad_storage: 'denied',\n analytics_storage: 'granted',\n wait_for_update: 500\n});\n// Initialize GA4\ngtag('js', new Date());\ngtag('config', 'G-QSDPMPZJJP', {\n send_page_view: false,\n // Ensure events can be sent even with consent updates\n allow_google_signals: false,\n allow_ad_features: false\n});","clientLogLevel","warn","newsletterEnabled","contactFormProtectionEnabled","routes/toolkit/items.$slug",{"_47":48,"_103":104,"_105":-7,"_99":100,"_66":67,"_106":28,"_107":8,"_7":8,"_108":109,"_110":111,"_112":113,"_202":28,"_203":8,"_204":205,"_206":-7,"_207":208},"item",{"_49":50,"_51":52,"_32":53,"_54":55,"_65":23,"_66":67,"_68":8,"_69":23,"_70":71,"_72":8,"_73":74,"_75":76,"_93":23,"_94":95,"_96":-7,"_97":-7,"_98":-7,"_99":100,"_101":102},"id","32ca80b7-1924-8074-90a1-e361b7b15d96","title","AI Governance for Professional Project Managers","scroll","tags",[56,57,58,59,60,61,62,63,64],"ai","career","agile","pmo","vmo","delivery","continuousimprovement","project","projectmanagement","path","status","Published","hasValidUrl","publishedLinkUrl","slug","ai-governance-basics-for-professional-project-managers","featured","sortDate","2026-03-23","description",[77],{"_32":78,"_78":79,"_82":83,"_91":80,"_92":-5},"text",{"_39":80,"_81":-5},"Project Managers have always assessed and managed risk, the new world of AI changes many things, and many established practices and principles for PMs still apply.","link","annotations",{"_84":8,"_85":8,"_86":8,"_87":8,"_88":8,"_89":90},"bold","italic","strikethrough","underline","code","color","default","plain_text","href","embeddedContent","format","Scroll","epubUrl","pdfUrl","heroMedia","visibility","public","discoverability","discoverable","blocks",[],"firstContentImageUrl","canViewContent","authed","authors",[],"tableOfContents",[],"relatedItems",[114,144,155,168,174,180,188,196],{"_49":115,"_51":116,"_70":117,"_94":118,"_119":23,"_120":121,"_54":122,"_66":67,"_99":100},"252a80b7-1924-80a2-b468-d8181eb02349","A Sample of Our Values Based Consulting Book","values-based-consulting-book-lets","FieldGuide","publishedLink","commonTags",[57,58,59,60,62],[123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143],"Career","Agile","Pmo","Vmo","Continuousimprovement","Management","Culture","Communication","Teamwork","Conflict","Collaboration","Product","Growth","Prompts","Governance","Compliance","Leadership","Outcomes","Alignment","Planning","Dependency",{"_49":145,"_51":146,"_70":147,"_94":118,"_119":23,"_120":148,"_54":149,"_66":67,"_99":154},"24ea80b7-1924-8002-a971-e75810837887","GenAI for Agile Delivery Teams","genai-agile-delivery-teams",[56,58,59,60,61],[150,124,125,126,151,152,153,134,136],"Ai","Delivery","MachineLearning","Scrum","public-with-auth",{"_49":156,"_51":157,"_70":158,"_94":118,"_119":23,"_120":159,"_54":160,"_66":67,"_99":100},"24ea80b7-1924-8015-9930-e8310c535331","KPIs, OKRs, Goals and Alignment Support with GenAI","genai-support-okrs-kpis-goals",[58,59,60,63,64],[124,125,126,161,162,163,164,165,140,141,166,167],"Project","Projectmanagement","Kpi","Workforce","Goals","Scaling","Portfolio",{"_49":169,"_51":170,"_70":171,"_94":118,"_119":23,"_120":172,"_54":173,"_66":67,"_99":154},"24ea80b7-1924-807f-a75e-f3352d813c9b","Cross-Team Coordination and Dependency Management","genai-coordination-dependency-management",[58,59,60,61],[124,125,126,151,130,133,143,166,134,136,131],{"_49":175,"_51":176,"_70":177,"_94":118,"_119":23,"_120":178,"_54":179,"_66":67,"_99":154},"24ea80b7-1924-80e9-9246-d0d69019d9e7","Adaptive Governance and AI-Supported Decision Making","adaptive-governance-ai-decision-making",[56,59,60],[150,125,126,137,138,166,136],{"_49":181,"_51":182,"_70":183,"_94":95,"_119":23,"_120":184,"_54":185,"_66":67,"_99":100},"32da80b7-1924-80cc-85ee-ce803771d815","Agile + Product + Tech for AI-Enabled Delivery","ai-agile-dev-scroll",[58,61,62],[124,151,127,134,186,187,133],"Development","Kaizen",{"_49":189,"_51":190,"_70":191,"_94":192,"_119":23,"_120":193,"_54":194,"_66":67,"_99":100},"299a80b7-1924-80ae-add4-ffdf1999c5f2","AI Enhanced Career Management for Project and Portfolio Managers","AI-enhanced-career-management-for-professional-project-managers","Handout",[56,57],[150,123,129,195,136,135],"Guide",{"_49":197,"_51":198,"_70":199,"_94":118,"_119":23,"_120":200,"_54":201,"_66":67,"_99":154},"24ea80b7-1924-8070-af1d-f79a37736cd2","AI-Augmented Decision Support for Agile Leaders","genai-agile-leader-support",[56,61,62],[150,151,127,136,139,134,186,142,128],"fieldGuideDescriptionEnabled","fieldGuideContentHidden","scrollHtmlContent","\n\n\nAI Governance for Project Management Professionals\n\n\n\n

\n \n

AI Governance Isn't A New Discipline. It's Your Discipline Applied To New Risks.

For Project Management Professionals

\n\n

\n \n Why This Matters Now\n

\n\n

\n 63%\n Organizations lack clear AI accountability\n

\n 40%\n Lower settlement costs with documented review\n

\n 90\n Days to implement basic governance\n

\n 3\n Places AI can show up in your projects\n

\n\n

AI failures rarely announce themselves. Most begin as productivity wins and reveal their impact only after decisions have been made, commitments delivered, or trust affected.

\n\n

Federal Court Sanctions

Domain 1 Impact: Attorneys submitted legal filings containing nonexistent court cases generated by AI. The PM equivalent: a deliverable with fabricated references that looked legitimate.

PM Accountability: Could you defend this output if challenged? Was validation required before delivery?

\n\n

AWS AI Agent Outage

Domain 2 Impact: AI coding agent with excessive permissions bypassed approval workflows, triggering configuration errors. The PM equivalent: team tools making changes without review gates.

PM Accountability: Do you know what AI tools your team is using? Are review mechanisms in place?

\n\n

Retail AI Chatbot

Domain 3 Impact: Home-improvement retailer's AI gave instructions for electrical work requiring licensed professionals. The PM equivalent: product behavior creating liability exposure.

PM Accountability: Who owns the AI decision when it produces harmful guidance? Was this tested?

\n\n

Project managers are on the front lines of accountability. This is not theoretical. This is happening now.

\n\n

\n \n The PM's Job Doesn't Change\n

AI doesn't create a new profession. It creates new risk categories inside the one already held.

\n \n

Risk Management

Schedule, cost, resource, stakeholder risk. AI adds to this list. The Federal Trade Commission has made clear: businesses remain fully accountable for AI-assisted claims and representations.

\n \n

Accountability

AI tools don't share responsibility. Responsibility follows existing roles. Documentation of human review reduced settlement severity by over 40% compared to cases with no review trail.

\n \n

Governance

Projects are already governed. AI governance is the same discipline applied to new domains. It's everyday ownership of decisions, outputs, and consequences.

\n\n

\n \n Three Ways AI Affects Your Projects\n

\n \n

AI doesn't require a new role. It requires understanding three distinct risk categories already familiar to PMs: deliverable accountability, team process oversight, and product quality assurance.

\n \n

Domain 1: AI You Use

\n Your deliverables. Your signature. Your accountability.\n \n

This is where most failures start. A status report drafted by AI. A client email that sounds polished. A risk summary that feels complete. The output looks finished, reads professionally, and arrives fast.

\n \n

The Problem: AI doesn't generate verified content. It generates plausible content. When those two things look identical, the difference disappears.

\n \n

PM Accountability Question: Can you defend this deliverable if challenged? What did you verify?

\n \n

What This Means:

Every draft is exactly that: a draft requiring validation
Speed gains evaporate when errors reach clients or leadership
The name on the deliverable owns the outcome, not the tool that created it

\n\n

Domain 2: AI Your Team Uses

\n The tools in your delivery process, whether sanctioned or not.\n \n

Code generation. Design mockups. Test automation. Data analysis. These tools are already embedded in workflows, often without formal approval or oversight.

\n \n

The Problem: AI-generated work can introduce defects that pass initial review. A security vulnerability hidden in clean-looking code. IP concerns from training data sources. Automated actions that modify production systems without human checkpoints.

\n \n

PM Accountability Question: Do you know what AI tools your team is using? Are review mechanisms in place?

\n \n

What This Means:

Cannot govern what cannot be seen—visibility comes first
Review mechanisms must exist even when the PM isn't the reviewer
Risk register must reflect AI-assisted delivery, not just project constraints

\n\n

Domain 3: AI in the Product Being Built

\n When AI is the feature, not just the accelerator.\n \n

This is where traditional PM assumptions break down. Testing strategies built for deterministic systems fail against probabilistic behavior. A model that works at launch may drift over time as data patterns shift.

\n \n

The Problem: Same input doesn't guarantee same output. Edge cases multiply. Bias isn't always visible in testing. Post-launch monitoring becomes mandatory, not optional.

\n \n

PM Accountability Question: Who owns the AI decision when it fails? Was accountability defined before launch?

\n \n

What This Means:

Testing must address probabilistic behavior, not just pass/fail scenarios
Model drift and monitoring belong in handoff documentation from day one
Accountability for AI-driven decisions must be defined before launch, not after incidents

\n\n

\n \n Domain 1: How AI Actually Fails\n

\n \n

Generative AI rarely fails in dramatic ways. Most failures begin as productivity wins and reveal their impact only after decisions have been shaped, commitments made, or trust affected.

\n\n

\n \n

Hallucinations and Confident Error

NIST identifies this as a core risk: systems produce false or misleading information that appears credible. Confident and wrong is a known characteristic, not an edge case. Errors look like finished documents.

\n\n

\n \n

Context Misuse and Scope Drift

AI is applied beyond original intent. Output created for internal convenience becomes external-facing without review. Scope drift happens because reuse feels efficient.

\n\n

\n \n

Over-Reliance and Skill Atrophy

Stanford research shows people consistently overestimate reliability of fluent AI outputs. When AI output becomes the default, review gets lighter. Errors compound.

\n\n

\n \n Every AI Output Is A Draft.
\n The Name On The Deliverable Owns The Deliverable.
\n The Tool Doesn't.\n

\n\n

\n \n Domain 2: AI Your Team Uses\n

\n \n

Quality Risk

AI-generated code can introduce defects, vulnerabilities, and maintainability problems that look fine on first pass. The PM must ensure qualified review exists and is expected.

\n \n

IP Risk

AI-generated work may incorporate training data material that's difficult to trace. Creates legal exposure, especially on projects with strict IP requirements or in regulated industries.

\n \n

Security and Operational Risk

AI automation tools can execute actions and modify infrastructure. An unreviewed automated action can create real operational disruption. These are risk events, not just delivery problems.

\n\n

\n \n Four Questions Every PM Should Be Able to Answer\n

Where is AI being used in the delivery process?
What review mechanisms exist for AI-generated artifacts?
Is team AI use documented anywhere?
Does leadership know the scope of AI use on this project?

These are not gotcha questions. They are basic project hygiene in 2026.

\n\n

\n \n Domain 3: AI in the Product\n

Where Traditional PM Assumptions Break Down

\n \n

Testing Challenge

Traditional testing assumes deterministic behavior: same input, same output. AI is probabilistic. Outputs vary, edge cases multiply, behavior evolves. Testing strategy must reflect this reality.

\n \n

Model Drift

AI models can degrade as the data environment shifts. A system that performs well at launch may behave differently six months later. Model drift belongs on the risk register.

\n \n

Bias and Fairness

Training data carries historical biases. An AI system used for decisions can produce unfair outcomes even when no one intended that. The PM must ensure this is surfaced and governed.

\n\n

\n \n PM Responsibilities for Domain 3\n

Ensure testing strategies address probabilistic behavior, not just pass/fail deterministic checks
Include model drift and post-release monitoring in the risk register and handoff documentation
Ensure stakeholders understand what the system can and cannot do
Define accountability for AI-assisted decisions before go-live
Make post-deployment monitoring a planned deliverable, not an afterthought

\n\n

\n \n The Three Pillars of AI Governance\n

\n \n

Three pillars address the three domains. Business Alignment ensures AI solves real problems. Data Discipline controls what goes in and out. Risk & Ethics ensures responsible outcomes.

\n \n

Business Alignment

Connect AI use to measurable outcomes. Use case first, tool second. Reject AI where business purpose is unclear.

\n \n

Data & Tool Discipline

Define data boundaries. Prohibit sensitive inputs. Standardize on approved tools. Default: AI outputs are inputs to human work.

\n \n

Risk, Ethics & Adoption

Match oversight to impact. Define review steps before reliance. Permit escalation without penalty. Ensure responsible outcomes.

\n\n

\n \n 90-Day Governance Strategy\n

\n \n

Small organizations succeed by treating governance as an everyday operating discipline, not a maturity model or transformation initiative. Start with real work.

\n\n

Phase 1: Explore & Align
(Days 0-30)

Make current AI use visible across the organization
Identify 3-5 candidate use cases rooted in actual workflows
Evaluate across Business Value, Data Feasibility, Risk Exposure
Assign named owner for overall AI use and outcomes
Align early AI use to real business priorities

\n Done Looks Like:\n

Named owner, approved use case list, one-page charter outlining scope and objectives, first-pass acceptable use policy, red-flag data zones documented

\n\n

Phase 2: Design & Prototype
(Days 31-60)

Select priority AI use case to move forward
Define success measures and guardrails
Test small-scale prompts using low/no-code tools
Design workflows, review points, and acceptable use
Build lightweight, testable prototype with governance built in

\n Done Looks Like:\n

Working prototype for one use case with logging, reviewer routing, stop-rules, and prompt QA/review loops established

\n\n

Phase 3: Pilot & Evaluate
(Days 61-90)

Run controlled pilot with small group to gather real-world data
Monitor outcomes, quality, and risk using qualitative and quantitative data
Assess impact against targets, including unintended byproducts
Capture lessons from real-world use
Decide whether to scale, refine, or stop based on evidence

\n Done Looks Like:\n

Evidence-based decision to expand, refine, or stop. Policies updated based on learnings. Review cadence and ownership set for ongoing operation.

\n\n

\n \n Four Things to Do Before End of Week\n

\n \n

\n \n Start with visibility\n

Ask the team this week: where is AI being used?
Frame it as a planning conversation, not an audit
Cannot govern what cannot be seen
Start with use cases, not tools

\n\n

\n \n Name one owner\n

On every project, one person owns AI governance decisions
In a small team, that's often the PM. Make it explicit.
Assign ownership at both organization and use case level
Same person may hold multiple roles, but functions must still exist

\n\n

\n \n Create one use case charter\n

One page: task, who's authorized, what data can be used, what review is required, who can stop it
This is the unit of governance, not a policy manual
Include purpose, scope, allowed/prohibited inputs, required review, known limitations, named owner
This becomes the reference model for future use cases

\n\n

\n \n Add AI risk to the register\n

At minimum: accuracy risk, data exposure risk, model behavior risk if delivering an AI-enabled product
Identify who could be harmed if output is wrong or biased
Define where speed may conflict with accuracy or fairness
Define clear stopping conditions and escalation triggers
It's a real risk. Treat it like one.

\n\n

\n \n

Three Things Worth Remembering

Risk management discipline is the right foundation. AI doesn't require a new professional identity. It requires applying what's already known to new risk categories.

AI shows up in three places, and each demands a different governance response. Most failures begin as productivity wins.

A policy manual is not needed to start. One charter and one honest conversation with the team is needed.

\n\n

\n \n Learn More\n

For a comprehensive guide to AI governance implementation:

\n Getting Started with AI Governance: The Field Guide for Small Businesses
\n by John Halberstadt and Steve Daniel
\n En Dash Consulting, 2026\n

\n \n \n \n View on Amazon\n \n \n

\n\n","scrollScripts","__cacheKeys",{"_12":209,"_14":221},[210,215,218],{"_211":212,"_213":214},"label","Page","key","toolkit:ai-governance-basics-for-professional-project-managers",{"_211":216,"_213":217},"Post","post:32ca80b7-1924-8074-90a1-e361b7b15d96",{"_211":219,"_213":220},"Blocks","post:32ca80b7-1924-8074-90a1-e361b7b15d96:blocks",[],"actionData","errors"]

AI Governance Isn't A New Discipline. It's Your Discipline Applied To New Risks.

\n \n \n !\n \n Why This Matters Now\n

Federal Court Sanctions

AWS AI Agent Outage

Retail AI Chatbot

\n \n \n \n \n \n The PM's Job Doesn't Change\n

Risk Management

Accountability

Governance

\n \n \n \n \n \n Three Ways AI Affects Your Projects\n

Domain 1: AI You Use

Domain 2: AI Your Team Uses

Domain 3: AI in the Product Being Built

\n \n \n 1\n \n Domain 1: How AI Actually Fails\n

Hallucinations and Confident Error

Context Misuse and Scope Drift

Over-Reliance and Skill Atrophy

\n \n \n 2\n \n Domain 2: AI Your Team Uses\n

Quality Risk

IP Risk

Security and Operational Risk

\n \n \n ?\n \n Four Questions Every PM Should Be Able to Answer\n

\n \n \n 3\n \n Domain 3: AI in the Product\n

Testing Challenge

Model Drift

Bias and Fairness

\n \n \n \n \n PM Responsibilities for Domain 3\n

\n \n \n \n \n \n The Three Pillars of AI Governance\n

Business Alignment

Data & Tool Discipline

Risk, Ethics & Adoption

\n \n \n 90\n \n 90-Day Governance Strategy\n

Phase 1: Explore & Align(Days 0-30)

Phase 2: Design & Prototype(Days 31-60)

Phase 3: Pilot & Evaluate(Days 61-90)

\n \n \n \n \n Four Things to Do Before End of Week\n

\n \n \n \n \n \n Start with visibility\n

\n \n \n \n \n Name one owner\n

\n \n \n \n \n Create one use case charter\n

\n \n \n !\n \n Add AI risk to the register\n

Three Things Worth Remembering

\n \n \n \n \n Learn More\n

\n \n Why This Matters Now\n

\n \n The PM's Job Doesn't Change\n

\n \n Three Ways AI Affects Your Projects\n

\n \n Domain 1: How AI Actually Fails\n

\n \n Domain 2: AI Your Team Uses\n

\n \n Four Questions Every PM Should Be Able to Answer\n

\n \n Domain 3: AI in the Product\n

\n \n PM Responsibilities for Domain 3\n

\n \n The Three Pillars of AI Governance\n

\n \n 90-Day Governance Strategy\n

Phase 1: Explore & Align
(Days 0-30)

Phase 2: Design & Prototype
(Days 31-60)

Phase 3: Pilot & Evaluate
(Days 61-90)

\n \n Four Things to Do Before End of Week\n

\n \n Start with visibility\n

\n \n Name one owner\n

\n \n Create one use case charter\n

\n \n Add AI risk to the register\n

\n \n Learn More\n

Related Items

A Sample of Our Values Based Consulting Book

GenAI for Agile Delivery Teams

KPIs, OKRs, Goals and Alignment Support with GenAI

Cross-Team Coordination and Dependency Management

Adaptive Governance and AI-Supported Decision Making

Agile + Product + Tech for AI-Enabled Delivery

AI Enhanced Career Management for Project and Portfolio Managers

AI-Augmented Decision Support for Agile Leaders