Healthcare Is Paying Interest on Work It Never Retired
A healthcare organization introduces a new system. The expectation is clear: this will replace an older process, reduce manual work, and make the workflow easier. Six months later, the new system is live.
So is the old spreadsheet.
The manual report still gets produced. The email chain still exists. The meeting created to manage the previous problem is still on the calendar. Staff are now maintaining both the new process and parts of the old one because no one ever formally decided what should stop.
Nothing was intentionally retained. Nothing was intentionally retired either. So the organization carries both.
At Living with SHAPE, we believe this pattern helps explain an important part of healthcare administrative burden. Organizations constantly create new processes, technologies, reporting requirements, workarounds, committees, and workflows. But the arrival of something new does not automatically remove what came before it.
Over time, that accumulation creates what we might think of as organizational debt. Like technical debt, organizational debt is the cost of carrying old structures, processes, and requirements forward after their original value has weakened or disappeared. And every piece of outdated work that remains in place keeps charging the workforce interest.
Healthcare Is Very Good at Adding
New work usually arrives for legitimate reasons.
A regulation changes
A safety concern appears
A technology implementation begins
A leader needs better visibility
A temporary workaround is created
A quality initiative launches
A new reporting requirement is introduced
In the moment, adding something often makes sense. The challenge is that many organizations have stronger processes for beginning work than ending it.
There is a project plan for implementation, but no retirement plan for what the implementation should replace. There is a launch meeting for the new workflow, but no future date when the old workflow will be reviewed. There is clarity about who owns the new requirement, but less clarity about who is authorized to stop the previous one.
That imbalance matters. If the organization keeps adding while rarely removing, even good ideas begin to compete with the weight of everything already in place. This connects directly to When Everything Is a Priority, Healthcare Loses the Ability to Prioritize. A new priority does not enter an empty organization. It enters a system already carrying years of accumulated work.
The more old work that remains, the harder every new priority becomes to absorb.
Temporary Work Has a Way of Becoming Permanent
Some of the most persistent organizational debt begins as a temporary solution. A spreadsheet is created to bridge a technology gap for three months. Three years later, people are still updating it. A meeting is created during implementation to resolve issues quickly. The implementation ends, but the meeting remains. A manual check is added because a system cannot yet perform a task reliably. The technology improves, but the check continues because no one has formally removed it. A report is created for a specific leader or decision. Years later, the report still gets produced even though no one is sure who reads it.
Individually, these activities can seem too small to matter. Collectively, they consume real time and attention. This is part of what makes organizational debt difficult to see. The burden is often distributed across dozens or hundreds of small tasks rather than concentrated in one obviously broken process.
Ten minutes here.
Thirty minutes there.
One extra meeting each month.
One duplicate entry.
One manual reconciliation.
One report that still has to be prepared.
The work becomes normal because people have been doing it for so long. But normal does not necessarily mean necessary.
Organizational Debt Charges Interest
The cost of old work is not limited to the time required to perform it. Each additional layer makes the organization harder to operate. Employees have more processes to remember. They maintain duplicate information. They reconcile differences between old and new systems. They attend meetings created by previous initiatives. They learn exceptions that exist only because earlier workflows were never fully retired.
This is where the idea of “interest” becomes useful. Old work does not simply remain static. It increases the cost of future work.
A new employee has more processes to learn
A new technology has more legacy requirements to accommodate
A new initiative has to navigate additional committees, reports, workarounds, and dependencies
A manager has to explain why the official workflow says one thing while the team still does something else
In The Hidden Cost of Healthcare Workarounds, we explored how temporary adaptations can become permanent dependencies. Organizational debt is what happens when those dependencies accumulate across the system.
Yesterday’s fix becomes today’s routine. Today’s routine becomes tomorrow’s constraint.
The organization is no longer only carrying the original task. It is carrying the history around it.
Some Healthcare Complexity Is Historical, Not Necessary
Healthcare is genuinely complex. Clinical care, regulation, reimbursement, privacy, safety, technology, workforce structures, and organizational responsibilities all create complexity that cannot simply be designed away. But not every complicated process exists because healthcare itself is inherently complicated.
Some complexity is historical.
A step exists because it was needed when an older system was in place
A meeting exists because a problem once required close coordination
A manual check exists because a technology used to be unreliable
A report exists because someone needed it five years ago
A workflow contains extra approvals because of an issue that may no longer exist.
Over time, these decisions stack on top of one another until the current process becomes difficult to explain. That creates a useful question: If we were designing this process today, would we still build it this way?
If the answer is no, history may be consuming present-day capacity. This does not mean old processes are automatically bad. It means they should not be protected simply because they are familiar. Past usefulness should not become permanent justification.
Retirement Should Be Part of Implementation
Healthcare transformation often focuses heavily on what needs to begin.
What new technology needs to launch?
What new process needs to be adopted?
What new metric needs to be tracked?
What new capability needs to be built?
A stronger implementation discipline also asks: What should this allow us to stop? Every major implementation should include a retirement conversation.
Which old workflow disappears?
Which manual step should no longer be required?
Which report can end?
Which duplicate documentation can be removed?
Which workaround should become unnecessary?
Which meeting no longer serves a purpose once the new process is stable?
This is the operational counterpart to the prioritization question we raised in the previous blog. If something new truly matters, leaders should not only ask where the capacity to add it will come from. They should also ask what the new capability makes possible to remove.
Otherwise, transformation does not replace old work. It layers over it. And the organization becomes more complicated with every attempt to improve.
Simplification Is a Capacity Strategy
Simplification is sometimes treated as administrative housekeeping. Something organizations get to once the “real work” is done. But simplifying old work is strategic because it gives capacity back.
Removing an unnecessary report returns time.
Ending a redundant meeting returns attention.
Eliminating duplicate documentation reduces cognitive load.
Retiring a manual reconciliation step makes a workflow easier to learn.
Clarifying which process is now authoritative reduces confusion.
That recovered capacity can be used for work the organization actually wants to improve. This connects to The Work Healthcare Keeps Adding Without Taking Anything Away. Workforce capacity is not created only by hiring more people or asking existing employees to become more efficient.
Sometimes capacity is created by asking people to carry less unnecessary work. There is a major difference between telling employees to do more with less and intentionally removing work that no longer creates enough value to justify the effort it consumes.
The first extracts capacity. The second restores it.
Existing Work Should Have to Keep Earning Its Place
One reason organizational debt persists is that new work is often evaluated more rigorously than existing work. A new program may require a business case. A new technology may require approval. A new position may require justification.
But an old meeting can remain indefinitely simply because it is already scheduled. An old report can continue because nobody has asked whether it still matters. An outdated step can survive because removing it requires a decision while leaving it alone requires none. That creates an asymmetry.
New work has to prove that it deserves capacity. Old work gets to keep consuming capacity by default.
Healthcare organizations can reverse that pattern by periodically asking existing work to justify its place.
Does this still reduce risk?
Does this information still influence a decision?
Does this meeting still require everyone currently attending?
Does this manual step still add value?
Does this report still have a clear audience?
Does this workflow still reflect how the organization wants work to happen?
The purpose is not indiscriminate cutting. Some existing work is essential precisely because it protects safety, reliability, compliance, or quality.
The point is simpler: Not all existing work is unnecessary. But all existing work should periodically have to justify the capacity it consumes.
A Practical Leadership Practice: The Organizational Debt Review
Choose one recurring workflow, report, meeting, committee, or manual process that has existed long enough that few people remember why it started. Then examine it with fresh eyes.
First, ask what purpose the work originally served. Was it created because of a temporary implementation, a technology limitation, a regulatory need, a specific leader request, or a past operational problem?
Next, ask whether that original condition still exists.
Then look at the full cost of maintaining the work today. Include preparation time, attendance, duplicate documentation, follow-up, reconciliation, and the cognitive effort required to remember the process.
Finally, ask three questions:
What value does this still create?
What would actually happen if we stopped doing it?
If the work is still necessary, could it be simpler now?
The point is not to eliminate something simply because it is old. It is to make continuation a decision rather than an assumption. One retired meeting will not transform organizational capacity. But the discipline of regularly retiring outdated work can prevent years of accumulation from becoming permanent.
Regenerative Psychology™ and Organizational Renewal
Regenerative Psychology™ asks whether systems renew the resources they depend on.
Organizations depend on human attention, time, judgment, energy, and implementation capacity. Those resources are finite.
An organization that continuously adds work without removing what no longer serves it gradually consumes the capacity required for future improvement.
A regenerative organization therefore does more than build. It also lets go. It periodically asks: What are we still carrying that no longer strengthens the system?
That question is not about efficiency for efficiency’s sake. It is about renewal. Healthy systems need the ability to stop, simplify, retire, and reorganize as conditions change. Letting go can be just as important as building something new.
Progress Sometimes Starts With Subtraction
Healthcare will always need new capabilities. The question is whether every new capability has to sit on top of everything that came before it.
Organizations cannot create unlimited capacity. But they can recover some of the capacity already buried underneath outdated processes, duplicate work, temporary fixes, standing meetings, manual checks, and requirements that have outlived their purpose.
That recovered capacity matters because it creates room for what comes next. For healthcare leaders, a useful place to begin is one recurring piece of work and one simple question: If we stopped doing this tomorrow, what would actually happen?
If the answer is clear and consequential, the work may still deserve its place.
If nobody is quite sure, that may be exactly where the next capacity conversation should begin.
Sometimes progress starts by building something new. And sometimes it starts by finally deciding what the organization is ready to stop carrying.
Comments