Ivory & Co.
AEA by Ivory & Co.StandardsKnowledge & ResearchImplementationCertificationIvory & Co.

The eleven architectures of AEA by Ivory & Co.Eleven ways of understanding one enterprise.

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.

A business is one thing. Understanding it means telling apart things that are fundamentally different.

Strategy and execution are different. So are capability and participation, technology and authority, and what a business intends compared with what is happening inside it.

Stated like that, the distinctions sound obvious. In practice organisations collapse them all the time. They treat organisational structure as capability, process documentation as operating reality, access permissions as decision authority, and the availability of information as understanding.

The consequences stay hidden for a while. They surface when the business grows, changes, introduces new technology, acquires another organisation or tries to automate work that was never properly understood in the first place.

Adaptive Enterprise Architecture addresses this through eleven distinct architectural dimensions. Each establishes a different kind of truth about the enterprise, with its own governing question, definitions, boundaries and responsibilities, and each operates in relationship with the others. Think of eleven precise cuts through one enterprise. The cuts are deliberately separate. The enterprise stays whole.

The Architecture Set

The eleven are described in two groups. The Value Nucleus holds the concerns through which the enterprise establishes, performs, expresses, explores and understands its business propositions. The Operating Ring holds the concerns through which it develops understanding, composes participation, provides enablement and establishes warranted reliance.

The groups are neither phases nor levels of authority. The eleven form a flat set and operate concurrently.

·Architecture Set

The Value Nucleus

Seven architectures through which the enterprise establishes, performs, expresses, explores and understands its business propositions.

01 · INTENTDirectional Architecture

Where is the enterprise choosing to go, within what strategic scope, and through what choices?

Every enterprise is shaped by decisions about what it intends to become. Which markets will it serve? Which opportunities will it pursue, and what will it deliberately leave alone? What trade-offs is it prepared to make?

Directional Architecture establishes the strategic scope and choices the business must be designed to realise, which gives a basis for examining whether everything else supports that direction. A business can run highly efficient operations and still be organised around choices that no longer serve its future. Direction and efficiency are different questions.

Explore Directional Architecture →

02 · SCOPEDomain Architecture

What business are we architecting, how does it create economic value, and what stable business abilities must exist for that value logic to operate?

An enterprise needs to understand what it must be capable of doing before deciding how those abilities should be fulfilled. Domain Architecture establishes the value logic of the business and its stable capabilities.

A retailer needs capabilities for demand management, product management, procurement, fulfilment and customer service. Those capabilities exist independently of the departments, software and employees currently doing the work. They are enduring business abilities that can be fulfilled through different arrangements over time, which is what lets an enterprise change its operating model without losing sight of the business it is there to operate.

Explore Domain Architecture →

03 · INTERCONNECTEDNESSEcosystem Architecture

What Actors and Relationships must exist around the enterprise, what passes between them, and what Dependencies arise through that interconnectedness?

No enterprise exists in isolation. Businesses take part in networks of customers, suppliers, partners, regulators and intermediaries, and value moves through those relationships along with information, obligations, resources and rights.

Ecosystem Architecture establishes the actors, relationships, exchanges and dependencies through which the enterprise creates, accesses, exchanges and sustains value. It lets a business examine who it deals with and, more importantly, how its ability to operate depends on them. Outsourcing payroll changes who does the work. The enterprise still depends on people being paid correctly.

Explore Ecosystem Architecture →

04 · INSTRUCTIONSExecution Architecture

How is this work to be performed?

Knowing what a business must be capable of doing says nothing yet about how the work should be performed. Execution Architecture defines the instructions of the enterprise for performing work, so that work can be composed, varied and reused without losing the conditions that make it valid.

A process does not have to be one enormous sequence. It can be built from bounded modules with defined requirements, permissible variants, tasks and instructions. That matters most when work is performed by combinations of people, intelligent agents and automated mechanisms, because the instructions have to stay distinguishable from whoever or whatever is carrying them out.

Explore Execution Architecture →

05 · INDIVIDUALITYExpression Architecture

How should this enterprise express who it is and the value it offers, to this audience, in this context?

A business communicates its identity and value through far more than a logo, advertising and brand guidelines. Expression shows up in customer experiences, commercial propositions, interactions, physical spaces and every form through which the enterprise makes itself recognisable.

Expression Architecture establishes how the enterprise gives form to its identity and value for particular audiences and contexts. The same enterprise expresses itself differently to customers, employees, investors and partners, and remains one business throughout. This architecture protects the relationship between identity, intended experience and the ways both are made visible.

Explore Expression Architecture →

06 · OPTIONALITYPossibility Architecture

What could become possible for the enterprise?

The future of an enterprise is wider than the decisions it has already made. Possibility Architecture establishes how the enterprise systematically imagines, explores and preserves possibilities as its understanding develops. It is the architectural home for hypotheses, alternative futures and questions that have yet to become decisions.

A business can investigate a new market, operating model or commercial arrangement without committing to it, and several futures can stay open at once. Possibility Architecture lets those alternatives be developed and examined while keeping potential separate from actuality and from strategic commitment. It makes no attempt to predict a single inevitable future.

Explore Possibility Architecture →

07 · ACTUALITYReality Architecture

What is the enterprise’s actual position?

What an enterprise intends to do and what it actually does can differ. Reality Architecture establishes the basis for capturing the actual position of the enterprise across time, and it distinguishes designed arrangements from evidenced operating conditions.

A process is approved and inconsistently followed. A capability exists and performs differently from one business unit to the next. A technology implementation is complete while the outcomes it was meant to produce have yet to appear. Reality Architecture establishes what is actually the case, what has changed and what remains unknown. It manufactures no certainty and turns no observation into a judgement.

Explore Reality Architecture →

·Architecture Set

The Operating Ring

Four architectures through which the enterprise develops understanding, composes participation, provides enablement and establishes warranted reliance.

08 · UNDERSTANDINGIntelligence Architecture

What is required for the enterprise to understand what an architecture has determined must be understood?

Information and understanding are different things. An organisation can hold extensive data, documents and reporting and still be unable to answer important questions about its own operations.

Intelligence Architecture establishes how the enterprise develops and maintains the understanding its architectures require, across time and horizons. The need for understanding always originates in another architectural concern, and Intelligence fulfils it. Possibility Architecture may need to understand the conditions under which a new commercial model could succeed, and Reality Architecture establishes the actual position that understanding is tested against. Intelligence connects the knowledge, evidence and interpretation without taking ownership of the subjects it helps explain.

Explore Intelligence Architecture →

09 · PARTICIPATIONWorkforce Architecture

What participation is required, and who or what will fulfil it?

Work begins with a requirement for participation, well before anyone draws an organisational chart. Workforce Architecture establishes the roles that enterprise work requires and determines how those roles are sourced, fulfilled, structured and assigned.

A role may be filled by a person, an intelligent agent or an organisation, and it is a different thing from a job title or a box on a chart. A business can build a capability internally, buy it as a service or partner for it. Each choice changes how participation is arranged and leaves the underlying role requirements in place, so different fulfilment models can be compared without mistaking the current workforce for the work.

Explore Workforce Architecture →

10 · ENABLEMENTEnvironment Architecture

What physical and technological enablement must be provided, and how will that requirement be fulfilled, for the enterprise’s instructions to be executable as intended?

Work needs an environment in which it can be performed: physical facilities, equipment, technological infrastructure, applications and, for intelligent agents, execution environments.

Environment Architecture establishes the physical and technological enablement required for instructions to be executable as intended. It starts from what execution requires, where most technology planning starts from an inventory of what the organisation owns. A motorcycle workshop needs hoists, tools and floor space before a service can be done properly. A digital service needs the right technological resources. An agent needs an execution environment that supports its assigned activities within its constraints. The architecture connects each requirement to its fulfilment and keeps resources, participants and instructions distinct.

Explore Environment Architecture →

11 · RELIANCETrust Architecture

What can be relied upon, under what conditions, and with what authority?

Enterprises run on reliance. Customers rely on businesses to keep commitments. Executives rely on information when they decide. Teams rely on instructions, systems and one another, and automated mechanisms increasingly act on information and conditions established somewhere else.

Reliance is not warranted just because something exists, is accessible or has worked before. Trust Architecture establishes the conditions under which reliance between parties is warranted, and how that reliance is established, maintained, changed, transferred, lost and restored. It keeps trust distinct from technical access, authority, confidence and assurance, which matters whenever an enterprise delegates activity, automates decisions or depends on long chains of participants and systems.

Explore Trust Architecture →

Separate by meaning. Connected by design.

The eleven are designed to work together. Consider a Brisbane furniture maker deciding whether to start selling in New Zealand.

Directional Architecture holds the strategic choice itself. Domain Architecture identifies the capabilities the move requires. Ecosystem Architecture examines the freight partners, retailers and regulators the business would come to depend on. Possibility Architecture keeps the alternatives open: export from Brisbane, license a local manufacturer, or open a showroom. Intelligence Architecture develops the understanding needed to assess them. Execution Architecture defines how the chosen work would be performed, Workforce Architecture the participation it requires, and Environment Architecture the facilities and technology that make it executable. Expression Architecture considers how the identity and value of the business should be presented to a new audience. Trust Architecture establishes what customers and partners can rely on, and under what conditions. Reality Architecture captures what actually happens once the arrangements are operating.

One decision, examined through eleven concerns. No architecture has to take ownership of another’s propositions, and the enterprise stays connected because the relationships between those propositions are explicit.

The set has no sequence

Nothing requires Directional Architecture to be finished before Domain Architecture is examined, or capabilities to be fully documented before Workforce or Environment is considered. Questions arise when they arise. A change in operating reality challenges a strategic assumption. A workforce constraint reveals a capability requirement nobody had understood. An emerging possibility exposes dependencies that need investigating.

A sequence is often useful for running a workshop, designing a solution, investigating a problem or presenting information. That sequence is a choice made by the application, and it establishes no hierarchy within the set.

From one person to a complex enterprise

A founder developing a new business may start with a handful of architectural propositions. A mature enterprise may need extensive detail across its capabilities, relationships, operating arrangements and dependencies. The amount of architecture differs and the distinctions hold: a role is still different from a participant, a capability from an instruction, an intended outcome from an actual position.

The discipline does not have to be replaced when the enterprise outgrows what one person can understand. Its architectural knowledge becomes more detailed, more interconnected and more extensively supported by technology.

Built for an operating model that can change

AEA prescribes no operating model, whether human-led, automated, hybrid or agentic. It makes no assumption that capabilities sit inside the organisational boundary, that technology stays passive or that work is done by people. The enterprise can change how its work is fulfilled while the architectural meaning of the work is preserved.

This matters more as intelligent agents become capable participants in business operations. Asking which tasks an agent can perform is only the start. The fuller questions are what work is required, how it must be performed, who or what may participate, what enablement is necessary and under which conditions reliance is warranted. The eleven architectures supply the distinctions for examining those coherently.

One enterprise. Eleven dimensions.

The value of the separation lies in preserving meaning while understanding relationships. An enterprise can change its workforce without necessarily changing its capabilities, and its technology without necessarily changing its operating instructions. It can explore a possibility without committing to it, hold an intended design while acknowledging a different operating reality, and use information without assuming the information warrants reliance.

Connected, those distinctions let a business be understood as something greater than the sum of its functions, processes and systems. Precision of separation enables coherence of composition.

The standards behind this page

Each of the eleven is established through its own governed Architecture Standard. The Standards Library gives an introduction to each, followed by the complete publication. The Architecture Set Standard holds the rules that keep the eleven coherent, and AEA Design records what happened when the eleven were applied to the discipline itself.

Continue with the principles, the hybrid enterprise or the Body of Knowledge.

Keep readingEvery enterprise is shaped by the choices it makes about where it intends to go.Topic · Directional →
→Continue

Where to go next.