Making policy part of execution.
In a recent Harvard Business Review piece, Sangeet Paul Choudary highlights what may be the most repeated sentence in enterprise AI: “Keep a human in the loop.” It is meant to reassure boards, regulators, and the people whose jobs are changing. In procurement, I would argue it has become an excuse not to redesign anything.
Here is what I see in too many organizations. AI drafts the sourcing recommendation. A category manager reviews it. Finance reviews it. Legal reviews the contract language. Someone signs off on the exception. We added a very fast step to the front of the process and kept every slow step behind it. The result is more work, not less.
The problem is not the AI. It is where we have put governance.
Governance bolted on at the end
Most procurement governance still works like inspection at the end of an assembly line. The work is done. Someone checks against thresholds, contract terms, and risk rules. Then it is approved or sent back.
That model was strained long before AI arrived. Gartner finds that 86% of procurement leaders have formal, documented policies, yet the business partners who need to follow them often cannot find or apply them.
Policy lives in a PDF. Decisions happen in the workflow.
AI widens that gap for a reason researchers identified decades ago. As automation grows more reliable, the people monitoring it become complacent and their skills atrophy. Lisanne Bainbridge called this an “irony of automation”: the more you automate, the more you depend on the very human capabilities automation takes away.
As Choudary argues in The Human-in-the-Loop Fallacy, AI makes this problem worse because its failures sound as confident and well-structured as its successes. A reviewer grading coherence is not grading correctness. A governance checkpoint at the end does not scale with AI. It becomes the bottleneck.
Rebundle governance into the work itself
Choudary’s answer is not less governance. It is “governance of a different kind: rules embedded in the work, owned by accountable people, and verified continuously.” He calls it rebundling governance into the work itself.
In procurement, that means the transaction carries its own controls. Instead of AI recommending a supplier and a person validating every recommendation, the workflow itself applies spend thresholds and approval rules as a request is created, checks purchases against contract terms and preferred supplier requirements, flags policy exceptions the moment they occur, and records decision rationale so the audit trail builds itself.
Output is governed during creation rather than inspected after completion.
The control tower is where governance lives
If governance is embedded in every workflow, leaders need one place to watch it work.
That is the role of a procurement control tower: a real-time, unified view across spend, suppliers, contracts, and risk that shows where policy is holding and where it is being tested.
PwC puts it bluntly: a modern governance architecture “cannot be limited to bureaucratic approval workflows; it must be deeply embedded in both technical and organizational processes.”
Data is the precondition. McKinsey estimates that procurement functions use less than 20% of the data available to them for decision-making and argues for a common data spine across spend, suppliers, contracts, and market benchmarks. You cannot embed a rule in a decision the system cannot see.
The control tower brings those data sources together and provides leaders with continuous visibility into the performance of their controls. It becomes the place where governance, risk, compliance, supplier intelligence, and procurement execution converge.
From inspectors to system designers
The bigger shift is about people. When governance moves into the workflow, procurement professionals stop being the checkpoint and start designing the checkpoints.
McKinsey describes a future in which procurement staff guide and coach their digital counterparts while AI agents take on repetitive transactional work. The shift is significant.
Procurement governance that is bolted on reviews transactions, enforces policy after decisions are made, tracks spend, and relies on people to execute workflows. Procurement governance that is built in designs the decision systems that execute transactions, embeds policy into decisions, predicts risk and opportunity, and relies on people to govern the agents executing the work.
The people who understand categories, suppliers, contracts, and risk appetite become the ones who set thresholds, design supplier evaluation models, define escalation paths, and manage the exceptions that require judgment. Procurement stops running purchasing processes and starts designing how purchasing decisions get made. It is the difference between driving the car and designing the traffic system.
Where to start
This does not require a multiyear transformation program. McKinsey notes that organizations with the right data foundation can move from prototype to pilot in weeks and from pilot to scale in less than a year. Three moves matter most.
1. Turn policy into decision points
Gartner recommends translating policy into role-based guidance and explicit stage gates, including mandatory fields, required documentation, and threshold-based approvals. These are exactly the kinds of rules a system can enforce automatically.
2. Match governance to risk
Large, irreversible, high-risk decisions deserve strong controls. Small, reversible decisions require less intervention. Tiering governance allows low-risk spend to move efficiently while attention is focused where it matters most.
3. Make review continuous
Regulation changes quickly. Gartner reports that 36% of CPOs cite monitoring and adhering to new regulations as a top priority. Feedback loops should ensure that every exception improves the rules and strengthens the system.
Governed autonomy
Most procurement technology is still sold on faster workflows. Speed matters. Speed without embedded governance simply means making ungoverned decisions faster.
That is the future we are building toward at Focal Point. Our view is simple. Governance should not be the step that slows the work down. It should be the reason the work can move fast. Procurement leaders are not managing workflows anymore. They are managing decision systems. The control tower is where they do it.
If you are rethinking where governance sits in your procurement organization, I would welcome the opportunity to compare notes.