The Productivity Dip After Go-Live

The productivity dip after a go-live is one of the more predictable events in this work. It rarely appears in the model that justified the change, which is why it lands as a surprise.

The dip is the most predictable part of an implementation

Almost everything about an implementation is uncertain until it happens. The productivity dip is not. In the first weeks after a new system goes live, encounters take longer, the day runs later, and the schedule the practice was seeing on Monday is not the schedule it can sustain by Thursday. That pattern holds whether the replaced software was paper or another EHR.

It is not a sign the choice was wrong or that anyone is performing badly. It is what happens when a whole practice's habits, the shortcuts and keyboard patterns people had accumulated over years, get reset in an afternoon. Those habits come back, but they come back at the speed of daily use, which is measured in months rather than weeks.

The financial case that justified the change never contains the trough

The case supporting a system change is built on what the new system will do better. That is the appropriate content of a pro forma, and it does not prepare a practice for the weeks after go-live. Vendors do not lead with the dip in a proposal, and RFP responses do not carry a line for the visits that will not be seen while people learn the new workflow. The information tends not to arrive anywhere.

So the number that reaches the budget is the steady-state one. The transition gets treated as a rounding error, or as a training expense that ends when the training does. What actually happens is a share of the practice's revenue going missing without anyone having recorded that it would.

What was replaced changes the shape of the dip

Not every dip is the same size, and the size follows from what came before. A practice moving from paper to a first EHR tends to lose more early and recover more slowly, because it is learning both a system and the discipline of typing while a patient is speaking. A practice moving between two EHRs loses less and recovers faster, but often finds the assumptions of the old system had been built so deep into how work was done that the new system's better idea reads as an obstacle.

The other variable is how much of the old configuration was carried across. Migrations that preserve familiar templates shorten the dip and inherit the old habits with them. Migrations that rebuild from scratch make the dip longer and produce something closer to what the new system was chosen for. That trade sits inside the implementation plan, and it usually gets settled by whoever is free the week the question comes up.

The hours go somewhere that does not appear in a report

Where the time actually goes is worth naming, because otherwise it is invisible except as a schedule running late. A physician spends longer per encounter because the click path is unfamiliar and templates do not yet fit their language. A medical assistant asks more questions of billing because fields have moved. Someone stays two hours after clinic finishing notes that used to get done between patients.

None of that appears as a line anywhere. What it produces is a small rise in overtime, a jump in message volume between departments, and a decrease in same-day chart closure. The revenue effect lives in the schedule reduction and in slower charge posting for the visits that did happen.

Planning for the dip is mostly deciding what will not happen

A plan for the dip is largely a plan for scarcity of attention. The schedule for the first several weeks gets reduced by some amount, chosen ahead of time, and then defended when it feels like a waste of capacity. Non-urgent projects sharing people with the implementation move out of the same quarter. The payer renewal somebody was going to press on, the operational review of the referral loop: each can wait, and each will otherwise consume attention that is not available.

Communication with patients about scheduling around the change is a piece of it too, since a patient who tried to book a routine visit during a week the practice could not see them does not always call back. Whether it is worth doing depends on specialty and the expected length of the dip.

The rebound is not always symmetric

The dip ends. Some of the shortcuts that lived in the old system's muscle memory do not come back with it, because the new system will not accommodate them, and the workarounds they were part of become visible for the first time in years. That is part of the value of the change, and it does not always feel like value in the month it happens.

Occasionally a practice does not fully return to its earlier volume, and the honest reading is usually that the earlier throughput was borrowed from documentation the new system will not accept. The new baseline is the real one. What is left to answer a year on is whether the reasons written into the pro forma are being realized, or whether the practice absorbed a hard six months and now works around the new system the way it worked around the last.