The past, made portable.
A named model converts a past win into a future capability. Each of these was built inside the P&L it served, survived my departure, and is documented well enough to build again. That is the work: operating models and governance that make quality, experience, and margin move together.
Clinical-Operational Dyad Leadership
The problem
South Carolina's largest health system, 18 hospitals, 300+ practices, 1.2M patients, ran clinical and administrative functions against separate scorecards. Decisions stalled between silos, patient satisfaction sat at 55%, and 22 service lines carried duplicated cost structures after merger.
The model
Physician leaders paired with operational directors across six service lines, with shared accountability for quality, financial, and experience metrics. Escalation tiers resolve conflict below the executive level. A Value Management Office holds $22M accountable through benefit-measurement methodology, adopted by the CEO-level Executive Steering Committee, and the post-merger operating model consolidated 22 service lines into one patient-engagement infrastructure.
Why it transfers. Any organization where two functions optimize against different scorecards: clinical versus administrative, product versus operations, growth versus margin.
Physician Adoption Framework
The problem
1,200+ radiologist owners across 12 practices, 60+ imaging locations, and four states, 33,000 daily studies, a population nobody has authority over, migrating off legacy voice recognition under hard contract deadlines while adopting an AI reporting platform.
The model
Triage structural barriers before applying behavioral change methodology, then route the adoption message through practice presidents rather than IT. A hospital AI security authorization framework anchored on HIPAA Covered Entity status sets the governance guardrails, approved at a Level 1 Trauma Center and adopted as the company template. A physician champion model at the highest-performing practice, 97% adoption, becomes the regional template.
Why it transfers. Any AI rollout where the users are high-autonomy experts who cannot be mandated: physicians, engineers, attorneys, senior sales.
Global Operations Model
The problem
A $7M operating loss in a $41M healthcare IT services division with no operational infrastructure behind it: no standardized contracts, no customer success function, no scalable delivery structure.
The model
Standardized contract methodology and complexity-based pricing; a Customer Success Manager function built from scratch; requirements vetting and scope-change protocols that eliminate uncompensated work; training infrastructure cutting agent development from one year to 90 days. Built as an operating system, not a rescue, so it outlasted the tenure.
Why it transfers. Turnarounds where the fix is an operating-model rebuild, not cost cutting: services businesses, post-acquisition integrations, shared-services and capability-center buildouts.
Customer Risk Score & Rapid Resolution
The problem
A global support operation across the US, Mauritius, and India with NPS at -52 and a knowledge-hoarding culture protecting seven-hour hold times.
The model
The Customer Risk Score framework predicts at-risk accounts before complaints surface, with individual quality performance tied to customer outcomes. The Rapid Resolution concierge model protects top-tier accounts. A SaaS support operating-model transition and a Leadership and Development Series with defined career tracks close the loop, so proactive service becomes the default rather than the exception.
Why it transfers. Any distributed service organization where culture, not process, is the constraint, and where proactive service must become the default.
The models, applied on merit alone.
The independent chapter shows these operating models applied as a fractional operator, where every structural change held because the reasoning did, in front of clients who could have simply said no.
Read the independent chapter