Generative AI is reshaping how complex programmes are planned, delivered, and governed. This page sets out my practical understanding of GenAI — what it can do for project managers, how I apply it across the delivery lifecycle, and how I manage its limitations.
Generative AI learns patterns from vast datasets and produces original content — text, images, code, and data analysis — from a simple natural-language prompt. Unlike traditional AI that classifies existing data, GenAI creates new content grounded in contextual understanding.
For project and programme managers, this is transformative: complex deliverables that once took hours — charters, RAID logs, stakeholder communications, status reports — can now be produced as high-quality first drafts in minutes, leaving more capacity for the thinking and leadership that genuinely requires human judgement.
The key is using GenAI as an accelerator, not a replacement. The PM's role becomes one of directing, validating, and refining AI outputs — and knowing when not to rely on them.
Discriminative AI: "Is this project on track or not?"
Generative AI: "Draft a corrective action plan for a programme running 3 weeks behind schedule, with a fixed go-live date and an executive steering committee meeting next week."
From initiation through close-out, GenAI reduces administrative overhead and sharpens delivery quality across every phase.
Status reports, RAID logs, meeting summaries, and project charters produced in minutes rather than hours — freeing capacity for stakeholder management and decision-making.
Stakeholder emails, change-request memos, and board updates drafted and tailored to any audience, maintaining consistent tone across a complex multi-stakeholder programme.
WBS structures, sprint backlogs, milestone charts, and risk registers generated on demand — giving the team a solid baseline to refine rather than a blank page.
Alternative approaches, edge-case scenarios, and risk identification surfaced rapidly — useful in programme recovery situations where speed of diagnosis matters.
Project data consolidated and analysed faster than manual methods allow, enabling evidence-based decisions with stakeholders before positions have hardened.
RAID logs generated, likelihood and impact assessed, and mitigation strategies proposed across all 10 PMBOK knowledge areas — including risks that might otherwise be missed.
Complex, multi-workstream programmes handled without proportional increases in team overhead — particularly valuable in lean contract and consulting engagements.
Administrative and documentation burden redirected to AI, so the PM's time goes where it counts: stakeholder trust, risk judgement, and commercial negotiation.
How I apply Generative AI at each stage of a programme — from initiation through close-out.
Successful AI integration in a complex programme requires more than selecting a tool. These are the principles I apply.
AI integration must be grounded in the programme charter. Define where AI adds value, align it to strategic KPIs, and include it explicitly in the requirements — not as an afterthought.
Infrastructure maturity, data availability, and cultural readiness all determine how quickly AI can be embedded. Rushing deployment ahead of readiness creates more risk than it removes.
Identify stakeholders who understand AI capabilities and assign clear ownership. AI integration without governance is a scope and quality risk like any other.
Apply SMART criteria to all AI objectives. Stakeholders need to understand both what AI can do and what it cannot — unrealistic expectations are a leading cause of AI programme failure.
Embed AI tasks as formal work packages in the WBS and network diagram. Track AI integration milestones on the schedule — if it isn't tracked, it won't be delivered.
AI deliverables must pass the same acceptance criteria as any other. Test outputs against requirements, gather stakeholder feedback, and don't close out until scope is fully verified.
A selection of the prompts I apply in day-to-day programme work. Click any prompt to copy it.
Draft a project charter for [Project Name]. Include: goals, success criteria (SMART), scope in/out, assumptions, constraints, key milestones, roles, stakeholders, and a 1-page executive summary.
Generate a RAID log for [Project Name] with 8 entries. Fields: ID, Type (Risk/Assumption/Issue/Dependency), Likelihood, Impact, Owner, Trigger, Mitigation, Status.
Write a stakeholder update email to [CIO / Steering Committee] for [Project Name]. Include: current status, top 3 risks, decisions required from leadership, and the 2-week plan. Keep it under 300 words.
Generate a planned vs. actual progress report for [Project Name] up to [Date]. Include corrective action recommendations for any variances over 10%.
Prepare a Change Request summary for [Change Description]. Include: rationale, business value, scope/schedule/cost impact, risks, affected stakeholders, and a recommendation (Approve/Reject/Defer).
Create a lessons-learned document for [Project Name]. Cover: what went well, what to improve, root causes of issues, and recommendations for future projects.
Effective use of GenAI requires clear-eyed awareness of where it falls short — and governance structures to manage that in a programme context.
AI models can produce factually incorrect content — including hallucinated references and figures — which can undermine credibility if outputs aren't validated before use.
Inputting sensitive programme data — commercial terms, personal data, IP — into public AI tools creates significant GDPR and confidentiality risks that are often underestimated.
GenAI cannot generate truly novel ideas beyond its training data. It excels at synthesising and accelerating existing knowledge, not at the creative leaps that often define programme-level breakthroughs.
The AI regulatory landscape — EU AI Act, sector-specific rules, evolving data protection law — is moving quickly and creates compliance risk for programmes that don't account for it.
AI tools and capabilities are evolving at a pace that makes today's integration decisions potentially obsolete within months — creating technical debt risk in longer programmes.
Connecting AI tools to existing enterprise systems — ERP, PMIS, data warehouses — is non-trivial and requires the same architecture discipline applied to any major systems integration.
My GenAI capability has been developed through formal study alongside active application to programme delivery work.
A strategic reference guide for structuring large language model interactions to navigate complex technology delivery. Click any prompt block to copy it.