The Governing PM
The PM job didn't just add AI features. It quietly added governance nobody named.
This is Part 2 of a three-part series on what changes when agents, not just people, become your product’s clients: The New Front Door · The Governing PM · The Same Discipline, One Layer Deeper
“AI is changing the PM role” has become a throat-clearing sentence at the top of a hundred posts. The more useful question is narrower: “What specifically is a PM now accountable for that a requirements doc never covered?”
Writing “the agent should escalate ambiguous refund requests” answers a question a traditional requirements doc almost never had to answer out loud: what is this feature allowed to decide on its own, and where does it have to stop and hand off to a person? Most PMs are answering that question right now without anyone naming it as a distinct piece of the job.
I’ve written plenty of requirements that never touched this. “Refunds under $50 process automatically” describes feature intent, what should happen for the clean case the threshold covers. It says nothing about the refund the threshold doesn’t cover: $75, a defective product, and a shipping delay stacked together. A person standing at that point applies judgment and the gap gets filled for free, silently, the way it always has. The moment the actor at that point is an agent instead of a person, the same requirements doc has a hole in it unless something else spells out what the agent can decide alone in that ambiguous case and what it has to escalate. That’s not a new discipline replacing requirements writing. It’s a dimension that almost never had to be written down explicitly before, because a person was always there to absorb it.
Where the Job Actually Changed
Forbes Tech Council’s March 2026 analysis describes the shift as product leadership taking on what it calls ethical stewardship, classifying AI use cases by risk and documenting the oversight that keeps a system accountable when it acts without a human in the loop.
That’s a real function. It’s also, in most organizations I’ve seen, a function with no department. Legal owns compliance. Security owns access. Nobody owns the specific question of what an autonomous feature is allowed to decide before a human ever sees the decision, so it falls to whoever is already writing the requirements.
I’ve argued a version of this before, about a different piece of the same contract. The New Front Door made the case that once agents call your systems directly, the interface documentation stops being an afterthought and becomes the specification: what happens on ambiguous input, what side effects exist, what an agent can rely on without asking. Decision authority is the highest-stakes term in that same contract, not a separate discipline sitting next to it. It’s the clause that decides what happens when the system itself, not just the interface in front of it, has to make the call alone.
Two Questions, One Spec
The Job Nobody Titled
Agents Today’s analysis of the PM job market describes a sharp split forming between PMs fluent in directing AI agents and everyone else, with the middle ground that used to hold most mid-level PM careers eroding fast. The report doesn’t connect that split to decision authority specifically. My own read, watching this split from inside it, is that at least part of it is the PMs who’ve started specifying decision authority alongside feature intent, whether or not their organizations have a name for that skill yet.
I made a version of this case in When AI Mandates Meet Reality, about the gap between mandating AI use and having the organizational scaffolding to support it. The governance gap is the sharpest version of that scaffolding problem I’ve seen yet. Most organizations I’ve worked with or watched closely this year are still years away from standing up a real AI governance function with its own budget and headcount. Until one exists, the job doesn’t go undone. It lands on the PM closest to the feature, whether or not anyone updated the job description.
Specifying Authority, Not Just Intent
The difference comes down to one question: what happens at the edge? Feature intent can leave the edge case to human judgment, because a person is standing there. Decision authority has to specify the edge case in advance, or accept that the agent resolves it however its training happens to resolve it, with nobody having actually decided that was acceptable.
The New Front Door covered the rest of this same contract, the interface an agent calls. Decision authority is the sharpest-edged clause in it, and the harder one to skip past, because a bad interface annoys people while an unspecified decision rule makes one for them.
What I’m Not Sure Organizations Should Do
I don’t think every PM should become a governance officer, and I’m wary of the version of this advice that turns into another certification to chase. What I do think is that naming the accountability honestly changes how it gets staffed. Every PM I know who’s shipping agent-facing features is carrying some version of this governance work informally right now, without the authority or the cover that comes with an actual mandate, and that’s a worse position for both the PM and the organization than admitting the function exists.
What’s the last AI-facing decision your team shipped without anyone writing down which decisions it’s allowed to make on its own?
Continue to Part 3: The Same Discipline, One Layer Deeper
