What PMO Leaders Should Develop When AI Does the Analysis

When a project falls 3 months behind, most PMO teams can now get a decent diagnosis and a set of recovery options from an AI tool in minutes. What they rarely get, unless someone thinks to ask, is an answer to the more important question: should this be recovered at all?

We hear versions of this from portfolio leaders constantly. AI is taking on more of the reporting, coordination and initial analysis that their teams used to do, and most organizations have responded by training people on the tools. While that training is worth doing, utilizing AI tools is quickly becoming something everyone is expected to do well, so it won't distinguish one PMO from another for long.

It's not long before attending a Copilot course will feel like being sent on an Outlook training day.

A PMO that has integrated AI into every workflow but is unclear about what it is trying to decide will simply produce more analysis, faster, for decisions nobody is making. The analysis is only as good as the questions it is asked. For a portfolio team, asking better questions depends on 3 things: understanding delivery well enough to read what the data is really saying, seeing the investment question behind a project problem, and having the confidence and standing to act on the answer, even when that means telling a senior sponsor their project should stop. A team focused on how much it uses AI, rather than what it is using AI to achieve, won't build any of these by accident. PMO leaders will need to make time for them, and to back their people when the answer is unpopular.

Framing the investment question

AI is good at answering the question it is given, and in portfolio management that is often the wrong one. A project team that is behind needs to know how to recover its schedule. The portfolio team needs to know whether recovery still justifies the investment once you account for the remaining benefit, the cost to complete and what else the same people could be working on. An AI tool asked the first question will answer the first question.

Portfolio teams therefore need the business context to notice when a question is too narrow, and enough confidence to follow it where it leads, even if the conclusion is unpopular. Sometimes that means recommending that the work stop. Most organizations already find reprioritizing or stopping work much harder than starting it, and AI is making starting easier still. When a business case takes an afternoon and a working prototype takes a few weeks, more work gets started, and each piece arrives with a sponsor and momentum of its own. Without someone prepared to stop things, a portfolio fills up fast. Faster analysis makes the case for stopping quicker to build, but it still takes someone willing to raise it.

Staying close to delivery

Better automated reporting has an odd side effect. Information reaches the portfolio team faster and in better shape, but the team ends up further from the work itself.

It is possible to receive excellent status reports without understanding delivery any better.

Jira and Azure DevOps will tell you that work is moving. They won't tell you whether the remaining scope still supports the business case, or whether a slipping dependency is about to become someone else's problem. Connecting what delivery is doing with why the organization is paying for it is the portfolio team's job, and it needs people who can read both.

This matters more as funding practices change. Organizations that move from approving large initiatives on the strength of a business case to funding small, quick tests will find that more of the evidence behind their funding decisions comes from delivery itself.

None of this requires a return to manual status chasing. PMO leaders should make sure portfolio staff are in the room when forecasts change and recovery options are chosen, so they learn to tell a reporting anomaly from a genuine portfolio problem.

Developing judgment in less experienced staff

Give the same AI-generated analysis to a senior portfolio leader and to a new analyst, and they will get very different things from it. The senior leader has years of reference points to test it against: projects that looked like this before, estimates that turned out to be optimistic, sponsors who always said the benefits were nearly there. The analyst has a polished analysis and not much to challenge it with.

The uncomfortable part is that the work which used to build those reference points, such as assembling reports and doing first-pass analysis, is the work AI is taking over. Deloitte's 2025 Global Human Capital Trends research raises the same concern more broadly: as routine work is automated, what remains relies more on judgment, which is hard to develop without real practice. Microsoft's 2026 Work Trend Index points the same way, with 50% of surveyed AI users saying quality control of AI output was becoming more important.

The simplest fix is to make sure less experienced staff are in the room where decisions actually get made: the funding conversation, the difficult call with a sponsor, the meeting where a recovery plan is quietly dropped. That is where they learn how a well-reasoned analysis and practical reality sometimes part company. An AI analysis might assume a team can move onto new work next month. The people in the room know it can't, and why.

Junior staff now see far more analysis than they used to and far fewer of the conversations that give it meaning, and that balance needs to shift back.

Asking for their view before the senior people give theirs helps the lesson stick. It costs little more than a seat at the table, and it gives them something a training course can't: a close view of how judgment is actually exercised.

Making the time

All of this takes time, and it is tempting to assume AI will provide it. It usually doesn't, at least not visibly. Because AI has made proposals, reports and analysis cheaper to produce, more of them arrive, and each one still needs someone to review it. One transformation lead we spoke to for our 2026 State of Portfolio research runs a portfolio of around $250 million with a team of five. She told us AI was helping her work faster, and that she had no spare capacity at all.

PMO leaders therefore need to decide where the time goes rather than wait for it to appear. Where automation does reduce effort, some of the saving can go to handling more work, and for some PMOs that is the right call. Others are short of people who can challenge an investment case or make sense of conflicting delivery signals. They should put more of the saving back into real portfolio analysis and decisions, including time for senior leaders to go through their team's reasoning properly instead of simply approving the final output.

What PMO leaders should develop

For the last 30 years, PMO has earned its place by producing analysis. AI now produces much of that analysis faster and more cheaply, but it still depends on someone deciding which question to ask and what to do with the answer. That is the capability worth developing: teams that can frame the investment question, understand delivery well enough to read its evidence, and have the judgment and standing to recommend that something stop. It takes longer to build than tool proficiency, and it will stay valuable for much longer.