I built an operating model around a simple commitment: every call gets a visit.
Not eventually. Same day.
To sustain that standard as volume grew, I added a registration representative as the first point of contact — a non-clinical bridge that allowed us to respond immediately while a clinical team member was mobilized. The methodology held. The responsiveness held. And referral sources built their expectations around both.
What we had created wasn't just an efficient process. It was a brand promise — one that referring physicians, discharge planners, and social workers had quietly factored into how they made decisions about where to send their patients.
Then the service model expanded. And with that expansion came a recommendation to modify the same-day response methodology — a reasonable-sounding adjustment when viewed purely as an operational change in a new environment.
What it didn't account for was the relationship infrastructure that had been built on the foundation of that original commitment. The referral sources didn't receive a memo. They just started experiencing something different from what they had come to depend on.
Referrals fell significantly. And even after the organization recognized the damage and attempted to course correct within months, the trust that had taken years to build required years to recover.
The lesson wasn't that the methodology could never evolve. It was that operating models must have variable options built in for when volume, scope, or service lines change — so that growth decisions don't inadvertently dismantle the responsiveness that created the growth in the first place.
What exists today in your operating model was built for a specific volume and a specific promise. As both of those change, the question isn't whether to adapt — it's whether the adaptation protects what your referral sources and patients have come to rely on.
That requires intention. And it requires that the people closest to those relationships have a seat at the table when the model changes.