Recently, one of our largest hospital partners gave us difficult feedback: gaps in communication were creating dissatisfaction for their team.
This was not a new relationship. We had been working together for more than 15 years. They knew our standards, our brand, and the level of service they should expect from us. They also knew that the experience they were having was unusual.
Something was off.
My first response was to bring our team together and conduct a root-cause analysis. I was proud of how everyone showed up. They came prepared, engaged, and willing to look honestly at what had happened.
That response reflected a culture we have worked hard to create: a spirit of service in the pursuit of excellence.
But culture is not proven when everything is going well. It is revealed when a client tells you that you have fallen short.
The problem was not a lack of care
As we examined the situation, we traced the communication gap back to an operational change two months earlier: the launch of a new intake platform.
The platform had changed how information moved through our intake department. Part of the team had the ability to see patient updates. Another part had access to the client portal and could communicate with the hospital partner.
But the two capabilities had not been connected as they needed to be.
The team members who had the updates did not have access to the portal. The team members who had access to the portal did not have the same visibility into the updates.
Our people were working. Information existed. The system was in use.
From the client’s perspective, however, they were reaching out for patient updates and receiving what felt like radio silence.
That distinction matters.
A process can be functioning internally and still be failing the customer.
When implementation is mistaken for completion
The lesson was not that the new platform was inherently wrong. The lesson was that we had defined implementation too narrowly.
We had launched the technology. We had changed the operational process. But we had not fully tested what the change meant for the client’s experience from beginning to end.
We had not asked every necessary question:
- Who can see the information?
- Who can act on it?
- Who has access to the communication channel?
- Who owns the handoff?
- How do we know the client received a clear response?
Those questions are easy to overlook because internal teams often experience a process in pieces. One group sees the intake information. Another manages the client communication. Each team may be doing its part while the overall experience still breaks down between them.
Customers do not experience our organizational chart. They experience the handoffs between our teams.
The closed-loop change test
This experience gave me a simple way to think about operational change. Before declaring a new platform, process, or system fully implemented, leaders should test four things:
1. Visibility
Does each person involved have the information needed to take the next step?
2. Access
Can each person reach the system, tool, or communication channel required to do their job?
3. Ownership
Is it clear who is responsible for communicating with the client and moving the issue forward?
4. Closure
Can we confirm that the client received an answer and that the communication loop was actually closed?
Technology can make information available without making action possible. A process can assign responsibility without giving someone the access required to fulfill it. And a team can work hard without realizing that the customer is still waiting.
The closed-loop test helps reveal those gaps before the client has to find them for us.
Customers do not experience our organizational chart. They experience the handoffs between our teams.
What we did next
Once we understood the root cause, we moved quickly. We conducted the analysis, developed a corrective action plan, and presented that plan back to the client.
Most importantly, we worked to restore the close-loop communication that had existed before the new intake platform was implemented.
The goal was not simply to explain what had happened. It was to make sure the process worked better going forward.
That required both operational correction and honest communication with the partner who had trusted us enough to raise the concern.
I am grateful for that trust.
It would have been easier for the client to quietly become frustrated or begin looking for alternatives. Instead, they called us and said, in effect, “This is not like you. What is going on?”
Their feedback gave us the opportunity to see a blind spot we had not recognized ourselves.
The leadership lesson I am carrying forward
Operational change is often measured by internal milestones: the platform launched, the training completed, the process documented, the team transitioned.
Those milestones matter. But they are not the same as a successful customer experience.
A change is not complete when the technology goes live.
It is complete when the people responsible for the experience have the information, access, ownership, and communication pathways required to serve the customer well—and when the organization has tested the full journey, not just its individual parts.
Our client reminded us that close communication is not a soft extra added after the process is built. It is part of the process.
And the most important measure of an operational change may not be whether the system works inside the organization.
It may be whether the customer can feel that it works.
An operational change is only successful when the customer experiences the improvement—not the complexity behind it.
