Digital health budgets are under pressure everywhere. In our work with NHS trusts and departments, and clinically-led startups, we recognise there is little tolerance for wasted spend.
One of the most common reasons digital health projects stall or overshoot is not the technology itself, but a gap between how clinical pathways operate in practice and how they are communicated to the teams building the tools.
When pathways are not fully documented or widely understood, both delivery teams and clinical partners risk working from partial information. Assumptions replace certainty, and systems can grow to accommodate every possible interpretation of the workflow. Over time, this uncertainty drives complexity, rework, and rising costs. In practice, the same problems tend to surface again and again.
Digital tools don’t match existing pathways
A digital system can only streamline a process if that process is already fully understood by the developers. When workflows differ between sites, shift patterns, or even individual clinicians, the digital version inherits that variability and costs increase.
Typical examples include:
- steps in the pathway that are handled differently depending on setting or service context
- assessment forms that record the same information in slightly different places
- pathways that rely on tacit knowledge not written down anywhere
These variations make a digital build larger, slower, and harder to stabilise.
Poor alignment creates duplication
Without a clear pathway, it becomes difficult to understand where digital touchpoints sit in relation to existing systems, roles and responsibilities.
This often leads to duplication such as:
- clinicians entering information already recorded elsewhere
- admin teams uploading documents that already exist in another system
- digital tools introducing extra paperwork rather than replacing it
Duplication is one of the fastest ways to burn through digital health budgets and damage adoption.
Incomplete pathways lead to guesswork
When the end-to-end journey isn’t mapped, teams fill the gaps with good intentions. Features are added “just in case”, screens are designed for hypothetical situations, or patient flows are built on assumptions rather than verified practice.
The outcome is fairly predictable. Once real users see the system, they point out missing steps, incorrect branching, or duplicated work. Entire sections then need redesigning.
A rework is rarely minor and can consume the budget originally allocated for improvements and optimisation.
Address risks early
These patterns all stem from the same challenge: when clinical pathways are not fully documented, agreed, and clearly understood, ambiguity can creep into digital delivery. Both delivery teams and clinical partners need to be aware of these risks from the outset. Addressing them early ensures the project stays predictable, manageable, and aligned with real-world practice.
Bring clinicians into the design
Involving clinicians from the start is a crucial part of defining and agreeing pathways. Their input prevents unrealistic assumptions, highlights variations across teams, and identifies opportunities to streamline workflows.
Clinician involvement improves quality and reduces the volume of revisions later, which is where many projects lose time and money.
Clear pathways reduce risk and cost
When teams work together to define the pathway early — including decision points, edge cases, handovers, data flows, and escalation routes — delivery becomes far more predictable.
Clear pathways enable:
- accurate estimation
- fewer change requests
- quicker decision-making
- earlier identification of risks
- a build that aligns with how care is actually delivered
For most digital health projects, this single step has more impact on cost control than any technical decision.
Why this matters
Digital health delivery depends as much on shared understanding as it does on technical capability. When clinical pathways are clearly articulated and consistently understood by the people building digital tools, uncertainty reduces and delivery becomes more predictable. Where that clarity is missing, teams compensate by designing for ambiguity. Systems grow more complex, assumptions replace evidence, and rework becomes unavoidable.
Achieving clarity is a joint responsibility. Digital teams and clinical partners need to work together from the outset to define, document, and agree the pathway, ensuring the final system reflects how care is actually delivered. When both sides invest in this early work, projects run more smoothly, digital health budgets are controlled, and the system is far more likely to be adopted successfully.
Digital health that works
Most digital overruns aren’t caused by technology; they come from ambiguity in clinical pathways. Before committing to building, integrating, or procuring a tool, delivery teams and clinical partners should work together to define, document, and agree the pathway.
This early collaboration is often the highest-ROI intervention in a digital programme. It’s the clearest way to protect budgets, reduce rework, and ensure the final system reflects the reality of care.
For a deeper look at the patterns that drive digital delivery risk, download our white paper — Digital Health that works: why human-centred design is the missing piece in NHS digital transformation.
Download the White Paper here