The Owner Who Can't Take a Two-Week Vacation Has a Systems Problem | Practice Now

Operations

The Owner Who Can't Take a Two-Week Vacation Has a Systems Problem


June in Arizona has its own particular urgency. The temperature is already fighting words, school just let out, and everyone with any sense is booking a flight to literally anywhere else — San Diego, Colorado, a gas station in Flagstaff. It doesn't matter. Out is out.

And somewhere in a medical practice right now, an owner is doing the mental math on what two weeks away would actually cost them. Not in dollars. In chaos.

Calls that only they know how to handle. Decisions that will queue up like a waiting room with one front desk person. Staff who are competent and well-meaning and completely unarmed with written protocols. A phone that will buzz through every snorkeling session, every poolside hour, every attempt at sleep in a hotel that doesn't smell like a medical office.

They'll probably go. But they won't really leave.

"If the practice stops when you step out, you haven't built a practice. You've built a job — and you're the only one who can show up for it."

We hear this constantly. Not as a complaint, usually — physician-owners are not complainers by nature. It comes out sideways, as a joke about never really logging off, or a half-proud, half-exhausted comment about being indispensable. We don't find it funny. We find it fixable.

Why This Keeps Happening to Smart, High-Functioning People

This isn't a competence problem. The practices where the owner can't step away without things wobbling are often the best-run practices in the room — because the owner is exceptional, and their involvement is what makes the machine work. That's exactly the problem.

A practice built around one person's judgment, availability, and tribal knowledge is only as resilient as that person's capacity to show up. Which, in a healthcare setting, is already maxed out before you add "sole operational decision-maker" to the list.

The practices that run without the owner — not perfectly, but well, in a way the owner can trust — didn't get there by hiring better people. They got there by building better systems and making sure those systems were actually used.

There's a difference. Staff don't fail because they're not capable. They fail because no one handed them a playbook, defined their authority, or gave them permission to make decisions without checking first. That's not a people problem. That's a design problem.

How We Actually Diagnose This at Practice Now

We don't start with solutions. We start with a real look at what's holding your practice together right now — and whether that thing is a system, or a person.

Our approach follows four phases, and they're not interchangeable. You can't prescribe what you haven't diagnosed. Here's what that looks like in the context of operational resilience:

Phase 1

Examine

We look at your actual workflows — not how they're supposed to work, but how they work on a random Tuesday. Who makes what decisions. Where things get stuck. What only exists in one person's head.

Phase 2

Diagnose

We identify the specific failure points — not generic "communication issues," but the exact workflows, roles, and gaps that would cause things to unravel if you were unreachable for two weeks.

Phase 3

Prescribe

We build a plan that fits your practice — not a generic framework. The SOPs, authority structures, and coverage plans that your specific team can actually use, in the way your practice actually operates.

Phase 4

Improve

We don't hand you a binder and leave. We help you implement, test, and refine — because a system only works if people use it, and people only use it if it's been tested before you're on a plane.

The reason most consulting engagements don't produce lasting change is that they stop at Diagnose. They hand you a report and a list of recommendations. We consider that the halfway point.

The Vacation Test: A Diagnostic You Can Run Right Now

Before you call us, here's a quick self-assessment. Not a 47-point survey — just four questions that will tell you most of what you need to know:

Decisions

List the five decisions that crossed your desk last week. How many of them required you — versus just defaulted to you because no process existed?

Documentation

Do written SOPs exist for your most common exception scenarios? When was the last time anyone actually used one?

Authority

Is there a named person with defined, written authority to make operational decisions in your absence? Not "check with whoever seems available." A name.

Communication

Do your staff, patients, and referral partners know who handles what when you're out — or will they find out by calling you?

If you answered "no" or "sort of" to more than one of these, the vacation test has already told you something worth paying attention to.

What We Tell Owners Who Are Skeptical

Fair enough. There's no shortage of consultants who will hand you a framework, charge you for it, and move on. So let's be direct about what's actually at stake.

The Real Cost of Owner-Dependency

Operational fragility isn't just a vacation problem. It shows up as a growth ceiling — because scaling a practice that runs on one person's bandwidth is almost impossible. It shows up in hiring — because good staff leave practices where they can't make decisions without escalating everything. It shows up in revenue — because the workflows that generate and protect revenue are the same ones that collapse without documentation.

Owner-dependency is operational debt. It accrues interest quietly, and it comes due at the worst possible time — a health event, a family emergency, or simply the point where you've had enough and want out on your own terms.

A practice that can't run without you also can't be sold at full value, can't attract a partner, and can't survive a period where you're unavailable. The vacation is just the surface symptom. The systemic resilience is the actual asset.

Practical Steps — Before You Call Anyone

You don't need a consulting engagement to start. Here's what we'd tell you to do this week:

  1. 1
    Track your interruptions for five days

    Every time someone comes to you with a question or a decision, write it down. At the end of the week, categorize: which ones genuinely required your expertise, and which ones just didn't have an answer written down anywhere? That second list is your first SOP backlog.

  2. 2
    Pick your highest-friction workflow and document it this week

    Not everything — one thing. The process that generates the most repeated questions, the most exceptions, the most "let me check with the doctor" moments. Write it down as if you're handing it to a new hire. That document is worth more than it looks.

  3. 3
    Name your coverage lead — in writing, with actual authority

    Pick a staff member, define the scope of their authority during your absence, and give it to them on paper. Then let them practice using it before you leave town. You want to find out what breaks during a test run — not at 30,000 feet over New Mexico.

  4. 4
    Take a long weekend before the long trip

    Three or four days, actually offline. What broke is your priority list. What ran fine tells you where you've already built something worth keeping. You can't run the vacation test from inside the office.

Why Trust Us With This

We work inside the specific reality of your practice — the workflows, the staff dynamics, the patient population, the way decisions actually get made on a busy Wednesday. We're not installing a template. We're building something that fits what you have, and making sure it holds when we're not there to prop it up.

We've seen what happens when practices build real operational infrastructure. Owners take the vacation. They actually come back rested. Staff make better decisions because they finally have the tools and the authority to do it. Revenue cycles stabilize. Hiring gets easier because candidates can see that the practice is professionally run — not held together by one exhausted physician's force of will.

"The owners who eventually step back gracefully built something before they left. They didn't just survive long enough to escape."

It's June. Arizona is doing what Arizona does. You should be able to go somewhere that isn't 114 degrees — and actually be present when you get there.

If you're not sure where to start, start with a conversation. We'll tell you honestly what we're seeing and whether we're the right fit. No report, no slide deck, no obligation. Just a straight look at what's going on and where you actually stand.

Let's Talk About What It Would Take

A conversation costs nothing. We'll tell you what we're actually seeing in your practice — and whether we can help.

Schedule a Conversation