DOCTRINE
Outcome-Defined Enterprise Integration
An operating doctrine for distributed service enterprises.
A distributed service enterprise — hospital, university, industrial campus, hospitality operation, commercial portfolio — depends on the integrated performance of a dozen service disciplines that are rarely trained together and almost never led together. Environmental services, food services, laundry and linen, facilities engineering, clinical engineering, supply chain, safety and risk, capital projects, water and wastewater. Each has its own vocabulary, its own metrics, its own professional culture. Each is typically directed by a specialist whose career depth runs vertically through one of them.
Integration across them is not a coordination problem. It is a design problem. It requires a doctrine — a shared way of thinking about how outcomes flow through the enterprise — that leaders across all disciplines can apply in their own domains while remaining coherent with each other. That doctrine has to be portable, transferable, and survivable across leadership transitions. Without it, every new executive rebuilds integration from scratch using whatever model they inherited from their previous employer, and the enterprise oscillates.
Integration across service lines is not a coordination problem. It is a design problem.
Outcome-Defined Enterprise Integration — ODEI — is the framework I have developed across 35 years of running integrated service operations at scale. It is the answer to a specific question: how do you make integration a design discipline rather than a coordination hope?
The five principles
The framework rests on five principles.
These are the organizing ideas that appear, in one form or another, on every service-line page of this site. They are derived from the observation that successful integration in distributed service enterprises always exhibits the same handful of structural properties. Name them, and you can design for them.
I
Outcome first. Always.
The orientation of every operational analysis begins with the outcome required — patient experience, infection control, financial performance, regulatory compliance, asset value — and works backward to identify the straightest line of events that produces it. This is the inverse of the default, which is to inventory current activities and look for optimization opportunities. The default produces local efficiency without enterprise coherence. The outcome-first orientation produces both.
II
The straightest line of events.
Once the outcome is defined, the next question is always the same: what is the minimum sequence of events — actions, decisions, handoffs, measurements — necessary to produce it? Any step that does not contribute to the outcome is waste, whether it originated in tradition, specialist preference, or organizational inertia. This is lean thinking applied at the enterprise level rather than the shop floor. The analysis is ruthless by design.
III
Cross-discipline integration is the work.
Every service line touches every other. The EVS protocol depends on the facilities engineering schedule. The food service workflow depends on the supply chain. The clinical engineering program depends on the safety and risk framework. A doctrine that treats service lines as independent is a doctrine that guarantees failure at the seams. ODEI assumes integration is the subject, and the service lines are the domains in which it is expressed.
IV
Dual perspective — owner and operator.
Every decision in a distributed service enterprise has an operator consequence and an owner consequence. The operator asks whether the work can be done safely, efficiently, and to standard. The owner asks whether the investment is aligned with the portfolio’s financial and strategic objectives. Most leadership in this space is trained in one perspective and defers the other. ODEI requires both to be held simultaneously. The practitioner’s judgment depends on it.
V
Measure what outcomes require — nothing else.
Measurement discipline is the place where most enterprise integration efforts fail. Organizations measure what is easy to measure, or what they have always measured, rather than what the outcome actually requires. ODEI begins measurement design at the outcome and works backward, in the same pattern as everything else. The resulting measurement set is usually smaller than what the organization was producing, sharper in what it tracks, and closer to decision-relevant. It also survives scrutiny, which is the ultimate test.
How the principles are applied
From doctrine to practice.
The service-line pages of this site demonstrate how these five principles express themselves in specific domains. Integrated Facilities Management is the parent frame. Environmental Services shows outcome-first thinking applied to infection control and patient experience. Food and Nutrition Services shows the straightest-line-of-events analysis applied to a department that most organizations treat as a cost center. Facilities Engineering shows dual perspective at work in plant operations. Each page is an instance of the doctrine, not a capability list.
Read them in whatever order makes sense for your enterprise. If you are a hospital CFO, start with Capital Planning & Project Management. If you are a hospital operator, start with Environmental Services. If you are an institutional owner thinking about asset management at portfolio scale, start with Integrated Facilities Management. The doctrine is the same on every page. What changes is the domain in which it is demonstrated.
Outcome-Defined Enterprise Integration (forthcoming, 2026).
ODEI is being published as a full-length operating doctrine for distributed service enterprises, covering governance, delivery frameworks, implementation pathways, and outcome measurement. The book extends the five principles articulated here into a detailed framework — including case-based analysis, implementation roadmaps for service integration, and a measurement architecture designed to survive leadership transitions.
The book is intended for senior leaders responsible for the performance of integrated service operations, and for the consultants and advisors who support them. It will be published through Problem Solved Consulting, LLC in 2026.
A note on how to read this site.
The service-line pages that follow are not capability descriptions. They are demonstrations of the doctrine at work in specific domains. If a service line you need is not covered here, it does not mean the work cannot be done — it means a doctrine-forward treatment of that domain has n0t been written yet. Contact me if you want to discuss one.