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

AEA by Ivory & Co. principlesPrecision of thought changes what becomes possible.

Seven principles keep a business’s knowledge of itself meaningful as it grows and changes. Each is shown here through an ordinary business situation.

A business can change its organisational structure without changing how it operates. It happens remarkably often.

A new CEO arrives. The business announces a restructure. Departments are combined, reporting lines change, leadership positions are renamed and a new organisational chart is circulated. For a few weeks, everyone is busy adjusting.

But customers still meet the same problems. Decisions still travel through the same bottlenecks. Teams still depend on information they cannot easily reach. The underlying work is substantially unchanged.

The organisation has been rearranged. Whether the business has been redesigned is another question entirely, and it is a useful place to begin. Before we can deliberately change an enterprise, we need to be precise about what we are changing.

Why business architecture principles matter

In a small business, people resolve ambiguity through conversation. The founder knows what was intended. The operations manager understands why an exception exists. Someone remembers the decision that led to a particular arrangement.

As the business grows, that shared understanding becomes harder to hold. Knowledge spreads across people, departments, systems and outside relationships. Specialists develop their own vocabularies and their own pictures of the enterprise. Eventually the business can possess an enormous amount of information about itself and still be surprisingly difficult to understand.

The principles of Adaptive Enterprise Architecture describe what it takes for a business’s knowledge of itself to stay meaningful, coherent and usable as that complexity increases. They rest on one proposition: we must be able to distinguish things before we can reliably understand how they relate.

1. Preserve the meaning of what you are describing

A leadership team agrees that the business needs to improve its customer service capability. It sounds like a clear decision, until the discussion turns to implementation.

One executive proposes hiring more people. Another wants a new CRM. Operations recommends redesigning the complaints process. Finance wants to know whether the existing team is productive enough. Each recommendation may have merit, and each is an answer to a different question.

The capability the business requires, the work needed to realise it, the people who take part and the technology that enables them are related concerns with different meanings. When those distinctions are lost, a business can invest heavily in a solution without having established the requirement it was meant to satisfy.

Words such as capability, process, role, system, outcome and control are used everywhere in business, and their familiarity conceals real differences in meaning. Agreeing on terminology helps. Precision asks for more: knowing what a concept describes, where its meaning begins and ends, and how it relates to its neighbours.

The benefit is practical. A business can examine several ways of meeting the same requirement without redefining the requirement each time. That creates room for better choices.

2. Understand the whole without losing the distinctions

Finance, operations, strategy, people, technology, marketing and risk each bring knowledge the business needs. The enterprise, however, does not operate within the boundaries of those disciplines. Each specialist can be right about their own concern while the combined result is still a problem.

Take a business introducing a premium delivery service. Marketing establishes the proposition. Finance approves the commercial assumptions. Operations designs the delivery arrangements. Technology configures the supporting systems. Every function completes its assigned work, and the service launches.

Then the problems begin. The customer promise assumes delivery conditions that operations cannot consistently meet. The pricing does not account for certain fulfilment costs. The systems capture transactions but give little visibility of exceptions.

Each contribution may have been well executed. The relationships between them were poorly understood. The quality of the whole depends on more than the quality of its parts, so we need to know what each concern contributes, what it requires, and what follows when something changes.

3. Separate what the business requires from how it is currently fulfilled

Return to the restructure. Six people respond to customer enquiries. The new design combines their team with another department, changes the manager’s title and redistributes reporting lines.

Has the business changed how customer enquiries are handled? Possibly, but the organisational changes alone do not establish it. The underlying requirement may be exactly as it was. Customers still need information, assistance and resolution, and the business still needs the ability to respond.

How that requirement is fulfilled is a separate design question. The business could use employees, an external provider, AI agents or a combination. It might redesign the work, keep the existing arrangements, or find that different enquiries need different approaches.

A building architect designs the frame, the walls and the way the building will be used before anyone moves in. Business architecture works the same way. Describe the business first. Then fit the people, the systems and the capabilities into a structure that already makes sense.

An enterprise whose architecture is inseparable from its current employees, departments and systems will struggle to examine a different way of operating. A business that understands its requirements independently has more freedom in how it meets them.

4. Keep intention, evidence and actuality distinguishable

A retailer sets a target of reducing customer returns by twenty per cent. The target appears in the strategy. A project is launched, new procedures are introduced and a dashboard is built to monitor progress. Six months later the dashboard reports a substantial improvement.

Has the business achieved what it intended? Several questions remain. Was the measure defined consistently? Did the business change what it counts as a return? Has the customer experience improved, or have customers simply found returns harder to make? Does the evidence support the conclusion being drawn?

A strategy records an intention. Evidence contributes to understanding. Actuality concerns what is really occurring. Each plays a different part in business judgement, and organisations regularly confuse them: the existence of a plan is taken for progress, and the availability of a measurement is taken for certainty about what it means.

The same care applies to the future. A proposed operating model may look financially attractive, and a technology may show promising results. Those findings deserve consideration. They do not establish that the proposed future already exists, or that its assumptions have been met.

5. Preserve responsibility when the participants change

A business introduces an AI agent to handle routine supplier enquiries. It performs well in testing. It retrieves information, answers questions and completes permitted administrative tasks.

Then a supplier asks it to approve a change to payment terms. The agent has access to the relevant records. It understands the request. Technically, it may even be able to make the change.

Capability, access and authority are three different questions. The ability to perform an action does not establish that the action has been authorised. A successful result does not, by itself, show that the enterprise has met its responsibilities.

Changing the participant can change the operating arrangement considerably. The questions of authority, accountability and reliance are still there to be answered. These principles let a business examine them without assuming that every role must be filled by a person, or that every piece of technology is a passive tool. The opportunity is substantial. So is the need for precision.

6. Make uncertainty visible

Businesses are expected to make decisions with incomplete information. That is a normal condition of enterprise. The trouble starts when uncertainty disappears from the record because a decision had to be made.

An assumption becomes a planning figure. The planning figure enters a business case. The business case is approved. Months later the original assumption is repeated as though it were an established fact. Nobody set out to mislead anyone. The information lost its context as it travelled.

An expansion proposal built on an expected rise in demand may be entirely reasonable, supported by market research, customer enquiries and past performance. It remains a forecast. A disciplined enterprise keeps what is established apart from what is anticipated, so that leaders can revisit assumptions as evidence arrives and avoid stacking further decisions on certainty that was never justified.

Uncertainty becomes manageable when it stays visible.

7. Allow the architecture to evolve without losing coherence

An adaptive enterprise must be capable of change. The harder question is how it changes without undermining the meaning of what it has already established.

Businesses constantly introduce new processes, technologies, operating arrangements and management practices. Some reflect new requirements. Some are different ways of meeting existing ones. Some replace arrangements that are no longer useful. Without a coherent foundation, each change brings new terminology, duplicated responsibilities or a competing account of how the business works. Over time the enterprise becomes harder to understand precisely because it has been changing.

Established knowledge can be authoritative and still open to challenge when evidence shows it to be insufficient. But change needs discipline. A new technology does not, by arriving, create a new fundamental concern of business. A new management technique rarely needs a new category of its own.

Adaptability depends on recognising what is truly different, what remains valid and what needs to be reconsidered.

What happens when these principles are ignored

Back to the restructure. The new organisational chart is complete. Reporting lines are clear, job descriptions are updated and managers know their teams. Customer complaints continue to rise.

The organisation changed its structure without examining the requirements that structure was meant to fulfil. It moved responsibilities without reconsidering how work flows between them. It left critical dependencies untouched. And it judged the restructure by whether the new structure was implemented, when the real test was whether the business became more capable of delivering what it intends.

None of this guarantees that every business decision will be correct. It improves the conditions under which decisions can be understood, challenged and made.

The discipline behind adaptability

The word adaptive is often associated with speed: faster decisions, faster delivery, faster responses to markets and technology. Speed can be valuable. A business can also move quickly in the wrong direction. It can automate an unsuitable process, reorganise around a temporary problem or scale an arrangement whose weaknesses are not yet visible.

The more consequential opportunity is to make change deliberate. A business that can describe itself can move. A business that cannot will stall: slowly in stable markets, quickly in volatile ones.

The more precisely we understand an enterprise, the more deliberately we can design its future.

The formal Meta-Laws and Architecture Set Principles are set out in the Architecture Set Standard.

Keep readingEleven ways of understanding one enterprise.AEA by Ivory & Co. · The eleven architectures →
→Continue

Where to go next.