Article
The account of healthcare AI adoption usually concentrates on implementation: integration, clinical validation, workflow change. Those are real. They are not where most projects fail. Most fail before implementation begins, in decisions made and not made during procurement, planning and governance design. By the time the technology arrives the conditions for failure are set.
Failure one: technology procured ahead of governance
An organisation identifies a tool for an apparent problem, secures budget and buys it. The governance questions, intended purpose, accountability, monitoring, escalation, are addressed during implementation if at all. Governance is far harder to retrofit than to design. A system deployed without a stated purpose is hard to classify under MHRA guidance. A workflow built around an AI output without oversight is hard to change once staff have adapted to it. Accountability not assigned at procurement is hard to assign once several teams have a stake in the system continuing.
Technology procured ahead of governance does not fail at go-live. It fails six months later, when the deferred questions can no longer be avoided.
Failure two: data readiness assumed
Organisations regularly discover during or after implementation that their data does not support the use case they bought. The recurring problems: data structured inconsistently across sites or time; information governance that does not permit the data flows the tool needs; quality problems invisible in the demonstration and material in production; consent frameworks not written with AI use in mind. All of it is discoverable before procurement with a structured data readiness assessment. Few organisations do one.
Failure three: staff preparation treated as training
How to press the buttons is necessary and insufficient. The larger change is in how staff understand their own role in relation to the output. A clinician unclear about their responsibility for reviewing AI-generated content is a governance risk. A care worker treating an AI care plan as authoritative is following the process as they understood it. The failure is in how the system was introduced and how accountability was communicated. That is change management, not training.
Failure four: vendor assessment mistaken for independent review
Vendors assess their own products. That is useful for understanding what a system does. It is not a substitute for independent governance review. An organisation relying on vendor-supplied validation, vendor-asserted classification and vendor-recommended implementation has outsourced its governance to a party with a commercial interest in adoption. That becomes apparent the first time something goes wrong and accountability has to be located.
The preventable pattern
Each of these is preventable without significant additional resource. What it requires is a different sequence: governance assessment and readiness work before procurement, not during implementation or after go-live.
This article sets out Novatib's advisory position. It is not legal or regulatory advice.