Category Archives: Leadership

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.

Your Gates Aren’t Protecting the Business. They’re Protecting Themselves.

Posted on by

Nobody sets out to build a bureaucracy. Every heavy stage-gate process started as three good intentions: get bad projects killed early, get good projects through fast, and keep a clean record of why each call was made. Then it grew a review board nobody remembers approving, and the good projects started waiting as long as the bad ones.

That is the actual failure. Not that gates exist. That almost nobody still measures them against the job they were built to do.

 

The Test a Stage Gate Was Actually Built to Pass

Governance run properly delivers three things, and nothing else matters as much as these: faster decisions, so a good project stops waiting weeks for a yes. Earlier kills, so a weak one frees up capital instead of quietly draining it for another two quarters. And a clean audit trail, so nobody has to reconstruct the reasoning after the fact. Get those three right and a stage gate speeds decisions. Miss them and it slows every decision down, good and bad alike, because the mechanism has stopped doing the job it was built for.

Someone genuinely has to decide which projects live, which pivot, and which ones are quietly draining the business. That much was never in question.

 

Why the Mechanism Rots

Four patterns do most of the damage, and each one accumulates quietly rather than arriving as a single bad decision. Entry gates get heavy while exit and kill discipline stay weak or disappear entirely, so zombie projects clog the funnel and starve the strong ones of attention. Panels grow larger and meetings grow longer until authority is spread across so many people that nothing actually gets decided. Reviews turn into theatre, rubber-stamping or deferring rather than choosing, and momentum dies in the gap between gates. And decision rights stay ambiguous enough that nobody is the clear owner of the yes or the no, so everything escalates and stalls at once.

Each of those four is a governance design that stopped serving the teams running through it and started serving itself, not a process flaw you fix by adding another step. The entry gate feels productive, so it keeps growing. The exit gate feels harsh, so nobody wants to own it, and that imbalance is where most of the trouble actually starts.

 

The Numbers Behind the Frustration

The frustration shows up in real operating numbers, not just complaints. At Vivix Vidros Planos, a Brazilian flat-glass manufacturer, resolving a customer complaint used to take weeks, long enough for a buyer to lose patience and take the next contract elsewhere. After building an AI-powered chatbot into its existing production and quality data, that shrank to minutes, an 80% reduction in complaint resolution time. Responses to production-line issues sped up by a further 85%. Both figures come from Vivix’s own case study, published jointly by Siemens and AWS. The underlying pattern holds regardless of the exact numbers: the real cost of a slow gate shows up as lost trust and lost contracts, not just lost hours.

 

What Minimum Viable Governance Actually Looks Like

The fix is sizing each gate to the actual risk in front of it, rather than running every decision through the same heavy process regardless of what it actually requires. A low-risk process tweak does not need the same panel as a bet-the-quarter platform launch, and treating both the same is exactly how standing committees fill up with work they should never see in the first place. High-risk decisions keep full board review, because that rigor is proportionate there. Mid-tier decisions get a lightweight gate with a single accountable owner. Low-risk work proceeds by default through a simple intake form, with oversight applied only if something in it actually warrants it.

The useful design target sits between two failure modes: above a ceiling, controls become bottlenecks and teams quietly route around them; below a floor, real risk creeps in unmanaged. Getting that band right is not abstract. One organisation that tightened its policy down to the minimum viable version halved the time complex decisions took and surfaced three times more opportunities than peers still running the heavier version.

 

The Test Most Gates Would Fail

Pick the last three projects your organisation killed at a gate, and the last three it approved. If the kills took longer to reach than the approvals, the gate is not protecting the business from bad decisions. It is protecting itself from having to make any decision at all.

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.

Your Twenties Reward Hustle. Your Forties Reward Judgement. Few People Notice the Shift in Time.

Posted on by

Nobody tells you when the game changes. You keep playing the twenties game in your forties and quietly wonder why the same effort stopped yielding the same results.

The shift is real, not a mood. It has a name in the research and a shape most people never get to see clearly enough to plan around.

 

What Actually Peaks in Your Twenties

Stanford’s Center on Longevity has the cleanest explanation of why hustle works so well early. Fluid intelligence, the raw ability to solve new problems quickly without relying on prior knowledge, peaks as people enter their third decade. That is a genuine cognitive advantage, not a myth about youthful energy. Speed, pattern-spotting on unfamiliar problems, and the appetite to grind through volume are all things a twenty-something brain does better than it ever will again.

That is exactly why hustle gets rewarded so visibly early on. It is the highest-value thing on offer at that stage, and organisations are right to reward it.

 

What Actually Peaks Later, and Why Nobody Notices

The mistake is assuming that advantage holds. It does not, and something else takes its place instead of just fading. Crystallized intelligence, the accumulated knowledge and judgement built from lived experience, keeps rising well into the seventh decade. Emotional intelligence peaks in the forties. Moral reasoning keeps improving through adulthood. Stanford’s own framing of it is the clearest version I have read: the twenty-five-year-old brings speed and fresh perspective, the fifty-year-old brings integration and judgement, the seventy-five-year-old brings wisdom and pattern recognition across decades none of the others have lived through.

Almost nobody plans their career around that curve, because almost nobody is shown it. The result is a lot of very capable forty-somethings still competing on twenties metrics, wondering why the hours are not converting into the same visible wins they used to.

 

Early Excellence Does Not Predict What You Think It Does

A December 2025 review published in Science, covering nearly 35,000 world-class performers across sport, music, chess and the sciences, found that early standouts and eventual world-class performers are largely different people. Peaking early does not reliably predict who ends up at the top later. The performers who lasted tended to explore broadly before specialising, building a wider base of judgement to draw on rather than narrowing down early and grinding one lane harder than everyone else.

The same pattern shows up at executive level. Generalist chief executives, the ones with genuine cross-functional experience rather than a single specialist lane, file more than double the patents annually compared with specialist peers, with 55% higher originality ratings. Jeff Bezos building AWS and Satya Nadella’s Microsoft turnaround both drew on lateral experience outside their original speciality, not deeper hustle inside it.

 

What Judgement Actually Looks Like at Work

Judgement rarely looks impressive in the moment, which is part of why it goes unrewarded for so long. It looks like not escalating something that will resolve itself on its own, and letting a good-enough answer stand instead of spending three more hours perfecting a version nobody asked for. It looks like knowing which fight is worth having this quarter and which one can wait, a decision hustle never had to make because hustle just took every fight.

The forty-something who is still measuring their own value in hours and visible output is applying a twenties scorecard to a role that has already moved past it. The actual multiplier at that stage is rarely personal execution. It is knowing which three things matter this month and being willing to let the other twelve go undone.

 

The Shift Worth Naming Out Loud

Nobody sends a memo when hustle stops being the highest-value thing you offer and judgement takes over. It happens quietly, somewhere in the decade nobody warns you about, and the people who notice early enough to adjust are the ones whose forties look like a promotion instead of a plateau.

The question worth asking yourself this year is not whether you are working hard enough. It is whether you are still being rewarded for the twenties game, or you have quietly moved into a different one without updating your scorecard.

Why Traditional Project Management Is Failing Modern Teams

Posted on by

Why Traditional Project Management Is Failing Modern Teams

Most project failures get blamed on execution. A missed deadline. A stakeholder who went quiet at the wrong moment. A scope that crept until nobody could point to when it happened.

Look earlier and the failure was already built in before a single sprint started.

A Forbes Technology Council analysis makes the point directly: misalignment gets embedded into the foundation long before execution begins, not manufactured somewhere in the middle. The team that won the deal rarely stays involved in delivery. The customer’s actual operating mindset only reveals itself once work is already moving. The incentives written into the contract often point delivery and client in different directions before day one. Teams execute a plan that was already structurally unsound before the first sprint started.

Traditional project management was never built to catch that kind of problem. Waterfall assumes you can define requirements fully upfront, lock them, and deliver against a fixed spec months later. That assumption survives about as long as the first change request. Priorities that shift inside a six-week planning cycle, which describes most programmes now, make a locked spec obsolete before it has even shipped.

 

Rigidity Is the Symptom. Something Else Is the Disease.

Here’s the twist most framework debates miss. Methodology by itself isn’t what separates the teams that deliver from the ones that don’t. PMI’s most recent Pulse of the Profession research found project performance sits at roughly 73.8% whether a team runs predictive, hybrid, or agile delivery, and whether people work remote, hybrid, or in-person. What actually moved the needle was business acumen: professionals strong in it posted 27% lower failure rates, regardless of which framework sat on the wall.

Framework still matters. It was just never the whole story, and treating “which methodology” as the central question misses where most programmes actually break.

A PM Solutions case study makes the same point at a larger scale. A U.S. staffing company with more than 8,000 internal and 90,000 contract employees had already tried and failed to stand up a PMO once. On the second attempt, the team built a hybrid methodology suited to the client’s actual environment, blending traditional project management, agile, and the touchpoints where each meets software delivery, then added a governance structure, portfolio visibility and resource planning on top of it. Within six months, every project flagged red under the new reporting system, more than $13 million worth of work, was recovered. One severely troubled multi-year project, over budget and behind schedule, was turned around in four weeks once it had a dedicated programme manager working inside that structure. Not a framework doctrine. Governance and visibility.

 

The Real Adoption Curve

That pattern shows up in the adoption numbers too. Hybrid delivery has grown 57% since 2020, while purely predictive approaches have fallen 24% over the past three years. The pattern behind that shift is simple: pure Waterfall and pure Agile were both answering questions the actual work wasn’t asking, and organisations are admitting it with their adoption numbers rather than in a strategy memo.

Rigid, one-size-fits-all implementation is what actually ages badly, more than the framework choice underneath it. Portfolios that mix delivery models by what the work actually demands, a predictable cadence for mature products, flow-based delivery for continuous work, fast validation cycles for early bets, consistently outperform portfolios that force every initiative through the same certified process regardless of fit.

 

What This Means for the Programme You’re Running Now

The practical shift isn’t abandoning structure for chaos. It’s building governance that travels with whichever delivery model fits the work, instead of assuming the delivery model is the governance.

Start by naming decision rights before the kickoff, not after the first dispute breaks something. Someone owns scope changes. Someone owns the call when a dependency slips. Everyone on the programme should be able to name both without asking. Build the escalation path into the plan itself rather than inventing one under pressure in week eight, and match the delivery model to the type of work in front of you rather than to what worked on the last programme. A regulated, multi-vendor transformation and a ten-person product team shipping a new feature are not the same problem, and forcing them through the same framework produces the same failure pattern twice.

Track what the framework was supposed to deliver, not whether the ceremonies happened. A team that ran every stand-up and still shipped nothing useful followed the process and failed anyway.

 

The Question Every Kickoff Should Answer First

Before the next programme gets a charter and a framework stamped on the cover page, ask a harder question first: who owns the decision when priorities collide, and does that answer exist in writing before the first sprint starts?

If it doesn’t, the framework on the cover page was never going to save the programme underneath it.

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.

The Governance Training Nobody Budgets For

Posted on by

Nobody has ever failed a project because they didn’t know how to build a Gantt chart. However some failed because nobody taught them who was allowed to say no.

I have sat in quite a number of programme inductions, and every one of them covers the same ground. Scheduling. Budgeting. Risk logs. RAID templates. Reporting cadence. Then, somewhere around the second afternoon, someone puts up a slide about governance and the room’s attention visibly leaves the building. It is treated as the compliance module, the thing you sit through before you get to the real work. Nobody walks out able to say, with any confidence, who actually owns the call when a decision does not fit neatly on a template.

That gap is not an oversight. It is a choice organisations keep making, year after year, without ever naming it as one.

 

The curriculum has a hole in it

Ask a newly promoted programme manager to explain their RAID log and they will do it fluently. Ask them who has the authority to accept a risk above a certain threshold without escalating it, and watch the pause. That pause is the sound of someone realising they were never actually taught the answer, only ever expected to absorb it by watching more senior people long enough.

A 2026 AI Governance Gap Report surveying more than 500 HR professionals found that only 45 per cent of organisations provide AI literacy training to all employees, one concrete, measurable instance of the broader governance-literacy gap this piece is about. Two-thirds of HR teams are already using AI to shape compliance and policy decisions, and the same report found fewer than half have given employees even that AI-specific literacy training to keep pace. The gap shows up well beyond HR too, in every function that has ever built a decision-rights framework, filed it in a folder, and assumed the document itself did the teaching.

Documents do not teach. People do, and usually only the ones who were already senior enough to have picked it up somewhere else.

 

Decision rights are treated like folklore

Most organisations do not lack a governance framework. They have one, usually a good one, sitting in a policy library that almost nobody outside the PMO has opened. What they lack is a mechanism for turning that document into instinct.

The result is a workforce that learns decision rights the hard way: by guessing wrong in front of a steering committee, by escalating something trivial and being quietly told off for wasting everyone’s time, or by not escalating something serious and finding out only when it has become a crisis. Every one of those is an expensive way to teach a lesson that could have been taught in an afternoon.

This is where the “knowing-doing” research cited by Harvard Business Review becomes uncomfortable reading for anyone who runs a training budget. Two out of three managers say they are still uncomfortable having accountability conversations with their own people, despite most of them having sat through the leadership training designed to prepare them for exactly that. The problem was never a shortage of content. Knowing a framework exists and being able to act on it under pressure are two entirely different skills, and organisations keep training the first while assuming it produces the second.

Governance training suffers from the same fault line. Knowing there is an escalation policy is not the same as recognising, in the middle of a stressful Tuesday, that the decision in front of you is the one the policy was written for.

 

The training everyone skips because it looks obvious

There is a reason this particular gap survives budget reviews when almost nothing else does. Governance training looks like it should be simple, so nobody prioritises building it properly. Everyone assumes the framework document is self-explanatory, right up until the moment someone makes the wrong call and the post-incident review discovers that three different people had three different understandings of who was supposed to decide.

I have run those reviews. The finding is almost never “the framework was wrong.” Almost always, nobody had ever been walked through what the framework meant in a live situation, so everyone applied their own version of common sense, and common sense is not actually common.

 

What actually needs teaching

A longer policy document will not fix this. Longer documents get read less, not more. The fix is teaching people to recognise a decision point before it arrives, not after.

That means running people through real scenarios instead of abstract categories, trading “what is your escalation threshold” for “here is a supplier problem that looks small and is not, what do you do in the next ten minutes.” It means naming, out loud and often, the handful of decisions in your organisation that carry disproportionate weight, so people learn to feel the shape of one before it is labelled for them. And it means treating governance literacy the way you would treat safety training: refreshed, tested, and taken seriously enough that senior leaders visibly participate in it themselves, rather than left as a one-off induction module.

The organisations that get this right build fewer, better decision-makers rather than thicker governance frameworks: people at every level who can spot a genuine decision point on instinct, the same way an experienced engineer can hear an engine fault before the dashboard lights up.

You cannot budget for the crisis a decision creates and then refuse to budget for teaching people to see it coming.

 

 

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.

Two-Thirds See AI Working. The CFO Still Can’t Prove It.

Posted on by

Two-thirds of organisations say AI is delivering real productivity gains. Ask the CFO whether that translates into a return they can defend, and the answer changes completely.

 

Two Surveys, Same Landscape, Different Question

Deloitte’s 2026 State of AI in the Enterprise report, surveying 3,235 senior leaders across 24 countries, found 66% of organisations reporting real productivity and efficiency gains from AI, and 53% reporting genuinely better insights and decision-making. That is not a marginal result. Two-thirds of a very large sample are seeing the operational benefit show up in how the work actually gets done.

EY’s 2026 Global DNA of the CFO Survey, covering 1,610 CFOs, finance directors, and heads of finance at organisations with over a billion dollars in revenue, was fielded in the same window and asked a different question: not whether AI is helping, but whether finance can prove it in the language capital allocation actually requires. The answer is uncomfortable. Just 12% of CFOs say their finance transformation outcomes exceeded expectations over the past two years. Only 21% describe their function’s AI readiness as leading or advanced. And 71% say plainly that traditional metrics are not enough to evaluate initiatives that combine people and technology.

 

This Is Not Two Surveys Disagreeing

Read carelessly, that looks like a contradiction: one report says AI is working, the other says it isn’t. It isn’t a contradiction. It is two different functions answering two different questions, and the gap between the answers is the actual story.

The operational teams reporting gains in the Deloitte data are measuring what they can see directly: faster cycle times, fewer manual steps, sharper analysis. None of that is fabricated, and none of it is trivial. But productivity gain and return on invested capital are not the same measurement, and the EY data shows finance has not built the bridge between them. Sixty-one per cent of CFOs cite data quality and bias as their top challenge in securing further AI investment, which is a polite way of saying the numbers underneath the business case are not yet reliable enough to defend in a capital allocation meeting.

A separate July 2026 survey of 1,505 senior finance leaders across the US, UK, Australia, and India found the same pattern from a slightly different angle: 92% feel active pressure to prove AI investment is paying off, while only half report their AI agents have actually achieved a measurable return. The pressure to prove value is running well ahead of the organisation’s actual ability to measure it.

 

The Real Governance Gap

None of this is a technology problem. The Deloitte numbers show the technology is doing what it was bought to do, in a majority of cases, across a very large sample. It is not really a capital problem either. Boards are still funding AI investment at pace, and EY’s own data shows CFOs largely expect that to continue.

It is a measurement problem, and measurement problems are governance problems wearing a data costume. Somebody has to own translating “the team says this is working” into “here is the return, measured the way capital allocation actually requires it to be measured,” before the investment decision, not after it, using metrics that were agreed while everyone could still agree on them.

Most organisations have not assigned that ownership to anyone specific. It sits, by default, somewhere between IT, who built the thing, and finance, who has to defend the number nobody built the measurement framework to produce.

 

What Actually Closes the Gap

Fixing this does not start with better AI. It starts with defining, before the next AI investment gets approved, exactly what “return” means for that specific initiative, in terms finance and the operational team both sign off on before deployment, not after. It means putting one named owner against that measurement framework, not a committee, and not IT by default because they happened to build the system. And it means accepting that a lot of the value AI is already producing is real but currently invisible in the metric finance is required to report against, which is a reason to fix the metric, not to distrust the value.

 

The Question Worth Asking Before the Next AI Business Case

The next time someone asks whether an AI investment delivered a return, the sharper question is whether anyone defined, in advance, what return was actually supposed to look like, and in whose language it would need to be proven. Most organisations running significant AI programmes right now cannot answer that question. That is the real gap the numbers are describing, and it is entirely fixable, starting with the next business case, not the last one.