Category Archives: Leadership

Handling Stakeholder Expectations in Digital Transformation: The Honesty Problem

Posted on by

 

Most failed digital transformations were not derailed by technology.

They were derailed by a gap between what was promised at the start and what was achievable in reality. That gap existed from day one, embedded in the business case, and neither the sponsors nor the delivery team chose to address it directly until the programme was already in trouble.

The stakeholder expectation problem in digital transformation is routinely framed as a communication challenge. Better updates. More frequent steering committee engagement. Clearer reporting. These are sensible practices. They are also, in most cases, insufficient, because the problem is not that stakeholders were not kept informed. It is that they were kept informed using numbers and timelines that were not honest about the uncertainty behind them.

That is an honesty problem, not a communication problem. And the fix for it happens at the beginning, not during delivery.

 

The Business Case That Everyone Signed Off On

Digital transformation business cases are almost universally optimistic. Not because the people who write them are dishonest, but because the incentive structure in most organisations rewards ambition and penalises conservatism. A realistic business case, one that acknowledges uncertainty ranges, models downside scenarios, and commits to fewer benefits with higher confidence, is harder to get approved than an ambitious one. So the ambitious one gets written.

The consequence is that the business case becomes a set of commitments rather than a set of hypotheses. By the time the programme moves into delivery, the numbers in the original document are treated as targets rather than as estimates, even when the assumptions underlying them have already been revised. The expectation gap was always there. It was just papered over.

BCG’s analysis of more than 850 companies found that only 35% reach their stated digital transformation goals. Gartner’s October 2024 survey of more than 3,100 CIOs found only 48% of digital initiatives meet or exceed their business outcome targets. The gap is not primarily a delivery capability problem. It is a framing problem.

 

Scope at Altitude

The second structural cause of expectation gaps is scope defined at too high a level of abstraction. Transformation programmes are typically scoped during a phase when the delivery architecture is not yet understood, which means scope boundaries are drawn based on intent rather than on a detailed model of what delivery will actually require.

Both sides, sponsor and delivery team, leave the scoping phase with genuine but different understandings of what is included. Neither party is misrepresenting anything. They simply have not gone deep enough to discover the ambiguity. That ambiguity is then carried into the contract, into the programme plan, and eventually into the steering committee deck, where it will surface as a scope dispute at the moment least convenient for everyone involved.

The fix is not to define scope more tightly in the abstract. It is to define scope at a level of specificity that forces the ambiguity into the open before commitments are made. That is harder and slower than moving quickly to contract. It is also significantly less expensive than managing the dispute six months into delivery.

 

What the Programme Board Actually Hears

Stakeholder management, in practice, often means giving senior sponsors the confidence to remain supportive rather than giving them the information they need to make good decisions. Status reporting in large programmes tends to converge toward reassurance. RAG ratings stay amber longer than conditions warrant, because the consequences of going red feel disproportionate in the moment. Risks that have materialised are carried as risks rather than re-classified as issues. Forecasts are revised gradually rather than reset to reflect the actual picture.

This is not cynical. It is human. Nobody wants to be the person who delivers bad news. The programme team has worked hard. The delays feel temporary. There is always a reasonable argument for holding the line a little longer.

The problem is that by the time the gap between expectation and reality is reported honestly, it is too large to close without a significant reset. The reset conversation is much harder than it needed to be, because the sponsor was not kept informed of how the gap was developing.

 

The Expectation Reset Conversation

When the gap surfaces, and it always surfaces, the response that preserves the programme is not to defend the original business case. It is to reframe the conversation around what is still achievable, with what degree of confidence, on what timeline. That requires the delivery team to be willing to put a revised view in front of the sponsor, acknowledge that the original framing was overoptimistic, and propose a credible path forward.

That conversation is significantly easier when the relationship between sponsor and delivery has been built on honest reporting from the start. It is significantly harder when the sponsor has been receiving optimistic status updates and now feels misled, not because anyone intended to mislead them, but because the communication was shaped by the desire to maintain confidence rather than the obligation to maintain accuracy.

 

Less Ambiguity, Earlier

The conditions that produce the stakeholder expectation problem are well understood: optimistic business cases, scope defined at altitude, and status reporting shaped by the incentive to maintain confidence. None of these are inevitable.

The organisations that manage stakeholder expectations well are not the ones with the best communication strategies. They are the ones with the discipline to be specific about uncertainty before programmes begin, to define scope at a level of detail that surfaces ambiguity early, and to build reporting practices that give senior sponsors the information they need to make real decisions rather than the reassurance they want to maintain support.

Less ambiguity earlier. Fewer numbers presented as certain when they are estimated. Fewer commitments made before the delivery architecture is understood.

That is the fix. It is harder to sell at the outset and significantly easier to live with throughout delivery.

The AI Infrastructure Race Has Already Been Decided, Just Not Where You’re Looking

Posted on by

 

Four companies have committed more capital to a single region’s AI infrastructure than most countries spend on national defence in a year.

AWS, Google, Microsoft, and Oracle have collectively committed more than 160 billion US dollars to building AI infrastructure across Asia-Pacific between January 2024 and May 2026, according to McKinsey’s analysis of the region’s data centre demand. That is not a forecast or an aspiration. It is capital already committed, over a 28-month window, by the four organisations best positioned in the world to judge where AI compute demand is actually heading.

Most enterprise conversations about AI strategy still treat the geography of AI capability as fixed, anchored in North America and Europe. That assumption stopped being accurate somewhere in the last two years, and the redrawing is happening in Asia-Pacific, largely unnoticed by the boardrooms it will eventually affect.

 

The “Follower” Narrative Was Already Wrong

The conventional framing of AI outside North America and Europe has always been one of catching up, adopting capability built elsewhere, closing a gap set by others. That framing was already inaccurate before this capital started moving, and the UAE is the sharpest evidence of it. Microsoft’s AI Economy Institute put the UAE’s working-age AI adoption at 70.1 per cent in its Q1 2026 diffusion report, the highest of any economy measured, against a global average of 17.8 per cent. Abu Dhabi is also home to Stargate UAE, a 5-gigawatt AI campus built with OpenAI, Oracle, and Nvidia that is now the largest AI infrastructure deployment outside the United States. Neither of those is a country catching up. That is a country leading.

The hyperscaler capital now moving into Asia-Pacific specifically, the $160 billion figure McKinsey tracks across AWS, Google, Microsoft, and Oracle, sits in a different regional bucket to the UAE in most analysts’ own classifications, McKinsey included, which places the Gulf within EMEA rather than APAC. But read together, the pattern is bigger than either region’s infrastructure story on its own. AI leadership has already decentralised away from North America and Europe in adoption terms. The capital now following it into Asia-Pacific is the same shift playing out in infrastructure terms, just in a different part of the map. The four largest cloud infrastructure providers on earth are not building in Asia-Pacific because the region is catching up. They are building there because the assumption that AI capability originates in the West and diffuses outward has already been disproven elsewhere, and they are positioning for where demand actually sits next.

That distinction matters for anyone making a ten-year technology strategy decision today. Compute infrastructure built now does not simply serve current workloads. It becomes the physical foundation that shapes what is commercially viable to build on top of it for the following decade. The parallel worth drawing is North American cloud infrastructure investment around 2015, which quietly determined which companies had a structural cost and latency advantage for the cloud-native decade that followed. Most of those advantages were locked in years before most executives recognised the pattern.

 

Building Faster Than Anyone Can Govern

What makes this moment genuinely worth attention is not just the scale of the capital commitment. It is the gap between that commitment and what has followed it.

The physical infrastructure, the data centres, the compute capacity, the power agreements, is being built at a pace the market has not seen before. The governance, integration, and organisational capability needed to actually use that infrastructure well has not kept pace at anything like the same speed. This is the same structural gap showing up across every AI signal this year: deployment and physical capacity moving faster than the organisational readiness required to extract value from either.

For enterprises operating in or adjacent to Asia-Pacific markets, this creates a specific and immediate strategic question, not a hypothetical one for next year’s planning cycle. The infrastructure being built now will define whose AI workloads run cheaply, quickly, and reliably in the region from 2027 onwards. Enterprises without a considered position on that infrastructure are not neutral bystanders. They are watching the operating environment for their future competitors being constructed, largely without their input.

 

What This Actually Requires From Leadership

Chasing every regional infrastructure headline is not the answer. Two things are.

The first is a straightforward board-level question that most technology strategy committees have never actually asked: does our AI roadmap account for where the compute capacity underneath it is being built, and by whom? Most enterprises with APAC exposure have not asked this, because compute geography has always been treated as an IT procurement detail rather than a strategic input.

The second is timing discipline. The infrastructure decisions with the longest shelf life, cloud provider selection, data residency architecture, regional partnership structures, are being made now, this year, by enterprises that recognise the window. Wait for the 2027 competitive gap to become visible and the decision will already have been made, by whichever provider has the compute capacity and the customer relationship in the region first.

The infrastructure race rarely announces itself as urgent while it is still open to influence. It only looks urgent in hindsight, once the capital is spent and the advantage is locked in. Right now, for Asia-Pacific, it is still open.

Your Enterprise Architecture Is Built on a Map That No Longer Exists

Posted on by

Most enterprise technology decisions are made on a map that no longer reflects the territory. Vendors occupy defined positions. ERP here, CRM there, ITSM in its lane, workflow tooling beneath. Procurement, architecture, and integration planning all proceed on the assumption that those positions are reasonably stable.

Two announcements made within days of each other in May 2026 did not just shift those positions. They rendered the map itself unreliable.

At Knowledge 2026, ServiceNow unveiled Autonomous CRM, covering sales, service, quoting, order fulfilment, invoice disputes, renewals, and the full customer lifecycle. A direct entry into Salesforce’s core market from a vendor whose identity has been workflow and ITSM. At Sapphire 2026, SAP declared itself a business AI company, launched its Autonomous Enterprise vision, in which AI agents execute end-to-end business processes, with humans directing strategy rather than managing individual steps, and acquired Reltio to make enterprise data AI-ready. An ERP vendor positioning as an AI orchestration layer across the entire enterprise.

Most commentary has treated these as two separate vendor stories. They are not.

 

Two Announcements. One Signal.

What ServiceNow and SAP announced is not primarily about features. It is about boundaries, and the dissolution of them.

For the past decade, enterprise technology portfolios have been built on a category model. You choose an ERP, a CRM, an ITSM platform, a workflow layer, and you integrate them. Vendors in each category compete within it. The architecture question is mostly about how the categories connect, not whether the categories themselves hold.

That model has broken. ServiceNow is not extending into adjacent territory around the edges. It is standing directly in Salesforce’s most defensible ground, covering sales pipeline, quoting, order management, and customer lifecycle, with AI as the differentiator. SAP is not adding AI features to its ERP. It is repositioning as the orchestration intelligence for the entire autonomous enterprise, with a master data acquisition to back it.

The category model that procurement teams, architecture boards, and technology roadmaps are built on is now operating on assumptions that neither vendor supports.

 

The Roadmap Problem

This matters less as a vendor story and more as a planning problem.

Enterprise technology decisions have long lag times. A CRM strategy agreed in 2023 reflects assumptions about what Salesforce competes with and how. An ERP consolidation approved in 2024 was scoped against SAP doing one thing and other vendors doing adjacent things. Integration architectures designed eighteen months ago were designed for a world where the platforms stayed in their lanes.

None of those assumptions survived May 2026. And the organisations currently finalising multi-year enterprise software contracts, negotiating renewal terms, or approving architecture blueprints need to know that before they sign.

The problem is not that ServiceNow and SAP have made bold moves. Vendors always make bold moves. The problem is that decisions downstream of those moves, about what to buy, what to build, what to integrate, and which vendor relationships to deepen, are still being made against the old map.

Two specific conversations are worth having before any major enterprise software decision closes in the next twelve months.

The first is the vendor dependency audit. When your workflow vendor is also your CRM, and your ERP vendor is also your AI orchestration layer, the concentration risk in your technology portfolio changes. So does the negotiating leverage. So does the cost and complexity of exit if you need it later. These are not hypothetical concerns. They are the direct consequence of vendors collapsing categories.

The second is the integration investment review. Integration work designed to connect cleanly bounded platforms does not simply carry across when those platforms expand into each other’s territory. Some of it becomes redundant. Some of it creates conflict. Some of it was justified by a separation of function that no longer exists. If your architecture team has not reviewed integration design against what ServiceNow and SAP announced in May 2026, that is a gap worth closing quickly.

 

What the Briefing Should Have Said

Technology updates for executive teams and programme boards tend to cover vendor announcements as market news. ServiceNow does this, SAP does that, here is what it means for the industry. That framing is too distant to be useful.

The briefing transformation leaders needed, and in most cases did not receive, is this: the vendor categories on which your enterprise architecture is built are collapsing. Two of the largest platform vendors are now competing directly across the boundaries that your current roadmap treats as fixed. The decisions you need to revisit are specific, and the window before contracts close is finite.

That is a different conversation from a product announcement. It requires someone in the organisation to have read the news, synthesised its implications, and brought it to the table as a strategy question rather than a technology update.

Most organisations are not structured for that kind of synthesis. Technology teams report on what vendors do. Strategy functions rarely track vendor positioning in this level of detail. The CIO’s office is often the only place where the two sets of knowledge meet, and it is frequently operating at capacity on current programmes rather than monitoring future architecture exposure.

The gap this creates is real, and it has a cost. Not immediately, but at contract renewal, at architecture review, at the moment an integration investment turns out to have been built against a boundary that no longer exists.

The ServiceNow and SAP announcements are not the story. The story is that the category model your technology decisions are built on changed, and most of the people who need to know have not been briefed. That is an organisational problem, not a technology one, and the organisations that address it before the next contract closes will be in a materially different position from the ones that address it after.

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.

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.

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.

What Regulated Industries Know About Speed That Everyone Else Is Learning the Hard Way

Posted on by

 

There is a common assumption in business that regulation slows you down. That the organisations operating fastest are the ones least constrained by oversight. That compliance is a tax on progress.

The organisations now paying the heaviest price for AI governance failures are the ones that operated for years on exactly that assumption.

IBM’s 2025 Cost of a Data Breach Report found that 63% of organisations experiencing a material breach either had no AI governance policy or were still developing one. Shadow AI alone added an average of $670,000 to individual breach costs. The Stanford HAI AI Index recorded 233 documented harmful AI incidents in 2024, a 56% year-on-year increase. These are not primarily failures in regulated sectors. They are failures concentrated in organisations that never had to build governance infrastructure because, until recently, they never had to.

Financial services, healthcare, and government have something that fast-moving technology companies are now being forced to acquire under duress: the institutional knowledge of how to move at pace while the governance is on.

The Misconception About Constraint

Leaders who have spent most of their careers in lightly regulated environments tend to read compliance as friction. Something that adds time to a decision, introduces review cycles, and requires additional sign-off. In that framing, less compliance means faster execution.

What this framing misses is the distinction between compliance as architecture and compliance as checkpoint. A checkpoint is friction. It exists at the end of a process, adds a review stage, and slows the pipeline. Architecture is different. When governance is built into how a system is designed and how decisions are made, it does not add a stage to the process. It is the process.

The organisations in financial services and healthcare that move fastest on AI deployment are not the ones that find clever ways around their regulatory obligations. They are the ones that have built governance into their operating model, their system design, their approval authorities, and their risk frameworks so thoroughly that compliance is not a separate consideration. It is already done by the time a decision reaches an approval point.

Thirty Years of Governance Muscle

This is not an accident. Regulated industries have had decades of pressure to solve exactly this problem. A bank that cannot move fast cannot compete. A hospital that cannot adopt new clinical technology falls behind in patient outcomes and staff capability. A government department that does not modernise its systems loses efficiency and public confidence.

The answer these sectors arrived at, not by choice but by necessity, is embedded governance. Named senior owners for material deployments. Cross-functional oversight bodies with actual authority to pause or redirect, not just to advise. Pre-approved frameworks that allow decisions to be made quickly within defined boundaries, rather than requiring full escalation every time.

The results are measurable. Healthcare AI adoption in outpatient and ambulatory care doubled in two years, from 4.6% of firms in 2023 to 8.7% in 2025, within one of the most tightly regulated environments in the world, according to research published in PMC drawing on US Census Bureau Business Trends and Outlook Survey data. That pace of change did not happen despite the regulation. It happened because enough organisations in that sector had built the infrastructure to move quickly and safely at the same time. Overall healthcare AI adoption still lags sectors such as information services and professional services, where adoption exceeds 20%. The doubling reflects a strong rate of growth, not yet sector leadership in absolute terms.

What the Unregulated Sector Is Now Facing

The regulatory picture for AI is more complex than it appeared eighteen months ago, and understanding that complexity matters.

The EU AI Act has been materially reshaped. Prohibitions on unacceptable AI practices came into force in February 2025. Obligations for general-purpose AI models followed in August 2025. But an AI Omnibus legislative package, agreed in May 2026, delayed the Act’s most commercially significant provisions, those covering employment, biometrics, critical infrastructure, and education, until December 2027 at the earliest. The timeline has extended. The direction has not changed.

In the United States, the trajectory is different. The current federal administration has moved toward a consolidated national framework, explicitly designed to preempt the patchwork of state-level regulation that was developing. Colorado’s original AI Act, among the most comprehensive state-level frameworks, was replaced in May 2026 by a narrower successor focused on disclosure obligations rather than risk management requirements. The patchwork has changed shape. Any organisation planning its governance around a specific jurisdiction’s requirements may be planning around a moving target.

AuditBoard’s 2025 research found that only one in four organisations has a fully implemented AI governance programme. Among organisations with only partial AI governance guidelines, just 25% feel confident in their AI posture. Among those with mature, embedded governance frameworks, that figure rises to 48%, according to research from the Cloud Security Alliance and Google Cloud. Governance maturity is the strongest predictor of AI readiness, above deployment volume, tool selection, or the pace of regulatory change in any given jurisdiction.

The leaders with an advantage right now are not necessarily the ones tracking the latest regulatory guidance. They are the ones who understand that IBM’s breach cost data is accumulating well ahead of any enforcement regime. The external pressure may have shifted its timeline. The operational risk has not.

Governance as Competitive Advantage

The organisations that will move fastest through the current period of regulatory evolution are not the ones trying to stay ahead of each new requirement as it emerges. They are the ones building governance architecture now that will not need to be retrofitted later, whatever form external pressure eventually takes.

That means a named owner for every material AI deployment, not a committee, a person. It means oversight that has genuine authority to pause a deployment, not just to note concerns. It means pre-approved tooling and decision boundaries that allow teams to move without full escalation while still operating within defined risk tolerances.

This is not new governance theory. It is the operating model that financial services and healthcare organisations were forced to develop, iteration by iteration, under regulatory pressure. The knowledge exists. The question is whether leadership teams outside those sectors are willing to learn from it before the external pressure forces the same hard lessons.

The evidence that governance accelerates rather than inhibits deployment is not theoretical. Databricks’ State of AI Enterprise Adoption report found that financial services leads across industries in moving AI from experimental to production, reducing its ratio of experiments per production deployment from 29:1 to 10:1, the sharpest improvement of any sector measured. That is not a coincidence of timing. It is the measurable output of thirty years of building the infrastructure that makes fast deployment safe.

Speed and compliance are not opposites. In the organisations that have figured this out, they are not even in tension. Governance is the infrastructure that makes speed sustainable.

The industries that built that infrastructure under duress are now, inadvertently, the ones best positioned to show everyone else how it works.

The mechanics of building that architecture, including the five characteristics that separate real governance from the committee-and-checkpoint version most organisations have built, are covered in the companion piece Governance Is Not a Committee. It Is a Decision Architecture.