The Signal

A weekly read for operators thinking seriously about AI. Less noise, more signal.

The Lead

Reports were never the value

For twenty years, the project management profession has been telling itself the same story. Project Management Offices are too administrative. The work is too transactional. The future PMO will move upward, away from status reports and toward strategic decision support. AI agents will finally free us from the administrative burden, so we can become the strategic partners we were always meant to be.

The story is comfortable. It is also wrong in a way that AI agents are about to make impossible to keep telling.

The PMO of 2026 looks remarkably like the PMO of 2006. The promise of "moving upward" predates Gen AI by two decades — it was the same argument made when project portfolio management software arrived, when business intelligence dashboards became standard, when Slack and Teams replaced email status updates. Every wave of technology was going to free the PMO from administration. None of them did. Why?

Because the PMO never had a different job. The administrative work was not a distraction from the real work. It was the real work — what got the PMO budgeted, measured, and continued. Asking a PMO to move upward into strategic advising is asking it to do work the organization does not pay it to do, demand from it, or measure it on. The PMO that tries to "move upward" runs into the same wall every year: the organization wanted the report, not the judgment.

AI agents are different from previous waves in one specific way. Previous technologies made the administrative work faster. Agents do the work entirely. When a leader can ask an agent for the status of a project, the deviation from plan, the resource utilization across the portfolio, and get an answer in seconds — they no longer need a human to produce the report. The PMO is not "elevated" by this development; it is routed around. Not by choice. By indifference.

This is the moment where the twenty-year-old story finally has to confront the question it has been avoiding. If reports were not the value, what was? If the PMO survives the agent, it survives because it owned something the agent cannot replicate — the decision logic, the escalation paths, the institutional judgment under uncertainty, the political navigation of resource conflicts between executives who do not want to talk to each other. None of those is administrative work. All of those are the work that nobody ever quite paid the PMO to do, but that the best PMOs were doing anyway, in the gaps between the reports they were paid to produce.

The PMOs that survive 2026 will be the ones honest enough to write down what they were actually doing. The audit is uncomfortable. Most PMOs will discover that the answer to "what were we doing besides producing reports" is shorter than they wanted to believe. That is information, not failure. The functions that can name their non-administrative value become candidates for becoming the operators of the agent layer — the humans who encode the decision logic, set the escalation rules, and own the governance the agents need to operate safely. The functions that cannot name their non-administrative value become candidates for not surviving.

This is not bad news for the project management profession. It is the most useful diagnostic the profession has had in a generation. The PMOs that have been doing real decision work alongside the report production will discover they have been undersold for years. The PMOs that have been doing only report production will discover the opposite. Both groups need to know which one they are before the executive team finds out without them.

Three Things Worth Knowing

The interface collapse is real. The question is what survives it.

The argument made repeatedly this month — software stops being the product, execution becomes the product, intelligence becomes the interface — is correct, and the implication for operators is sharper than the argument lets on. When the interface goes away, the part of the job that consisted of navigating the interface goes with it. What remains is the part that was always human work: judging when to escalate, deciding which tradeoffs are acceptable, taking accountability when something goes sideways. The operators making productive bets right now are the ones planning for which of those they will own when the SaaS layer collapses out from under them.

Regulatory disruption is now a vendor risk category

Anthropic's most advanced models remain disabled following a US government directive. The press framed this as a story about AI safety. The operator framing is harder. The directive is a leading indicator that the frontier model your team is depending on can become legally unavailable for some workloads with very little notice. Multi-year roadmaps built on a single vendor's strongest model just acquired a regulatory risk category that did not exist in 2024. The teams that build vendor optionality into their architecture this quarter will be in a defensible position when the next directive lands. The teams that did not will spend the next quarter scrambling to migrate workloads under deadline.

Governance is replacing capability as the competitive question

Through 2024 and 2025, the operative question for AI projects was "which model is best." Through 2026, the operative question is shifting to "whose governance posture lets them deploy safely." The capability gap between frontier models is narrowing — every major lab can now do most of what enterprise AI projects need. The differentiator has moved upstream into the decisions teams make about which AI gets deployed where, with what oversight, against what audit trail. Capability is the floor. Governance is the ceiling. The teams winning in the next eighteen months are not the ones with the best AI; they are the ones with the clearest decisions about how to deploy what they already have.

From the Practice

The non-administrative inventory

There is a diagnostic we run with functions that suspect they are exposed to the agent transition. PMOs. Operations teams. Finance and reporting groups. The diagnostic is one question, applied repeatedly across every output the function produces: "If an agent could produce this artifact directly, what would the team need to know that the agent does not?"

The list of answers is the function's non-administrative inventory. The political navigation. The institutional context. The unwritten decision logic. The judgments under uncertainty that nobody recorded because there was nobody to record them to. This list is what the function actually delivers, separate from what it produces.

Functions that try this exercise discover one of two things, and either discovery is useful. They discover the non-administrative inventory is long, specific, and difficult to articulate to executives because nobody has ever asked. Or they discover the inventory is short. The first group has a strong case for becoming the operators of the agent layer. The second group has a case for asking themselves what comes next, while there is still time to choose.

The functions that came through our recent engagements strongest were not the ones with the most impressive process documentation. They were the ones honest enough to do this exercise on themselves before the executive team did it to them.

The Field Manual

How to audit a function for what survives automation

AI agents arriving in any function expose what the function was actually providing. The exposure can be a threat or a clarifying moment, depending on whether the function ran the audit before the executive team did. This is the process for running the audit on yourself first.

Four steps, roughly half a day for a focused team. The output is a document you can defend to executives in any quarter going forward.

Inventory the outputs

List every artifact the function produces in a typical month. Status reports. Dashboards. Recurring meetings. Approvals. Recommendations. Documented decisions. Each one gets its own line. The list is usually longer than the team expects and the act of writing it down is the first uncomfortable moment of the audit. If the team cannot list more than ten things, that is information.

Score each output for agent replicability

For each output, score from one to five how confidently an AI agent with access to the underlying systems could produce the same artifact. A five means an agent could produce it today with no human input. A one means producing it requires irreducible human judgment, political navigation, or institutional context that does not exist in any system. Resist the temptation to over-score one or over-score five. The honest numbers tend to cluster in the threes and fours, which is where the audit becomes useful.

Identify the residual work

For every output scored four or five, ask what work the human was doing that the artifact did not capture. The chasing of late submissions. The political navigation of which executive wants what visibility. The timing decisions about when to escalate and when to wait. The framing of the artifact for the specific audience receiving it. This is the residual work, and it is almost always uncaptured anywhere. Write it down for each output. The residual work is the function's actual delivery.

Build the case

The residual work is what the function survives on. Document it in the vocabulary the executive team uses to discuss strategy, not in the internal jargon of the function. The functions that move toward the agent layer successfully are the ones that can articulate their residual work in language that translates to executive priorities. The functions that cannot will be measured on the artifacts the agent produces and will lose the comparison.

The meta-rule

This is not a defensive exercise. It is a discovery exercise. The functions that come out of it strongest are the ones that discover they have been delivering value the organization was not measuring or paying them for. Once they can name that value, the conversation about their place in the agent layer becomes much more interesting than it was.

The functions that try to defend the artifact list lose. The functions that lead with the residual work win. The audit decides which group you are in. Better to find out now.

Running this audit on a function in your organization and want a second set of eyes on what you find — or want ResonAi to run it for you? That is exactly the conversation a Discovery call is for. Bring the function. We will work through what survives.

Book a Discovery Call

Whether or not a call makes sense, I'd genuinely like to hear how this issue lands. If you have a counterargument, a question, a story from inside a PMO that proves the lead wrong, or you think I got something wrong — just reply. The best issues of The Signal have come from readers pushing back, and the pushback usually finds its way into a future practice note.

Or read this issue on LinkedIn.

Applied AI strategy, training, and implementation.

Ryan Rezeika · Founder · Vancouver, BC
ryan@resonai.ai · resonai.ai · LinkedIn

You're receiving this because you subscribed at resonai.ai/signal. · Unsubscribe