Category Archives: Management

Pre-Mortem: The Big Four’s AI Citation Problem

Posted on by

On 28 July 2026, PwC Middle East responded to an investigation into four of its own published reports. The investigation, run by the AI-detection company GPTZero, had found fabricated citations, non-existent sources, and, in one report, a teenage blogger with 280 followers cited as an authority on a JPMorgan initiative. PwC’s statement: the company “takes the accuracy of our published research seriously” and was “updating a limited number of supporting citations.”

PwC was not first. It was the fourth.

This is the sixteenth piece in the Pre-Mortem series. Five questions, applied to the public record, before the outcome is known.

 

The Bet

Deloitte, EY, KPMG and PwC are betting that a pattern spanning five publicly documented reports, four countries, and under two years can be absorbed as unconnected incidents rather than treated as a shared problem with a shared cause. Each firm has responded on its own terms: a partial refund from Deloitte, quiet withdrawals from EY and KPMG, a promise to update “a limited number” of citations from PwC. None has published a shared verification standard. None has described what changes in how AI-assisted work is reviewed before the next report carries its name. The bet is that four reputations, built over more than a century, can absorb five independently verified failures of the most basic check a research report is supposed to pass: that the sources it cites exist.

 

The Assumption

Every one of the four firms has offered a version of the same explanation once caught. KPMG cited guidelines requiring human oversight to validate content and verify sources. PwC cited quality control processes it expects all its people to adhere to. The assumption underneath both statements: that a written guideline is itself a control, that if a policy exists, a human somewhere is presumed to have applied it before publication. EY’s report, “Points of Attack: Uncovering Cyber Threats and Fraud in Loyalty Systems,” carried the names of two partners and a senior manager in its byline. GPTZero’s analysis put the document at roughly 72 per cent AI-generated content, with more than half its 27 sources failing to correspond to anything real. Two partners and a senior manager reviewed that document before it went out, in name. What “reviewed” required in practice is the question none of the four firms has answered.

 

The Sequence

December 2024. PwC Middle East publishes “Agentic AI: The New Frontier in GenAI,” later found by GPTZero to contain fabricated citations.

October 2025. KPMG publishes “Total Experience: Redefining Excellence in the Age of Agentic AI.” GPTZero later finds 45 citations, 5 accurate, at least 16 fabricated.

October 2025. Deloitte refunds AU$97,000 of its A$440,000 contract with Australia’s Department of Employment and Workplace Relations, after a fabricated Federal Court quote and references to non-existent research papers are identified.

November 2025. Newfoundland and Labrador’s C$1.6 million Deloitte health workforce report is found to contain fabricated citations, including one crediting a Dalhousie University researcher as author of a paper that does not exist. Premier Tony Wakeham calls it “concerning.” Deloitte stands by its findings.

27 April 2026. South Africa’s draft National AI Policy is withdrawn 17 days after publication, after 6 of 67 citations are found fabricated. Minister Solly Malatsi calls it “an unacceptable lapse.”

14 May 2026. EY withdraws “Points of Attack” after GPTZero finds more than half its 27 sources do not correspond to real material.

12 June 2026. GPTZero publishes its investigation into KPMG. Five days later, this series covers a separate KPMG story without connecting the two.

28 July 2026. GPTZero publishes its investigation into four PwC Middle East reports. PwC responds that it is updating “a limited number of supporting citations.”

 

 

The Pager

Five public failures, four countries. Three were identified by the same three researchers, Paul Esau, Om Ogale and Alex Cui, working at GPTZero, not at any of the firms and not at any client who paid for the work. Every firm-level response has stopped at the firm: a refund, a report removed from a website, a statement that guidelines exist. No named individual at any firm has been identified as responsible for approving a document whose sources were not real. The one structural change on record did not come from a firm. Newfoundland and Labrador overhauled its own procurement process, requiring disclosure of AI use in future contracts. The government fixed what the contractor did not.

 

The Proof

None of the four firms has published a verification standard: a description of what checking a citation actually involves before a report carries its name. That is the proof measure, not an apology and not a quiet correction, but a public description of the review step, specific enough to be checked against the next report. The IAASB, the International Auditing and Assurance Standards Board, is revising ISA 500, the international standard governing what constitutes sufficient, appropriate audit evidence. That project is still at the research stage and covers formal audit engagements, not the thought-leadership publishing where three of these five failures occurred. Until one firm publishes what verification looks like in practice, every new report each of them publishes resets the same test.

 

Verdict

If one firm publishes a specific, checkable verification standard before a sixth incident surfaces, it becomes the reference point the other three are measured against, the position peer accountability once created around data breach disclosure, where one actor’s transparency made silence from the others harder to sustain. Newfoundland’s government has already shown the structural fix is available: a procurement clause requiring AI disclosure, written in days. If no firm moves first and a sixth incident surfaces, the pattern stops reading as isolated mistakes and starts reading as an industry’s operating baseline. Five failures in under two years, three caught by the same outside team. The firms selling AI governance advisory to clients have not yet demonstrated they can apply the same standard to their own published work. The next report each of them publishes is the test.

EasyJet Fixed an Age Bias in Recruitment. Most Digital Transformation Teams Haven’t

Posted on by

 

The number of easyJet cabin crew aged over 50 has more than doubled since 2022, up 127 per cent, according to the airline’s own figures. EasyJet says crew aged over 60 have “almost quadrupled” over the same period, and the airline has opened a fresh recruitment drive for the 2027 flying season, with applications opening in September. Getting there took a deliberate campaign. A large share of potential applicants assumed cabin crew work was reserved for younger people, and easyJet’s Director of Cabin Services, Michael Brown, put the fix plainly: over-50s bring both the skills to do the job and “a wealth of life experience that is appreciated by our customers and colleagues alike.”

 

This Is a Bigger Problem Than One Airline

The Centre for Ageing Better’s State of Ageing 2025 report shows why that perception carries a cost well beyond one airline. The UK’s employment rate for 55 to 64 year olds sits at 65 per cent, against 75 per cent in the Netherlands and Switzerland and 81 per cent in Iceland. The wider 50 to 64 employment rate sits 14 percentage points below the 25 to 49 rate. Closing that gap by 2030 would add an estimated £9 billion a year to the UK economy and £1.6 billion in annual tax and National Insurance revenue, according to the same research. That is the scale of value sitting behind a single, correctable assumption about who is fit to do a job.

 

The Same Bias, Earlier and More Expensive

The same assumption shows up earlier, and more expensively, in technology. CWJobs, working with the Centre for Ageing Better, surveyed 2,000 UK workers plus 250 people in tech who had experienced age discrimination, and found that tech employees start experiencing age bias at 29 and are considered “too old” by 38, roughly a decade before most people reach senior delivery roles. Forty-one per cent of tech workers report observing ageism at work, against 27 per cent across other sectors. Forty-seven per cent say they weren’t offered a role because of their age, and 31 per cent say they were passed over for promotion for the same reason. “Digital skills shortages mean discriminatory attitudes against age makes no business sense,” CWJobs director Dominic Harvey said when the findings were published, a point that has only got truer as the skills shortage he was describing has continued.

 

The Bias Has Already Reached a Tribunal

In Selazar Limited v McCabe, a tech company’s 29-year-old founder was found to have instructed a recruitment consultant to find “a younger team member who was more in tune with a young tech start company” in place of the firm’s 55-year-old finance director. The tribunal awarded her £125,604.98, including £20,000 for injury to feelings, and heard evidence that the founder had also signalled to potential investors that she was “too old to understand” the business. The case puts a figure on the same instinct easyJet had to overcome in reverse: treating experience as a cultural mismatch with a “young”, “digital” or “agile” identity, rather than as a straightforward capability question.

 

What Transformation Programmes Are Actually Short Of

That instinct is expensive in a way that goes beyond tribunal awards. Transformation programmes run into trouble for reasons that have nothing to do with technical skill: unclear governance, resistance treated as a communications problem rather than early diagnostic information, decisions made by people who have never been accountable for the outcome. Institutional knowledge, stakeholder trust built over years, and the judgement to recognise when a plan won’t survive contact with how the organisation actually operates are not junior capabilities. Screening for “young and agile” screens that experience out at precisely the point a programme needs it most, and does so before anyone has assessed whether the person applying could actually do the job.

 

The Fix Was Never Complicated

EasyJet’s fix did not require lowering a bar. It named the specific bias, redesigned recruitment and onboarding around it, then published the retention data alongside the recruitment numbers rather than stopping at the headline. Technology employers already have research going back years, and a tribunal ruling now sitting on the public record, telling them the same bias exists inside their own hiring and promotion decisions.

 

The Question Worth Asking Before the Next Senior Hire

What’s missing isn’t evidence. It’s a leadership team willing to treat this as a workforce design problem rather than a hiring afterthought. Before the next transformation lead, architect, or programme director role goes out with language built around “energy” or “digital native” instincts, it is worth asking what specific capability that language is actually screening for, and whether the organisation can afford to keep losing the experience it screens out along with it.

Nobody Owns AI in Your Organisation. That Used to Be Survivable.

Posted on by

 

In most organisations, nobody owns AI, not really. Not officially, not on an org chart, not in a way anyone could point to under pressure. For the last few years, that has been fine. Everyone touched AI a little, so no one needed to own it entirely.

That fuzziness is now expensive.

Two things changed the maths. The first is regulation. From 2 August 2026, the EU AI Act’s transparency obligations became enforceable: AI systems that interact directly with people, generate synthetic content, or use emotion recognition or biometric categorisation now require disclosure (European Commission), with providers facing fines of up to €15 million or 3 per cent of global annual turnover, whichever is higher (Cooley). A regulator does not care whether your organisation has formally assigned AI ownership. It cares who signs the compliance filing.

The second is spend. Global AI spending, including infrastructure capital expenditure, is on track to reach $2.5 trillion this year, a 44 per cent increase on last year, according to Gartner research reported by Fortune. Next year, Gartner expects that figure to climb to $3.3 trillion. That is capital being committed at a scale that normally comes with a name attached to the decision, not pocket-change experimentation.

Except it doesn’t. A Pearl Meyer survey of board members, CEOs, C-suite executives and senior managers found that just 34 per cent of C-suite executives say it is consistently clear which executive or team makes the calls on AI, the lowest confidence score of any group polled. Board members are considerably more settled, at 53 per cent. Senior managers below the C-suite, who carry out the actual AI work day to day, are more confident still, at 57 per cent. The C-suite sits in the middle of that gap, managing expectations from above and execution from below, and is the only group unsure who is actually in charge.

Meanwhile, PwC’s 29th Global CEO Survey, drawn from 4,454 CEOs across 95 countries, found that 56 per cent report no significant financial benefit from their AI investment so far, and only 12 per cent report gains on both cost and revenue (PwC). Spend accelerating, returns lagging, ownership unclear: three symptoms, one disease.

 

Governance Failure Wearing an Investment Story

I have watched this exact pattern play out on transformation programmes long before AI made it fashionable. A programme gets funded because the business case looks compelling on a single slide. Nobody sits down and decides who has the authority to stop it, slow it, or redirect it once it is underway. The absence of that decision does not read as a problem at the time, because everything is moving and everyone is busy. It reads as a problem eighteen months later, when the programme has drifted from its original purpose and there is no single person whose job it was to notice.

AI is running the same play at a faster clock speed. A RACI chart is not corporate theatre. It is the difference between a decision someone made on purpose and a decision that happened to everyone by default. Right now, most organisations have the second kind.

 

What an Actual Owner Looks Like

Contrast that with the UAE’s approach to its own AI commitment. In April 2026, Sheikh Mohammed bin Rashid Al Maktoum announced that 50 per cent of UAE government services and operations would run on agentic AI within two years, making it the first government in the world to commit to autonomous AI at that scale (Khaleej Times). Whatever view you take of the ambition, the governance structure was not an afterthought. Sheikh Mansour bin Zayed Al Nahyan was named to oversee implementation. Mohammad Al Gergawi was named to chair the taskforce running it. Before the programme scaled, someone’s name was attached to it.

It is not that most organisations lack ambition for AI. It is that they have skipped the one governance step that made every other major technology rollout survivable: deciding, on purpose, who is accountable before the spending accelerates past the point where anyone can meaningfully intervene.

 

Three Things That Actually Fix This

Name a single accountable owner for AI decisions at the level where spending actually happens. Not a committee. A person.

Separate who evaluates AI performance from who decides whether to scale it. Those are different jobs, and conflating them is how bad bets survive their first review.

Treat AI spending with no named owner attached to it as a governance red flag before it becomes an investment number on a board slide, not after.

 

None of this requires new technology. It requires the same discipline that used to be applied to every large capital commitment, before AI convinced everyone the normal rules no longer applied. They always did. The bill has simply arrived: from a regulator, from a survey, and from a CEO’s own board asking where the money went.

Pre-Mortem: NHS Federated Data Platform

Posted on by

 

On 3 August 2026, NHS England apologised. The apology confirmed what National Data Guardian Nicola Byrne had identified five days earlier: the Data Protection Impact Assessment (DPIA) for the Federated Data Platform had stated that only NHS staff could access identifiable patient data. That statement was wrong. Palantir staff held access to identifiable patient information within the national data integration environment, an arrangement the DPIA had not disclosed.

This is the fifteenth piece in the Pre-Mortem series. Five questions, applied to the public record, before the outcome is known.

The Bet

NHS England is betting that a £330 million platform built on Palantir’s proprietary Foundry software can serve as the trusted data infrastructure for NHS analytics, and that the governance commitments made publicly about data access are auditable in practice. The bet has been partially called already. The DPIA that underpinned the programme’s public accountability framework described access controls that did not match operational reality. NHS England acknowledged the error and corrected it. The bet that now matters: that the February 2027 break clause decision, whether to extend or exit, can be made on the basis of accurate information.

The Assumption

The single belief the whole framework rests on: that NHS England can demonstrate meaningful oversight and control of a platform whose codebase NHS analysts cannot read or edit. Palantir owns the Foundry software. NHS analysts work within the platform but cannot examine or modify the code that shapes its outputs. The National Data Guardian (NDG) criticism was triggered by the gap between what was publicly asserted about data access and what was operationally true. If the accountability assertion in the DPIA did not survive scrutiny, the assumption that NHS England can verify what Palantir staff do with patient data inside a proprietary system deserves the same examination.

The Sequence

November 2023. Palantir wins the £330 million FDP contract.

April 2026. Parliamentary debate on the FDP. NHS England officials warned staff internally not to criticise the platform’s performance.

12 May 2026. NHS England confirms Palantir staff have administrative access to identifiable patient data in the national data integration environment, contradicting earlier assurances.

June 2026. The government announces a formal review of the Palantir contract, following a Science, Innovation and Technology Committee report that branded the company “an unacceptable point of weakness” in UK public sector infrastructure.

9 July 2026. The Health and Social Care Committee writes to the Health Innovation Minister recommending the exercise of the February 2027 break clause, citing “serious mistrust” among the public towards Palantir.

29 July 2026. National Data Guardian Nicola Byrne formally criticises NHS England for inaccurate DPIA disclosure.

3 August 2026. NHS England apologises and confirms the DPIA error.

The Pager

The National Data Guardian used her statutory function and the result was a public apology from NHS England. The named individual who authorised the submission of a DPIA that did not accurately describe Palantir staff access has not been identified publicly. Jules Hunt, interim Director General for Technology, Digital and Data, holds the relevant executive function. The chief digital and information officer role has not had a permanent holder since at least early 2025; the most recent interim departed in April 2026, before the DPIA error became public. The programme sits with interim leadership in the window immediately before the most consequential procurement decision of its lifespan.

The Proof

February 2027 is the break clause decision point. The Department of Health and Social Care must actively trigger the first extension; if it does not, the contract lapses in spring 2027. The Health and Social Care Committee’s recommendation is on the public record. The government has not yet responded. The outcome measure is binary and specific: the break clause is exercised or it is not. Whether the platform’s actual adoption record across NHS trusts factors into that decision is the proof measure.

Verdict

If the government exercises the February 2027 break clause, it becomes the first time a cross-party parliamentary committee recommendation, a National Data Guardian rebuke, and a public apology from the contracting body have together produced a procurement exit in NHS technology history. That would be a significant accountability signal for every future public sector AI contract. If the contract is extended, the question shifts to what changed in the governance architecture to justify continuation, and whether the interim executives carrying the programme can demonstrate what that change looks like in operational terms. The break clause is not a threat. It is a proof point with a date.

Pre-Mortem: A Billion Workers Scored in Secret. Is It Legal?

Posted on by

On 20 January 2026, two job applicants filed a class action against Eightfold AI Inc. in a California state court. The complaint alleged that the company had scraped personal data on over one billion workers, scored every candidate on a zero-to-five scale, and discarded low-ranked applicants before any human saw their application. The legal basis is the Fair Credit Reporting Act (FCRA). The plaintiffs’ central claim is not that the algorithm was biased. It is that the algorithm existed in secret.

This is the fourteenth piece in the Pre-Mortem series. Five questions, applied to the public record, before the outcome is known.

 

The Bet

Eightfold AI and the companies deploying its platform are betting that an AI system which aggregates third-party data, including social media profiles, location data, and online tracking cookies, to score individuals for employment purposes does not meet the legal definition of a Consumer Reporting Agency under the Fair Credit Reporting Act. The complaint names Microsoft, Morgan Stanley, Starbucks, BNY, PayPal, Chevron, and Bayer as companies using Eightfold in their hiring process. Co-Founder and CEO Ashutosh Garg responded with a public statement on responsible AI, noting that the platform undergoes third-party bias audits and that data comes from candidates or employers, not third-party scraping. The bet is not about whether the algorithm is accurate. It is about jurisdiction: whether the FCRA, written before algorithmic hiring existed at this scale, reaches far enough to cover what Eightfold built.

 

The Assumption

The single belief the whole framework rests on: that an AI platform scoring candidates for employers is categorically different from a consumer reporting agency, because the platform does not produce a consumer report in the form the FCRA contemplates. Eightfold filed a 35-page motion to dismiss arguing precisely that. The hearing was held on 4 August 2026 before U.S. District Judge Yvonne Gonzalez Rogers in Oakland. No ruling has been published. If the assumption is wrong, the compliance obligations the FCRA places on consumer reporting agencies, including disclosure, consent, and accuracy mechanisms, apply to every AI hiring platform operating on third-party data at comparable scale.

 

The Sequence

20 January 2026. Class action filed by former EEOC Chair Jenny R. Yang and the nonprofit Towards Justice. The complaint: Eightfold AI functioned as an unregistered consumer reporting agency across a dataset of over one billion workers.

18 June 2026. Plaintiffs’ opposition to Eightfold’s motion to dismiss filed.

22 June 2026. In the parallel Mobley v. Workday case, a federal judge denied Workday’s motion to dismiss claims of race, age, and disability discrimination through AI hiring tools.

9 July 2026. Eightfold reply brief filed.

4 August 2026. Motion to dismiss argued in Oakland before Judge Yvonne Gonzalez Rogers. No ruling published as of 16 August 2026.

13 August 2026. Eightfold AI named “Agentic AI HR Solution of the Year” at the HR Tech Breakthrough Awards.

 

The Pager

Kistler et al. v. Eightfold AI Inc., No. 3:26-cv-01768 names Eightfold AI as defendant. No talent acquisition leader or CHRO at Microsoft, Morgan Stanley, Starbucks, or any other company deploying the platform has been named as a defendant, and no deploying company has publicly committed to disclosing the tool’s existence to applicants. The pager sits with the vendor. The question of who carries it at the companies deploying the platform remains unanswered.

Garg’s public statement on responsible AI is a creditable position. It does not address what obligations the companies using Eightfold carry, or what those companies owe to the candidates who may have been scored and discarded before a human saw their application.

 

The Proof

The motion to dismiss ruling is the first proof point. A denial advances the FCRA question to discovery and the merits. It would be the first federal answer on whether AI candidate scoring constitutes consumer reporting. A grant sends the question back to the FTC and Congress, where progress has not matched the scale of deployment. The outcome measure worth watching is not which side wins the motion. It is whether any major Eightfold client commits to applicant disclosure before the court decides whether disclosure is legally required.

 

Verdict

If Judge Gonzalez Rogers denies the motion to dismiss, the case advances and the FCRA question gets its first federal answer in the context of AI hiring tools. That ruling will matter to every organisation using algorithmic screening, not only Eightfold’s clients. A denial does not mean Eightfold loses; it means the question gets answered in a setting with evidence, argument, and binding precedent. If the motion is granted, the accountability gap returns to regulatory and legislative channels, where the pace has not matched the scale of the deployment. What would change this assessment is action of a different kind: a major employer publicly committing to applicant disclosure before the court makes the decision for them.

Prompt Injection Is a Governance Failure Wearing a Technical Costume.

Posted on by

Every prompt injection headline reads like a technical failure. A model got tricked. A filter didn’t catch it. The vendor needs to patch something.

That framing is comfortable, and it is wrong. The technical trick is real. The governance failure sitting underneath it is the actual story, and it is the one almost nobody in the room wants to own.

 

Why the Trick Works in the First Place

The mechanism is architectural, not a bug in the usual sense. Large language models treat the system prompt, the user’s request, and any text retrieved from an external source as a single stream of tokens. There is no reliable internal boundary between an instruction and a piece of data. A hostile sentence buried in a document, a web page or a support ticket can carry the same authority as a command typed directly by a trusted user, because the model was never built to tell the difference.

OWASP’s 2026 State of Agentic AI Security and Governance report found prompt injection now maps to six of its ten top categories for agentic applications, up from a mostly theoretical concern in the 2025 edition to one backed by documented breaches and tracked vulnerabilities. Coding agents dominate the attack data, and only 37% of organisations report having a policy in place to even detect unauthorised AI deployments running inside their own environment.

 

The Failure Is a Control Boundary, Not a Model Flaw

This is where the governance framing actually matters. Prompt injection succeeds because enterprise workflows assume the model can reliably tell trusted instruction apart from hostile text, an assumption that fails the moment one interface carries user intent, retrieved content and tool-facing control signals in the same session. Most organisations respond by treating guardrails as a static filter list rather than a real system of content separation, monitoring and authorisation. A filter can catch a known bad phrase. It cannot answer the actual governance question, which is who controls what the system is allowed to do once it has been steered.

Security researcher Simon Willison’s “lethal trifecta” names the actual risk condition plainly: an AI agent with access to private data, exposure to untrusted content, and the ability to communicate externally, all three at once, is where exfiltration happens. Meta’s own internal guidance treats those three properties as a budget rather than a checklist. Combine all three and the agent needs a human in the loop before it acts, not after.

 

Why This Keeps Getting Treated as IT’s Problem Alone

Handing this to the security team as a patching exercise misses what the data is actually showing. A model update might close one exploit path. It will not answer who approved an agent’s access to a customer database, why that same agent can also send emails externally, or what happens the day it does both at once because nobody ever wrote down that it should not be allowed to. Those are ownership questions, not model questions, and ownership questions do not get solved by a vendor release note.

 

What Governance-First Actually Requires

Start by classifying every channel an agent reads from according to trust level, and keep untrusted content out of instruction scope entirely rather than hoping the model sorts it out at runtime. Quarantine tool access behind explicit policy gates, so an agent combining private data access, untrusted content and external communication needs sign-off before it can act, not a retrospective audit after it already has. Treat a pattern of near-miss prompts as an abuse signal worth escalating, not a string of isolated one-off incidents each closed out individually.

All of it is the same governance discipline organisations already apply to identity and access management, pointed at a new kind of actor that happens to run on language instead of credentials, not a new technology purchase.

 

Who Approved This, and Did They Know What They Were Approving

Before the next prompt injection incident gets logged as a technical exploit, ask who actually approved the access the exploit relied on.

If nobody can answer that cleanly, the model was never the vulnerability. The governance around it was.

The $5.5 Trillion Bill for Doing Nothing About AI Skills

Posted on by

IDC put a number on the cost of enterprises not knowing what to do about AI skills: $5.5 trillion. Not by 2030. By the end of 2026.

That is not a distant workforce-planning problem. It is the price tag on decisions organisations are making, or more often deferring, this quarter.

The number comes from IDC’s survey of enterprise IT leaders across the US and Canada. It measures a specific kind of pain: product delays, lost competitiveness, and business walking out the door because the people needed to build and run AI capability were not there when the work needed them.

An IDC Spotlight Paper distributed via workforce-skills platform Workera applies the same figure directly to the AI skills conversation, and the application largely holds up. Most of what IDC’s original survey describes as a broader tech talent shortage is, in practice, an AI capability shortage wearing a wider label.

Three other figures make the same point from different angles. The World Economic Forum’s Future of Jobs Report 2025, surveying over a thousand employers and 14 million workers across 55 economies, found that 59% of the global workforce will need reskilling or upskilling by 2030, and that 11% of that group are unlikely to receive it. Indeed’s hiring data shows the share of job postings with “AI” in the title has more than tripled since 2022, from 2.6% to 8.3%. And PwC’s 2026 Global AI Jobs Barometer, built on more than a billion job advertisements, found that AI-skilled workers now command a 62% wage premium over comparable peers, up from 57% the year before and roughly 25% two report cycles before that.

These numbers describe a market that has already repriced itself, not a future state, while most enterprise workforce plans are still budgeted as though it hasn’t.

 

The Premium Is the Market Telling You Something

Wages move slowly almost everywhere except where genuine scarcity exists. A skill premium that has climbed from roughly 25% to 62% across three consecutive PwC survey cycles is not a normal labour-market signal. When a specific skill commands 62% more pay than the equivalent role without it, and that gap is still widening year over year, that is the market pricing in a shortage faster than most HR functions can respond to it, not a talent management curiosity.

Second Talent’s 2026 research puts a shape on that shortage: roughly 1.6 million open AI-related roles globally against around 518,000 candidates qualified to fill them, a demand-to-supply ratio a little over three to one. Every organisation competing for AI capability right now is competing inside that gap, and every quarter spent treating reskilling as a training-budget line item rather than a capital allocation decision is a quarter spent losing that competition to whoever moved first.

 

Why This Belongs in the Risk Register, Not the Learning and Development Plan

Most organisations still route AI reskilling through the same governance as any other training initiative: an L&D budget line, a completion metric, a once-a-year review. That treatment made sense when the skills in question were incremental. It does not hold up against a $5.5 trillion cost estimate and a wage market moving by double digits year over year.

A capital risk gets tracked differently to a training initiative. It gets a named owner, a quantified exposure, and a review cadence tied to the business calendar rather than the HR calendar. Few organisations apply that discipline to AI skills, because the function historically responsible for skills, HR, was never built to run risk registers, and the function that runs risk registers, finance and the PMO, was never asked to own workforce capability.

That gap in ownership is the reason the $5.5 trillion figure keeps compounding instead of shrinking, not a technicality.

 

What Actually Changes the Trajectory

Closing this gap requires three specific shifts most organisations have not made, not a bigger training budget.

Put a named executive owner on AI capability risk, distinct from whoever owns general L&D, with the same reporting rigour as any other material risk on the register. Measure the capability gap in the terms the wage market already uses: roles you cannot fill, roles you are overpaying to fill, and work you are declining because you lack the people to do it, not completion percentages on a training platform. And treat the reskilling decision as time-sensitive capital allocation, where every quarter of delay is a quarter in which the 62% premium, and the competitors already paying it, get further ahead.

 

The Window Is a Cost Curve, Not a Deadline

There is no single date after which the AI skills gap becomes unrecoverable. What exists instead is a cost curve that gets steeper the longer it is ignored, priced daily by a labour market that has already decided what AI capability is worth.

The organisations that treat this as a 2027 problem will be paying 2026 prices for it well into the decade. The ones already moving are the ones setting the price.

Small Talk Is Not Wasted Time. It Is the Only Rehearsal for Big Trust.

Posted on by

Most executives treat small talk as the tax you pay before the real conversation starts. Research on negotiation and workplace behaviour suggests it’s closer to the opposite: the low-stakes rehearsal that determines whether the real conversation goes anywhere at all.

 

What the Research Actually Shows

A frequently repeated claim holds that people who make small talk before negotiating are four times more likely to reach agreement. That number doesn’t survive a check against the study it’s supposedly drawn from. The actual 2002 research behind it, published in Group Dynamics, found something more modest but still real: negotiators who “schmoozed” beforehand reported significantly higher rapport than those who didn’t, and reached an impasse less often, 40.6% of the time versus 60.7%, though that gap was only marginally significant. The finding itself is that small talk measurably raises rapport and modestly improves outcomes. It is not some four-times multiplier, and repeating the inflated number would undercut exactly the kind of precision this argument needs to be taken seriously.

 

The Mechanism, Confirmed More Recently

A 2021 study in the Academy of Management Journal tracked 100 employees across 978 daily workplace observations over three weeks and found small talk works through a specific, two-sided mechanism: it “enhanced employees’ daily positive social emotions at work,” which increased helpful, cooperative behaviour toward colleagues, while simultaneously disrupting people’s ability to concentrate on their actual tasks in the moment. Both things are true at once. Small talk builds the social capital that makes cooperation possible later, and it costs a small amount of focus right now. A 2024 qualitative study of 35 B2B professionals found the same rapport-building mechanism operating specifically in negotiation contexts, identifying genuine curiosity, active listening, and respect for boundaries as the actual ingredients, not just friendly chatter for its own sake.

 

The Counterargument Worth Taking Seriously

Not everyone in this field agrees, and the disagreement is worth taking seriously rather than editing out. Kim Scott, whose Radical Candor framework has shaped how a generation of executives think about direct feedback, has argued the opposite case directly: real trust with employees comes from substantive one-on-ones and working relationships, not casual chat, and treating small talk as the relationship-building mechanism risks substituting a comfortable habit for the harder work of actually knowing someone. That critique lands hardest in ongoing management relationships. The negotiation and cross-cultural research above is mostly about a different situation: the first few minutes with someone you don’t yet have a working relationship with, where there’s no substantive history to draw on yet, and small talk is the only tool available to establish enough trust for the real conversation to start at all.

 

Why This Matters More in Some Rooms Than Others

Research on Arab business negotiators found relationship-building carries even more weight in that context, with negotiators leaning on personal networks and trust-building as central to how deals actually get made, rather than an optional warm-up. The mechanism isn’t unique to any one culture. It’s just more visibly load-bearing in markets where trust is built through recurring personal contact rather than through contracts alone.

 

What This Means in Practice

Skipping small talk to “get to the point faster” isn’t efficient. It’s removing the only low-stakes moment where two people calibrate whether they trust each other, before the stakes get high enough that a miscalibration actually costs something. The application is genuine curiosity about the person in front of you, delivered before you need anything from them, rather than performed friendliness, so that when you do need something, the trust required to ask for it is already there.

Regional Leadership Roles Reward a Different Kind of Patience Than Western Corporate Careers Teach.

Posted on by

Most Western executives arrive in a regional leadership role with the instincts that got them promoted at home: move fast, show visible wins early, let the quarterly numbers do the talking. Those instincts do not transfer. They actively work against you.

Western corporate careers train impatience, and reward it. Promotion cycles run on twelve to eighteen month windows. Performance reviews measure the quarter just closed. The fastest route up is a visible individual win, attached cleanly to your name, delivered before the next review cycle starts. None of that is wrong inside the system that built it. It is a system optimised for institutional and contractual trust, built on the assumption that the relationship survives even if the individual leaves tomorrow.

 

What Regional Leadership Rewards

Gulf leadership runs on a different clock, and the data on how regional leaders actually spend their time backs that up. PwC’s most recent Middle East CEO survey found Saudi Arabian chief executives dedicate 27% of their time to planning five years or more ahead, compared with 16% globally, and GCC chief executives overall spend meaningfully more of their schedule on long-term strategic planning than their global counterparts. That time allocation is a rational response to a business environment where relationships carry the weight of a deal through its inevitable rough patches.

The mechanism underneath that patience has a name: wasta, the use of personal relationships and trust networks to get things done. Research summarised by Northeastern University’s D’Amore-McKim School of Business puts it plainly: “in the Arab context, trust at the interpersonal level needs to be established before any business relationship can unfold.” That is not a bureaucratic delay. It is the actual mechanism through which decisions get made, and skipping it does not speed anything up. It just means the decision never fully lands.

 

The Failure Rate Everyone Quotes Does Not Hold Up

Ask any expat executive circle and you will hear it: 20 to 40% of international assignments fail. It is one of the most repeated statistics in expatriate management, and it is very likely wrong. Anne-Wil Harzing’s 1995 analysis traced the figure back to a small number of frequently misquoted articles, only one of which actually contained solid empirical evidence, and that evidence showed failure rates to be low. The myth persisted for three decades anyway, because it made a better opening line for a consulting pitch than the more boring truth.

The more useful question is why the ones who do fail actually fail. The qualitative research on that is far less contested: misjudging the local pace of trust-building rather than any shortage of competence or effort.

 

What Patience Looks Like in Practice

Cross-cultural consultancy Commisceo Global puts the practical advice plainly: do not expect deals to be completed in two visits to the region, because the relationship has to be nurtured before the commercial conversation can move forward at all. That advice sounds soft to an executive trained to treat a second meeting without a signed term sheet as a stalled deal. It is a description of how decisions actually get authorised in a hierarchy where personal trust in the room outweighs the org chart on paper.

Twenty years running programmes across markets that operate on this clock, the pattern I have seen most often has nothing to do with understanding the concept. Most executives can recite the advice back accurately in an interview. Where they struggle is stopping themselves from behaving as though the Western clock is still running underneath it: checking for the win they would expect by month three, reading the absence of one as a signal that the relationship has stalled, when it has not.

 

Three Things That Actually Help

Building trust deliberately, rather than waiting for it to accumulate on its own, takes specific behaviour. Spend real time in the room before asking for the decision. Learn who actually holds influence in a given relationship, because it is rarely only the most senior title at the table. And resist manufacturing a visible early win for the story it tells back home, because the fastest way to damage the trust being built is to be seen optimising for your own next review cycle instead of the relationship in front of you.

 

What This Requires

The patience regional leadership rewards has nothing passive about it. Ninety-three per cent of CEOs across the GCC expect domestic momentum to keep strengthening, against 55% of their global peers. These are not leaders coasting on a slow market. The patience is aimed at a specific target: building the trust that makes fast execution possible later, instead of chasing a fast, visible win the relationship cannot yet support.

That is a genuinely different skill to the one a Western corporate career trains for, and it rarely shows up on the resume that got someone the role in the first place. The executives who actually succeed in regional leadership rarely arrive already patient. They learn to notice, quickly, that the clock they were trained on is the wrong clock, and recalibrate before the org chart tells them they have run out of time to.

Your Transformation Programme Is Burning Out the People Who Are Supposed to Deliver It

Posted on by

Most digital transformation programmes are designed to transform the organisation. The people carrying that transformation are expected to adapt around it.

That sequencing is the problem.

The burnout, the disengagement, and the resistance that characterise most large transformation programmes trace back further than communication or change management execution. They are downstream consequences of decisions made at the very start of the programme, when the workforce was treated as a delivery resource rather than as the primary constraint to be understood before anything else was designed.

The result is predictable. BCG’s own analysis of digital transformations found that only 30% fully succeed, 44% create some value while missing their targets, and the remaining 26% deliver little or nothing. Bain’s most recent research goes further: 88% of leaders are confident their reorganisation will deliver, but only 36% of the employees actually working inside it agree. McKinsey’s analysis consistently identifies culture and people factors, not technology underperformance, as the primary driver of transformation failure. Its survey research puts a number on one specific piece of that: when senior leaders personally model the behavioural changes they are asking employees to make, the transformation is 5.3 times more likely to succeed.  And yet most programme designs continue to treat the technology as the dependent variable and the workforce as a constant.

The workforce is the one variable that determines everything else.

 

The Capacity Crisis That Everyone Can See and No-One Will Name

66% of American employees reported experiencing burnout in 2025, an all-time high. The rate is worse among the workers most exposed to change: 81% of those aged 18 to 24 and 83% of those aged 25 to 34 report burnout, against 49% of workers aged 55 and older, precisely the cohort most transformation programmes lean on hardest to adopt new systems and new processes.

Only 31% of US employees were actively engaged at work in 2024, the lowest rate recorded in a decade, and 17% were actively disengaged. Gallup’s mid-2025 data puts engagement at 32%, effectively flat rather than recovering.

These numbers describe the actual workforce that transformation programmes are asking to do additional, unfamiliar, and often stressful work on top of existing commitments, not some abstract backdrop to the real business of delivery.

Most large transformations run in parallel with business as usual. The assumption, rarely made explicit but almost always present in the programme design, is that the existing workforce will carry both. The system analyst who is supporting the live operation and attending the new system design workshop and completing their module in the learning platform and updating their change readiness survey: these activities all draw from the same finite capacity. And when that capacity is already under strain, the transformation gets what is left.

 

Where the Design Failure Actually Happens

The standard response to workforce resistance and burnout in transformation programmes is to commission more change management activity. More communication. More engagement events. More of the same interventions applied harder.

The reason this rarely resolves the problem is that it treats the symptom, disengagement, resistance, fatigue, as the cause. It does not address the underlying design decision that produced the symptom.

The design failure is earlier and more structural than change management can reach. It happens when the programme scope is defined before anyone has seriously assessed what the existing workforce is currently carrying, what discretionary capacity genuinely exists, and what the realistic absorption rate for change actually is in this organisation, at this time, in this context.

Prosci’s research on sponsorship effectiveness found that projects with highly effective executive sponsorship are almost 3.5 times more likely to meet or exceed their objectives than projects with weak sponsorship. That finding is routinely misquoted as being about change management activity in general, when it specifically measures the quality of sponsorship: the extent to which senior leaders visibly own the change, actively communicate its rationale, and stay engaged with it once the initial announcement has faded. Sponsorship of that kind is a design discipline applied from the beginning, shaping the scope, the pace, the sequencing, and the ask on the workforce before the business case is finalised, not a communications workstream bolted on afterwards.

 

The Three Decisions That Set the Conditions

There are three decisions made at the start of most transformation programmes that determine whether the workforce becomes an enabler or a constraint. All three are made before the first delivery milestone is reached. And in most programmes, all three are made in a way that prioritises ambition over capacity.

The first is scope. The scale of a transformation programme is typically determined by what the organisation wants to achieve and what the technology enables. The workforce’s current capacity, existing obligations, and realistic absorption rate are rarely weighted with the same rigour. A scope that is technically achievable but humanly unsustainable will fail through attrition, quality erosion, and the slow withdrawal of discretionary effort.

The second is sequencing. The order in which change is introduced to the workforce matters more than most programme designs acknowledge. Asking the same population to absorb multiple concurrent workstreams, new system, new process, new skills, new reporting lines, compounds the cognitive and emotional load in ways that tend to surface as resistance but originate as exhaustion.

The third is investment in workforce capacity before deployment. The organisations that sustain transformation over time do not wait for resistance to emerge and then address it. They assess the workforce’s capacity constraint honestly at the outset and make deliberate investments, in backfill, in reduced BAU commitments during peak change periods, in genuine relief on existing obligations, before the transformation work begins.

 

The Longer View

The organisations that sustain transformation over time are rarely the fastest movers in the first twelve months. They are the ones still moving in month thirty-six, because the workforce has not burned out, has not disengaged en masse, and has not lost the institutional confidence that the programme will actually deliver.

Disengaged employees cost the global economy an estimated $8.8 trillion annually, roughly 9% of global GDP. Most of that is preventable. Not by communicating more, but by designing better, starting with an honest understanding of what the workforce can actually carry, and building the programme around that constraint instead of ignoring it.

The people are not the risk to be managed. They are the foundation on which every transformation outcome rests.

Design around them first.