A two-week AI experiment should not wait a month for sign-off. In many organisations it does. The result is not safer AI. It is AI that nobody can see. Research and policy news from the past three weeks point the same way. Governance that sits outside the delivery process is failing product teams, and they are the ones left holding the risk.
Slow approvals push AI underground
AWS published its Reimagine 2026 research on 28 September. It draws on interviews with 154 executives at 128 organisations. One pattern stood out. Approval processes built for six-month IT programmes are being applied to work that takes days. When experiments stall waiting for sign-off, teams stop asking for permission.
Governance vendor OneTrust puts a number on it. Its 2026 AI-Ready Governance Report surveyed 1,200 senior decision-makers across eight countries. A third reported staff using unapproved AI because approved tools or processes were not available quickly enough. OneTrust sells governance software, so weigh its framing with that in mind. Still, AWS heard the same story in its own interviews.
Incidents are common. Ownership is not.
The same OneTrust survey found 86% of organisations had at least one AI-related incident in the past year. Only 27% slowed or paused deployment in response.
Agents sharpen the problem. 87% of organisations encourage staff to use AI agents. Only 47% have governance, oversight and controls in place. 28% reported two or more occasions when an AI system or agent acted without authorisation.
Help Net Security's coverage adds the figure that should worry product leads most. Only 5% of respondents say coordination and accountability are defined across the AI lifecycle.
Accountability is also climbing the political agenda. On 1 October, US Senators Josh Hawley and Chris Murphy announced a bill that would hold developers and operators of AI agents criminally and civilly liable when their models hack into other systems. It is early-stage US legislation. The direction of travel is still clear. "The model did it" will not be an acceptable answer for much longer.
What product teams can do this quarter
- Name one owner per AI feature. Not a committee. A person who signs off the release and answers for incidents.
- Match the gate to the risk. An internal summariser does not need the same review as an agent that can act on customer data. Tiered review keeps the fast path fast, so nobody needs to work around it.
- Put agent limits outside the agent. Executives in the AWS research stressed that security boundaries should sit outside the agent, not inside it, so they cannot be worked around.
- Keep evaluation evidence with the release. Test results, known failure modes and sign-off belong in one place. That is what a buyer, an auditor or a regulator will ask for.
On that last point, the EU AI Act's Digital Omnibus moved the Annex III high-risk deadline to 2 December 2027. Treat that as time to build the habit, not a reason to wait.
Make governance part of delivery
Good governance should speed up a release, not block it. If you want clear, repeatable evaluation criteria that your team owns and can show to anyone who asks, EvalSpec can help you define what good looks like before production.
Try EvalSpec free - evaluate your AI system across all 5 dimensions. No code required.
Start your free evaluation