AI is showing up in every conversation about project delivery right now. Teams are being asked to move faster, reduce manual work, and make better decisions with limited time and resources. That pressure is real. So is the temptation to throw AI at every problem and hope it creates instant efficiency.
But speed by itself is not the goal.
When AI is introduced without a clear purpose, it can create more noise, more steps, and more confusion. The real opportunity is not to use AI everywhere. It is to use it where it removes friction, improves planning, and helps teams make faster, smarter decisions.
“AI is not the magic pill for everything.” -Diane Buckley-Altweis
That idea sat at the center of our recent webinar, where Matthew Sparkes, Steve West, and Diane Buckley Alawi explored practical ways project teams can use AI and automation to move faster without adding unnecessary complexity.
Start with the outcome, not the tool.
One of the most important reminders from the conversation was that AI is not a strategy. It is a capability. If teams are not clear on what they are trying to improve, more technology may just accelerate the wrong work.
Before using AI in project delivery, it helps to ask a few simple questions. What are we trying to make faster? What kind of output would save time or improve clarity? Where is human judgment still essential? Where is work slowing down today?
Project teams still need process, prioritization, and a clear understanding of outcomes. AI works best when it supports those things, not when it tries to replace them.
Reduce friction in the work project managers do every day.
A practical place to begin is with the work that project managers know has to get done, but that often pulls time away from higher-value thinking.
Meeting minutes. Action items. Status updates. Portfolio narratives. Follow-up summaries. These tasks matter, but they can become a drain on time and attention if they are all being created manually.
AI can help reduce that friction.
Teams can use transcripts to generate structured meeting notes, identify actions and decisions, and surface risks more quickly. Status updates can be drafted faster. Summaries can be tailored for different audiences based on what a leadership team actually needs to know.
That does not mean the project manager steps out of the process. It means the project manager spends less time retyping information and more time validating, refining, and directing what matters.
One of the strongest points made during the webinar was that AI-generated content still needs review. A summary that gets a name wrong, assigns a task to the wrong person, or overstates a decision can create new problems just as quickly as it solves old ones.
That is why the win is not automation alone. The win is removing manual effort while keeping accountability and accuracy in place.
Use AI to strengthen planning.
Planning is another area where AI can offer real value when used thoughtfully.
It can help teams get started faster by turning a blank page into a first draft. That includes clarifying requirements, drafting a work breakdown structure, suggesting task descriptions, surfacing possible dependencies, and highlighting the likely impact of scope changes.
For project managers, that kind of jump start can save meaningful time. Instead of starting from nothing, teams can start with something, review it, improve it, and shape it around the realities of the project.
“The goal isn’t to replace what you would normally do on your own, but to just jump start it.”- Steve West
That is the right mindset.
AI is useful when it gives teams a faster starting point. It becomes less useful when it floods them with output that is too detailed, too generic, or disconnected from how the organization actually works.
A team still needs to decide how granular a task should be. It still needs to determine whether the sequence makes sense, whether a dependency is real, and whether the work belongs in the plan at all. A generated WBS may look impressive, but if it does not reflect actual delivery conditions, it is just more content to clean up later.
Planning still requires judgment. AI just helps teams get to the discussion faster.
Better decision-making is part of faster delivery.
Project work does not only slow down because of administrative effort. It also slows down because decisions take too long.
This is where automation, visibility, and AI-supported analysis can make a major difference.
When project and resource data live in one place, teams can see capacity issues, overallocations, schedule pressure, and project health in real time. That gives leaders a clearer view of what is happening before small issues become bigger ones.
Instead of spending hours gathering updates, checking spreadsheets, or chasing down resource availability, teams can move more quickly into the conversation that really matters: what needs attention, what tradeoffs exist, and what decision should be made next.
That is an important shift.
When decision-making becomes faster, teams spend less time waiting and more time executing. Project managers can focus less on collecting scattered details and more on helping stakeholders understand the impact of their choices.
This is especially valuable when organizations are trying to balance multiple priorities at once. If a new initiative is introduced, leaders need to know what that means for current work, available capacity, and expected delivery timelines. Better visibility makes that conversation faster and more grounded in reality.
Watch how Project Insight surfaces overallocations and helps teams evaluate alternate resources:
https://www.youtube.com/live/rSKyS-haZEk?t=1943
See how Project Insight highlights project health issues automatically so teams can respond faster:
https://www.youtube.com/live/rSKyS-haZEk?t=2046
What-if planning creates better leadership conversations.
One of the most powerful ideas discussed in the webinar was the role of what-if planning.
Leaders often want to move quickly on a new request. That is understandable. But every new priority has a ripple effect. It may add hours to a team that is already full. It may delay another initiative. It may require a different staffing approach. It may change the overall risk profile of a portfolio.
What-if planning allows teams to explore those tradeoffs before committing.
That changes the conversation. Instead of reacting with either resistance or blind agreement, project leaders can show what a decision would actually mean. They can help executives understand the consequences of adding work now versus later, shifting resources, or choosing between competing priorities.
That kind of decision support is where project delivery becomes more strategic.
It is not only about completing tasks faster. It is about giving leadership a clearer picture of what is possible and what each choice will cost.
Watch how Project Insight models what-if scenarios to help leaders weigh tradeoffs before committing:
AI cannot fix a broken process.
This may be the most important caution in the entire conversation.
AI can make good processes faster. It can make strong teams more efficient. It can reduce manual work and help teams move more confidently. But it cannot rescue a broken operating model on its own.
“If you have broken processes already and you throw AI on top of it, you’re not necessarily going to help yourself.” -Diane Buckley-Altweis
That line is worth sitting with.
If an organization lacks clarity, discipline, ownership, or good data, AI may simply generate faster rework. If teams are already juggling too many disconnected tools, layering on more outputs and more steps can actually make execution harder.
This is why the fundamentals still matter. Keep project plans current. Define outcomes clearly. Know the audience for each update. Maintain review and approval discipline. Understand where human judgment matters most. Make sure usage aligns with security, data, and policy requirements.
AI is not a substitute for those things. It is an amplifier.
The question is whether it is amplifying a healthy delivery process or a messy one.
Start small and prove value.
One of the most practical recommendations from the session was not to begin with a massive AI transformation effort. Begin with one use case that is easy to test and easy to evaluate.
Take one messy meeting and turn it into a usable set of decisions, actions, and risks. Turn one vague request into acceptance criteria and test cases. Generate one executive-ready project summary. Run one retrospective using AI to help identify what slowed the team down.
These are manageable experiments. They help teams see what actually saves time, what still needs human refinement, and where AI adds value without adding confusion.
That is where confidence comes from. Not from hype, but from practical results.
The real goal is not more AI. It is better delivery.
Project teams are not looking for more technology for its own sake. They are looking for ways to move faster without creating more burden. They want fewer bottlenecks, less busywork, clearer decisions, and stronger execution.
That is where AI can help most.
Used well, it reduces friction. It supports planning. It shortens the path from information to action. It helps teams focus more of their time on the work that actually drives outcomes.
But the organizations that benefit most will not be the ones that use AI everywhere. They will be the ones that use it intentionally, with discipline, and with a clear understanding of what better delivery really requires.
“Work towards getting clarity before you start.” -Steve West
That is still the best place to begin.