Pre-Mortem: Eight Companies, No Published Accountability Standard

Posted on by

The Pre-Mortem is a weekly series on this blog. Each piece applies five questions to a major technology commitment before the outcome is known.

In February 2026, the United States Department of War signed agreements with eight of the world’s leading artificial intelligence companies, OpenAI, Google, Microsoft, SpaceX, Oracle, Amazon Web Services, NVIDIA, and Reflection, to deploy their advanced AI models inside its classified networks. Impact Level 6 (IL6) covers data classified at the Secret level. Impact Level 7 (IL7) covers compartmented intelligence and the most sensitive operational systems, where the United States military runs its actual warfighting decision support. This is the first time that large language models have operated within IL7 environments. What has not been published is who carries accountability when one of them gets something wrong.

 

The Bet

The Department of War’s stated aim is to establish the United States military as an AI-first fighting force, achieving what its AI Acceleration Strategy calls decision superiority across all domains of warfare. The eight agreements are the mechanism. The AI systems will summarise surveillance feeds, synthesise intelligence data, and suggest tactical options to human operators. The Department of War’s five AI ethics principles, responsible, equitable, traceable, reliable, and governable, are on the record. The bet is that those principles are sufficient architecture for what happens inside a classified environment.

 

The Assumption

The whole bet turns on this: that “humans remain accountable for AI outcomes” as a stated principle is equivalent to a published accountability framework.

That distinction is where there is a gap. The Department of War’s Responsible AI Strategy and Implementation Pathway establishes process. It does not name the specific individual, command role, or governance layer accountable when an AI-assisted intelligence summary inside an IL7 environment shapes a decision that turns out to be wrong. Principle and framework are not the same thing, and in a classified environment that distinction cannot be tested publicly.

 

The Sequence

In July 2025, Anthropic’s Claude became the first frontier AI model approved for use on classified networks. The Pentagon subsequently sought to renegotiate those terms, demanding Anthropic permit its models to be used for all lawful purposes without limitation. Anthropic declined, citing concerns about mass domestic surveillance and autonomous weapons. On 27 February 2026, President Trump ordered all federal agencies to stop using Anthropic. The following day, OpenAI signed its classified deal with commitments that included prohibitions on domestic mass surveillance and human responsibility for the use of force, positions that aligned with the guardrails Anthropic had sought to retain. By May 2026, the remaining seven of the eight, Google, Microsoft, SpaceX, Oracle, Amazon Web Services, NVIDIA, and Reflection, had signed equivalent agreements.

The sequence reveals something structural. The accountability architecture for classified military AI was settled by commercial negotiation and political designation, not by a published governance framework.

 

The Pager

Legal scholars on autonomous weapons identify the same accountability fracture that applies in the decision-support context here. When an AI-assisted output causes harm in a classified environment, accountability distributes: software developers could not have anticipated all operational contexts, commanding officers disclaim responsibility for machine-generated outputs, vendors invoke contractual limitation of liability. The human-in-the-loop design means a person reviews AI suggestions before acting. It does not mean accountability for acting on a wrong AI output has been named anywhere in the command chain.

No published document names the specific individual role, command layer, or governance body accountable for a wrong AI-assisted output inside an IL7 environment. No congressional oversight mechanism covers classified operational AI use. No published error reporting standard exists. By the nature of classified operations, none can.

 

The Proof

Eight companies, the highest classification levels, large language models operating on top-secret data for the first time: the scale of the commitment is confirmed. The outcome data will not follow. Classified operational AI performance is not publicly reviewed, by design. This is the only deployment in this series where the proof question cannot be answered from the outside, not because the data is not collected, but because it cannot be published.

The accountability question is not whether humans are in the loop. They are, by stated commitment. The question is whether the framework for who carries it specifically, when they get something wrong, inside a system that cannot publish what it got wrong, exists in any enforceable form.

 

The Verdict

If the Department of War’s five principles are operationalised into a named, enforceable command accountability chain for AI-assisted decisions at every classification level, if the commercial guardrails in all eight agreements are independently verifiable by a body with appropriate clearance, and if a congressional oversight mechanism specific to classified AI operational failure is established, then this is what responsible military AI deployment at scale should look like.

Without all three, eight of the most powerful AI systems on earth are running inside the most classified networks in the world. The decisions they shape will not be publicly reviewed. The wrong ones will not be counted.

The accountability is a principle. The framework has not been built yet.

AI Gets the Blame. Governance Built the Problem

Posted on by

When an AI system causes serious harm, the story is easy to write. Biased algorithm. Dangerous model. Technology that cannot be trusted. The headline names the AI and moves on.

What the headline does not name is the governance meeting that never happened. The audit trail that was never built. The accountability structure that should have existed before the first automated decision was made, and did not.

That absence is the story.

Across healthcare, hiring, public services, and criminal justice, the pattern repeats with such consistency that it has stopped looking like bad luck and started looking like a structural failure. AI is deployed to solve a genuine operational problem. The deployment decision is made without the governance architecture that would constrain it, audit it, or catch its errors before they compound. Consequential harm compounds. And then AI gets the blame, while the process failure is buried somewhere in paragraph twelve.

These are not AI stories. They are governance stories. AI is the mechanism.

 

The Cases That Make It Visible

In January 2026, a class action was brought against Eightfold AI, a hiring platform used by major employers globally. The case was filed by Jenny Yang, former chair of the Equal Employment Opportunity Commission. It does not argue that the algorithm was biased, though that question remains open. It argues that the system operated in secret. Eightfold had scored over one billion workers on a scale of zero to five, and candidates ranked at the bottom were discarded before a human being ever saw their application.

Seventy per cent of companies using AI in hiring allow AI to reject candidates at the initial screening stage, with no human review at that point. One in five goes further, allowing AI to reject candidates at every stage of the process with zero human involvement at any point. That is not a technology decision. It is a governance decision. Someone, somewhere, made the deliberate choice to remove the human from the loop. Nobody built an accountability structure around what happened next.

The pattern is not new. In 2021, the Dutch government resigned after an AI system falsely accused twenty thousand families of child welfare fraud. Courts ordered repayments of tens of thousands of euros per family. In Australia, the Robodebt programme issued four hundred thousand wrongful fraud accusations before it was ruled unlawful and the government repaid over one billion dollars. In Michigan, a 2024 settlement reimbursed three thousand plaintiffs for what a benefits fraud algorithm had wrongly taken from them.

In each case, the AI system did what it was designed to do. What nobody designed was the mechanism that would question whether it was doing the right thing.

 

The Structural Argument

The research makes the pattern numerical.

An analysis of a hundred and forty enterprise AI implementations found that only twenty-three per cent of failures were caused by model performance, data quality, or technical integration. The remaining seventy-seven per cent came down to strategy, governance, and change management.

Three-quarters of AI failures have nothing to do with the technology.

Only one in five organisations has a mature governance model for autonomous AI agents. This is the population deploying AI at scale, across consequential decisions in hiring, healthcare, benefits, credit, and criminal justice, mostly without the mechanisms needed to know whether the AI is producing correct outcomes, or what to do when it does not.

This is not a portrait of reckless technology. It is a portrait of reckless deployment. The AI worked. The organisation around it did not.

 

Governance as Delivery Discipline

Most organisations treating AI governance as a compliance function are building the next wave of failures right now. Compliance asks whether the system meets a threshold at the point of deployment. Delivery discipline asks whether the system is behaving as intended across every subsequent decision it makes, and whether there is anyone accountable when it does not.

These are not the same question. That gap is where accountability ends and harm begins.

Effective AI governance is not about slowing deployment. It is about building the accountability architecture alongside the deployment. An agreed definition of what the system is supposed to achieve. A method for measuring whether it is achieving it. A human being, with authority and accountability, responsible for reviewing outcomes at meaningful intervals. An appeals mechanism when the system gets it wrong, because it will. Documentation that allows an audit when something goes wrong, rather than after the damage is done.

 

The Question Worth Asking Before the Next Deployment

The Eightfold case will not be the last of its kind. The healthcare billing figures will grow before they shrink. More governments will face the political and financial cost of systems that automated consequential decisions without the mechanisms to catch errors before they multiply.

The organisations that avoid this are not the ones that move slower on AI. They are the ones that treat governance as part of what delivery means, not as a separate conversation to have later, when the headlines arrive.

By then, the structure has already failed. The question worth asking now is whether yours is being built.

Your Enterprise AI Programme Is Structured Backwards.

Posted on by

There is a research paper that has been making rounds in enterprise AI circles and deserves more attention than the single line most people have taken from it.

The Stanford Digital Economy Lab published its Enterprise AI Playbook in April 2026. It is drawn from 51 live, production-grade deployments across 41 organisations, seven countries, and more than one million employees. And what it found cuts against almost every assumption the technology industry has built its messaging around.

In every deployment that succeeded, and in every deployment that failed, the determining factor was not the model. It was not the vendor, the feature set, the benchmark performance, or the integration timeline. In every case, the variable that decided outcome was the organisation: executive sponsorship, governance architecture, and the quality of workforce change management. Seventy-seven per cent of the implementation challenges in the study traced to non-technical factors: change management, data quality, and process redesign.

 

One Finding in 51 Deployments

The research does not say technology does not matter. It says it matters significantly less than most programmes treat it as mattering, and that the organisations which led with governance and change management consistently outperformed those that led with model selection.

One adjacent data point makes this more concrete. Sixty-one per cent of the successful deployments in the study followed at least one prior failed attempt. Those organisations had not found a better model on the second attempt. They had changed what they were actually doing. And in almost every case, that meant addressing the organisational variables they had underestimated the first time: governance structure, change management approach, and clarity of executive ownership.

The technology was not the lesson. The organisation was.

 

How Most Programmes Are Actually Structured

I have sat in enough enterprise AI programme kick-offs to recognise the pattern before the second slide.

The programme begins with a vendor selection process. A proof of concept is scoped, model performance is evaluated, pricing tiers are compared, latency is benchmarked. The technology conversation consumes the first two to six months of the programme. By the time it concludes, the organisation has committed significant capital and credibility to a specific platform before the questions the Stanford data confirms are the real determinants of success have been seriously engaged.

Those questions are not complicated. Who is the executive sponsor, and what does their sponsorship mean in terms of decision-making authority and resource commitment, not just endorsement? What is the governance architecture for the AI programme, not for the AI system, but for the programme? How does the organisation plan to manage the workforce transition that a serious deployment requires, and what does it know about the change-readiness of the teams it is deploying into?

These are not questions that get answered in a vendor evaluation. They are not questions that appear on most programme charters. They are the questions that decide whether the programme succeeds.

 

What Leading With Governance Actually Means

Leading with governance does not mean delaying deployment while a committee produces documentation nobody will read. It means defining, before the technology is in the ground, who owns the programme’s outcomes, how the workforce transition will be handled, and what the decision-making structure looks like when the deployment hits the friction that every serious AI implementation hits at scale.

Because the friction will come. It always does. And how an organisation responds to it reveals which frame it used at the start.

Programmes built on a technology frame diagnose the friction as a technology problem. The model is adjusted. The integration is patched. The interface is redesigned. The organisational dynamics actually driving the resistance go unexamined, because the programme was never looking at them. Programmes built on a change management frame diagnose the same friction differently. The conversation shifts to whether the right people were involved in design, whether transition support was adequate, whether the governance gave teams the clarity they needed to work confidently with the new system. Those questions lead somewhere. The technology-first version usually leads to another vendor call.

 

The Argument That Is Now Evidence

This is not a new insight for experienced transformation leaders. I have been making a version of this argument for years, and so has almost everyone else who has led a serious enterprise change programme. The frustration, and the genuine value of Stanford’s work, is that it can now be asserted with data.

For transformation leaders making the case for governance investment in leadership conversations where the pressure is almost always to accelerate on technology, the Stanford Playbook is the data point that turns an argument from opinion into evidence. It does not require arguing against the technology. It requires arguing about sequence and proportion, and it gives you the empirical foundation to do it.

The organisations still leading with model selection are systematically delaying the decisions that actually determine whether a deployment succeeds.

Fifty-one real deployments confirm it. That should be enough.

Workplaces Don’t Just Pay You. They Shape You

Posted on by

There is a version of career advice that treats every job as essentially equivalent, a set of roles, responsibilities, and remuneration packages to be evaluated primarily on their individual merits. You assess what the role requires, what it pays, and what it advances you toward. This is a reasonable framework. It is also incomplete.

The workplace you spend three or five years in does not just pay you. It shapes you. It forms the decision-making patterns, the risk tolerance, the communication instincts, and the professional identity that you carry into every subsequent role. Often in ways you cannot fully see until you have left.

 

How Environments Form Capability

The formation happens gradually and mostly below the surface. In an organisation with strong analytical discipline, you learn, often without realising it, to interrogate assumptions before committing to a course of action. In an organisation where pace is valued above rigour, you learn to move quickly and make decisions with incomplete information. In an organisation where challenge is welcomed, you develop the confidence to push back. In one where it is not, you develop the habit of working around problems rather than confronting them.

None of these formations is necessarily good or bad in isolation. All of them travel with you.

The professional who has spent five years in a high-accountability, high-clarity environment arrives in their next role with a set of instincts (about what questions to ask, what risks to flag, what evidence to require before deciding) that their counterpart from a lower-accountability environment simply does not have. The gap between them is not qualifications or experience in any formal sense. It is formed professional judgement.

That formation is not something a training course produces. It is the cumulative output of the environment itself: the decisions you are asked to make, the standard your work is held to, the conversations you are included in or excluded from, the quality of the thinking you are surrounded by.

 

What the Research Confirms

LinkedIn’s 2025 Workplace Learning Report found that 88 per cent of organisations say employee retention is a concern, and that providing learning opportunities is their top retention strategy. That finding is usually read as an HR insight. It is also a signal about what people themselves understand: the environment you work in is the primary determinant of your professional growth, and its absence is what drives capable people out of the door.

The same research found that only 36 per cent of organisations qualify as genuine career development champions, with robust and actively used development programmes in place. Thirty-three per cent have no meaningful initiatives at all, or are just beginning to build them.

The gap between those two groups is not a gap in intention. Most organisations understand that development matters. It is a gap in practice. Capable people read the environment accurately. When it stops investing in them, they leave for ones that do. The organisations that cannot close that gap are not simply struggling with retention. They are handing their best people, already formed by the investment made in them, to the competitors who will benefit from what that formation produced.

 

The Compound Effect

Development is not linear. The professional who is given increasing challenge, exposed to better quality thinking, and held to a rising standard does not improve at the rate of their individual training investments. They compound. Each year of a strong environment builds on the previous one in ways that create something qualitatively different from the sum of the parts.

The professional who spends the same years in a low-challenge environment is not standing still. They are becoming expert at a narrower set of conditions. They are developing the instincts that environment rewards and allowing the ones it does not reward to atrophy. They will be competent within those conditions for as long as they apply, and brittle when they change.

This is not a moral observation about which organisations are virtuous. It is a structural one about how professional capability is formed. The environment is the curriculum.

 

The Decision You Are Actually Making

When you accept a role, you are making two decisions. The explicit decision is about the role: the responsibilities, the scope, the compensation. The implicit decision is about the environment: who you will learn from, what standard you will be held to, what kinds of problems you will be asked to think about, and who will be in the room when consequential decisions are made.

That first decision shapes the next two or three years. The second shapes the decade that follows.

Most career conversations focus almost entirely on the explicit decision. Salary, title, scope, promotion trajectory. These are real considerations. They are also the shorter-term ones.

The question worth asking, and the one asked too rarely, is what this environment will make of you. Not what you will do in it. What it will do in you.

An organisation that invests seriously in the development of its people, one that exposes them to hard problems, holds them to high standards, and creates the conditions for genuine challenge, is offering something that does not appear in the compensation package. It is offering the formation of a professional who will be more capable, more resilient, and more effective in every role that follows.

 

What This Means for Leaders

For leaders, the obligation this creates is clear. You are not simply extracting the capability your people currently have. You are shaping the capability they will have. The quality of that formation is your responsibility.

The organisations that take this seriously produce people others want to hire. That is a leading indicator, not a lagging one. If the market consistently values what comes out of your environment, you are building something. If it does not, the environment is telling you something.

Choose the environments you build as carefully as you choose the people you put in them.

Your AI Risk Register Does Not Reflect Your Actual Risk

Posted on by

 

On 22 June 2026, the intelligence agencies of the United States, United Kingdom, Australia, Canada, and New Zealand spoke in a single voice about enterprise AI risk, and what they said demands attention.

The Five Eyes cybersecurity agencies issued a joint statement warning that frontier AI models are improving at a pace that will allow them to bypass prevailing enterprise cybersecurity defences within months. Not within years. Not in the next planning cycle. Within months. The statement’s own language: “The timeline is not years, it is months.”

 

This Is Not an Abstract Warning

Joint statements from the Five Eyes agencies carry a different category of authority than vendor advisories or consultancy threat reports. These are national intelligence services with access to classified threat intelligence, speaking to government and enterprise leaders simultaneously. When they frame a risk as both imminent and enterprise-specific, take it at face value.

What sets this advisory apart from every AI security conversation most enterprises have been having is one thing: specificity. The Five Eyes statement does not describe abstract AI risks. It specifically names the enterprise AI tools deployed at scale in the last 18 months: copilots, AI assistants, browser-connected agents, and systems with access to operational and customer data. The primary attack mechanism, developed across Five Eyes guidance published earlier this year, is prompt injection: an adversary embeds hidden instructions in content the AI system processes, causing it to act outside its intended scope.

That specificity matters. It means the tools that most large enterprises have already deployed are the attack surface being described.

 

The Threat Moved Faster Than Your Review

Most organisations that have rolled out AI copilots, enterprise agents, or browser-integrated assistants have conducted security reviews of those deployments. The Five Eyes advisory is not questioning whether those reviews happened. It is saying that the threat has moved faster than the defences, and that a review conducted six months ago may no longer accurately reflect the risk profile today. The gap is not in intent. It is in elapsed time against a threat that has not stood still.

The advisory is explicit that this is not solely a security-team problem. The statement directs its recommendations at leadership, framing AI-driven cyber risk as a governance and board-level accountability question. The statement’s own title: “The AI shift in cyber risk: why leaders must act now.” That framing has direct implications for how risk registers are built and how AI deployment decisions are reported to boards.

 

Three Things Worth Doing Before Your Next Board Meeting

The advisory points to three things transformation leaders should act on before their next board meeting.

The first is a current security review. Every AI deployment connected to operational data, whether customer records, financial systems, or internal communications, needs a review that specifically addresses prompt injection risk. Not the review conducted at go-live. A current one, calibrated to the threat capability the Five Eyes describe as arriving within months.

The second is an updated risk register. Most enterprise risk frameworks assessed AI security risk at the point of initial deployment. The Five Eyes advisory says the threat environment has changed materially in the months since, and the assessment needs to reflect current threat capability rather than historical assumptions. An outdated risk assessment is not a minor administrative gap at this point. It is a governance exposure.

The third is using the advisory to reframe the conversation at board level. Six cybersecurity agencies from five countries issued this statement with an explicit focus on business leadership. That gives transformation leaders the instrument they need to move boards that have been treating AI security as an implementation detail. The Five Eyes advisory makes it a governance question. Use it as one.

The AI deployment decisions taken in the last 18 months created an attack surface. Most enterprise risk registers have not yet priced what that surface is worth to an adversary with AI-powered attack tools that are months from bypassing prevailing defences. That gap needs to close, and it closes with a current assessment, not one accurate at the time of go-live.

The EU AI Deadline Your Compliance Team Probably Missed

Posted on by

The EU AI Act enforcement date most organisations have been tracking is not 2 August 2026. They have been watching the high-risk provisions, the conformity assessments, the prohibited applications. Those timelines stretch into 2027 and beyond, and enterprise compliance teams have planned accordingly.

Article 50 has a different clock. It takes effect in 31 days, it applies to a far wider population of organisations than most realise, and for most of its obligations there is no grace period.

 

Not the Regulation You Were Watching

For the past two years, enterprise AI governance conversations have centred on the Act’s high-risk classifications. Which systems require conformity assessments? Which use cases are prohibited outright? The questions were legitimate, and the extended timelines attached to those provisions created a reasonable sense of runway.

That runway does not apply to Article 50.

Article 50 covers transparency obligations, and it lands on 2 August 2026. It requires any organisation deploying customer-facing AI systems to disclose to users that they are interacting with an AI. It requires providers of generative content tools to implement machine-readable marking on AI-generated outputs. Operators running emotion recognition or biometric categorisation systems must notify the individuals affected. And for any new system entering the EU market on or after 2 August, compliance is required from day one.

One aspect of the regulation that most compliance programmes have not fully processed: Article 50 is not jurisdictional. Article 50 follows the user, not the provider. That is how the Act defines its own scope. A company headquartered in Dubai, Singapore, or New York that deploys AI-generated content visible to EU users is in scope. Where the output lands determines the obligation. The practical consequence is that Article 50 applies to any organisation with a customer base that includes EU residents, regardless of where that organisation is incorporated or where its AI systems are built and operated.

The organisations that will be caught short are not the ones building prohibited systems. They are the ones that assumed the regulation was still in the planning stage, or that it would only apply to organisations based in Europe.

 

The GDPR Comparison That Matters

GDPR was announced in 2016 and took effect in 2018. Two years of awareness campaigns, legal seminars, board-level briefings, and vendor remediation work. The compliance industry built an entire ecosystem around it. Privacy officers were hired. Data mapping exercises ran for months. By the time enforcement began, organisations at least understood what was expected of them, even if some were still catching up.

GDPR also reached beyond EU borders from the start. Any organisation processing the personal data of EU residents was in scope, regardless of where it was based. Article 50 operates on the same principle: it reaches wherever EU residents are on the receiving end of AI-generated content or AI-driven interactions.

Article 50 does not have that context. Most enterprise compliance functions have been tracking the Act’s overall timeline without separating out which provisions take effect when. The transparency obligations were not deferred. They were always scheduled for August 2026. But because the high-risk provisions dominated the conversation, the transparency rules arrived quietly, and they arrive soon.

Thirty-one days is not a planning horizon. It is an implementation sprint, or it is already a compliance gap.

 

What Article 50 Actually Requires

The obligations are more specific than the general framing of “AI transparency” suggests, and that specificity matters for scoping the work.

The most broadly applicable obligation is disclosure. If a user is interacting with a chatbot, a virtual assistant, or any automated system capable of conversation or personalised response generation, they must be told. The requirement is not a buried terms-and-conditions clause. It is a functional disclosure at the point of interaction. This applies from 2 August, to all systems, with no transitional provisions.

Generative content carries a second obligation. Organisations using generative AI to produce content distributed in EU-market contexts must ensure outputs carry machine-readable markers indicating AI generation. This applies to text, images, audio, and video. The AI Omnibus agreement provisionally agreed in May 2026 and expected to be formally adopted before 2 August extends this specific requirement to 2 December 2026 for systems already on the market before 2 August. For any new system entering the market from that date, the obligation is immediate. The extension is not a signal to deprioritise: December 2026 is not far away, and the technical implementation is not trivial.

Emotion recognition and biometric categorisation carry a third obligation, active from 2 August with no transitional period. Individuals must be informed when these systems are operating on them.

None of these obligations are complex in isolation. The difficulty is that most organisations have not mapped which of their current systems fall within scope, and that mapping exercise takes longer than 31 days when it is starting from scratch.

 

What to Do in the Next 31 Days

Non-compliance carries fines of up to €15 million or 3% of global annual turnover, whichever is higher. This is not a planning conversation. It is a board conversation.

Article 50 requires operational change: disclosure mechanisms built into interfaces, technical markers implemented in content pipelines, notification processes embedded in operational workflows. A policy document does not close this gap.

The practical starting point is a scoping exercise, and it needs to happen this week, not at the end of July. Three questions define the scope: Which customer-facing systems use AI in any form of interaction or response generation? Which content production workflows use generative AI to produce material distributed in EU-market contexts? Are any systems using emotion recognition or biometric categorisation?

If the answer to any of those questions is yes and the disclosure or notification mechanism is not already live, that is an Article 50 compliance gap.

Once the scope is clear, triage by exposure. Not every system carries the same risk. Externally facing consumer products in regulated sectors carry a different risk profile than internal productivity tools. Sequence the remediation by audience, jurisdiction, and volume of interaction.

Confirming the mechanisms actually work is where most programmes get caught. A disclosure notice that technically exists but is not surfaced at the point of interaction does not satisfy the requirement. The same applies to machine-readable markers that are added to some content outputs but not systematically applied across all generative workflows. Implementation is not the same as compliance.

 

31 Days Is Not a Problem. 32 Days Is.

There is still time to close this gap for organisations that act now. August 2026 is not GDPR day one, when regulators were finding their feet. It is an enforcement event in a regulatory framework that has had two years of published timelines. Regulators will not be looking the other way.

The organisations that treated the high-risk provisions as the whole story now have 31 days to correct that assumption. Wherever they are based.

Pre-Mortem: Apple Intelligence at Work

Posted on by

The Pre-Mortem is a weekly series on this blog. Each piece applies five questions to a major technology commitment before the outcome is known.

On 9 June 2026, Apple used its annual developer conference to announce that Siri had become something different. Not a smarter assistant. An agentic AI layer that could take actions across applications, services, and workplace workflows on behalf of its users, across a hardware ecosystem of more than 2.5 billion active devices. The world’s most valuable company had turned its operating system into an AI agent. The question the keynote did not answer was straightforward: when it gets something wrong at work, who is responsible?

The Bet

Apple is betting that privacy and accountability are the same problem. Its Private Cloud Compute architecture is genuinely novel: stateless, ephemeral, cryptographically auditable, with production builds published within 90 days for independent inspection. At WWDC 2026, Craig Federighi stated: “data is only used to execute your request, and outside experts can continue to verify this promise at any time.” The claim is that if Apple cannot read your data, no one can. What this architecture was not designed to answer is what happens when Apple Intelligence takes a workplace action on your behalf and gets it wrong. That is a different question. Apple has framed the privacy answer as if it covers both.

The Assumption

Everything turns on one distinction: that an architecture designed to prove Apple cannot access your data also constitutes a framework for enterprise accountability when AI actions produce incorrect outcomes.

It does not. Privacy means Apple is not the party reading your data. Accountability means someone is responsible for what the AI produces from it. Those are different obligations. No document currently published by Apple closes the gap between them. The existing AppleCare for Enterprise terms explicitly disclaim liability for lost profits, damage, corruption, or loss of data, or interruption of business. There is no AI-specific carve-out, no enterprise service level agreement for Apple Intelligence outputs, and no accuracy standard committed to publicly.

The Sequence

Three weeks before WWDC 2026, Apple settled a $250 million class action over Siri AI features it had promoted during the iPhone 16 launch but did not deliver. The settlement included no admission of wrongdoing. In April 2026, Apple’s CEO Tim Cook announced his departure from the role, with John Ternus, the head of hardware engineering, confirmed as his successor from September 1, 2026. Ternus had no publicly stated role in shaping Apple Intelligence. At WWDC 2026, enterprise MDM controls for Apple Intelligence were available in beta only, with general availability expected in autumn 2026. The agentic deployment was announced. The governance controls that enterprises need to deploy it responsibly were not yet generally available.

The Pager

Craig Federighi, Senior Vice President of Software Engineering, is the named face of Apple Intelligence. Amar Subramanya, Vice President of AI, is the operational lead, reporting to Federighi since the retirement of John Giannandrea earlier this year. Neither has made any public commitment regarding enterprise accountability for AI outputs. By September 2026, John Ternus will carry the CEO accountability for a deployment he did not architect, operating under governance terms that were written before agentic AI was part of the product. No named individual or governance body is publicly committed to what Apple Intelligence does in enterprise workflows when it goes wrong.

The Proof

Apple has published no enterprise outcome measure for Apple Intelligence. No accuracy benchmark, no error rate commitment, no service level agreement for business customers. The company’s transparency commitments for Private Cloud Compute are real: production code published within 90 days, a cryptographically auditable log, a virtual research environment for security testing. These are privacy verification mechanisms, not performance standards. A survey of approximately 100 enterprise IT administrators published in May 2026 found that the primary concern was data exfiltration to unmanaged providers, and that eight per cent of organisations had already moved to prohibit AI features entirely. No one at Apple has publicly committed to a measure that would settle that question.

The Verdict

Apple has done more than most technology companies to make its cloud AI architecture independently verifiable. Private Cloud Compute is a credible attempt to resolve the privacy half of the enterprise AI problem. The accountability half remains open. If Apple publishes enterprise terms that define who carries responsibility for agentic errors in business workflows, and if John Ternus names a specific accountable owner for enterprise AI governance before the full iOS 27 rollout, the MDM controls announced at WWDC 2026 become the foundation of something credible. Without both, the hundreds of millions of Apple Intelligence-enabled devices deployed into enterprise settings are operating on a privacy promise. That is not the same thing as an accountability framework.

Your AI Initiative Isn’t Failing Because of the Technology

Posted on by

The technology works. That is almost never the problem.

Across most large organisations right now, AI pilots are running. Proof-of-concepts are producing results that make it into board presentations. Vendor demos are impressive. The innovation team is energised. And then, somewhere between the pilot environment and actual production, the whole thing quietly stops.

According to Deloitte’s 2026 State of AI report, drawn from more than 3,200 business leaders, only 25% of organisations have moved 40% or more of their AI experiments into live production. That number deserves to sit with you for a moment. Three in four organisations are running AI experiments that have not become operational capability. The technology is not the constraint. Something else is.

You Have Seen This Before

If you have been in transformation long enough, this pattern is not new. It is the same pattern from every large ERP programme that never fully went live. Every data platform that became a reporting tool rather than a decision-making engine. Every digital transformation that delivered a new front end while leaving the back-office processes unchanged.

The technology becomes the story because it is visible, measurable, and exciting to talk about. The execution conditions that determine whether the technology actually delivers are harder to photograph and harder to put in a slide: ownership, integration, adoption. So they get managed as a substream, treated as implementation detail, and quietly become the reason the initiative stalls.

This is not an AI problem. It is an execution problem that has found a new context.

Ownership Is Not a Committee

The single most common structural failure in AI deployments is diffuse accountability. Someone owns the technology. Someone owns the data. Someone owns the security review. Someone owns the business case. Nobody owns the outcome.

Committees do not drive production deployments. They review them, adjust them, query them, and occasionally approve them. The organisations that close the gap from pilot to production consistently have a single named individual who is accountable for whether the capability lands in the hands of users, works as intended, and is actually being used. Not a steering group. Not a centre of excellence. One person with the authority and the obligation to make it happen.

This is not a preference for a particular organisational design. It is what the evidence shows, consistently, across every transformation context where the accountability question has been seriously investigated. Singular ownership is not sufficient on its own. But its absence is almost always present when a deployment fails.

The Metric You Are Probably Not Tracking

Most AI initiatives are measured on model accuracy, inference speed, and technical performance. These are valid measures of whether the technology works. They are not measures of whether the initiative is delivering value.

The question that actually determines success is adoption. Is the tool being used? By how many people? How often? Has it changed the decision they were making, or is it an additional step they complete before making the same decision they always made?

Deloitte’s 2026 data found that despite AI tools being available to approximately 60% of the workforce in organisations surveyed, fewer than 60% of those workers actually use them regularly. Access is not adoption. Availability is not value. If you do not have an adoption metric from day one, not a plan to measure adoption eventually but an actual metric that someone is accountable for, you are measuring the wrong thing and you will find out too late.

Scope Is Your Production Variable

There is a reason pilots succeed and production deployments struggle. A pilot can be run by a small team, in a controlled environment, with curated data, limited integrations, and a sponsor who is personally invested in making it work. Production is fundamentally different. It requires integration with existing systems that were not designed for this. It requires security and compliance review. It requires monitoring, maintenance, and the ability to handle the variability of real-world use at scale.

The organisations that consistently move from pilot to production do one thing differently: they scope production more narrowly than they scoped the pilot. Not because they are being unambitious, but because a narrow, fully integrated, fully adopted capability that actually works is worth ten pilots that demonstrated potential and then stalled in the transition.

Start smaller in production than you think you need to. Prove the integration. Prove the adoption. Then expand. The ambition for scale is valid. The timing of it is where most programmes get it wrong.

The Pattern Closes the Same Way Every Time

The 54% of organisations that Deloitte found expecting to move the majority of their AI experiments to production within three to six months are not describing a plan. They are describing an aspiration. The organisations that will actually close that gap are the ones that address the execution conditions, not the technology stack.

Singular accountability. Adoption as the primary metric. Scope narrowed deliberately in production. None of these are technology decisions. They are leadership decisions, and they can be made before the next pilot is commissioned.

The technology is ready. The question is whether the organisation is.

 

The Dashboard Won’t Save Your Project. Your People Will

Posted on by

We have built an entire industry around the wrong obsession.

Walk into any project or programme environment today and tell me what you see. Dashboards. RAG statuses. KPI scorecards. Burndown charts. Milestone trackers. Automated reports that nobody reads in full but everyone references in meetings as though they tell the complete story.

We have convinced ourselves that if we can measure it, visualise it, and put it on a screen, we are in control.

We are not in control. We are comfortable. And those are not the same thing.

Because the thing that actually determines whether your project succeeds or fails, the thing that has always determined it, is not sitting in any dashboard. It is sitting at a desk, joining a call, navigating a problem at 4pm on a Friday when the system throws an error nobody anticipated and the go-live is Monday morning.

It is your people.

And most leaders have quietly forgotten that.

How We Got Here

The shift happened gradually, and it happened with good intentions.

Technology gave us visibility we never had before. We could track progress in real time, surface risks earlier, and report upward with confidence. That was genuinely valuable. Nobody is arguing for less information.

But somewhere along the way, the tool became the answer. The dashboard became the proxy for understanding. The metric became the substitute for the conversation. And the leader who once walked the floor, read the room, and sensed the real mood of a programme started trusting the green status on a screen instead.

The result is a generation of project environments where the reporting is polished and the delivery is fragile. Where everything looks healthy until it suddenly is not. Where nobody saw it coming, except the people closest to the work, who saw it coming for weeks and had nowhere safe to say so.

That is not a data problem. That is a leadership problem.

 

What the Software Cannot Tell You

Your project management software does not know that your lead developer has been quietly updating her CV for three weeks because she feels invisible on this programme.

Your dashboard does not know that the business analyst who owns the most critical workstream is running on empty and has been covering for a colleague who disengaged two months ago.

Your RAG status does not know that the reason everything is green is because the project manager is too afraid to report amber. Because the last time someone reported amber, the steering committee treated it as a personal failure rather than useful information.

Your metrics do not know that the vendor’s implementation team has internally deprioritised your programme because a larger client demanded more of their attention, and your account manager has been managing that fact rather than disclosing it.

None of this shows up in the data. All of it will show up in the outcome.

Professor Bent Flyvbjerg’s research on major project delivery, one of the most comprehensive analyses of project outcomes conducted, found that 91.5% of major projects experience cost overruns, schedule delays, or both. The primary driver is not technical failure. It is optimism bias: the structural human tendency to underestimate problems, which reporting cultures then amplify. A team that does not feel safe surfacing bad news will report optimistically. And the gap between what is reported and what is real compounds week by week until it cannot be managed.

This is the gap that leaders who have outsourced their judgement to software cannot see. The human information. The signals that travel through relationships, not reporting lines. The early warnings that only surface when people feel safe enough, and trusted enough, to tell you the truth.

People Deliver. Not Platforms

Let me be direct about something that gets lost in every technology conversation.

The software does not write the requirements. A person does. The platform does not manage the stakeholder who keeps changing scope. A person does. The dashboard does not have the difficult conversation with the supplier who is underperforming. A person does. The metric does not hold the team together at the point when the pressure peaks and the temptation to cut corners becomes real.

A person does.

Every single meaningful act in the delivery of a project or programme is a human act. The technology supports it, documents it, and reports on it. But it does not do it.

This sounds obvious. And yet the way most organisations invest their leadership attention, their development budget, and their improvement energy tells a completely different story. They upgrade the tools before they develop the people. They add another dashboard before they ask whether their team leaders have the skills to have honest conversations. They buy new software to solve problems that are fundamentally about trust, capability, and culture.

And they wonder why the new system does not fix the delivery problem.

The People Who Confirm Success

Here is the other half of the equation that rarely gets enough attention.

It is not just the people who deliver the project that matter. It is the people who decide whether it worked.

The clinician who was supposed to use the new system and quietly reverted to the old one because nobody involved her in the design. The frontline manager who was presented with a new process in a one-hour training session and had nowhere to raise the fact that it does not reflect how the work actually happens. The customer who was told the transformation would make their experience better and is still waiting.

These people are the real success criteria. Not the go-live date. Not the project closure report. Not the benefits case that was written eighteen months before anyone understood what was actually being built.

Transformation succeeds when the people it was designed for adopt it, use it, and tell you it made a difference. And they will only do that if they were treated as participants in the process, not recipients of its output.

What Recalibration Actually Looks Like

Leaders who get this right do not look fundamentally different from the outside. They attend the same meetings. They review the same reports. But they do something that most of their peers have quietly stopped doing.

They go to where the work is.

Not to check on it. Not to apply pressure. To understand it. To ask the questions that the dashboard cannot answer. How are you actually finding this? What is slowing you down that is not on the risk register? What do you know that I should know?

Google’s Project Aristotle, an internal study of more than 180 Google teams, found that psychological safety was the single strongest predictor of team effectiveness, above individual talent, structure, and every other measurable factor. Amy Edmondson’s research at Harvard Business School reinforces this from a delivery perspective: teams where people feel safe to raise problems surface them earlier, when they are still recoverable. When people do not feel safe, the information gets filtered. And filtered information is what produces the green dashboard above the failing project.

They treat their team’s energy as a delivery asset, because it is. They notice when someone has gone quiet. They notice when the language in status reports starts becoming defensive rather than informative. They notice when the optimism of the first month has been replaced by the grinding compliance of a team that no longer believes the work matters.

And they act on what they notice. Not with a new metric. With a conversation.

They invest in the human layer of delivery the way that most organisations invest in the technical layer. Deliberately. Consistently. Not as a soft add-on to the real work, but as the foundation of it.

The Investment Gap

The question is not whether your tools are good enough.

For most organisations, the tools are fine. In many cases, the tools are excellent. The dashboards are sophisticated. The reporting is comprehensive. The project management frameworks are mature.

And yet the delivery outcomes have not improved at the rate the technology investment suggested they should. PMI’s research, tracking project performance across thousands of organisations globally, found that communication failure contributes to one in three project failures. The gap between organisations that invest seriously in the human and communication layer of delivery and those that do not is measurable, consistent, and significantly larger than most leaders assume.

The gap is not in the software. It is in the leadership attention.

What would change if you spent the same energy on understanding your people that you currently spend on reviewing your reports? What would surface if your team genuinely believed that telling you the truth was safer than protecting the status? What decisions would you make differently if you had the human information as clearly as you have the data?

Those are not rhetorical questions. They are the questions that separate the programmes that deliver from the ones that drift.

The Skill No Platform Replaces

Every programme failure I have ever been close to had warning signs that the data did not capture. The signs were there in the people. In the energy levels. In the conversations that stopped happening. In the problems that got managed rather than solved.

And in almost every case, the leaders were looking at a screen when they should have been reading a room.

The software is not the problem. The hardware is not the problem. The metrics and the dashboards are not the problem.

The problem is that we have allowed them to replace the most important leadership skill there is.

The ability to understand people. To create the conditions where they do their best work. To recognise when they are struggling before it shows up in a project status. To build the kind of trust that means the real information travels fast enough to matter.

No platform does that. No tool does that.

Only you do that.

And the projects that remember it are the ones worth talking about.

Pre-Mortem: Twenty Million Members, No Published Error Rate

Posted on by

The Pre-Mortem is a weekly series on this blog. Each piece applies five questions to a major technology commitment before the outcome is known.

By the end of this year, twenty million Americans will use an AI companion to check whether their treatment has been approved, understand their benefits, and find out where they stand on a coverage dispute. UnitedHealth Group, the largest health insurer in the United States, calls it Avery. What the company has not published is what happens when Avery gets it wrong, and who carries it.

The Bet

UnitedHealth Group is investing more than $1.5 billion in AI in 2026. Avery is one part of a portfolio of over one thousand AI applications now operating across its insurance, pharmacy, and healthcare delivery businesses. The company expects a two-to-one return, much of it within the next eighteen months.

The scope goes further than the navigation functions Avery handles publicly. UnitedHealth has stated its intention to embed AI across claims decisions, clinical documentation, billing code selection, and fraud detection. The bet is that AI can absorb these regulated, high-stakes workflows faster than the accountability architecture around them can be clarified.

The Assumption

The whole bet turns on this, that an AI companion helping members find their benefits is categorically different from an AI algorithm making coverage decisions.

That distinction matters to UnitedHealth and to the regulatory debate around it. It is also the exact point where the accountability gap lives. Avery’s scope includes claim approval status and benefit explanations. In the sequence of a denied treatment, those interactions are not neutral, they are the moments where a member either understands their rights or does not. The line between navigation and decision sits precisely where the product is deployed.

 

The Sequence

UnitedHealth has been here before. Between 2019 and 2022, its subsidiary naviHealth deployed an AI tool called nH Predict to manage post-acute care decisions for Medicare Advantage members. A Senate investigation found that UnitedHealth’s denial rate for post-acute care claims more than doubled after nH Predict was deployed. A federal class action, Lokken v. UnitedHealth Group, alleges that the algorithm overrode treating physicians’ recommendations and carried a 90 per cent error rate on appeal, nine of every ten denied claims reversed when challenged.

That lawsuit is still advancing. In March 2026, a federal court ordered UnitedHealth to disclose its AI denial algorithm documentation, including internal AI Review Board materials, documents related to government investigations, and business records reaching back to 2017. Avery launched the same month to 6.5 million members, with a target of 20.5 million by year-end.

The sequence matters. The error rate history of the predecessor tool is documented and in litigation. The commitment not to repeat it with Avery has not been published in measurable form.

The Pager

UnitedHealth states that Avery is governed by a responsible use policy with review and approval from its AI Review Board. That board governs model development. No published framework names which specific individual, body, or governance layer is accountable when an Avery interaction contributes to a coverage outcome that causes patient harm.

The regulatory picture does not close that gap. At least twenty-five states have issued guidance under the National Association of Insurance Commissioners (NAIC) model bulletin. Alabama, Indiana, Washington, and others have enacted specific laws requiring human sign-off on AI-assisted denials, most taking effect in 2026. But the Employee Retirement Income Security Act (ERISA) preempts state action against self-insured employer plans, which cover the majority of employer-sponsored insurance. Federal oversight through the Centers for Medicare and Medicaid Services (CMS) and the Department of Health and Human Services (HHS) covers Medicare Advantage but carries no published standard for AI liability in individual claim decisions. The accountability is distributed. No name is on it.

The Proof

The $1.5 billion figure is confirmed. No committed outcome measure has been published for Avery’s error rate, its impact on denial rates, appeal success rates under AI-assisted decisions, or any patient safety incident reporting cadence.

Per CMS disclosures filed March 2026, the first year the agency required public reporting, UnitedHealth’s prior authorisation denial rate was 16.3 per cent in 2025, 4.8 percentage points above the industry average of 11.5 per cent. The company announced in May 2026 that it will eliminate prior authorisation for 30 per cent of services by year-end. Whether that changes the AI-in-the-loop accountability question for the remaining 70 per cent has not been addressed.

The Verdict

If the governance architecture catches up, if AI Review Board accountability is mapped to individual outcomes, if state AI denial laws close the ERISA gap, and if a committed outcome framework for Avery is published and audited, then this is exactly what responsible AI deployment in healthcare should look like, a major operator taking the accountability question seriously under public and regulatory scrutiny.

Without all three, twenty million people are interacting with an AI system whose error rate is undisclosed, whose predecessor carried a 90 per cent reversal rate on appeal, and where no named human is accountable for what it tells them about their care.

The bet is bold. The architecture to carry the loss has not been built yet.