Three Problems, One Discipline: The Case for Enterprise Transformation Assurance
by Gabriel Rea & Henry Darch
There is something specific to say about why healthcare's digital investments keep falling short of their promises, and it is not a mystery in need of new research. Digital is usually the route, but transformation is the point, and most organisations are struggling to reach the destination because the thinking is often not sequenced that way. And the cost of that missequencing is not marginal. For a major hospital programme, an investment of less than one per cent of the total budget in getting the discipline right can protect tens of millions of pounds of capital and operational expenditure across the lifecycle of the facility.
The failure modes are known because the evidence is consistent, and they can be reduced to three problems that repeat across health systems with almost tedious reliability. Name them honestly, and the discipline required to solve them names itself, Enterprise Transformation Assurance.
Surveys of healthcare organisations show the scale of the issue. Of those that have implemented major EHR systems, around 40 per cent report significant issues, and only 38 per cent judge their efforts successful. The causes cited are insufficient change management, insufficient training, insufficient staffing and inaccurate expectations set at the point of sale, organisational failures, every one. Healthcare organisations do not need more disconnected digital activity. They need a clear way to define, procure, govern and realise transformation. The three problems below are what stands in the way.
Problem One: Organisations Buy Technology Before They Have Defined the Transformation
Too often, digital programmes begin with products, vendors or isolated work packages. An EMR is procured. A digital strategy is written. An enterprise architecture piece is commissioned. A smart building partner is appointed. An implementation provider fills the gaps. Each may be useful, but none necessarily holds the whole transformation intent, and because the technology decision came first, the clinical, operational, workforce and financial outcomes it must enable were never defined in terms objective enough to test anything against. The result is product-defined transformation rather than transformation-defined technology: requirements reverse-engineered from the system, workflows mapped to the software rather than the software to the care.
The consequences are not abstract. Implementing an EMR is far more than a technology upgrade; it is a transformational journey that touches every aspect of how care is delivered, managed and supported. The system provides the foundation, but it is leadership alignment, clinical workflow redesign, workforce engagement and organisational readiness that determine whether the programme succeeds. Buy the foundation before defining the building, and the scaffolding gets improvised afterwards, which is precisely what the survey data shows happening.
Problem Two: Strategy, Procurement and Delivery Become Disconnected
Even where the ambition is well defined, it rarely survives the handovers. A digital strategy is written by one group, procurement shaped by another, implementation led by a third, and benefits owned by someone else again, if by anyone at all. The result is drift. The golden thread from business case to delivery is lost, and each successive party optimises for its own contract rather than the original intent.
The pattern that follows is so common it can be plotted as a lifecycle. At programme launch, work is split across multiple contracts and suppliers. Mid-delivery, integration issues emerge; schedules slip and costs rise. Then comes the reset: contracts extended, additional funding approved. Finally, the outcome shortfall, partial benefits realised, or the programme abandoned. The public record supplies the price tags. The National Audit Office's examination of NS&I's transformation found an overspend above £1 billion, a four-year delay, and tens of millions of pounds of spend that delivered nothing. And the comparative evidence from NHS and UK public-sector programmes points the same way: fragmented supplier models dilute accountability into gaps, overlaps and finger-pointing, while integrated, clearly accountable delivery achieves nearly double the benefits realisation. Fragmentation is not just inefficient. It is roughly half as effective.
Problem Three: Clients Lack a Clear, Objective Way to Govern Complex Digital Decisions
The third problem is the quietest and the most damaging. Boards, executives, digital teams, clinicians, estates teams and vendors use different language and different measures of success. Without a shared, objective frame, it becomes genuinely hard to know which risks matter, which requirements are real, which decisions need escalation, and whether delivery is still aligned to the original transformation intent. Governance exists, committees meet, papers are written, risks are logged, but it does not decide anything the programme's momentum has not already decided.
The Northern Territory's Acacia digital patient record programme, now before a Public Accounts Committee inquiry, shows where that leads. The programme had formal governance structures, but clinical concerns did not translate into effective action, and budget control sat with the IT agency rather than the clinical organisation that would live with the system. Clinicians reportedly raised serious concerns years before the emergency department rollouts; those concerns were not resolved before go-live. The go-live decision was not sufficiently safety-gated, rollback followed in major sites, and a programme that began as a $186 million concept reached a reported $320 million. The medical association's submission to the inquiry draws the essential conclusion: the greatest risks were never solely technical. They arose from insufficient clinical engagement, workflow integration, governance and change readiness. Governance on paper is not governance. Objective, empowered, evidence-based governance is, and most programmes do not have it.
The Answer: Assurance on the Client Side of the Table
Notice what the three problems have in common. None is caused by the vendor, and none can be solved by the vendor. They live on the client side of the table, in how the organisation defines, buys and governs. That is why the answer is not another supplier in the delivery chain, but a discipline that sits alongside the client for the whole journey: Enterprise Transformation Assurance.
The model is straightforward to state. Define the transformation outcomes that technology must enable, and translate ambition into objective requirements, answering Problem One before a single vendor conversation shapes the answer. Assess the current EMR and digital estate honestly against those requirements, and align procurement with the business case and benefits, so that what is bought is contractually tethered to what was promised. Establish architecture, governance and assurance with real authority, a shared frame in which clinical safety, operational risk, technical dependencies and readiness gaps are scored before implementation decisions are made, and in which real risks can be distinguished from perceived blockers. Work constructively with vendors and national programmes rather than against them; assurance is not adversarial, it is alignment. And maintain the golden thread from strategy through procurement, delivery, go-live and optimisation, so that benefits realisation is an engineered outcome rather than a hopeful afterthought.
Underneath all of it sits one further principle the failures keep teaching: people, process and technology must move in unison, and the weakest of the three sets the ceiling for the whole investment. Assurance that reviews only the technology will miss exactly the risks that sank the programmes now being examined by inquiries.
What the Numbers Say
The strategic case for this discipline is one argument. The financial case is another, and it deserves to be stated plainly. Enterprise Architecture, the engineered layer that sits underneath Enterprise Transformation Assurance, returns value in ways a finance director will recognise from the outset: through the avoidance of technology duplication, the reduction of integration and rework costs, the optimisation of digital and estate investments, and improved operational productivity across the workforce and the estate. For a major new hospital scheme, these are not small numbers.
Application rationalisation, the removal of duplicate systems, and the standardisation of technology platforms and licences typically deliver a 10 to 20 per cent reduction in digital estate costs, which for a major programme translates to somewhere between £2 million and £10 million or more. Defining interoperability requirements, data standards and system interfaces before construction and deployment typically delivers a 20 to 40 per cent reduction in integration and rework costs, another £1 million to £5 million saved. And streamlined clinical workflows, reduced administrative burden and more efficient use of workforce resources typically deliver a 2 to 5 per cent improvement in operational productivity, which in a large acute hospital compounds to £5 million to £15 million a year on a recurring basis.
Add in the avoided cost of programme risk and design changes during construction, and the reduced long-term expenditure on technology refresh from a scalable, interoperable architecture, and the picture is clear. The Enterprise Architecture and assurance investment typically represents less than one per cent of a major hospital programme's budget. What it protects is tens of millions of pounds across the lifecycle. It is one of the highest-return decisions available to a programme sponsor, and one of the most consistently under-invested in.
Our Role, Plainly Stated
This is what Tektology does. Our role is not to sell a product or act as a traditional system integrator, we help the client become an intelligent buyer and governor of transformation, defining what they need from digital, data, EMR, workflow, smart infrastructure and technology partners; testing whether current systems and suppliers are delivering it; shaping procurements around objective transformation requirements; and providing the governance and assurance that keeps delivery aligned with the original business case and outcomes.
The goal is not digital transformation for its own sake. The goal is better care, better patient and workforce experience, better operational flow, better use of resources, and more reliable delivery of the outcomes the organisation has already committed to achieve. Three problems, one discipline, and assurance is how you make sure you arrive.
Gabriel Rea is CTO at Tektology, based in Australia, with over two decades of experience in healthcare digital transformation across NHS trusts, government health departments, private hospitals and global health systems.
Henry Darch is an Associate Director at Tektology, based in the UK, where he leads business development and works with healthcare organisations on the practical realities of transformation across operational improvement, estates and infrastructure, and digital delivery.
Together, they work with clients helping healthcare organisations define, buy and govern digital investments so that the outcomes match the ambition.