Warning signs include more manual work, repeated reauthentication, poor fit for different clinical roles, and new data quality risks after digitisation. If staff spend more time managing the system than using it, the project may be adding friction instead of value. A good assessment should look for unintended effects on safety, speed, and clinician attention.
How health IT projects start to lose value in practice
A health IT project erodes its own value when the workflow it creates is heavier than the work it replaces. That usually shows up as extra clicks, duplicated data entry, more coordination overhead, and a growing gap between how the system is designed and how clinicians actually work. The project may still be “live,” but the operational benefit is shrinking.
The key question is not whether the system is technically functional, but whether it still reduces friction, supports clinical judgment, and preserves attention. A project can meet delivery milestones and still become less useful if it adds manual reconciliation, slows handoffs, or forces staff to work around it.
Signals that the system is creating friction instead of benefit
The clearest warning signs are behavioural and operational. If users are repeatedly reauthenticating, entering the same information in multiple places, or spending more time navigating the system than serving patients, the design is no longer aligned with real clinical work. That is especially important in environments where speed, handoff quality, and attention are part of safety.
Another sign is role mismatch. Health IT often gets judged by whether it works for a general use case, but clinical work varies sharply across nurses, physicians, specialists, clerks, and support teams. If the system fits one role well and creates workarounds for others, adoption may look stable while actual value degrades.
Finally, watch for new data quality risks after digitisation. Errors introduced through copying, field workaround behaviour, stale structured data, or weak validation can make the system look more complete while making the underlying information less trustworthy. That is a common pattern when the technology captures data but does not improve the integrity of the workflow that produces it.
Why value erosion matters beyond simple user dissatisfaction
Value erosion in health IT is not just an inconvenience issue. More manual effort can increase latency, raise the chance of transcription mistakes, and fragment attention at the point of care. If a project shifts effort from clinical work to system management, the organisation may be paying for digitisation while losing speed and reliability.
The deeper problem is that these failures often accumulate gradually. A project may begin with a defensible improvement, then lose value as exceptions, workarounds, access friction, and maintenance overhead grow. Once that happens, teams often normalise the friction instead of re-evaluating whether the system is still delivering net benefit.
What to examine before deciding the project is still worth the overhead
Assessment should follow the workflow, not just the feature list. Start with where the system adds steps, where staff must switch context, and where the data created by the system is later corrected elsewhere. Those are usually the places where value leakage becomes visible first.
A practical review should ask whether the system still improves three things: safety, speed, and clinician attention. If any one of those is getting worse, the project may need redesign rather than more user training. This is where operational evidence matters more than implementation intent.
It is also useful to compare expected benefit with the cost of exceptions. A system that works in the average case but fails in common edge cases can create a hidden support burden and push teams back to manual processes. That is often how a project stops being a productivity gain and becomes a process tax.
Practitioner Guidance
What to prioritise: Review the highest-friction workflow moments first, especially repeated sign-in, duplicate documentation, and role-specific workarounds. Those are often the earliest indicators that the project is transferring effort from the organisation to the user.
What to verify: Check whether staff are bypassing the intended workflow to complete core tasks, whether data is being corrected downstream, and whether the system is reducing or increasing time-to-task for each clinical role. A project can look successful in rollout metrics while quietly degrading day-to-day utility.
Decision rule: If the system is creating measurable friction in safety-critical work, treat redesign as a value issue, not a training issue. Training cannot fix a workflow that is misaligned with how care is actually delivered.
Practitioner takeaway: The strongest signal of value erosion is not user resistance by itself, but repeated evidence that the system is forcing extra work, weakening data quality, or taking attention away from care.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on September 26, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
