What is AEA by Ivory & Co.?What, exactly, is an adaptive enterprise?
An adaptive enterprise is a business that can describe itself clearly enough to change on purpose. Size has nothing to do with it. AEA is the discipline for seeing the whole business that way: its people, its work and its decisions, not only its technology.
AEA by Ivory & Co. is Adaptive Enterprise Architecture, developed and stewarded by Ivory & Co. It is distinct from the Association of Enterprise Architects, and from academic uses of the name Adaptive Enterprise Architecture.
Everything has an underlying architecture. Including business.
Every business has an architecture. Whether anyone has deliberately designed it is another question.
It exists in the choices the business makes, the value it creates, the capabilities it develops, the people and technologies that perform its work, the relationships it depends on and the conditions it operates under. It exists in the things that work beautifully together, and in the things that don’t.
For much of business history we have relied on people to hold these relationships together. Founders carry an extraordinary amount of the business in their heads. Experienced employees know why things work the way they do. Executives understand their own domains, and teams develop local practices to get around the complexity near them. This works remarkably well, until the business becomes too complex for any one person to understand as a whole.
Adaptive Enterprise Architecture (AEA) is a discipline for making the architecture of business legible. It gives a structured way to describe, design and examine an enterprise through eleven distinct, interconnected architectural concerns. The business stays as complex as it is. The complexity becomes intelligible.
Enterprise is a way of seeing a business, whatever its size
“Enterprise” says nothing about size. A ten-person company and a ten-thousand-person corporation are both trying to understand what outcomes matter, what they need to know, what they can rely on, who can act and where work happens. The complexity differs. The architecture does not.
A small business can have complicated commercial arrangements, specialised capabilities, several operating models, outside partnerships and heavy technological dependencies. A large one can have areas of remarkable structural consistency. What makes a business hard to understand is the number and nature of the relationships that have to be understood, and headcount is a poor measure of that.
Seen as an enterprise, a business is one connected whole. An adaptive enterprise is one that can describe that whole explicitly, in a way its leaders share. When something changes, it can see what the change reaches, decide what should move and what must stay, and act with precision.
A strategist’s architecture of business, built on enterprise and business architecture
Ask ten people to describe the same organisation and you may receive ten entirely different answers. The chief executive describes its direction. The finance director describes its commercial performance. The operations manager describes how work gets done. The people team describes the workforce, the technology team describes the systems, and the customer describes their experience.
Each may be correct. None explains how the enterprise works as a connected whole.
AEA emerged from a strategist’s need to understand those connections. Enterprise Architecture and Business Architecture are established disciplines, and AEA builds on a world in which they already exist. Its starting point is the enterprise itself, where much architecture practice began with the technology estate and extended outward into the business. AEA is not a technology discipline. Technology is one part of the enterprise, and one pressure on it. The subject is the business: what it intends, what it must be capable of, how work is performed, who takes part, who may decide, and what can be relied on. Its contribution is a particular architectural treatment of that whole, with explicit boundaries between the different kinds of things that make an enterprise what it is.
It is intended for people making consequential decisions about businesses: founders and owners, boards and executives, strategists and operators, and finance, people, technology and transformation professionals. Increasingly, it is also for the intelligent systems taking part in enterprise work.
Eleven dimensions. One enterprise.
AEA describes the enterprise through eleven Architecture Standards. Each owns a distinct architectural concern, and each is anchored in a single word. They form a flat set: none is subordinate to another. The set is described in two groups, the Value Nucleus and the Operating Ring, and the grouping carries no hierarchy of authority.
Seven architectures.
Directional Architecture
The strategic scope and choices the enterprise is designed to realise.
Domain Architecture
The value logic of the business and the capabilities required to create and deliver value.
Ecosystem Architecture
The actors, relationships and exchanges through which the enterprise takes part in a wider ecosystem.
Execution Architecture
How work is to be performed, through defined, composable instructions.
Expression Architecture
How the enterprise gives form to its identity and value for its audiences and contexts.
Possibility Architecture
How the enterprise imagines, explores and preserves possibilities for its future.
Reality Architecture
The basis for establishing the actual position of the enterprise across time.
Four architectures.
Intelligence Architecture
How the enterprise establishes, maintains and develops the understanding its architectures require.
Workforce Architecture
The roles required to take part in enterprise work, and how they are sourced, fulfilled, structured and assigned.
Environment Architecture
The physical and technological enablement required for instructions to be executable as intended.
Trust Architecture
The conditions under which reliance between parties is warranted, and how that reliance changes over time.
Why the distinctions matter
A wholesale distributor decides to start selling directly to the public. On the surface it is a sales decision: build an online store and take orders.
The implications run much further. The business has to be clear about what it intends to achieve and which commercial choices the move supports. Selling single items to households calls on capabilities that selling pallets to retailers never needed, and on new instructions for how orders are picked, packed, returned and refunded. Someone has to decide which roles the work requires and whether staff, a logistics partner or software will fill them. The warehouse and the systems have to be able to carry out the work as designed. The retailers who already stock the product are affected, and so is the way the business presents itself to a customer it has never dealt with face to face. Those customers need grounds to rely on delivery promises. And once the store is live, the business needs to know what is actually happening, which may differ from the plan.
These concerns are connected, and they are different things. A role and the person filling it are separate. A capability can be met by many different instructions. An intention is still an intention after the results arrive. Having access to a system confers no authority to act through it. Understanding something does not entitle anyone to rely on it.
AEA preserves these distinctions because they matter when an enterprise is being designed, changed or operated. Without them, organisations build sophisticated systems on ambiguous assumptions.
Every picture shows one thing
Organisations usually manage their complexity by looking at one perspective at a time. An organisational chart shows reporting relationships. A process map shows the flow of work. A technology diagram shows systems and integrations. A financial report shows selected commercial outcomes.
Each is useful, and the enterprise exists across all of them. AEA is designed to preserve the relationships that connect these perspectives without collapsing their separate meanings, so the business remains legible as it changes and grows.
Beyond what one person can hold in their head
One of AEA’s foundational design properties is cognitive independence: the architecture of a business should not depend on its complexity fitting inside any individual’s head.
A founder understands a young business through direct experience. As it grows, that knowledge spreads across people, teams, systems and outside relationships, until nobody can reliably describe every consequential dependency. The business keeps operating, and its ability to understand itself comes to rest on fragmented institutional memory.
AEA provides a foundation through which those relationships stay explicit and traversable. Each participant can understand the part of the enterprise relevant to their work and still see how it relates to the whole. It also opens the way for intelligent systems to help interpret, analyse and operate enterprise architecture at scales beyond unaided human comprehension. The architecture should hold together whether its participants are human, organisational or technological.
An architecture that can change
Direction changes. Capabilities develop. The workforce evolves, relationships shift and operating instructions are refined. New possibilities emerge while reality challenges old assumptions.
Accommodating that takes more than keeping diagrams current. The discipline distinguishes what is established from what is proposed, what is uncertain and what is unknown. It preserves the identity and ownership of architectural propositions as they evolve, and it recognises that different operating contexts can legitimately be in different states at once.
The same applies to AEA itself. Current authority does not imply infallibility, and the discipline has to be open to refinement and extension when evidence shows its propositions are insufficient. Adaptation means evolving while the integrity of the architecture is preserved. It is never licence to add things without control.
Independent of the technology used to apply it
AEA is a discipline. It is no software product, and it depends on no particular AI model, platform, database or implementation method.
The discipline establishes architectural meaning. Technology can help capture, manage, analyse, traverse and operationalise that meaning. One business might apply AEA through facilitated architecture work, another through structured knowledge systems, specialised applications or increasingly automated operating environments. The implementations differ, and the underlying distinctions have to stay coherent across all of them.
That separation protects the independence of the discipline. An application built on AEA acquires no authority to redefine it, and a commercial implementation can extend how architectural knowledge is used without changing the standards that govern what it means.
From understanding to enterprise autonomy
Once the architecture of an enterprise is sufficiently structured, connected and governed, new things become possible. A proposed change can be examined across every concern it touches. Alternative operating arrangements can be compared. The business can see which capabilities, roles, instructions and enabling resources a strategic decision would require to change, and where actual operations have drifted from the intended design. Increasingly, it can use intelligent systems to assemble, analyse and carry out work inside explicit architectural and governance boundaries.
These are potential applications of the discipline, and no claim is made that every implementation delivers them today. They point to a different relationship between architecture and operation, in which architecture becomes part of the structured knowledge through which a business understands, changes and runs itself. Applications such as Adaptive Enterprise Autonomy are developed on that foundation. The discipline provides the architectural basis, and the application determines how it is put to work.
A discipline governed by standards
AEA is established through a governed body of knowledge, and each publication has its own job. The eleven Architecture Standards establish the architectural concerns, their definitions, boundaries and governing propositions. The Architecture Set Standard establishes the integrity of the set. AEA Design records the result of applying the eleven architectures to AEA itself. The Governance System Design describes how governance is designed to operate, and the Governance Standards establish the normative protections for governed consequence.
Together they let the discipline develop without leaning on undocumented interpretation or the authority of any one commercial implementation. Ivory & Co. stewards this body of knowledge and its continued development.
The business as a connected whole
The most important shift AEA introduces is a change in how we understand what a business is.
An enterprise is the connected architecture through which strategy, structure, processes, workforce, technology, finances and every other concern combine to create and deliver value. Understanding that architecture lets leaders see past the boundaries of their own functions. It lets a change be examined in relation to the enterprise it will affect, and it makes knowledge more explicit, more connected and more useful.
It also lets a business become more adaptive without becoming less comprehensible. The ambition is to make the complexity of every business understandable.
Read on: the eleven dimensions · the principles · the hybrid enterprise · the Body of Knowledge · the Standards Library · Knowledge and research.
Where to go next.
Principles
Seven principles keep a business’s knowledge of itself meaningful as it grows and changes. Each is shown here through an ordinary business situation.
The eleven architectures
AEA describes one business through eleven architectures. Each owns a different concern, from intent and work to people, decisions and reliance. Technology is one of the eleven. None ranks above another.
Interlocks
An interlock is the relationship between two distinct concerns of an enterprise. It lets a change in one place be traced to what it reaches elsewhere, while each concern keeps its own meaning and its own owner.