For a period of time, we kept encountering variations of the same operational problems.
A treatment room would not be fully ready.
An instrument would be unavailable when it was needed.
A doctor’s insurance pre-approval would still be pending.
Documentation or another administrative responsibility would require last-minute follow-up.
Each incident appeared to have a simple explanation.
Someone forgot.
Someone assumed another person was handling it.
The schedule changed.
The team became busy.
A reminder was missed.
So we responded to each incident individually.
We found the missing instrument, asked someone to complete the follow-up, rearranged the available coverage, reminded the team of their responsibilities and continued with the day.
The immediate problem was contained.
Then another version of it returned.
We were treating predictable outcomes as isolated incidents
When a problem happens once, it may genuinely be an exception.
When it continues happening, leadership must stop examining only the latest incident.
The more important question becomes:
What is the current operating model designed to produce?
In our case, we had more active rooms than nurses available to take stable ownership of them.
Nurses had to move between rooms, doctors and responsibilities according to the immediate needs of the day.
This created shared coverage, but it weakened individual ownership.
If several people could potentially follow up on a doctor’s approval, schedule, documentation or instruments, no single person carried complete responsibility for making sure it happened.
Everyone was helping.
No one fully owned the outcome.
The recurring problems were not surprising failures inside a well-designed structure.
They were predictable outputs of the structure itself.
The problem was larger than individual performance
It would have been easy to conclude that the team needed to become more organized.
That may have been partly true.
But asking people to “pay more attention” would not resolve the mismatch between capacity and responsibility.
Employees cannot maintain consistent ownership when ownership constantly moves.
A nurse covering different rooms and doctors throughout the day must repeatedly rebuild context:
- What does this doctor need?
- Which pre-approval is pending?
- What is tomorrow’s schedule?
- Which instruments must be prepared?
- What documentation remains incomplete?
- Where did the previous person stop?
Every transfer creates an opportunity for information to be delayed, misunderstood or lost.
The organization then experiences the consequences as individual mistakes.
But many of those mistakes begin with structural ambiguity.
This is an important leadership distinction.
Not every performance problem is caused by an employee refusing to take responsibility.
Sometimes the operating model has made responsibility difficult to locate.
We began redesigning around ownership
We started adding more nurses, working toward a capacity in which every operational room could have a nurse assigned to it.
But hiring additional people was not the full solution.
More people inside the same ambiguous structure would only create more ambiguity.
The important change was connecting capacity to ownership.
As nurses became consistently assigned to rooms and doctors, their responsibilities became clearer.
Each nurse could smoothly follow up on:
- The doctors assigned to the room
- Required approvals
- The upcoming schedule
- Documentation
- Instrument preparation
- Outstanding clinical and administrative requirements
Instead of reconstructing the situation every day, the assigned nurse retained the context.
Instead of assuming that someone else might follow up, there was a clear owner.
As ownership became stable, accountability became fairer, and execution became smoother.
Accountability requires an address
Leaders often demand accountability before designing where that accountability should live.
They tell teams to communicate better, cooperate more closely and take greater ownership.
But ownership requires boundaries.
A person must know:
- Which outcome belongs to them
- Which resources they control
- Which information they must monitor
- Which decisions they may make
- Which problems they must escalate
- How their performance will be evaluated
Without those boundaries, accountability becomes a general expectation directed at everyone.
And when accountability belongs to everyone, failures can always be explained as someone else’s responsibility.
A system needs an address.
When something is incomplete, leadership should be able to identify the role responsible for ensuring completion, not merely the person who happened to be nearby when the problem became visible.
The principle extends beyond healthcare
The same pattern appears across industries.
A sales lead is handled by several employees, but no one owns it from enquiry to conversion.
A customer complaint passes through different departments, but no one owns the final resolution.
A project has many contributors, but no individual is accountable for the deadline.
A branch has several supervisors, but standards vary according to who is present.
A purchasing request moves between operations, finance and management, but no one owns its progress through the complete approval cycle.
In each case, management may continue resolving incidents:
- Chasing the lead
- Answering the complaint
- Extending the deadline
- Correcting the branch
- Following up on the purchase
But solving today’s incident does not change what the system will produce tomorrow.
Five questions for recurring problems
1. Is there one identifiable owner?
Contributors can be shared. Final ownership should not be.
2. Does capacity match the responsibility?
Assigning ownership without adequate time, staffing or resources merely creates a person to blame.
3. Is the expected outcome clearly defined?
People cannot reliably own vague expectations.
4. Can the owner see and control the necessary information?
Responsibility without visibility or authority creates frustration, not accountability.
5. What structural change will prevent recurrence?
A reminder may prevent the next incident.
A redesigned system should prevent the pattern.
From reaction to design
Leadership is not demonstrated by how quickly we rescue the organization from recurring problems.
It is demonstrated by whether we eventually make those rescues unnecessary.
The first incident requires a response.
The second requires comparison.
By the third, leadership should be examining the system.
Because once a pattern becomes visible, continuing to treat every occurrence as an isolated mistake is no longer an operational issue.
It is a leadership decision.