Direct Contracting Failure Patterns: How Good Ideas Go Sideways

Direct contracting has enough success stories now that it is easy to forget how often the model underperforms or fails quietly.

When you talk to employers, advisors, and providers who have lived through those failures, common patterns emerge.

They rarely involve some dramatic blow-up.

More often, good ideas erode slowly under the weight of weak design and misaligned incentives.

Here are the failure modes we see most often — and what they imply for buyers.

Failure Pattern 1: Great pricing, no steerage

On paper, the contract looks brilliant:

• Strong discount or attractive percent-of-Medicare rates
• Clear scope of services
• Named providers with good quality signals

In practice, almost no volume moves.

Why it happens:

• Members never really hear about the program.
• Navigation vendors treat it as an edge case.
• Benefit design is too flat to create a meaningful difference at the point of decision.

What it looks like in the data:

• Direct contract partners show up on a slide, not in the claims file.
• Savings are theoretical, not realized.

What to do differently:

• Design steerage and incentives at the same time you design the contract.
• Make someone explicitly accountable for funnel metrics.

Failure Pattern 2: Strong concept, weak data rights

The model makes sense: better economics and access in exchange for steerage and predictable payment.

But the employer cannot see what is actually happening.

Why it happens:

• Reporting language in the contract is vague.
• Data feeds are delayed, incomplete, or locked behind extra fees.
• The platform insists on being the sole interpreter of performance.

What it looks like in the data:

• Quarterly slide decks instead of usable feeds.
• Inability to reconcile savings claims against your own numbers.

What to do differently:

• Treat data rights as a first-class clause, not an afterthought.
• Specify file formats, fields, and frequencies in the contract.

Failure Pattern 3: Misaligned provider economics

Providers sign up for direct contracting for a reason.

If that reason does not hold in practice, enthusiasm fades.

Why it happens:

• Payment timing is slower than promised.
• Volume is lower than the business case implied.
• Administrative friction is higher than under traditional arrangements.

What it looks like in the relationship:

• Delayed responses to issues.
• Less willingness to expand scope or innovate.
• Quiet drift back toward legacy referral patterns.

What to do differently:

• Be realistic about steerage commitments.
• Make payment timing and dispute resolution mechanics visible and reliable.

Failure Pattern 4: Governance by neglect

No one explicitly decides to let the program decay.

It just does.

Why it happens:

• No clear owner at the employer beyond initial champions.
• No recurring review cadence with finance and providers.
• Competing priorities crowd out attention.

What it looks like over time:

• Dashboards and reports exist but no one acts on them.
• Small issues accumulate into structural frustration.
• The program becomes "something we tried a few years ago".

What to do differently:

• Establish a simple governance rhythm before launch (e.g., quarterly reviews with HR, finance, TPA, and providers).
• Give someone explicit accountability for the program P&L and experience.

Failure Pattern 5: Overreach on scope

Ambition outruns operational reality.

Why it happens:

• Employers try to redesign too many service lines at once.
• Contracts span geographies and populations that are hard to steer.
• Implementation teams are stretched thin across initiatives.

What it looks like:

• Implementation timelines slip repeatedly.
• Confusion among members and HR about when and how to use the program.
• A sense that the program is "always launching" but never fully live.

What to do differently:

• Start with one or two service lines and geographies.
• Treat Year One as a proving ground, not a full network replacement.

Failure Pattern 6: Miscommunication with employees

Even a well-designed program can feel threatening if it is explained poorly.

Why it happens:

• Communications emphasize savings more than member benefit.
• Changes are announced in dense, legalistic language.
• Exceptions policies are unclear.

What it looks like:

• Rumors that the employer is "cutting coverage".
• Frustration when members discover changes after they are already in care.

What to do differently:

• Lead with member-level advantages (lower bills, better access, clearer pathways).
• Use plain English and multiple channels.

The bottom line

Direct contracting does not usually fail because the basic idea is flawed.

It fails when pricing, steerage, data, operations, and communication are not designed as a single system.

If you understand these failure patterns up front, you can build your program with guardrails that make quiet erosion less likely — and make it easier to course-correct before a good idea dies on the vine.