The Difference Between Installation And Transformation.

The go-live was on a Tuesday.

By Thursday, I was standing in a med-surg unit at 11:14 p.m. watching a nurse named Denise document a wound assessment on a Post-it note stuck to the side of a workstation on wheels.

Not in the EHR. On a Post-it. In 2019. On a system we had spent $40 million and eighteen months implementing.

I did not interrupt her. I waited until she finished her round, and then I asked, as gently as I could, what the Post-it was for.

She looked at me, this VP she had never met, standing in her hallway at nearly midnight,  and she said, "Because if I put it in the new system, it takes me nine clicks and I still can't find it tomorrow. So I write it here, and I put it in at the end of my shift when I have time. Except I never have time. So I mostly just remember."

She said this without shame. She said it the way you'd tell someone the coffee machine is broken.

I thanked her. I went back to my office. I sat down. And I understood, with total clarity, that we had not implemented an EHR. We had implemented a workaround factory.

I have been in healthcare operations for twenty years. I have led two enterprise EHR implementations, three revenue cycle overhauls, and more digital "transformations" than I care to count. I have signed the contracts. I have stood at the go-live podium.

And here is what I know, with the certainty of someone who has been wrong about it before:

Digital health transformation does not fail because of the technology. It fails because we mistake installation for transformation.

Installation is a project. Transformation is a shift.

Installation ends when the software goes live. Transformation ends, if it ends at all,  when the way people do their work has actually changed, and the new way is easier than the old way, and the workarounds have been retired simply because no one needs them anymore.

Most digital health initiatives I am called into as a consultant are somewhere between month nine and month twenty-four post-go-live. The technology is installed. The vendor has been paid. The project team has disbanded. Someone has been promoted.

And in the units, on the floors, in the clinics, people are running two systems: the one on the screen, and the one on the Post-it Note.

Here is what I have learned about why this happens, and what to do about it.

The clinical workflow was designed by people who do not do the workflow.

I do not care how many "clinical champions" sat in your design sessions. If your build team spent more time with the vendor's reference model than with the actual nurse who will use the screen at 2 a.m. during a code, you built for the vendor, not for the nurse.

The fix is not more training. The fix is going to the unit at 2 a.m. and watching. Not asking. Watching. What people do when they are tired, understaffed, and holding a patient's life in their hands is the workflow. Everything else is a diagram.

The measure of success was defined before anyone understood what success would feel like.

Most transformation scorecards I see measure adoption (did people log in?), utilization (did they click the thing?), and satisfaction (a survey no one has time to complete honestly). None of these measure whether the work got better.

The metric that matters is one almost no one tracks: time returned to the bedside. If your $40 million system did not give clinicians back time with patients, it did not transform anything. It just moved the paperwork to a screen.

The organization was not ready to receive the technology.

This is the one nobody wants to hear. Because "readiness" sounds soft, and boards want to see Gantt charts.

But readiness is not soft. Readiness is whether the nursing leadership has the bandwidth to redesign a workflow while running a unit. Readiness is whether the medical staff trusts the CMIO enough to bring their real objections to the table instead of sandbagging in the parking lot. Readiness is whether IT and clinical operations have ever, actually, in the history of your organization, built something together as equals.

If the answer to any of those is no, you are not implementing a system. You are performing one.

This is the space The Shift Method™ was built for. I do not do go-live support. I do the work before go-live, the readiness work, that determines whether the go-live is a milestone or a monument to good intentions.

Back to Denise.

We did not fix her Post-it problem by retraining her. We fixed it by rebuilding the wound documentation workflow with three nurses from her floor, in a room, with the vendor engineer on speakerphone, over the course of a week. It took nine clicks down to two.

We also did something harder. We publicly acknowledged, in a system-wide communication signed by me and the CMIO, that the original workflow had been built without adequate frontline input, and that we were changing our design process going forward.

That memo cost us nothing. It bought us more trust than any training module ever has.

Six months later, our EHR satisfaction scores on that unit had moved from the bottom quartile to the top. The Post-its disappeared. Not because we banned them. Because they were no longer necessary.

That is the difference between installation and transformation. Installation ends when the software is live. Transformation ends when the Post-it disappears on its own.

So here is what I want to ask the executives, CIOs, CMIOs, and board members reading this:

Walk your units this week. Not on a scheduled tour. Late. Unannounced. Look at the workstations on wheels. Look at the whiteboards. Look at the printer trays.

Count the Post-its Notes.

That is your real transformation scorecard. What are you going to do about it?

#DigitalHealthTransformation #HealthcareLeadership #TheShiftMethod