When everyone agrees with your implementation recommendations, it can feel like things are going well. There are no long debates, no repeated requests for clarification, and no decisions sitting unresolved.
I have learned to be a little suspicious of that kind of easy approval.
On one Epic implementation, the pharmacy leaders responsible for decisions approved almost everything we brought forward. That was unusual. Typically, people ask how a proposed change will affect their workflows, challenge an assumption, or want to understand an exception. We were not getting much of that discussion.
A leadership change exposed the problem. The incoming pharmacy director was knowledgeable and engaged, and he started questioning decisions that had already been approved. He wanted to revisit some of them.
His questions deserved attention. The difficulty was that we were now late in an integrated implementation, and revisiting a pharmacy decision could mean changing work other teams had already built around it.
A reasonable request can still have a difficult timeline
Order sets are a good example. A change may involve pharmacy, the orders team, and clinical documentation. What looks like a straightforward adjustment from one department's perspective can require broader review and oversight-board approval.
That makes timing part of the decision. You have to understand the requested improvement, the implications for other teams, and whether there is a reason it must happen before go-live.
In this case, I raised the issue with my manager. It went through the implementation director and then to executive leadership. The concerns were discussed, and the changes at issue were treated as appropriate for post-go-live optimization rather than changes that had to be made immediately for patient safety.
They were deferred and addressed several weeks after go-live, to the incoming director's satisfaction.
That distinction matters. This was not a reason to dismiss a new leader's concerns, and it is certainly not a rule that safety concerns should wait. It was a decision about the timing of specific changes, made through the project's escalation process.
The lesson I took away about sign-off
The part I would handle differently happened much earlier, when we were getting all those approvals.
I would ask decision-makers to explain the proposed change back to us in terms of their current workflow. What would their team do differently? Where might the new process create friction? What would they need to explain to the people actually using it?
Those are the discussions I wish we had prompted. A yes gives you an answer. A conversation gives you a better sense of whether someone understands what they are approving.
That is especially useful when leadership may change. The next person needs to understand the reasoning behind a decision, not just discover that somebody signed off on it.
A practical checklist for late implementation changes
Here is how I would structure the discussion when a previously approved decision comes back onto the table:
- Define the concern. Is it a safety concern, an operational problem, a preferred workflow, or an improvement opportunity? Bring in the appropriate clinical and operational reviewers rather than making that judgment alone.
- Map the dependencies. Which teams, workflows, and decisions would need to change? Use an order-set request as a cross-team conversation when it affects orders, pharmacy, and documentation.
- Explain the timing. What is the reason this needs to happen before go-live? What is the consequence of waiting? Be specific about both.
- Use the escalation path. Start with the people responsible for the work and follow the project's governance process. A disagreement should not quietly become an unauthorized build change.
- Make a deferred request visible. Recommend an owner, a review date, and a clear description of what will be reconsidered. “After go-live” needs a practical next step.
- Improve the next approval conversation. Ask reviewers to describe the workflow impact before treating their agreement as a completed review.
Good implementation work includes knowing when to revisit a decision and how to do it without ignoring the rest of the project. A useful improvement does not lose its value because it belongs in optimization. The important thing is that it gets a fair review, an appropriate timeline, and follow-through.
Planning an Epic implementation or bringing in additional consulting support? Talk with BridgeLine Health about the work you need covered, the decisions your team needs help moving forward, and the experience the assignment requires.