Why healthcare automation stalls between the pilot and the floor
2026-09-08 · 6 minute read
A working demo is not an implementation. The gap is access, exceptions, ownership, and a Monday morning that does not look like the sample.
Healthcare organizations do not fail at automation because nobody can imagine a better workflow. They fail because the pilot and the floor are different places. The pilot has a champion, a clean packet, and a system administrator who is still in the room. The floor has a fax that arrived at 6:40 a.m., a coordinator covering two branches, and an EHR session that timed out.
If the project ends at a recommendation, nothing in that room changes. If it ends at a purchase, the team has another login and the same re-entry. Implementation is the work of making the new path the one people actually use when the champion is in a meeting.
What the pilot usually hides
Access is the first hidden dependency. An agent or an integration cannot read a referral queue the organization has not authorized, and it should not. Least-privilege access takes longer than a demo, and it is part of the design.
The second is variation. Sample packets are complete. Real packets are missing the physician, the service line, or the page that tells you whether this is a resumption of care. A workflow that only handles the complete packet pushes the hard cases back onto the same people, with less time.
The third is ownership of exceptions. Someone has to clear the queue of items the automation could not finish. If that person is "the team," the queue will age. Name the role before go-live.
What implementation has to include
A future-state workflow, not a list of tools. A boundary around what the automation may do without a person. A test against the real variation, including the ugly packets. Training for the people who approve, override, and fix. A week of supported go-live. A measure that was baselined before anyone called the project a success.
Umble's work is that sequence: discover, design, build, implement, optimize. The point of the sequence is operational use. A slide that describes it is the start of the work.
