To understand a business is to look past its marketing, its mission statements, and its organizational chart. Beneath those abstractions, a business is an engineered entity—a complex, dynamic machine designed to process demand and output value.
For business decision-makers, architects, and consumers, visualizing the enterprise as an interacting grid of seven fundamental systems changes the conversation. It moves discussions away from isolated departmental silos and toward systemic health.
Here is the architectural treatise on those seven systems, and the crucial vocabulary that binds them.
The Core Distinction: Capabilities vs. Systems
Before examining the systems, we must define the spine of the architecture: Capabilities.
A capability is the vocabulary of what the business must be able to do. “Secure Data Routing,” “Next-Day Order Fulfillment,” or “Automated Customer Onboarding” are capabilities. They are agnostic to how they are achieved.
The most common—and expensive—architectural mistake is treating a capability as a system. You cannot buy a “capability” off a shelf. You can buy technology, but to manifest an actual capability, you must thread it through the seven structural systems below.
The Seven Structural Systems
1. Value (The Outcomes)
What outcomes does the organization produce, for whom, and why do they matter?
Value is the compass. It defines the external reality of the business. For a consumer, this is the product or service they exchange capital for. For an architect, Value dictates the non-negotiable requirements of the system. If an outcome does not matter to the end user (internal or external), then any energy spent optimizing it is wasted.
- Architectural lens: Value dictates scale and resilience.
- Decision-maker lens: Value determines market viability.
2. Work (The Engine)
What activities transform demand into those outcomes?
Work is the actual sequence of kinetic events. It is the value stream. This system is entirely concerned with processes, workflows, and the physical or digital transformation of raw inputs into the Value defined in System 1.
- Architectural lens: Work requires minimizing friction. It is the mapping of dependencies and the elimination of bottlenecks.
- Decision-maker lens: Work is where efficiency is won or lost.
3. Organisation (The Topology)
Who performs the work, and where does authority sit?
Organisation is not merely the HR hierarchy; it is the topology of authority and execution. It defines human nodes. If a system requires rapid pivoting, but the Organisation system dictates a rigid, multi-layered approval matrix, the system will fail.
- Architectural lens: The structure of the technical systems will inevitably mirror the communication structures of the Organisation (Conway’s Law).
- Decision-maker lens: Aligning authority with the people doing the Work.
4. Information (The Bloodstream)
What facts, records, and knowledge make the work possible?
Information is the state of the business at any given millisecond. It includes everything from transactional databases and customer records to institutional knowledge and telemetry. Work cannot happen without Information routing to the right nodes in the Organisation.
- Architectural lens: Establishing single sources of truth, data taxonomy, and ensuring low-latency access to required knowledge.
- Decision-maker lens: Ensuring data quality enables accurate forecasting and reality-mapping.
5. Technology (The Infrastructure)
What systems automate, constrain, or enable the work?
Technology is the physical and virtual tooling. It is the hardware, the codebase, and the networks. Crucially, Technology does not do the work; it enables or automates the Work (System 2) using Information (System 4) governed by rules (System 7). Whether migrating thousands of users across a distributed network or enforcing strict security baselines, Technology must serve the capability, not dictate it.
- Architectural lens: Ensuring systems are scalable, interoperable, resilient, and secure by design.
- Decision-maker lens: Managing technical debt and ensuring infrastructure investments directly enable Value.
6. Economics (The Fuel and Exhaust)
What resources are consumed, and where does value leak?
Every action in the other six systems incurs a cost—time, capital, attention, or physical resources. The Economics system tracks this consumption. Value leakage occurs when Work is inefficient, Technology is bloated, or Governance is overly bureaucratic.
- Architectural lens: Optimizing computing resources, licensing models, and operational overhead.
- Decision-maker lens: Maximizing the ratio of Value created to Economics consumed (ROI).
7. Governance (The Brakes and Steering)
Who decides, who controls, who accepts risk, and who is accountable?
Governance is the system of constraints. It includes regulatory compliance, security policies, risk management, and strategic decision-making. Governance ensures that the business survives its own operations. It determines what the organization will not do, even if it is technically possible and economically viable.
- Architectural lens: Enforcing policies, audit trails, and security baselines without strangling Work.
- Decision-maker lens: Balancing the acceptance of operational risk against the pursuit of Value.
Summary of the Architecture
A healthy business operates these seven systems in equilibrium. A failure in one propagates through the rest.
If you attempt to upgrade Technology without addressing Organisation, the new tools will be rejected by the culture. If you attempt to optimize Work without the right Information, you merely execute the wrong processes faster. If Governance ignores Economics, the business regulates itself into bankruptcy.
Whenever a new Capability is required, the architect must ask: How will this change the Value, Work, Organisation, Information, Technology, Economics, and Governance of the enterprise?