All Courses
Upcoming Course Dates
Professional Courses
Academy & Short Courses
IPM Courses
PMI® Courses
IPMA Courses
PRINCE2 Courses
Corporate Training
Corporate Partnership
University Partnership
Strategic Partnership
IPM Competency Pathway
Growth Partner
View More Academy Course
IPMA Certification
PMI® Certification
IPM CPM Level 1
IPM CPM Level 2
IPM CPM Level 3
IPM-AI
IPM-Sustainable
IPM-SCRUM
IPM-PMO
IPM-AGILE
IPM-ASSOCIATE
About IPM Hub
IPM Membership
EMEA Monthly Events
Mentorship
All Resources
Expert Insights
Ebooks & Toolkits
Publish Your Writing
IPM Jobs Portal
The Institute
Our Team & Faculty
Global Advisory Board
Apply to Lecture or Volunteer
Apply to Intern or Campus Ambassador
Speak to an Advisor
hamburger__close
AI has moved from boardroom talking point to everyday project tool. McKinsey’s 2025 State of AI survey found that 88% of organisations now use AI in at least one business function, yet few have scaled it in a way that moves the bottom line. The gap between using AI and benefiting from it is where AI readiness comes in.
For project managers, that gap is personal. You are the one asked to roll out the tool and show results, and weak foundations turn AI into another source of rework.
This month’s Data Digest looks at what it really takes. Across eight LinkedIn polls in September, we asked our community where their teams stand and what worries them most. Here is what they told us, alongside the wider research.
AI readiness is a project team’s ability to adopt AI tools in a way that improves delivery, safely and consistently. It covers the processes AI plugs into, the data it relies on, the skills of the people using it and the culture that decides whether anyone trusts the output.
A ready team knows which tasks AI should support, which it should not, and who checks the results. An unready team has the same tools but uses them ad hoc, with no shared rules and no way to tell whether they are helping.
Our community sits firmly in the middle of that journey. When we asked teams to describe their AI readiness, Building Basic AI Skills and Using AI in Some Tasks tied at 30% each. Most teams, in other words, are past curiosity but not yet at full integration.
Skipping readiness is expensive. Gartner predicts that through 2026, organisations will abandon 60% of AI projects that are not supported by AI-ready data. The technology rarely fails on its own; it fails because the inputs, processes or people around it were not prepared.
Readiness also protects the outcomes you are measured on. Confident but wrong AI estimates can damage a schedule faster than no AI at all.
There is a career angle too. PMI’s research found that roughly two in five project professionals already use generative AI in more than half of their project work. As our look at artificial intelligence in project management explores, PMs who lead adoption well are becoming the ones organisations rely on.
AI amplifies whatever process it touches. Clear, consistent workflows get faster; messy ones produce messy results faster. McKinsey found that redesigning workflows has the strongest link to real business impact from AI of any factor it tested.
That makes our second poll a useful reality check: 42% of respondents said their project workflows are still Mostly Manual Processes. That is not a failure. It is a signal that the first job is to document and standardise how work flows before automating any of it.
AI is only as good as the data it draws on, and project data is often scattered across spreadsheets, email threads and tools that do not talk to each other. Gartner’s survey found that 63% of organisations lack, or are unsure they have, the right data management practices for AI. Before adopting anything, agree where project data lives, who owns it and what must never be shared with an external tool.
Tools do not create value; people using them well do. When we asked which AI skill would benefit project teams most, Writing Effective Prompts came out on top with 39%. A clear prompt with the right context, as our guide to what ChatGPT can do for project management shows, is the difference between a usable risk register draft and generic filler. Prompting is only the start, though: teams also need to evaluate outputs critically and apply AI responsibly.
The newest tool is not always the right one. A clear majority of our community, 55%, said Project Requirements should guide the choice of AI tools. Start from the problem, such as faster status reporting or better risk identification, and work back to the tool. Our round-up of AI project management tools is a good place to compare options.
Even well-chosen tools stall without buy-in. Treat AI adoption as a change project: explain the why, involve the team early and make it safe to experiment and to say when something is not working.
If two or more of these sound familiar, strengthen the foundations before scaling up.
Our community was clear on where to begin: 60% said Review Current Workflows. Map how work actually moves through your project, including handovers, approvals and reports, and mark the repetitive, rules-based steps. Those are your best AI candidates. Then check the data and skills behind them.
Build a simple skills baseline, then offer practical training tied to real tasks, such as drafting a project brief or summarising stakeholder feedback. Pair confident users with newer ones so learning spreads naturally.
Before you sign off on a tool, decide what success looks like. Expected Outcomes topped our poll on what to evaluate before adopting an AI tool, at 38%. Weigh that alongside business fit, integration with your existing systems and data security. A tool that cannot meet your security rules is not the right tool, however impressive the demo.
Pick one workflow, one team and four to six weeks. Low-risk, high-frequency tasks such as meeting summaries or status report drafts work well. A focused pilot gives you real evidence and exposes problems while they are still cheap to fix.
User Adoption was our community’s most popular measure of progress, at 38%. Adoption matters, but it is a leading indicator, not the finish line. Pair it with time saved, output quality and process efficiency so you can see whether AI is genuinely improving delivery. Review each pilot, adjust, then scale.
The strongest response this month came on pitfalls: 52% of voters named Trusting Outputs Blindly as the biggest AI adoption risk for project teams. AI can produce fluent, confident answers that are simply wrong, so build human review into every workflow where AI output informs a decision. Our article on statistical debt in AI explains why this hidden risk grows over time.
Three other pitfalls to watch:
It is a team’s capability to adopt AI tools effectively and safely, combining mature workflows, reliable data, AI-literate people, the right tools and a culture open to change.
Most teams can complete an assessment and a first pilot within two to three months. Staying AI-ready is ongoing, because tools, skills and risks keep evolving.
Yes. Smaller teams often feel the benefits faster, because AI takes on admin work that would otherwise fall on a few people. The same foundations apply: clear processes, sensible data rules and someone checking the outputs.
AI readiness is not about racing to adopt the latest tool. It is about building the processes, data habits, skills and culture that let AI genuinely improve delivery. Our community agrees: most teams are still building foundations, would start by reviewing workflows, and worry most about trusting AI without checking it.
That is exactly the ground the IPM AI Project Professional course covers. You will learn to apply AI across every project stage, from planning and risk management to reporting, while keeping the human judgement that makes projects succeed. Explore the IPM AI Project Professional course and take the next step towards leading an AI-ready team.
