top of page

You’re Not the Only One Who Can Do It

Updated: 3 days ago

Why delegation feels risky and how holding onto everything can quietly limit a practice


Physicians are trained to notice what others miss, take responsibility when the stakes are high, and make decisions that affect people’s lives.


Then they open a practice and are told to “just delegate.” No wonder it feels uncomfortable.


Delegation can sound simple from the outside. Hand off the task. Trust the team. Stop doing everything yourself. But when you’re the person ultimately responsible for the patient experience, the finances, the staff, and the reputation of the practice, handing something over rarely feels simple.


It can feel like loss of control.


You may worry that explaining the task will take longer than doing it yourself. You may have delegated before and ended up correcting mistakes, answering more questions, or quietly taking the task back. And because someone else’s error may still become your problem, keeping control can feel safer. In the short term, it often is. In the long term, it becomes a bottleneck.


When every question, decision, and task comes back to the physician, the practice can only move as quickly as one person can think, respond, and work. Growth slows. Small tasks accumulate. Strategic work gets postponed because the inbox, schedule, and daily fires always feel more urgent.


Eventually, the physician becomes the practice’s most overqualified administrative assistant. That isn’t a criticism. It’s what happens when responsibility expands faster than the systems needed to support it.


Delegation doesn't mean handing over everything and hoping for the best. It also doesn't mean giving up oversight or asking someone else to make decisions that require your clinical judgment, license, or authority. Good delegation means deciding what truly requires you and creating enough clarity for someone else to manage the rest.


A useful place to start is with four questions:


  • Does this task require my license, judgment, or authority?

    If the answer is yes, it probably stays with you.

  • Am I doing this because only I can do it, or because I’ve always done it?

    Those are not the same thing.

  • Could someone else handle 80 percent of this with a clear process?

    It may not be done exactly as you would do it. That doesn't necessarily mean it's being done poorly.

  • What training, information, or guardrails would make this safer to delegate?

    Sometimes the problem isn't the person. It's that the task was handed over without context, a clear outcome, or a reliable process.


This is especially important when working with a virtual assistant. A VA can't read your mind, and “take care of this” isn't a system. They need to know what success looks like, what decisions they may make independently, when to ask for help, and where the information they need is stored. That takes effort upfront. There's no way around it.


The first few times you delegate a task, it may take longer than doing it yourself. You're transferring knowledge, testing the process, and finding the gaps. That isn't proof that delegation failed. It's the cost of building capacity.


You still have a role in the process

Sometimes a practice owner knows systems are needed, hires someone to build them, and then feels overwhelmed by the very process that's supposed to reduce the overwhelm.


That reaction is understandable. It's also where many delegation efforts stall.


A new workflow may require you to pause, review decisions, answer questions, learn a tool, or approve the way information will move through the practice. None of that feels urgent compared with patients, messages, and the daily demands already competing for your attention. But the system can't be built around your expertise if you're never available to transfer it.


You can't ask someone else to create a reliable process and then disengage when it's time to review, learn, approve, or correct it. You also can't reject the finished process because it feels unfamiliar after avoiding the steps that would have made it familiar.

At some point, the owner has to stop long enough to participate.


That means listening when the process is explained. It means asking questions before panic turns into resistance. It means approving what works, editing what doesn't, and allowing the system enough time to become routine.


Then comes the next step: trust, but verify.

Trust doesn't mean ignoring the work and hoping everything is fine. Verification doesn't mean hovering over every detail or taking the task back at the first imperfection. It means agreeing on what will be checked, how often it will be reviewed, and what should be escalated. A weekly dashboard, a short audit, or a clear exception report may provide all the oversight you need without pulling every task back onto your plate.


The goal is not to remove yourself from the practice. It is to remove yourself from work that no longer requires your constant involvement.


Trust matters, but trust alone is not enough. People need clear expectations. They need access to the right tools. They need feedback that helps them improve. And they need enough room to take ownership without being corrected at every turn simply because they approached the task differently.


Delegation isn't abandonment. It's leadership. It's choosing to spend your time where your expertise matters most while building a team that can carry the work that doesn't require your hands on every step.


Your practice can't grow if every road still leads back to you.

 
 
 

Comments


bottom of page