AI Isn't Useless In Project Management. Your Project Data Is
Why the PMs calling AI useless are diagnosing the wrong problem.
PMs are calling AI useless.
There’s a thread on r/pmp right now with dozens of replies agreeing.
They tried the tools. Got generic output. Moved on.
They gave ChatGPT a project brief and got back four paragraphs of corporate filler. They asked Copilot to summarise project status and it pulled from documents nobody’s touched since sprint two. They pointed AI at their Jira board and got a summary that missed every decision that mattered.
They’re not wrong about the experience. They’re wrong about the cause.
The complaint is valid. The diagnosis isn’t.
Every PM who’s called AI useless ran into the same wall.
They gave AI almost no context. Then expected useful output.
You open ChatGPT. Type “write me a stakeholder update for my website migration project.” Get four paragraphs of vague, boardroom-ready nothing. Close the tab. Tell a colleague AI doesn’t work for PM stuff.
That loop is real. I’ve seen it happen with PMs in my own agency. But it’s not a tool problem. It’s their input.
Context is everything if you want great results from AI tools.
The quality of what AI produces is directly tied to how much it knows about your project. Not projects in general. Your project. Your stakeholders. Your risks. Your decisions from last Tuesday.
Most PMs give it none of that. No project background. No stakeholder names. No recent decisions. No known blockers. Then they’re surprised the output reads like it was written by someone who’s never been in a standup.
Here’s the uncomfortable bit. If your project documentation is scattered, outdated, or lives in people’s heads, that was a problem before AI showed up. AI just made it impossible to ignore.
The PMs who already had decent documentation discipline? They’re getting useful outputs.
Your project knowledge isn’t where AI can reach it
Think about where your project information actually lives right now.
It’s in Teams threads from three weeks ago. Email chains between you and the client. A Confluence page someone started and never finished. Meeting notes in a Google Doc that four people can access. A RACI matrix in a spreadsheet that hasn’t been updated since sprint two.
And the most important stuff? Decisions made verbally. In a corridor. Over coffee. Never written down.
AI doesn’t know any of that.
This is why enterprise tools are struggling. Microsoft pushed Copilot into organisations from the top. No specific PM workflows. No training on what to feed it. There’s a thread on r/CopilotPro titled “No One is Using CoPilot.” Hundreds of knowledge workers with a tool they can’t get value from.
But on the same platform, someone shared 18 specific Copilot prompts for project leaders and cost controllers. Meeting prep. Cost tracking. PMO briefings. That person spent time understanding what the tool actually needs. And it’s working for them.
Same tool. Different operator.
Generic prompts produce generic outputs. Specific context produces specific value.
So what does the fix actually look like?
A project knowledge hub. One folder per project.
Everything AI needs in one place-it’s that simple!
Not a massive documentation overhaul. Not a new tool. A simple folder with all your files you probably already have in some form — just scattered across different platforms.
Here’s a starter structure:
project-brief — purpose, scope, key dates, success criteria
stakeholder-map — names, roles, communication preferences, who signs off on what
decisions-log — what was decided, when, by whom (the one everyone skips and everyone regrets skipping)
status-updates — weekly, consistent format, same place every time
meeting-notes — summarised after each meeting, stored in the hub (not buried in email)
risks-and-blockers — live document, updated weekly
You already know most of this. You just haven’t put it in one place.
Here’s the killer move. Connect AI to that folder. Point Claude, ChatGPT, or Copilot at your project hub and suddenly it has everything it needs. Stakeholder names. Recent decisions. Known risks. Current status.
The context it was missing every time you tried it before.
And here’s what makes this compound. AI helps you create better documentation — meeting summaries, status drafts, risk assessments. Better documentation makes the hub more useful.
The hub makes AI more useful. It’s a flywheel, not a one-off fix.
The PMs who fixed this are already ahead
While some PMs are writing off AI, others are building their own PM agents.
On Hacker News this month, someone launched an AI project manager that runs in the background. Another built one inside Slack that replaces Jira. On Reddit, a PM is building a custom assistant with RAG over their SharePoint project files — so it can actually answer questions about their projects using real data.
You don’t need to build your own agent. But you need to understand what they figured out.
AI handles admin work well. Scheduling. Reporting. Status summaries. Meeting prep. That’s roughly 80% of the repetitive tasks that eat your day. Most PMs are trying to use AI for the other 20% (stakeholder politics, ambiguity, motivation) and then calling it useless when it doesn’t deliver.
Point AI at the 80%. Build the knowledge hub so it can actually do it. Use the time you save for the judgment work that separates senior PMs from task trackers.
I’ve said it before. The PMs who treat AI as a shortcut to less work are standing still. The PMs who treat it as a way to do different work are the ones actually becoming senior.
The first step isn’t a better tool or a better prompt.
It’s a project folder AI can actually read.
The real fix
The divide in project management isn’t between PMs who use AI and PMs who don’t. It’s between PMs who built a knowledge hub and PMs still blaming the tool.
Spend one hour this week. Create a project folder. Add the brief, stakeholder map, and decisions log. Point AI at it. Watch what happens.
And, if this was useful, forward it to a PM who’s still calling AI useless. They need to hear this.
Speak soon,
Tim