Have you ever asked your team about something that didn't get done, only to discover that everyone thought someone else was handling it?
Maybe a new clinician was supposed to be added to your scheduling system before their first day. Your office manager thought the clinical director was taking care of it. The clinical director assumed it was part of the administrative onboarding process.
Everyone knew it needed to happen.
But no one actually owned it.
By the time someone realized it hadn't been done, the new clinician was starting, appointments needed to be scheduled, and you were the person trying to sort everything out.
These situations are frustrating, especially when you have capable people who genuinely care about doing their jobs well.
But before assuming someone dropped the ball, I think it's worth asking a different question.
Was it ever clear who was supposed to be holding it?
Working together isn't the same as sharing responsibility for everything.
As a practice grows, more people become involved in the day-to-day work.
Your administrative team manages scheduling and intake. Your clinical director supports clinicians. Your billing team handles claims and payments. Your practice manager oversees operations.
And of course, these responsibilities overlap.
That's normal. A healthcare practice depends on people working together.
But when several people are involved in a process, it becomes especially important to understand who is responsible for what.
Take clinician onboarding, for example.
Your hiring manager may be responsible for extending the offer. Human resources collects employment documents. Credentialing handles insurance enrollment. Your administrative team sets up scheduling and system access. Your clinical director coordinates training and supervision.
Each person has a part to play.
But who is making sure the entire process is moving forward?
Who notices when something is delayed?
Who follows up when one step hasn't been completed?
And who confirms that everything is ready before the clinician sees their first client?
If the answer is simply "the team," there's a good chance something will eventually get missed.
Not because your team doesn't care.
Because a group of people can all be working hard without anyone having a clear picture of the whole process.
Responsibility needs to be clear enough that people can act on it.
I've found that job descriptions don't always tell you much about how work actually happens.
You might have an office manager whose job description includes overseeing administrative operations.
That sounds reasonable.
But what does overseeing administrative operations mean in practice?
Are they responsible for ensuring client inquiries receive timely responses? Can they make changes to scheduling procedures? Are they expected to address administrative performance concerns? What decisions can they make without your approval?
If those expectations haven't been discussed, you and your office manager may have very different ideas about what the role includes.
And that's where frustration starts.
You believe you've delegated something.
Your employee believes they're supposed to check with you first.
You wonder why they're not taking more initiative.
They wonder why you're frustrated when they've been trying to keep you informed.
Neither of you necessarily has the same understanding of what ownership looks like.
This is why I think it's helpful to define responsibilities around outcomes, not just tasks.
Instead of saying someone is responsible for checking the intake inbox, consider whether they're responsible for making sure new inquiries are reviewed, responded to, and appropriately followed up with.
Those are different expectations.
One describes an activity.
The other describes a result.
And when the expected result is clear, you have a much better starting point for deciding what support, authority, and processes that person needs.
Pay attention to the handoffs.
One of the places I look first when work isn't getting done consistently is where it moves between people.
Let's say a prospective client reaches out requesting an appointment.
Your intake coordinator responds and determines what services they're looking for. The next step is confirming availability with a clinician.
But the clinician hasn't updated their calendar.
So the intake coordinator sends a message and waits.
A day passes.
The clinician responds, but the appointment time is no longer available.
Now the intake coordinator needs to reach back out to the prospective client.
At every point, someone may have done exactly what they believed they were supposed to do.
And yet the process still didn't work particularly well.
The issue may not be the effort anyone is putting in. It may be that the handoffs aren't clear.
When work moves from one person to another, everyone involved should understand what triggers the next step, how information is shared, and what happens when something is delayed.
Otherwise, employees spend a surprising amount of time following up with one another, searching for information, and trying to figure out who has the next action.
And eventually, those unresolved questions tend to find their way back to the owner.
Start with something that keeps falling through the cracks.
You don't need to rewrite every job description or build an elaborate organizational chart to improve accountability.
I'd start with one recurring problem.
Maybe it's clinician onboarding, intake follow-up, billing corrections, or responding to client complaints.
Choose something that involves more than one person and hasn't been working as smoothly as you'd like.
Then sit down with the people involved and walk through it together.
Ask:
Who owns the overall outcome?
Even when several people contribute, someone should be responsible for making sure the process reaches its intended result.
Who is responsible for each step?
Be specific. If someone is waiting for another person to complete something, make sure both people understand that expectation.
How does the next person know it's their turn?
An email, a shared task, a notification, or a conversation may all work. What matters is that there's an agreed-upon way to communicate.
What happens when something doesn't go according to plan?
People get sick. Priorities change. Someone misses a deadline. A system stops working.
Who follows up? Who makes the decision about what happens next? When should the issue be escalated?
Does everyone have the authority to do what they're responsible for?
It's difficult to hold someone accountable for a result if they can't make the decisions needed to achieve it.
You may find that the solution is relatively simple.
Clarify who owns the process. Agree on the handoffs. Give people the authority they need. Document the expectations somewhere everyone can access them.
Then try it.
See what works, what doesn't, and what needs adjusting.
Accountability doesn't have to mean micromanagement.
I think the word accountability can make people uncomfortable.
Sometimes it brings to mind someone checking up on every task, pointing out mistakes, or looking for someone to blame when something goes wrong.
But that's not how I think about it.
Good accountability begins with clarity.
People should know what's expected of them, have the tools and support to follow through, and understand how their work contributes to the larger organization.
They should also know when and how they'll discuss progress with their manager.
That might mean regular check-ins, a shared project tracker, or a quick conversation when something isn't going as planned.
It doesn't have to mean asking for updates every few hours.
And it certainly doesn't mean the owner needs to be copied on every email.
When responsibilities are clear and employees have the authority to carry them out, leaders can spend less time chasing tasks and more time supporting their teams.
Of course, there will still be times when someone doesn't follow through.
Those situations deserve a direct conversation.
But that conversation is much more productive when everyone had the same understanding of the expectation from the beginning.
Clarity is also a way of supporting your people.
There's a human side to all of this that I don't think gets enough attention.
Unclear responsibilities can create tension between employees who otherwise work well together.
One person feels like they're always picking up the slack.
Another feels like they're being blamed for something they didn't know was their responsibility.
Someone else is afraid to make a decision because they aren't sure whether they're allowed to.
Over time, those experiences affect trust.
I've found that people generally want to do good work. They want to know what's expected, feel capable in their roles, and understand how they're contributing.
When responsibilities are unclear, even strong employees can struggle.
And when responsibilities are clear, people have more room to develop confidence, solve problems, and take ownership of their work.
That doesn't mean everyone will agree on every decision or that conflict will disappear.
But it gives you a much healthier starting point for working through those situations together.
You don't have to be the person keeping track of everything.
If you regularly find yourself following up on unfinished tasks, answering questions about who should handle something, or stepping in when work gets missed, it may be worth looking at how responsibilities are defined in your practice.
Not just what's written in job descriptions.
How work actually gets done.
Where it moves between people.
And whether everyone understands what they're responsible for delivering.
Start with one process that's creating frustration.
Bring the people involved into the conversation. Clarify ownership, expectations, and handoffs. Make sure they have what they need to follow through.
Then give the new approach a chance to work