IPM CPM Level 1
IPM-AI
hamburger__close
Most of the conversation about AI in project environments starts and ends with productivity. Faster reporting, automated status updates, and instant draft plans. All of that is real, and I have benefited from it. But after more than a decade leading delivery teams, first in regional technology programmes and, more recently, managing a payments portfolio across three markets, I have come to believe the more interesting story isn’t about speed at all. It is about culture. AI is changing how project teams collaborate, build trust, and how the next generation of project leaders will learn their craft. Those shifts will determine whether AI integration succeeds, far more than the tools themselves.
Here is a scene I have lived more than once. A planning session is scheduled. In the past, the team would come up with ideas, argue over dependencies, sketch different options on a whiteboard, and walk out tired but aligned. Today, someone arrives with a polished, AI-generated plan already in hand. It looks complete. It is complete, in a technical sense. And yet something subtle gets lost: the room shifts its goal from co-creating a solution to reviewing one.
That distinction matters a lot more than it sounds. The workshops, planning increments, and problem-solving sessions that consume so much of a delivery manager’s calendar were never only about producing artefacts. They were how a group of individuals became a team with shared understanding. When the artefact arrives pre-made, the decision may come faster, but the alignment behind it can lag weeks behind. I have observed teams nod through a review of an AI-drafted roadmap, only to discover during execution that nobody had truly internalised the trade-offs it contained.
The lesson for project leaders is not to reject AI-generated inputs. It is to treat them as a starting point for discussion to build on, rather than a substitute. Automation can prepare the conversation; it should not replace it.
Trust has always been the backbone of delivery. High-performing teams run on transparency, accountability, and confidence in each other’s work. AI, however, introduces a new variable into that equation: content with an ambiguous origin.
When a specific recommendation lands in a steering committee deck, stakeholders increasingly ask a question that did not exist five years ago: who actually stands behind this? Was it subject matter expert judgement, or a language model’s pattern-matching? The question is entirely fair. Gartner has forecast that by 2030, around 80 percent of traditional project management tasks data collection, tracking, and reporting could be handled by AI, directing the project manager’s role decisively towards leadership, judgement, and stakeholder work (Gartner, 2019). PwC’s broader research on automation aligns with the idea that routine, data-driven tasks are the most exposed, while roles built on human relationships are the most durable (PwC, 2018).
In my experience, this does not erode trust so much as relocate it. Stakeholders no longer extend confidence to a document because it looks rigorous; they extend it to the person who can defend it under questioning. Leaders therefore need explicit norms: AI may draft, but a named individual owns the outcome. Every analysis, every forecast, every recommendation needs a human signature behind it someone prepared to explain the reasoning, not just present the output.
The change I worry about most is the slowest one to show itself. Project professionals have traditionally developed judgement the hard way through difficult stakeholders, failed estimates, recovery plans written at midnight, and mentors who asked uncomfortable questions. AI now offers a shortcut around much of that friction. Need a risk register? Generated in seconds. A communication plan? Done before the coffee is poured.
Speed, however, is not mastery. Systematic reviews of AI adoption in project management note that while these tools can improve forecasting and support risk identification, their application remains uneven and immature across the discipline, and over-reliance carries real risks for professional judgement (Bento, Pereira, Gonçalves, Dias & da Costa, 2022). In project environments, the defining challenges are rarely informational. They are ambiguous: a sponsor whose stated priority contradicts their behaviour, two teams who both believe the other owns a dependency, an executive decision that changes scope mid-increment. No generated document resolves those situations. Judgement does.
If junior professionals spend their formative years enhancing AI outputs rather than wrestling with messy problems, the industry will eventually feel the gap. Developing future leaders will require deliberately preserving struggle: assigning thorough analysis before allowing generation, running retrospectives that interrogate decisions, and creating more room for reflection rather than only acceleration.
If the risks above sound like an argument against AI, they are not. They are an argument against ad hoc AI use deciding in the moment, under deadline pressure, whether to hand a task to a machine. The teams I have seen extract genuine productivity from AI share one important habit: they decide the boundaries of delegation before anyone opens a prompt window.
Recent practitioner thinking has crystallised this into what is now called the AI Agile Framework: Assist, Automate, Avoid, which categorises work before AI is involved at all (Wolpers, 2026). In Assist mode, AI helps to generate drafts and options while the human retains full decision authority; the value is in expanding thinking, not replacing it. In Automate mode, AI executes repeatable tasks end-to-end: meeting summaries, action-item extraction, release-note drafts under explicit rules, human checkpoints, and regular audits. This is where the real productivity gains live, and leaders should pursue them deliberately rather than apologetically: freeing a delivery manager from an hour of status compilation each day is an hour returned to stakeholder work and coaching. In Avoid mode, certain work stays entirely human: performance feedback, conflict mediation, sensitive stakeholder communication, because the cost of a miscalibrated message is trust, and trust does not regenerate on a sprint cadence.
What makes this discipline powerful is not the categories themselves but the conversation they enable. When a team shares a vocabulary for delegation, suspicion (‘did you actually write this?’) gives way to norms (‘acceptance criteria are Assist, always human-reviewed; escalations are Avoid, no exceptions’). This also lets the approach travel across cultural contexts. Having led delivery teams across several markets, I have seen how differently teams relate to hierarchy, disagreement, and the visibility of individual work. A team in one culture may challenge an AI-generated plan openly in the room; a team in another may stay silent in the meeting and raise concerns privately afterwards. A framework that makes delegation boundaries explicit, rather than leaving them to unspoken assumptions, gives every team, whatever its communication style, a legitimate and non-confrontational way to negotiate how AI is used. The categories are universal; the norms within them are local. That combination is precisely how AI aids productivity across culturally different teams without flattening their differences.
Drawing these threads together, a few practical commitments stand out for anyone leading delivery through this transition. Make AI delegation explicit: agree as a team, in advance, which work AI may draft, which it may execute under audit, and which stays human. Prioritise alignment over speed, because a fast decision without shared understanding defers conflict. Invest more, not less, in facilitation, since workshops and planning events are now the primary venue for building genuine commitment. Encourage teams to challenge AI recommendations rather than accept them at face value, and make that challenge visible and rewarded. Keep accountability unambiguous: a person, not a tool, owns every deliverable. And finally, measure team health alongside efficiency; engagement, collaboration quality, and predictability tell you more about long-term delivery capability than throughput ever will.
AI is reshaping project work at a pace none of us fully anticipated. Yet the fundamentals of successful delivery have not moved: trust, collaboration, accountability, and leadership remain the deciding factors. The organisations that thrive will not simply be the ones with the most advanced tooling. They will be the ones that absorb the technology while protecting the human connections that make delivery work. For project professionals, the assignment has expanded: we are no longer only managing projects through change, but guiding our organisations through the human consequences of that change, while continuing to deliver outcomes that matter.
