Healthcare Runs on Duct Tape and Exit Interviews

By Fawad Butt | CEO & Co-Founder, Penguin Ai

I once sat in a meeting where an ops director presented a 14-slide deck showing that a single prior authorization workflow was costing her organization $2.3 million a year in rework alone. She had the root cause. She had the fix. She had the implementation timeline.

The room nodded. Leadership thanked her for the thorough analysis. Then they moved to the next agenda item.

Six months later, the workflow was untouched. She'd built two new workarounds to keep it from collapsing entirely. A year after that, she left the organization.

Nobody failed here. That's the terrifying part. Everyone in that room was doing their job inside a system that punishes the act of fixing things more than it punishes the cost of leaving them broken.

This is healthcare administration in 2026. And we need to talk about it.

They See Everything. They Control Nothing.

Your ops team can tell you, right now, which prior authorization workflows are broken. Which claims keep bouncing back for the same preventable reasons. Which manual processes could be automated tomorrow. Which workarounds have quietly become the actual infrastructure holding your operation together.

They know because they live it. Not in dashboards. Not in quarterly reviews. In the queue. Every day. Every rework cycle. Every "we've escalated your request" email that means absolutely nothing.

They've built spreadsheets documenting the dysfunction. They've proposed fixes. They've been told: "We hear you, but the timing isn't right." Or: "That would require a system change." Or the classic: "Let's revisit this next quarter."

Next quarter never comes. Everyone knows next quarter never comes. We say it anyway.

Let's stop pretending that's acceptable.

The Workaround Economy

So ops teams do what brilliant people always do inside broken systems. They adapt. They compensate. They perform daily miracles holding together workflows that should have been rebuilt years ago.

A manual review process layered on top of a failing automated one. A shared spreadsheet that became the unofficial source of truth because the actual system can't be trusted. A senior team member who is now the only human being on earth who understands a critical workflow because the documentation doesn't exist and the vendor won't help.

I call this institutional scar tissue. It accumulates silently. Layer by layer. Each workaround is rational in isolation. In aggregate, they create a system so fragile that no one dares touch it, and so complex that no one fully understands it.

And somewhere in a board deck, this gets labeled "operational maturity."

That's not maturity. That's an organization running on duct tape and institutional memory, one retirement away from catastrophe.

The Accountability Inversion

Here's what keeps me up at night.

Ops teams own the metrics. Processing times. Error rates. Staffing ratios. Throughput. They are measured, managed, and held accountable for outcomes they produce using tools they didn't choose, inside processes they didn't design, constrained by systems they aren't allowed to change.

But the people who designed those processes weren't building dysfunction on purpose either. They were solving a different problem in a different decade with different technology. And the leaders who inherited it all? They're navigating legacy contracts, regulatory complexity, vendor lock-in, and budget cycles that make meaningful change feel like pushing a boulder uphill in a hurricane.

Nobody is the villain. That's what makes this so hard.

The system distributes the pain downward and the power upward and gives neither group the tools to close the gap. Ops teams drown in the consequences. Leaders drown in the constraints. And patients drown in the middle, waiting for a system that isn't designed to move at the speed they need.

We've built an accountability structure where everyone is responsible and no one is empowered. That's not governance. That's paralysis with a reporting structure.

‍

Why This Persists

Because the patchwork has become the product.

Nobody designed healthcare administration to work this way. It accumulated this way. One regulatory change layered on top of a legacy system. One vendor integration bolted onto a workflow that was supposed to be temporary. One workaround built to survive a quarter that became permanent infrastructure for a decade.

Multiply that by twenty years across thousands of organizations. What you get is an industry where nobody chose the current state of things, nobody can fully explain it, and everyone is trapped inside it.

Changing a core workflow means touching a legacy system, which means a vendor negotiation, which means an IT project, which means a budget cycle, which means executive sponsorship, which means a committee. By the time all those gates are cleared, ops has already built three new workarounds and the original problem has mutated into something the proposed fix no longer addresses.

So the cycle continues. The organization mistakes the absence of collapse for the presence of health. It calls survival "stability."

It's not stability. It's stagnation. And someone is paying for it right now. A patient waiting for an authorization. A nurse spending 90 minutes documenting what she already knows. A coder grinding through the 87th straightforward case knowing there are 43 more before lunch.

That's not inefficiency. That's harm. Antiquated. Scaled. Normalized.

The Billion-Dollar Coat of Paint

Meanwhile, the industry keeps buying solutions that solve nothing.

Better dashboards. Smarter alerts. AI copilots that help humans do broken work 15% faster. Another vendor promising transformation while delivering a slightly shinier version of the status quo.

Let's be honest about what these tools actually do. They make the patchwork more visible. They make the dysfunction more measurable. They give ops teams prettier interfaces to manage the same impossible workload.

The work still exists. The burden remains. The patients still wait. But now there's a dashboard tracking how long they wait, so we can all feel informed about the problem we're choosing not to solve.

10% faster prior auths is 10% less waiting. Still waiting. 20% reduction in manual coding is 20% less burden. Still burdened. Incremental improvement of a fundamentally broken architecture is just slower failure with better reporting.

That's not progress. That's the patchwork getting another layer.

The Question Nobody Is Asking

Everyone is asking how to make ops teams more efficient. How to reduce processing times. How to optimize. How to do more with less.

Nobody is asking why the work exists in the first place.

Why does an experienced coder manually review straightforward cases that follow a clear, repeatable pattern? Why does a prior authorization for a routine procedure take days when the clinical evidence is unambiguous? Why does an appeal require a human to re-read the same documentation that was already submitted, already reviewed, already sufficient?

The answer is almost always the same: because that's how the process was built. Years ago. For a different era. Before technology existed that could handle structured, rules-based, high-volume decision-making autonomously.

The workflows haven't changed because the system makes changing them harder than enduring them. Not for any one person. For everyone.

That's the trap. The people closest to the pain can't change the system. The people who can change the system don't feel the pain at the same frequency. And the system itself has evolved to resist change from any direction, at any level, for any reason.

What Everyone in This System Deserves

Ops teams deserve to stop being the absorption layer for twenty years of accumulated patchwork. They deserve to spend their expertise on cases that actually require human judgment, empathy, and clinical reasoning. Not on work that insults their intelligence and wastes their training.

Leadership deserves the ability to act on what they already know is broken without navigating a twelve-month obstacle course of legacy dependencies just to change a single workflow.

Patients deserve healthcare that responds at the speed of human need, not at the speed of bureaucratic convenience.

Because here's what I know after years of living inside this system. The knowledge to fix healthcare administration already exists. It lives at every level of every payer and provider organization in the country. Ops teams carry it in their spreadsheets and process notes. Leaders carry it in the strategic plans they can't execute fast enough. Everyone sees the problem. Everyone knows what needs to change.

The problem was never a lack of insight. Never a lack of will. It's an architecture that makes change slower than the pain it's supposed to address. A system where the cost of fixing things always feels higher than the cost of enduring them, until one day it isn't, and by then the damage is done.

That's the thing that has to break. And it's not going to break incrementally.