Table of Contents

A recurring situation: billing says the problem is scheduling, scheduling says the problem is billing, and both descriptions are accurate. Each team can point to real evidence. Neither is being evasive.

This note sets out why that configuration is common, why it resists the usual approaches, and which questions tend to resolve it quickly.

Why the handoff is invisible

Departments are measured on what happens inside them. A scheduling team is assessed on fill rate and time-to-book. A billing team is assessed on days in receivable and denial rate. Both sets of measures are reasonable and both are bounded by the department.

The transfer between them is usually measured by nobody. It has no owner, no metric, and no meeting. It exists as an assumption on each side about what the other side will do with what it receives.

This produces a specific and consistent failure mode. Each department optimizes to its own measure, and a locally rational optimization degrades the handoff. Scheduling books more appointments faster, which is exactly what it is asked to do, and captures slightly less information at intake because capture takes time. Billing then works from incomplete records, which raises denials, which is billing’s problem to explain. Both teams are performing well against their own targets. The organization is performing worse.

The general shape of this, that optimizing components separately does not optimize the system and can actively harm it, is old and well established in operations and systems thinking. What is worth adding is how reliably it hides. Neither team can see it, because for each of them the failure appears at the other end.

What surfaces it

A few questions have been consistently more productive than a general process review.

Ask each side what they assume the other does. Not what the process document says. What they believe happens. Divergence here is common, and the size of the divergence is roughly proportional to how long the handoff has been unowned.

Follow one unit of work end to end. One patient, one order, one candidate. Not a sample, not an average, but a single case, traced across every system and person it touches. Aggregate reporting is specifically bad at revealing handoff failures because each department’s aggregate looks acceptable. The failure is visible in the trace and invisible in the summary.

Ask what people do when the handoff fails. There is almost always an informal workaround: a side spreadsheet, a standing phone call, one person who reconciles things manually. Locating the workaround locates the break. It is also, usually, the cheapest available description of what the fix needs to accomplish.

Ask who would be told if it broke entirely. If nobody can answer, the handoff has no owner, which is the underlying condition.

Why industry expertise can miss it

Deep domain experience is the right thing to hire for most problems. Someone who has billed a particular payer for a decade will beat a generalist on payer behavior, decisively.

Domain expertise is weaker on this specific class of problem, for a structural reason: expertise is generally acquired within a function. A billing expert has seen many billing operations and comparatively few scheduling operations. Their pattern library is deep in one column and thin across the row.

Someone who has watched the same handoff fail in a warehouse, a recruiting pipeline, and a clinic is not more knowledgeable about any of those industries. They are, specifically, faster at recognizing the shape. That is a narrow advantage and it is worth being precise about how narrow it is. It applies to problems that sit between functions. It does not apply to problems that sit inside one.

Limitations

The obvious risk in a heuristic like this is that it makes every problem look like a handoff problem. Plenty of problems are not. Sometimes billing really is the issue, the process is fine, and the answer is training or headcount.

The check is whether both sides independently report a problem they attribute to the other. If only one side is complaining, this pattern probably does not apply, and reaching for it will waste time that should be spent inside the department that actually has the problem.