Clarity over Complexity
Preventing Platform Strain
After more than twenty years inside healthcare operations, I have learned that most organizations do not struggle because the strategy is impossible. They struggle because the execution gap between what was planned and what actually happens in the building never fully closes.
This manual is built around a simple idea: clarity over complexity. Healthcare operations are complex, but the game plan does not always need to be. Each section focuses on a common challenge inside PE-backed platforms, specialty groups, and multi-site healthcare organizations. The goal is to identify the real issue, understand what is driving it, and create a practical path forward.
The manual is built from real operating experience, recent conversations, and the kinds of questions that come up when leaders are trying to scale, stabilize, integrate, or improve a healthcare organization.
The point is not to make healthcare operations more complicated. The point is to help the right people see clearly, align quickly, and move forward.
How PE-Backed Healthcare Platforms Actually Break
The failure modes in PE-backed healthcare are not usually dramatic. They are slow, quiet, and almost entirely predictable if you know what to look for. Most platforms do not implode in a single event. They erode through a series of small execution failures that compound until the organization is running on reputation debt instead of operational strength. By the time the data catches up, the damage is already months old.
The Leadership Vacuum After Close
When a practice is acquired, the original operational owner, often a physician or practice manager who built something from the ground up, steps back or steps out. What follows is a leadership vacuum that is routinely underestimated. The platform assumes continuity because the staff are still there. But continuity of staff is not continuity of leadership.
Day-to-day decisions that previously happened through relationship and institutional memory now happen through uncertainty and upward escalation. The organization has not lost its people. It has lost its operating nerve center, and no one has replaced it yet.
The Integration Calendar vs. The Operating Reality
Most integration timelines are built by deal teams, not operators. They reflect what needs to happen legally and financially, not what needs to happen operationally. The result is a calendar that closes the books on integration long before the organization is actually integrated.
Physicians are still waiting for answers. Workflows have not been mapped. The EHR conversion is behind. The platform has already moved to the next acquisition. Integration, by every relevant measure, has not happened. But the calendar says it has.
Performance Pressure Before Stability
PE-backed healthcare moves fast. That is part of the model. But applying performance pressure to an organization that has not yet stabilized is one of the most reliable ways to accelerate the erosion of what you just paid for. Revenue cycle disruption, staff turnover, and physician dissatisfaction tend to peak in the nine to eighteen months after close, precisely when the platform is most exposed.
The instinct to press for performance is understandable. The organizations that come through integration strongest are the ones that sequenced it correctly: stabilize first, then optimize, then scale.
The Data Gap
Most acquired practices have reporting structures built for a single-site operation, not a platform. EBITDA looks fine until it does not. By the time the data shows a problem, the operational conditions that created it are already months in the past.
Platforms that build operational intelligence early, that develop the ability to see what is actually happening at the site level, give themselves a significant advantage over those waiting for quarterly financials to surface a problem.
Doug's Take
The platforms that struggle most are often the ones that treat acquisition as the finish line.
Closing is not the end of the work. It is the beginning of the hardest part. The organizations that navigated integration successfully shared one thing in common: someone was accountable for operations from day one post-close. Not for the financial reporting. Not for the transition checklist. For the actual day-to-day operation of the organization.
That accountability does not have to be a full-time executive hire. But it has to exist. The absence of an operational owner in the integration period is not a gap that gets filled by good intentions or strong board decks. It is a gap that fills with problems.
Remember: clarity over complexity.
”From the Field
Q —What does platform erosion actually look like in the 9 to 18 month window, and what does it take to stabilize it?
A — Douglas Hemminger
The most common version I have experienced is integration fatigue. You know it is likely coming, and you do your best to prepare for it, but around that 9 to 18 month window the early energy from the transaction starts to fade. The practice is no longer newly acquired, but it is not fully operating as part of the platform yet. That is when you begin to see drift. Meetings are happening, but decisions are not moving. Dashboards exist, but they are not changing behavior. Local leaders may still be solving problems through old habits and relationships, while the platform is asking for more consistency, visibility, and execution discipline.
The stabilization work is usually about getting back to fundamentals. Reset the operating cadence, narrow the priorities, reconnect platform expectations to what the local team actually needs to execute, and rebuild trust through visible follow-through. Looking back, I would plan more intentionally for the fatigue curve itself. Integration plans focus heavily on the first 90 days, but the harder work often shows up later, when the urgency has faded and the operating habits have not fully changed. What we got right was not treating it as a failure of the practice. We listened, translated expectations into practical steps, and rebuilt momentum without making the team feel like everything had to change at once.
The Integration Window: What the First 90 Days Actually Require
The first 90 days after a healthcare acquisition close define more about the long-term performance of the platform than most deal teams want to acknowledge. This is not a soft observation. It is operational physics.
The decisions made, and the ones deferred, in the first quarter set the trajectory for everything that follows. The window is real, it is limited, and it closes whether or not you use it.
What "Integration Complete" Actually Means
Integration is not complete when the systems are connected or when the org chart is updated. Integration is complete when the acquired organization can operate independently within the platform's standards without requiring constant escalation to senior leadership. That is a meaningfully higher bar than most integration plans acknowledge, and most integration timelines do not account for the time it actually takes to reach it.
The First 30 Days as Diagnostic
The first 30 days reveal things that pre-close diligence missed. Not because diligence was careless, but because some things only become visible when the deal is done and incentives change. Staff who were on their best behavior during the process begin to sort themselves. Leadership who aligned around the sale now has to realign around the platform. The first 30 days are diagnostic, whether you treat them that way or not.
Operators who treat the first month as a listening and assessment period, rather than an execution period, consistently report better integration outcomes. The insight gathered in those 30 days is worth more than the action taken before it.
Physician Engagement in the Window
One of the most expensive mistakes in healthcare integration is treating physician engagement as a communications problem. Physicians in the integration period are not watching messaging. They are watching operational execution. If things are disorganized, if questions go unanswered, if commitments made during the acquisition are not being kept, they notice, and they begin making decisions accordingly.
Some of those decisions are quiet. Some are not. The time between the first physician concern and the first physician departure can be measured in months. The time between the first departure and a pattern is often shorter than platforms expect.
What Gets Deferred and Why It Matters
In the integration window, simultaneous pressure to source the next deal, report to the board, and manage daily operations creates a prioritization problem that consistently works against operational buildout. The items deferred are almost always the ones that do not appear in the next board deck: workflow mapping, supervisor training, credentialing alignment, reporting infrastructure.
They feel deferrable. They are not. Each month of deferral extends the period before the organization is actually functioning as a platform rather than a collection of acquired practices under one roof.
The 60-day deferred decision becomes the 180-day crisis. I have watched this happen enough times that it no longer surprises me. It does not have to be inevitable.
”Douglas Hemminger · H. Douglas Advisory
Doug's Take
The things that feel like they can wait, usually cannot.
I have worked through integration on both sides, as an operator inside an acquired practice and as the person sent in to stabilize one post-close. The single most consistent observation is that the items deprioritized in the integration window are never neutral. They either get addressed while the cost is still manageable, or they get addressed later at significantly higher cost, in time, in leadership attention, in physician goodwill, or in financial performance.
The integration window is the one period where the organization has both the attention of platform leadership and the tolerance of the acquired team for disruption. That combination does not last long. Use it deliberately.
”From the Field
Q —Nine months running a large specialty practice through acquisition and post-close. What did the first 30 days actually require?
A — Douglas Hemminger
The first 30 days were about protecting continuity while building the bridge between the practice and the acquiring platform. The most critical decisions were establishing a clear operating cadence, identifying the real leaders and influencers inside the practice, and getting fast visibility into the numbers and the field reality. You cannot manage that period only from the financials, and you cannot manage it only from hallway conversations. You need both. I wanted to understand what was working, where the risks were, who the physicians trusted, where staff were stretched, and which issues could create immediate instability if not addressed quickly.
Looking back, I would have formalized decision rights and the 30-60-90 day communication structure even earlier. In those transitions, a lot of friction comes from ambiguity, not bad intent. People are not always clear on what stays local, what moves to platform leadership, and who owns the next step. What we got right was not overcorrecting in the first month. We kept the practice moving, protected physician relationships, listened before changing too much, and created enough structure to stabilize the transition without making the team feel like everything they had built was being replaced overnight.
Physician Alignment as an Operating Problem
Every platform executive understands that physician relationships are important. Most manage physician alignment as a relationship problem, something addressed through town halls, engagement surveys, and leadership retreats. It is not. Physician alignment is an operating problem. It has operational causes, it requires operational solutions, and it produces measurable operational outcomes. The organizations that recognize this distinction navigate it significantly better than those that do not.
What Physicians Actually Watch
Physicians in acquired practices are not primarily concerned with culture statements or organizational mission. They are concerned with their ability to practice medicine without unnecessary friction. Will their patients be scheduled correctly? Will their staff be supported? Will their administrative burden increase? When the operational answers to those questions are unclear or negative, alignment erodes, regardless of how well the communication plan was executed.
The Compensation-Operations Disconnect
Most physician alignment conversations focus on compensation. Compensation matters. It is not irrelevant. But it is rarely the primary driver of physician dissatisfaction in the post-acquisition period. The operational environment, scheduling workflow, support staffing, EHR friction, authorization burden, administrative support quality, accounts for more physician departures than most platforms track, partly because it does not show up cleanly in exit interview data.
A physician who leaves because they cannot get their prior authorizations processed is often recorded as leaving for a compensation reason. The actual driver was operational and therefore addressable, if it had been identified.
Alignment Through Operational Credibility
The fastest path to physician alignment is operational credibility. When physicians see that the platform can execute on its commitments, that workflows improve, that staffing concerns are addressed, that their problems receive operational responses rather than communications responses, alignment builds. This is not a soft process. It is a measurable result of consistent operational execution against commitments made during the acquisition.
The Physician Leader Problem
Many platforms rely on physician champions or medical directors to bridge the gap between clinical and operational worlds. When the gap is narrow and the operational environment is functional, this works well. When the operational gap is large, the physician leader role becomes a pressure absorber rather than a bridge. The result is a frustrated physician leader caught between platform expectations and frontline physician concerns, with insufficient operational authority to address either.
A physician leader can be an important bridge, but they cannot substitute for an operational solution.
Doug's Take
Physician alignment is a trust problem. Trust in this context is built operationally.
I have sat in rooms with physicians who were disengaged, frustrated, or mid-conversation with competitors, and in most of those situations, the origin was operational. Something was not working. Something that had been promised during the acquisition was not being delivered. When I could address the operational problem, the relationship problem often resolved without a separate intervention.
The platforms that do this well do not have better relationship managers. They have better operational execution. The distinction matters because only one of those is scalable.
Remember: clarity over complexity.
”From the Field
Q —Improving physician alignment through operational change, not communications. What did that actually look like?
A — Douglas Hemminger
Early in my career, I probably would have approached physician alignment mostly through communication and relationship building. Over time, I learned that alignment often changes when you fix the operating friction around the physician. In this case, the frustration was showing up around templates, staffing, clinic flow, and inconsistent expectations. We tightened visit types, reviewed provider templates, aligned staffing more closely to volume, and used access and productivity data in a way that connected directly to the physician's daily experience, not just platform reporting.
The shift was not immediate retention impact. It showed up first in behavior. Physicians engaged differently in operating conversations, accepted template adjustments, escalated issues earlier, and became more willing to work through process changes. You could usually see that within 30 to 60 days. What I would tell a platform COO is to start by asking where the operating model is making it harder for physicians to practice. If you reduce that friction first, alignment becomes easier, because the platform is solving a real problem, not just asking physicians to trust the process.
Workforce Architecture: Staffing, Retention, and the Attrition Trap
The staffing challenge in healthcare is real and well-documented. But most of the staffing conversations happening at the platform level are about acquisition, recruiting, sign-on bonuses, compensation benchmarks, rather than about the structural conditions that determine whether the people you hire stay. That distinction matters, because the cost of turnover in healthcare operations is not primarily a financial cost. It is an institutional knowledge cost, and it compounds with every departure.
The Attrition Trap
Healthcare organizations with high turnover develop structural conditions that perpetuate turnover. Undertrained staff leave. Their departures create vacancies that increase burden on remaining staff. That increased burden accelerates the next wave of departures. The organization enters a permanent state of hiring, onboarding, and losing, without ever diagnosing the conditions that created the cycle in the first place.
Escaping the attrition trap requires addressing structural causes, not just increasing the rate of hiring. More hiring into a broken retention environment produces more turnover, faster.
The Supervisor Layer as the Bottleneck
Most operational training investment goes to frontline staff. The supervisor layer, the people who manage day-to-day performance, address execution problems, hold accountability, and carry institutional knowledge, is frequently undertrained and under-supported at the platform level. When supervisors are not equipped to hold performance standards, the floor drops. When the floor drops, the staff who want to perform well become frustrated and leave first.
Investing in supervisor capability is one of the highest-leverage operational moves available to a healthcare platform. It is also one of the most consistently underfunded.
Role Clarity as a Retention Tool
A significant portion of healthcare operational turnover is driven by role ambiguity. Staff who are not certain what they are responsible for, who they escalate to, or how to handle workflow edge cases experience low-grade chronic stress that manifests as disengagement and eventually as departure. Workflow clarity is not just an efficiency tool. It is a retention tool, and one that does not require additional compensation to deploy.
The Backfill Default
When a position opens, the default response in most healthcare organizations is to backfill it, post the role, hire a replacement, and return to the previous configuration. Sometimes that is exactly right. But many organizations backfill positions reflexively rather than asking whether the role design still makes sense, whether the work could be redistributed more effectively, or whether the position itself is a symptom of a structural inefficiency rather than a genuine operational need.
Doug's Take
The math on retention is simple. The discipline to act on it is rarer than it should be.
I have reduced staffing costs in healthcare organizations without reducing headcount through terminations, by stopping the reflexive backfill of positions that were perpetuating broken workflows, and by investing operational attention in the supervisor layer instead of always starting at the bottom. The results were not accidental. They came from a willingness to ask what was actually causing the turnover before spending money to address the symptom of it.
The platforms that do retention well are not the ones with the best benefits packages. They are the ones where supervisors are equipped, roles are clear, and the daily experience of doing the job is not unnecessarily hard. Most of that is an operational problem, not a compensation problem.
”From the Field
Q —Where does staffing savings actually come from, and what resistance do you encounter getting there?
A — Douglas Hemminger
One of the biggest staffing lessons I learned is that savings do not always come from reductions. Sometimes they come from stopping the automatic backfill of roles that are supporting a broken workflow. The key is to look at the vacancy before filling it. Is the role still needed as designed? Is it covering for unclear ownership, weak supervision, poor workflow, or a process that should have changed months ago? Some of the largest savings came from redesigning roles, centralizing support where appropriate, and strengthening the supervisor layer instead of continuing to refill the same positions.
The resistance is usually fear. Leaders worry the team will feel abandoned. Staff worry that process improvement or technology means their jobs are at risk. That is why culture becomes even more important during periods of transition, growth, or PE partnership. You have to be clear about the direction, preserve institutional knowledge where you can, retrain people where it makes sense, and use normal attrition to reshape the model over time. A good attrition plan can often achieve the same financial goal as a layoff, with far less cultural damage.
Revenue Cycle From the Inside: What Diligence Misses
Revenue cycle is one of the most analyzed areas in healthcare operations and one of the most consistently misunderstood at the platform level. Most of the analysis happens from a data perspective: AR days, denial rates, collection ratios. Those metrics matter, but they are trailing indicators. By the time they surface in a report, the operational decisions that created them are already months in the past. The operator's advantage is learning to read what is happening upstream, before it becomes a financial problem.
What Diligence Typically Misses
Pre-close revenue cycle diligence reviews historical data: AR aging, payer mix, denial rates, coding accuracy. What it rarely assesses is the operational infrastructure that produced those numbers. A practice can have reasonable AR days and genuinely weak revenue cycle operations if volume is low or the payer mix is forgiving enough to absorb inefficiency.
The question diligence should consistently ask, and often does not, is whether the revenue cycle infrastructure can scale. A single-site practice with a competent biller and a manual workflow may produce clean numbers. The same practice as site three of twelve, with three times the volume, frequently does not.
The Credentialing Gap
Credentialing is one of the most consistently underestimated integration risks in healthcare acquisitions. When physicians are moved to a new tax ID or group NPI after close, every payer relationship has to be re-established. That process takes 90 to 180 days per payer, sometimes longer. In the interim, claims may not be paid, cash flow is constrained, and the platform is funding an organization it cannot yet bill for effectively.
Platforms that plan for this window, that model the cash flow impact and have an operational response ready, navigate it. Platforms that discover it after close face a problem that was entirely preventable.
Front-End Revenue Cycle as the Actual Leverage Point
Most revenue cycle conversations focus on the back end: billing, claims processing, denial management, collections. The back end can only work with what the front end creates. Scheduling accuracy, insurance verification at the point of scheduling, authorization management, point-of-service collection. These front-end functions determine revenue cycle performance more directly than most platforms acknowledge, and they are less frequently measured.
The Inherited Vendor Problem
Many acquired practices have outsourced components of their revenue cycle: billing companies, RCM partners, coding contractors. Platforms typically inherit these relationships without evaluating them against platform-level standards or scalability requirements. Some vendors are excellent. Others are carrying performance issues the practice never had the bandwidth to address. Inheriting a vendor relationship without assessing it is inheriting the performance problems that come with it.
Doug's Take
Revenue cycle is where operational problems show up as financial problems. The fix is almost always upstream.
When I have worked through revenue cycle underperformance in healthcare organizations, the cause has almost never been the billing team. It has been something upstream. A credentialing delay that was not planned for. A front-desk workflow that was not capturing insurance correctly. A scheduling pattern that consistently generated authorization failures. A vendor whose contract incentives were misaligned with platform performance.
The data shows you the revenue cycle problem. The building shows you the cause. You cannot fix the first without understanding the second.
Remember: clarity over complexity.
”From the Field
Q —Credentialing gaps and front-end revenue cycle breakdowns during acquisition. How do you identify them, fix them, and how long does recovery take?
A — Douglas Hemminger
A common acquisition risk is the gap between provider credentialing, scheduling, and front-end revenue cycle. The practice may be operationally ready to see patients, but the revenue infrastructure may not be fully ready to support those visits. That creates delayed cash, denials, claim holds, and avoidable rework. The way we identified it was by lining up provider start dates, active schedules, payer enrollment status, charge lag, denial trends, and front-end registration issues. Once you put those together, the pattern becomes clear.
The fix was operational, not just administrative. We created a weekly readiness cadence between operations, credentialing, RCM, scheduling, and site leadership. We clarified who owned each exception and built a provider readiness process before schedules were opened too far. Even with the right plan in place, you are still relying on multiple people and outside entities. In a large group, a provider or two may still be delayed. That is why constant monitoring matters. You have to stay close, communicate throughout, and redeploy resources until the problem is resolved.
Visibility can improve within 30 days. Stopping new leakage may take 30 to 60. Full recovery is typically 90 to 180 days depending on payer timelines and backlog. Credentialing cannot sit off to the side during acquisition or growth. It has to be managed as part of the operating model because it affects access, physician trust, and cash simultaneously.
Building a Platform That Can Be Acquired Again
PE-backed healthcare platforms are built to be sold. That is not a criticism. It is the model. The question operators should be asking from day one is not only how to create value in this cycle, but how to build an organization that a future buyer will recognize immediately as well-run. That recognition has a specific operational meaning: the infrastructure is visible, documentable, and transferable without depending on any single individual to explain it.
Operational Documentation as a Value Driver
Most healthcare organizations operate significantly on institutional knowledge, workflows that live in the heads of long-tenured staff, processes that exist because someone decided once and never formalized it, systems that function because a specific person knows how to navigate them. This is operationally fragile and financially discounted by sophisticated acquirers. Documented, reproducible operational processes are a real and measurable component of enterprise value.
Building documentation discipline is not an administrative burden. It is a value creation exercise, and one of the best predictors of retention during leadership transitions.
The Leadership Bench Question
A platform that depends on one or two operational leaders is a platform with key-person risk. Sophisticated buyers apply a meaningful discount to this, and they identify it quickly in diligence through leadership interviews, org chart analysis, and questions about what happens if a specific person leaves. Building a leadership bench, supervisors who can step up and functional leads who can hold performance independently, is not a human resources project. It is an enterprise value project.
Scalable Systems Before Scale
Growth consistently outpaces the operational infrastructure designed to support it in PE-backed healthcare. Platforms that add practices without first confirming that their core systems, credentialing, scheduling, EHR integration, revenue cycle, HR, can absorb the additional complexity tend to find that performance degrades across the portfolio simultaneously. Fixing systems after scale is significantly more expensive and disruptive than building them correctly before the next acquisition closes.
What the Next Buyer Will Find
The final measure of operational quality is a simple question: what will the next buyer's diligence team find when they walk in? Operators who hold that question in mind tend to make better decisions throughout the ownership period, not because they are managing to an exit, but because it is an honest measure of whether the organization is actually well-run or just looks well-run from a distance.
Documentation is current. Leadership is stable and can speak to their own processes without coaching. Revenue cycle is clean. Physician turnover is low and explained. These are not accidental outcomes. They are the product of consistent operational discipline, applied deliberately.
The organizations that command premium valuations are the ones that do not require the buyer to take a leap of faith on operational quality. That does not happen by accident.
”Douglas Hemminger · H. Douglas Advisory
Doug's Take
Build every quarter as if a sophisticated buyer is reviewing your diligence materials next week.
I have been on both sides of this, inside organizations being evaluated and advising on organizations going through a process. The ones that perform well in diligence are rarely surprised by what the process surfaces. Their documentation exists and is current. Their leadership team is stable and articulate. Their operational story has continuity. What they said they would build, they built.
The ones that struggle are not struggling because they did bad work. They are struggling because the work they did was not visible. It lived in the institutional memory of individuals rather than in the documented infrastructure of the organization. That gap costs real money. And it is entirely solvable, when addressed before the process begins.
”From the Field
Q —What is the most significant operational gap you have seen in platforms going through acquisition, evaluation, or transition, and what does it take to close it?
A — Douglas Hemminger
I have been involved in organizations during acquisition, evaluation, and platform transition, and one of the most consistent gaps I have seen is leadership dependency risk. The business may be performing, but too much of the operating knowledge sits with a small number of people. A strong administrator, a legacy physician leader, or a few experienced managers may be holding the model together through relationships, memory, and informal workarounds. That works until the organization needs to scale, integrate, or be evaluated by an outside party.
The operational gap is not always that the business is broken. It is that the business is not yet structured enough to prove it can perform without those individuals carrying it. To address that, I would focus on clarifying roles, strengthening the supervisor and director layer, building a consistent operating cadence, documenting key workflows, and creating clearer ownership for decisions and follow-through. The goal is to move from personality-based operations to a repeatable management structure, not by stripping away local knowledge, but by preserving what works, reducing dependency risk, and helping buyers or board members see that performance can be explained, repeated, and scaled.
A Final Word
The work is not to make healthcare operations more complicated. It is to help the right people see clearly, agree on the next move, and get the work moving.
Healthcare is complex, but the game plan does not always have to be. Most operational problems are solvable when the right people have time, structure, and a clear view of what is actually happening. The challenge is that issues often compound before anyone has the bandwidth to slow down, simplify the picture, and address what is really driving the problem.
H. Douglas Advisory is a principal-led practice. When you engage, you work directly with me. Not a large team. Not a staffed model. The same person who understands the situation is the person doing the work. I bring more than 20 years of operating experience across physician practices, multi-site healthcare groups, specialty operations, and PE-backed platform environments.
If something in this manual reflects a problem you are navigating, or a question you have been trying to put into words, start a conversation. That is how most useful work begins.