MANAGED CARE OPERATIONS
When the Workaround Becomes the Process
How hidden workarounds, repeated corrections, and compensating effort become accepted operating infrastructure
A perspective from Gentry Consulting
published October 2026
An organization may be achieving the reported result while absorbing substantial hidden effort to make that result possible.
Introduction
The file was delivered. The claim was processed. The directory was published. The service level was met. The report was completed. From the leadership perspective, the process appears to be working.
But the visible output may tell only part of the story.
Behind that completed result may be spreadsheets maintained outside the primary system, fields that experienced employees know not to trust, recurring corrections performed before every submission, informal rules passed from one employee to another, and reconciliations needed because two systems define the same information differently.
None of this necessarily indicates that the organization lacks capable people. Frequently, it indicates the opposite. Employees and functional leaders have become highly effective at responding to the conditions they face. They have created ways to keep the work moving despite weaknesses in information, systems, definitions, ownership, or process.
Over time, however, reliable compensation can conceal the condition being compensated for.
An organization can become highly capable at managing a problem it should no longer have.
When Adaptation Becomes Normal
Many workarounds begin for a practical reason.
A system does not contain a required field, so a team creates a spreadsheet. A source file arrives with inconsistent values, so someone develops a correction routine. Two departments use different definitions, so an experienced employee interprets the differences. A vendor feed produces recurring exceptions, so operations establishes a queue to resolve them.
Each response may be entirely rational. It solves an immediate problem without waiting for a larger organizational decision.
The risk emerges when the temporary response succeeds.
Once the spreadsheet is dependable, the exception queue is staffed, or the local interpretation becomes familiar, the underlying weakness becomes less urgent. Work continues. Deadlines are met. The adaptation becomes part of training, staffing, planning, and normal production.
Eventually, the workaround may no longer be recognized as a workaround. It is simply “how the process works.”
This normalization can happen without a formal decision. No one necessarily approves permanent dependence on manual corrections or local knowledge. The organization gradually adapts around the condition until changing it appears more disruptive than continuing to compensate for it.
The organization has not ignored the problem. It has absorbed it.
An organization can become highly capable at managing a problem it should no longer have.
Why Leadership May Not See the Condition
Leadership reporting generally answers an important question: Was the expected output produced?
It may show whether transactions were completed, files were transmitted, regulatory or contractual deadlines were met, service levels were maintained, or financial results fell within an expected range.
Those measures matter. But they do not always show what it took to produce the result.
A report may confirm that a monthly file was delivered without showing how many errors were manually corrected before submission. A dashboard may show that claims were processed without identifying the reconciliation performed across contracting, configuration, provider data, and payment operations. A directory may be published on schedule even though several teams repeatedly adjusted conflicting source information to make publication possible.
The reporting layer captures the outcome. The compensating work remains distributed among the people and functions producing it.
That distribution is especially important in managed-care environments. Outcomes frequently depend on several functions, systems, vendors, external organizations, and accountability structures. Each participant may see only the corrections within its responsibility. No single function necessarily sees the total effort or recognizes that several teams are compensating for different effects of the same underlying condition.
Everyone may be completing assigned work while leadership still lacks a coherent view of how the result is being produced.
This is not leadership negligence. It is a visibility problem created by reporting and accountability structures that show outputs more readily than adaptations.
The Possible Cost of an Acceptable Result
Hidden operational friction does not usually appear as one clean financial line item.
Its possible effects may be spread across manual maintenance, rework, exception handling, implementation delays, provider or member service activity, vendor expense, compliance review, payment recovery, management escalation, and technology built to cleanse or transform information before it can be used.
The consequence is not limited to labor efficiency.
Recurring compensation can consume capacity that might otherwise support more consequential work. It can delay decisions because information must first be reconciled. It can create dependence on employees who hold critical local knowledge but no formal ownership of the underlying condition. It may contribute to provider or member abrasion when internal inconsistencies become visible through incorrect information, repeated outreach, or avoidable service problems.
It can also distort investment decisions.
When leadership sees an unacceptable result but not the compensating structure beneath it, the next response may be another interface, vendor, technology implementation, resource request, or control. That investment may improve the organization’s ability to manage the friction without addressing what creates it.
Healthcare can mistake the automation of friction for the elimination of friction.
Information may move more efficiently between systems while still requiring recurring correction, reinterpretation, or exception handling. Technical interoperability establishes that information can be exchanged. It does not, by itself, establish that the information is current, consistently defined, attributable to an accountable source, or appropriate for the receiving workflow.
The issue is not that technology lacks value. The question is whether an investment removes the underlying condition or makes the organization more efficient at compensating for it.
Healthcare can mistake the automation of friction for the elimination of friction.
Necessary Complexity or Accepted Friction?
Healthcare is complex for legitimate reasons.
Regulatory requirements, contractual obligations, clinical differences, product structures, privacy protections, financial controls, and varied organizational relationships all create work that cannot simply be removed. Some apparent friction protects an important control or accommodates a meaningful difference.
The goal should not be to label every manual step, exception, or local decision as waste.
A better distinction is between necessary complexity and accepted friction.
Necessary complexity exists because the work requires it. Accepted friction exists when recurring effort compensates for a weakness that may be avoidable, such as unclear definitions, fragmented ownership, unreliable source information, redundant correction, misaligned processes, or technology layered over an unresolved operating condition.
The distinction cannot always be made from a dashboard. It requires understanding why the work exists and what would happen if it stopped.
A manual review that protects a meaningful financial or regulatory control may be necessary. A manual review that repeatedly repairs a preventable source defect presents a different leadership question.
The issue is not whether the work is manual. The issue is whether the work continues to serve a necessary purpose or merely enables the organization to live with a condition it no longer needs to accept.
A Representative Provider-Data Scenario
Consider a representative scenario combining recurring provider-data patterns observed across healthcare operations.
A health plan receives monthly provider rosters from several healthcare organizations. The files arrive on schedule and contain the information expected under the existing process. The participating organizations are capable, sophisticated institutions, and the employees producing and receiving the files understand their responsibilities.
Yet the files do not begin from a single operational truth.
A staffing or scheduling system may identify where a practitioner can be assigned, but that does not necessarily establish where the practitioner routinely sees patients, participates in a particular product, accepts new patients, or should appear in a member-facing directory.
Other functions supplement the data with credentialing, contracting, billing, network, or directory information. Records may be manually adjusted for a payer’s requirements. The payer may then correct or transform the information again before using it in downstream systems. An aggregator or interoperability platform may later normalize another version.
Every participant may be acting reasonably for its own purpose. The reported outputs may still be produced. The roster is transmitted, the data is loaded, and the directory is published.
But beneath those outputs, employees repeatedly reconcile definitions, remove formatting artifacts, interpret notation, resolve conflicting affiliations, and determine which version of a fact is appropriate for a particular use. The data moves, in part, because human and technological compensation makes movement possible.
The leadership concern is not merely whether the monthly roster was delivered or the directory published. It is whether the organization understands the recurring effort required to produce those outcomes, why that effort remains necessary, and whether further technology will remove the underlying condition or automate another layer of compensation.
Provider data is only one example. Similar patterns can emerge wherever multiple functions or organizations repeatedly reinterpret, correct, or reconcile information to produce an expected managed-care result.
What Leadership Should Ask
The first step is not a broad organizational assessment. It is recognition.
Leadership can begin with a small number of questions:
What recurring work exists only to compensate for another condition?
What workaround has become so dependable that it is now treated as part of the process?
Which reported outcomes depend on manual correction, local knowledge, private spreadsheets, or repeated reconciliation?
Where is the same information corrected more than once?
What condition is no longer escalated because everyone already knows about it?
Has technology removed the friction, or has it automated the compensation?
What is the smallest meaningful intervention that could test whether the condition can be improved?
These questions should not be used to search for individual fault. They should help leadership understand how the organization is actually producing an important result.
Capable people may be making entirely reasonable decisions within their responsibilities. The leadership opportunity is to determine whether those individually reasonable adaptations have collectively created an operating condition the organization would not deliberately design today.
Make One Condition Visible
Operational friction is easy to acknowledge in the abstract and difficult to address as an enterprise-wide idea.
That is why the starting point matters.
Leadership does not need to identify every workaround, calculate the total burden of accumulated complexity, or launch a broad transformation effort. It can begin with one recurring concern, one workflow, one output, or one source of repeated correction.
The objective is to understand the triggering condition, the work performed to compensate for it, the functions and systems involved, the possible downstream consequences, and why the workaround persists. The condition should be made visible without overstating precision and without presuming that every adaptation can or should be eliminated.
That visibility can support a practical decision.
The organization may determine that the complexity is necessary and the current control remains reasonable. It may clarify a definition, assign responsibility for one category of information, improve validation at the source, change a reporting measure, retire a redundant correction, or test whether two functions can resolve a recurring issue together rather than separately.
Or leadership may decide that the workaround remains the most practical response for now.
The important difference is that the organization is making a conscious decision rather than allowing an inherited adaptation to remain invisible.
The first step is not eliminating every source of operational friction. It is making one hidden condition visible enough for leadership to decide whether continuing to live with it is still the rational choice.
The important difference is that the organization is making a conscious decision rather than allowing an inherited adaptation to remain invisible.
