The Future of the PMO
Some functions reach a moment when outside forces change the work they were built to do. The usual response is to argue that technology cannot replace professional context and judgment. Sometimes that holds, and sometimes it does not. The PMO faces this question now, as AI automates parts of its administrative work. What should the function become?
The PMO may be well positioned to adapt if its leaders handle this moment deliberately.
What AI Takes and What It Cannot. AI can automate or assist with some of the work that has long consumed PMO time. Project tools can generate status reports. Algorithms can support schedule analysis, communication monitoring, and forecasting by flagging potential risks. Meeting summaries, action tracking, and document management are candidates too.
That work creates value, and in some organizations it has defined how people see the PMO. As it changes, leaders face a choice. Cutting headcount only because tasks got cheaper can overlook what else the function could contribute. One path is to redeploy some PMO capacity toward broader coordination and organizational learning. That can include Enterprise Readiness where it fits the mandate.
Thomas Davenport and Julia Kirby argue that what people add alongside automation often includes judgment and framing. Their view can inform a PMO's transition, though each organization's needs differ. Coaching taught me something similar. A coach's job reaches past keeping the stat sheet to building capability and coordination. For the PMO this is an opportunity, not a universal mandate or a guaranteed outcome.
What the Enterprise Readiness Professional Looks Like
From the Executive's Side of the Table
For years, the people who ran your projects introduced themselves by their credentials and methods.
Those labels described how they worked, not the full value they could create. Systematic project methods are now widely practiced, though how much they matter varies by market and organization. The Enterprise Readiness Professional is one way the role could evolve. It is more than a new title for a project or portfolio manager. This practitioner's main commitment is helping the organization recognize, understand, respond to, and learn from Strategic Situations.
For the executive, expectations can change. Scope can reach past the project portfolio to situations on the roadmap, anticipated situations, and plausible what-if scenarios. Success can be measured by organizational preparation and Decision Quality alongside schedule, method, and reporting. Project methods stay useful, joined by skill in organizational dynamics, executive communication, strategic thinking, decision science, and AI.
Making the Case for the Investment
The function that stewards Enterprise Readiness will face a budget conversation before an operational one. That conversation needs a financial model, not a framework presentation. The baseline is the organization's own Mobilization Tax across significant situations. It includes senior leadership time, governance overhead, stakeholder sequencing, and communication built under pressure. Delayed initiative value counts too, along with the opportunity cost of a window closing before the response was ready.
Preparation has a cost; calling it infrastructure does not erase the hours required to build and maintain it. Compare it with the organization's own repeated coordination work after a consequential situation arrives. A protocol earns its place when fewer handoffs and less assembly in actual use outweigh the effort of keeping its authority, owners, and first steps current. If the record does not support that exchange, simplify or retire the protocol rather than add another review layer.
Enterprise Readiness is meant to reduce avoidable assembly cost. That effect should be measured against the baseline, not assumed. The first Readiness Protocol built for a recurring situation type may cut assembly cost the next time that situation arrives.
Take a vendor-continuity protocol. In a normal quarter it could support the routine supplier review by keeping escalation contacts, dependency owners, and approved alternatives current. If that supplier later suffers a high-consequence outage, the team can adapt the protocol. Leadership can use the prepared authority map and review alternatives against current facts. Legal, operations, communications, and customer teams can coordinate without starting that assembly from scratch. The capability is useful in routine operations and available again when the stakes rise. Its value still has to be measured in the customer environment. A steward who builds the case with the organization's own numbers can judge payback against a cost the organization is already paying.
Where the PMO is absent, focused only on delivery, or short on enterprise trust, stewardship can sit elsewhere. It could sit with the COO, in Strategy or Transformation, in the Chief of Staff organization, in Enterprise Risk, or in a dedicated Readiness Office. The steward keeps the operating cadence and the record. Executives keep authorization, and Legal, Finance, Security, Communications, and other functions keep their domain decisions. Enterprise Readiness needs a stable steward, not a particular org chart.
Picture a weekly standing portfolio review. The Enterprise Readiness Professional asks the question the agenda never has: “Which of these initiatives exists because of a Strategic Situation we have not named?” Together, the executive team traces several initiatives back to the situations driving them. It finds one with no explicit owner, authority, or response window. From there, the review shifts from reporting progress to deciding what that situation requires and what preparation must exist before the next meeting. Nothing new went on the calendar; the team redeployed the existing structure around the situation.
The Core Mission. Beneath changing methods, technology, and identity, a PMO can keep a valuable integrative role. Organizations can be fragmented. Functions see different parts of the work, and executives weigh different dimensions of performance. Geoffrey Moore describes how established enterprises must run a proven business while responding to disruption. That calls for integration as parts of the organization change at different speeds.
Some PMOs have supplied that integration through project or portfolio governance. They may contribute to Enterprise Readiness where access, expertise, and mandate support it. Elsewhere, one of the other homes named above, or another function, may fit better. Methods and homes can change while the value of cross-functional coordination stays. As AI changes administrative work, a PMO may be able to redeploy some capacity toward that broader contribution. That is each organization's decision, not an inevitable future for every PMO.