Every executive has lived some version of this.
You approve a major programme. There’s a business case, a vendor roadmap, a neat slide with three phases and a cheerful timeline. The new CRM goes live. The cloud landing zone is ready. The AI assistant is switched on.
Then… nothing much happens.
People keep their old spreadsheets. Sales teams “forget” to log activity. Ops teams create workarounds that look harmless, then quietly become the real process. The tech works, yet the change doesn’t. The real challenge lies in the culture transformation that is necessary for success.
That moment is awkward. It can feel personal. It can feel unfair. You bought the kit. You funded the training. You even showed up to the town hall and did the speech.
Here’s the thing: most transformations don’t fail in the data centre. They fail in day-to-day behaviour. Culture decides what people do when nobody is watching, when the pressure is on, when the new way feels slower, and when a workaround looks like the fastest route to Friday. Understanding this culture transformation is essential.
And yes-this is the part some leaders try to skip.
The uncomfortable stat that keeps coming back
McKinsey has long cited that around 70% of transformations fail.
BCG’s research on digital transformation found that only about 30% succeed in meeting objectives, with the rest falling short to varying degrees.
Gartner has said it plainly: in a survey, CIOs reported culture as the main barrier, and noted clear failure in 50% of cases.
These aren’t tiny sample sizes from a niche blog. This is mainstream research, repeated enough to be boring. And when a truth becomes boring, it often becomes useful.
So what’s going on?
A lot of leaders treat transformation as a technology delivery problem. It’s rarely that. It’s a social adoption problem, with a tech component that requires a focus on culture transformation.
What “culture” actually means when you’re paying for it
“Culture” can sound like posters, values, and cheerful videos. That’s the fluffy version. The expensive version looks like this:
- What gets rewarded (and what quietly gets punished)
- How decisions really get made (not how the org chart claims they get made)
- Who can say “no” and slow things down
- How people react to risk and scrutiny
- How teams share credit and spread blame
- Whether bad news travels fast or gets filtered into nonsense
You can run SAP, Salesforce, ServiceNow, Azure, AWS, Workday, Jira-pick your stack. If the culture says, “Don’t surface problems,” you get glossy status reports and late surprises. If the culture says, “Protect your patch,” you get siloed data and “not my job” handovers. If the culture says, “Speed matters more than quality,” you get brittle builds and a growing queue of defects.
That’s not a tech issue. That’s a people system doing what it was built to do.
Why tech-first feels so tempting (and why it keeps backfiring)
Tech is tangible. Culture is awkward.
You can purchase licences. You can count servers decommissioned. You can point to a new Teams channel and call it “collaboration”. You can show a dashboard, and dashboards are soothing.
Culture asks for a different kind of leadership. It asks you to confront incentives, power, skill gaps, and habits that may have made the organisation successful in the past. That can feel like pulling at a thread in a favourite jumper.
So leaders reach for the measurable stuff first.
Yet that’s where the trap sits: technology is the easy part to fund and the hard part to absorb.
The work environment has become… noisy
One reason adoption is so fragile is simple: people are overloaded.
Microsoft’s 2025 Work Trend Index describes a capacity gap, with 80% of the global workforce saying they lack enough time or energy to do their work.
It reports that during the working day, employees are interrupted every two minutes by meetings, emails, or messages-and when you include activity outside core hours, it adds up to 275 interruptions a day.
It even notes meetings after 8 p.m. rising 16% year-on-year, tied to cross–time zone work.
So when leaders say, “Why won’t people adopt the new process?” a fair reply is: Adopt it when?
This is where culture bites again. In a high-trust culture, leaders remove friction, simplify priorities, and protect focus. In a low-trust culture, leaders add another tool, another meeting, another status ritual-then act surprised when people resist.
Culture shows up in the small moments, not the big speeches
Want to see whether culture will support transformation? Don’t start with a survey. Start with observation.
- When a pilot hits a snag, do leaders ask, “Who messed up?” or “What did we learn?”
- When a team raises a risk, do they get support or get labelled “negative”?
- When someone ships a workaround, do we praise speed or question safety?
- When a middle manager is confused, do they ask openly or suffer in silence?
- When metrics look good, do we test reality or celebrate the graph?
If you’re hearing “green across the board” while frontline teams sound exhausted, the culture has learned to tell you what you want to hear. That’s a survival skill in some organisations.
Psychological safety isn’t a soft perk. It’s a delivery engine.
Google’s re:Work summary of Project Aristotle put psychological safety at the top of the list for effective teams-above who is on the team, where they sit, or how senior they are.
This matters for transformation for a simple reason: change creates mistakes. If people fear embarrassment or punishment, they hide mistakes. Hidden mistakes become expensive mistakes.
A culture that lets people say, “I don’t understand,” or “This is breaking,” moves faster over time. It feels slower for a week, then it pulls away.
That’s the “mild contradiction” leaders struggle with: candour can feel messy, yet it’s the cleanest path.
The real blockers tend to be boring (and painfully common)
When programmes stall, the root cause often lives in one of these places:
1) Incentives that quietly punish the new way
- If bonuses reward output volume, people won’t slow down for quality controls.
- If promotions reward individual heroics, teams won’t invest in shared platforms.
- If leaders praise “delivery” while ignoring adoption, teams ship features nobody uses.
2) Decision rights that are fuzzy
Transformation needs crisp calls: data definitions, tool standards, risk acceptance, ownership. If every choice triggers a committee, people stop choosing. Work becomes waiting.
3) Middle management left out of the story
Senior leaders announce change. Frontline teams feel the impact. Middle managers translate it into daily work. When they don’t buy it, or don’t understand it, momentum dies quietly.
Gartner’s view that culture is a barrier isn’t abstract. Culture often sits right there: in how managers interpret uncertainty.
4) Skill gaps treated as attitude problems
A team that avoids a new tool may look stubborn. Often they’re anxious. They fear looking incompetent. They fear falling behind. Training that is practical, role-based beats grand “academy” launches that nobody has time for.
So what should leaders do? A playbook that doesn’t rely on theatre
1) Make the “why” a daily message, not a one-off slogan
McKinsey notes that a compelling “why” matters for getting thousands of people to choose a new way of working.
Not a poster. A repeatable story that answers: What pain are we removing? What risk are we lowering? What will feel different for customers and staff?
If you can’t say it in two sentences, people can’t repeat it at the coffee machine. And if they can’t repeat it, it won’t spread.
2) Reduce change noise before adding change
Look at the portfolio. What can you stop? What can you pause? What meetings can you kill?
The Work Trend Index data about interruptions and chaotic work is a warning sign: if you add transformation into a jammed calendar, you’ll get performative compliance.
3) Treat adoption like a product metric, not a project checkbox
Measure real usage and real outcomes:
- How many teams use the new process without shadow spreadsheets?
- How long does the new workflow take in practice?
- What errors fell, what cycle times fell, what customer complaints fell?
If you’re running Microsoft 365, you can observe patterns of collaboration. If you’re on ServiceNow, you can see ticket flow. If you’re on Salesforce, you can see pipeline hygiene. Use the data as a mirror, not a stick.
4) Build a culture that can handle bad news quickly
Reward early risk calls. Celebrate teams that surface issues at 20% completion, not 95%. Run short, honest retros. Keep them blame-light and learning-heavy.
This is where psychological safety pays rent.
5) Put your best people on the messy parts, not the shiny parts
Many organisations staff their best talent on the build. Then they hand adoption to a thin change team with limited influence.
Flip that.
The toughest work is behaviour change: new roles, new handoffs, new definitions, new controls. Put serious operators there.
6) Make culture practical: update the rules people live by
- Culture shifts when you change the “rules of the road”:
- Decision thresholds (who decides what, by when)
- Standards that are enforced (data quality, security, testing)
- Career signals (what gets you promoted)
- Consequences that are consistent (not random)
If those don’t change, culture doesn’t change. People learn fast.
7) Model the behaviour in public
- If leaders refuse to use the new tooling, nobody else will.
- If leaders demand certainty before making calls, teams will freeze.
- If leaders punish messengers, truth will go underground.
The unglamorous truth: culture is what leaders tolerate.
A final thought for your planning season
If you’re setting budgets and roadmaps right now, try a small test.
For every £1 you plan to spend on technology, ask: What are we spending to change habits?
Not comms fluff. Real habit change: training, coaching, role redesign, time protection, manager enablement, decision clarity.
BCG’s work on success factors highlights that organisations can materially shift odds when they get the broader set of factors right, not just the tech.
Gartner’s message is blunt: culture is a main barrier.
The data keeps tapping you on the shoulder.
Technology matters. Of course it does.
Yet culture decides whether that technology becomes value, or becomes another shiny object with a login nobody remembers.
