THE SYSTEM · DOMAIN STRUCTURE

Five permanent domains where enterprise behavior actually happens

Coordination failures, execution gaps, measurement distortions—these do not live in functions or departments. They live in the five structural domains every enterprise operates within. Naming the domain is how the condition becomes readable.

THE FIVE ENTERPRISE DOMAINS IN DEPTH →

WHAT THE DOMAINS ARE

Not departments. The geography enterprise behavior actually moves through.

The instinct, when something goes wrong inside an enterprise, is to locate the problem in a function. HR owns the people issue. Operations owns the process issue. Sales owns the customer issue. Finance owns the numbers issue. The assignment is tidy and almost always partially right—which is why it rarely produces a full reading of what is actually going on.

The Five Enterprise Domains name something different. They describe the structural conditions within which enterprise activity takes shape, regardless of how the enterprise is organized on paper. People + Alignment is not the HR function—it is the domain where human capacity, intent, and coordination either converge or fragment. Customer + Interaction is not sales or marketing—it is the domain where the enterprise's actual relationship with the market gets structurally arranged. The five domains are present in every enterprise, always, whether leadership has named them or not.

Reading an enterprise at the domain level produces a different picture than reading it at the function level. A coordination failure that presents as a Processes issue often originates in People + Alignment (unclear accountability) and ends up producing an Economics consequence (margin compression on rework). The problem is not in a function; it is moving through the structural geography. That is what the domains describe, and that is what they make readable.

THE FIVE DOMAINS IN DEPTH

Each domain, and the behavior it actually contains

Each of the five domains names a dimension of enterprise behavior that experienced leaders have watched, often for years, without vocabulary to isolate specifically. The descriptions below surface what the domain actually contains—the phenomena that show up there, and the work the name does in making those phenomena discussable.

People + Alignment

The team meeting where everyone nods but nothing gets done the same way afterward. The leader who feels they have said something clearly three times and is watching it land three different ways. The accountability that is documented but does not actually carry weight. People + Alignment is the domain where human capacity, intent, and coordination are organized—or fail to be. HR, talent management, and culture work happen inside this domain, but the domain itself is something larger: it is the structural condition that determines whether those functions produce coordinated behavior or produce the appearance of it.

Processes + Integration

The handoff that is always a little late. The coordination meeting that exists because two groups could not figure out how to talk to each other directly. The workflow that looks clean in the documentation and accumulates rework in practice. Processes + Integration names the domain where work actually flows between functions—where the structural design either supports the execution of strategy or quietly compensates for the places where it does not. Process improvement sits inside this domain. The domain itself is the question of whether the enterprise’s processes integrate across it.

Execution + Intelligence

The decision that got made last quarter and is quietly getting unmade this quarter, and nobody can quite explain when. The signal that should have changed behavior but got logged and forgotten. The lesson the enterprise learned two years ago and has somehow managed to forget. Execution + Intelligence is the domain where the enterprise observes its own operating conditions and either adjusts execution in response or does not. The distinction matters. This is not the domain of execution itself—it is the domain that determines whether execution is intelligent or merely active.

Customer + Interaction

The customer whose actual experience of the enterprise does not match the value proposition the leadership team committed to. The churn that feels concentrated in the places where the internal story and the external delivery come apart. The product that works in the demo and struggles in the deployment. Customer + Interaction is the domain where the enterprise’s relationship with the market is structurally organized—where stated intent either matches operational capability or diverges from it. Sales, marketing, and customer service do work here. What the domain governs is whether their work connects to a reality the enterprise can actually deliver.

Economics + Metrics

The dashboard that keeps showing “on track” while the leader feels something drifting. The financial report that technically ties out and somehow does not match what everyone knows is happening operationally. The metric that was right when it was designed and is no longer measuring what it is named for. Economics + Metrics is the domain where enterprise value is structured, measured, and interpreted—or obscured. Finance and accounting work here. What the domain determines is whether financial reporting reflects operational reality or produces a parallel narrative that slowly drifts from it.

“The domains are the geography of enterprise behavior. Conditions originate in one, surface in another, and consequence in a third. Reading any one in isolation produces an incomplete enterprise.”

ENTERPRISE SCIENCE · THE FIVE ENTERPRISE DOMAINS

HOW THE DOMAINS INTERACT

Conditions travel. That is why the domains are read together.

The five domains do not operate in isolation—a fact most experienced leaders already know in their bones, even without vocabulary for it. A measurement problem in Economics + Metrics does not stay there. It shapes the decisions made in Execution + Intelligence. Which shapes how work is designed in Processes + Integration. Which shapes how accountability lands in People + Alignment. The condition does not stop at a domain boundary because the enterprise does not actually have those boundaries.

This is why reading a single domain in isolation produces an incomplete diagnosis. The coordination failure that shows up as a Processes issue has probably originated in People + Alignment and is probably producing consequences in Customer + Interaction and Economics + Metrics. Each domain presents part of the condition. The full structural reading requires tracing the condition across the domains it is actually moving through.

Leaders do this tracing intuitively all the time. It is what separates a leader who reads their enterprise clearly from one who treats every condition as a local function problem to be solved in place. The Five Enterprise Domains give the tracing a vocabulary, which is what lets it become discussable—with a leadership team, with a board, with a practitioner—rather than remaining a set of intuitions that live only in the leader's head.

The interdependence is the structural argument for why the Five Enterprise Domains operate as one system rather than as five independent categories. The domains are the geography within which conditions move, and reading the enterprise requires the full geography.

HOW CONDITIONS PRESENT

Reading what the enterprise is already telling you

Enterprises are constantly emitting signals about their own structural condition. Some of those signals are obvious—margin moves, headcount changes, customer concentration. Others are quieter: how meetings are run, what gets escalated, where decisions pile up, how a leader describes their own enterprise in conversation. Experienced leaders read these signals all the time, often without putting the reading into words.

The Five Enterprise Domains turn that intuitive reading into something structured. The book The Five Enterprise Domains documents 120 signals across 28 categories—each signal tied to specific domain combinations, each described under both optimal and adverse conditions The signal tables are not a checklist. They are a reference that gives a name to what a leader is already seeing, and lets the seeing be shared, compared, and reasoned about.

Reading conditions this way is a practice, not a diagnosis. Enterprise behavior accumulates over weeks, months, quarters—and patterns emerge through sustained observation rather than from a single reading. The Operational Appendix System in the book provides instruments for that sustained practice: the Weekly Signal Scan, the Monthly Interface Review, the Quarterly Coherence Conversation. Each is a way of giving structure to the observing leaders are already doing, and letting the observations compound into a reading of the enterprise over time.

WHERE TO READ MORE

The deeper treatment lives in the book

This page gives the working summary of the domain structure. The full chapter-length treatment of each domain—the signal tables, the leadership patterns, the operational instruments—is in the book.

Publication

The Five Enterprise Domains

454 pages. 122 diagrams and tables. 120 enterprise signals across 28 categories. Activity Blueprint™ samples across industries and revenue ranges. Available June 1, 2026.

About the Book →

Adjacent Module

Activity Architecture™

The module that examines how work is actually carried across people, processes, and interfaces inside the domains. Activity Architecture and Activity Blueprint together make the domain structure readable at the operational level.

The System →

CONTINUE INTO THE SYSTEM

The other two dimensions

This page describes the domain structure. From here, the system opens along what Enterprise Science is at the institutional level and how the body of work is used in practice over time.

/system-overview

Enterprise Science System Overview

What Enterprise Science is, where it came from, and the adjacent categories it sits near but operates differently from.

System Overview →

/how-to-use

How the System Is Used

How leaders, practitioners, and institutions actually engage the body of work—the access modes, the use cases, and the recurring intervals of use.

How to Use →

INQUIRY

Direct inquiry

Direct inquiries arrive with a specific origin—licensing, certification, partnership, citation, or governance. Each routes by subject to the process responsible."

CONTACT ENTERPRISE SCIENCE →