A University of Zurich study published earlier this year made a claim that should be uncomfortable reading for any enterprise CTO or CDO: monasteries, some of them operating continuously for five centuries, are better at digital transformation than most modern businesses.
Not marginally better. Consistently, measurably better, across adoption rates, change durability, and staff buy-in.
The instinctive response is to dismiss it as a quirky academic finding. The more useful response is to ask why, and what it means for how you run your next transformation programme.
What the Research Actually Found
The Zurich study examined how organisations with long institutional histories respond to digital change. Monastic communities scored highly on three dimensions that most enterprises score poorly on: clarity of purpose, consistency of daily practice, and tolerance for long time horizons.
These are not technology capabilities. They are organisational and cultural ones.
Monasteries do not adopt a new tool because a vendor promised a 30% productivity uplift. They adopt it when they can articulate how it serves their core purpose and when leadership can model the new behaviour themselves. That sounds obvious. Most enterprise transformation programmes do the opposite: they mandate tools, skip the purpose conversation, and then wonder why adoption flatlines six months after go-live.
The B2B Problem: Still Running on Notebooks
This finding lands even harder in the context of B2B organisations, where digital transformation rhetoric has significantly outpaced reality. Analysts and practitioners have noted repeatedly that many B2B businesses, despite years of investment, still run critical processes on spreadsheets, email threads, and informal knowledge held by individuals who have been in post for fifteen years.
The problem is rarely a lack of technology. It is a lack of process discipline and a change model that treats technology deployment as the finish line rather than the starting gun.
Consider a hypothetical mid-sized professional services firm. It invests in a new CRM platform, migrates client data, and trains the team. Twelve months later, senior partners are still logging calls in their personal notebooks and the CRM contains incomplete data. The platform was right. The transformation model was wrong. Nobody redesigned the workflow, redefined accountability, or connected the new tool to something the partners actually cared about.
The Four Reasons Transformation Programmes Stall
After working across dozens of transformation programmes, the failure patterns are predictable.
1. Strategy Without Operating Model
A digital strategy that does not also redesign how the organisation delivers work is a vision document, not a transformation. Technology is only as effective as the operating model it sits inside. If your processes, governance, and team structures are unchanged, new software will be absorbed and neutralised by the existing system.
Monastic organisations, by contrast, treat a new practice as an operating model change first. The technology, whether a new bell schedule or a digital liturgy management system, follows the redesigned routine, not the other way around.
2. Change Management Bolted On at the End
In most transformation programmes, change management is treated as communications and training, deployed in the final weeks before go-live. This is structurally too late. By the time a system is built and ready to launch, the team designing it has made hundreds of decisions that will shape how people actually work. If the people affected were not involved in those decisions, resistance is not irrational, it is rational.
Effective change management starts at programme inception. It means involving frontline staff in process design, not just notifying them of the outcome.
3. Measuring Activity Instead of Outcomes
Transformation programmes tend to report on delivery milestones: systems deployed, training sessions completed, tickets closed. These are activity metrics. They tell you whether you did the work, not whether the work made a difference.
A more useful measurement model tracks the business outcomes the transformation was meant to deliver. If the goal was faster customer onboarding, measure onboarding time before and after. If the goal was reduced manual processing, measure headcount-to-volume ratios. Build these baseline measurements before the programme starts, not after.
Example outcome measurement framework:
Objective: Reduce time-to-onboard new enterprise clients
Baseline (pre-transformation):
- Average onboarding time: 34 days
- Manual touchpoints per onboarding: 18
- Client satisfaction at onboarding (CSAT): 6.2/10
Target (12 months post go-live):
- Average onboarding time: 14 days
- Manual touchpoints per onboarding: 5
- CSAT: 8.0/10
Measurement cadence: Monthly review, quarterly business case revalidation
4. Treating Culture as a Blocker Rather Than a Design Input
The phrase "culture eats strategy for breakfast" has been repeated so often it has lost meaning. But the underlying point is correct: you cannot mandate cultural change. You design conditions in which the desired behaviours are easier than the undesired ones.
This means looking at incentive structures, not just values statements. If your senior leaders are rewarded for short-term revenue and penalised for investing time in new ways of working, no transformation programme will change their behaviour. The monastery analogy is apt here too: monastic culture is shaped by daily rituals, shared accountability, and visible leadership behaviour, not posters on a wall.
What a Working Transformation Model Looks Like
A transformation programme that consistently delivers works across four layers simultaneously.
Strategy layer: A clear, time-bound articulation of what the organisation will do differently and why. Not "become digital-first" but "reduce cost-to-serve for mid-market clients by 25% over 18 months by automating the quote-to-cash process."
Operating model layer: A redesigned view of how work gets done: which teams own which decisions, how products are built and iterated, how technology and data are governed. This is the hardest layer and the one most programmes skip.
Technology and data layer: The platforms, integrations, and data architecture that enable the new operating model. This is where most investment goes. It should follow the operating model design, not precede it.
People and culture layer: The capability building, role redesign, performance management changes, and leadership behaviours that make the new model stick. This runs in parallel with everything else, not after it.
All four layers must move together. Advancing technology while leaving operating model and culture unchanged is the single most common reason transformation programmes deliver new systems and old results.
The Time Horizon Problem
The Zurich research highlights something that is structurally difficult for publicly listed companies and private-equity-backed businesses: monasteries plan on fifty-year horizons. Most enterprises plan on eighteen-month ones.
This creates a structural bias against the kind of deep, patient change that transformation requires. A programme that delivers real change to an operating model typically takes three to five years to fully embed. Boards and investors rarely give that runway without seeing interim results.
The solution is not to pretend the time horizon does not matter. It is to design transformation programmes in stages that deliver real business value in each phase, building the case for continued investment. Phase one should not be infrastructure work that nobody outside IT notices. It should visibly reduce friction for a customer or improve a metric leadership cares about.
The Honest Trade-offs
None of this is straightforward. Redesigning an operating model while running a live business is genuinely difficult. It requires sequencing decisions carefully, managing risk, and accepting that some things will break before they improve.
Change management done properly is expensive and time-consuming. Measurement frameworks require upfront investment in data and baselines that are hard to justify before the programme has started.
These are real costs. But they are significantly smaller than the cost of a transformation programme that deploys technology nobody uses.
How modernise.io Can Help
modernise.io works with enterprise and scale-up organisations on exactly the four-layer model described in this article: strategy definition, operating model redesign, technology and data architecture, and people and culture change. We do not separate these into distinct workstreams owned by different vendors. We treat them as a single, integrated programme because that is how transformation actually works.
Where many consultancies hand over a strategy document and disengage, we stay through delivery, helping teams build the governance, measurement frameworks, and operating routines that make change durable. We have worked with financial services, professional services, and technology-led businesses on transformation programmes ranging from single-function redesigns to enterprise-wide operating model change.
If your organisation has invested in digital transformation and is not seeing the business outcomes it expected, the problem is almost certainly not your technology choices.
Get in touch →