Dr. Douglas Won: Why MSO Strategy Fails Without Systems Thinking
- drdouglassungwon
- Feb 1
- 3 min read
By Dr. Douglas Sung Won, MD
MSO strategy has become one of the most discussed - and most misunderstood - concepts in modern healthcare.
On paper, Management Services Organizations promise alignment. They offer scale, operational efficiency, centralized services, and economic leverage. In practice, many MSOs struggle to deliver on those promises. The problem is not the MSO model itself. The problem is how it is conceived.
Most MSOs are built as administrative overlays rather than as systems.
They centralize functions without redesigning flow. They aggregate practices without architecting coherence. They standardize operations without addressing structural friction. What emerges is not a unified system, but a collection of entities sharing back-office services.
That is not systems thinking.
The Difference Between Management and Architecture
Management optimizes what already exists. Architecture determines what exists in the first place.
An MSO designed without systems architecture becomes a patchwork. Each practice retains its own logic, incentives, and clinical rhythms. The MSO attempts to impose efficiency from above, while complexity continues to grow beneath it.
This is why MSO leaders often feel like they are pushing water uphill.
The question I always ask is not, “What services will the MSO provide?” It is, “What system is the MSO creating?”
Those are fundamentally different questions.
Why Fragmentation Persists Inside MSOs
Healthcare organizations often believe that centralization equals integration. It does not.
Centralizing payroll, billing, compliance, or marketing does nothing to address:
Clinical decision flow
Referral architecture
Information propagation
Accountability across episodes of care
Incentive alignment between operators and enterprise
Without addressing these elements, the MSO becomes a cost center rather than a strategic engine.
This is why many MSOs plateau.
They manage complexity instead of eliminating it.
Systems Thinking Changes the Equation
When MSO strategy is approached architecturally, everything shifts.
The MSO becomes the operating system for care—not merely a service provider.
That means designing:
How patients move across practices
How data flows longitudinally rather than episodically
How authority is distributed and escalated
How incentives reinforce continuity rather than throughput
How growth preserves identity rather than diluting it
In this model, the MSO does not sit above the practices. It connects them.
It creates coherence where fragmentation once lived.
Lessons From Building Integrated Systems
When I built vertically integrated healthcare ecosystems, including at Lumin Health, MSO-like functions were embedded into the architecture from the start.
We did not ask, “How do we manage these assets?” We asked, “How should this system behave?”
That distinction matters.
Behavior emerges from structure. If you design structure poorly, behavior becomes unpredictable. If you design it well, excellence becomes repeatable.
This is the difference between growth that fractures and growth that compounds.
The Strategic Role of the MSO
The future MSO will not be judged by how many services it provides.
It will be judged by:
How much friction it removes
How much latency it compresses
How clearly it defines accountability
How well it aligns incentives across time
In other words, by how well it functions as architecture.
As Dr. Douglas Sung Won, MD, my advisory work consistently returns to this principle: MSO strategy is not a financial construct. It is a systems design problem.
Solve it architecturally, and scale becomes sustainable.
Ignore structure, and complexity will eventually win.
Get to know me a little more here:
Comments