This pattern is familiar across the health sector: a new digital health pilot launches with promise. Early feedback is positive, a small group of users are engaged, and initial results look encouraging. Then progress slows. There is no rollout, no scale, and no clear next step.
This happens repeatedly, and rarely because the idea was flawed or the technology failed. More often, it is because the pilot was not designed to support the decisions needed after it ends.
What follows are some of the most common reasons digital health pilots stall in our opinion, as well as the practical factors that tend to determine whether they move forward or quietly grind to a halt.
1. Digital health pilots don’t test the whole journey
Most pilots focus on a narrow scenario or a single service. That can be appropriate early on, but it often excludes the parts of the pathway that later determine whether rollout is viable.
In pilots that progress, teams usually:
- agree early which parts of the pathway are in scope now and which are explicitly not
- pressure-test at least one end-to-end journey, even if only at low volume
- surface integration, safety, and operational constraints early, while change is still possible
This doesn’t make the pilot heavier. It makes it more honest.
2. Early enthusiasm is mistaken for adoption
Early use during a pilot often comes from people who are interested, motivated, or directly involved in shaping the work. They make time for it, adapt their behaviour, and are willing to overlook friction.
That can give a false sense of confidence. Wider teams may have less flexibility, different pressures, contexts, or routines that were not considered during the pilot.
Pilots that progress tend to look beyond who is using the tool and ask how it fits into everyday work. They pay attention to where time is added, steps are duplicated, or workarounds appear, because those issues usually surface at scale, not during early enthusiasm.
3. The pilot doesn’t collect the evidence decision‑makers need
Many digital health pilots are set up to show that a tool works, but not to support the decision to roll it out.
During a pilot, teams often focus on feedback, engagement, and early signs of value. That information is useful, but it is rarely enough on its own. Commissioning and leadership teams usually need clearer signals, such as whether pressure is reduced, outcomes improve for patients, or risk is lowered in a measurable way.
When a pilot has not been designed to gather that kind of evidence, it becomes difficult to move forward. By the time the pilot ends, it is often too late to collect baseline data or make meaningful comparisons.
This is why it can feel successful in practice, but still struggle to justify rollout.
4. Governance arrives after momentum has gone
Information governance and clinical safety are often left until a pilot has finished, with the assumption that they can be addressed once value has been shown.
In practice, this is where progress often slows. By the time governance processes begin, the team that ran the pilot may have moved on, funding may have ended, and urgency has faded.
Pilots that move forward usually clarify governance expectations early and use the pilot period to prepare what will be needed later. This helps maintain momentum and avoids the sense that rollout requires starting again.
5. Ownership dissolves after the pilot
A pilot is often driven by innovation funding or short-term programmes. When those end, responsibility can become diffuse.
Digital health pilots that progress usually have:
- a named owner beyond the pilot phase, even if their role evolves
- clarity on who carries risk, who makes decisions, and who advocates for scale and sustained use
- continuity of intent, even when teams or funding change
Without this, even well-designed pilots have a tendency to fade.
What actually determines progress
Digital health pilots fail less often because of resistance to change, and more often because they were never positioned to survive success.
When a pilot is treated as the first phase of delivery rather than a proof-of-concept, it creates momentum instead of uncertainty.
Our white paper explores this in more depth, setting out how digital health pilots can be designed from the outset to move beyond pilot and into sustained use, without over-engineering or false certainty.
Much of the digital health work we do at Corporation Pop sits in this space: supporting teams to design pilots that are realistic about adoption, evidence, and governance from the outset. Not to over-engineer early work, but to reduce the risk of pilots stalling once initial momentum fades.