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

Change impact across a business, in AEA by Ivory & Co.An enterprise is a system of consequences.

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.

Change a strategy and you may change the capabilities the business requires. Change how a capability is fulfilled and you may introduce new participants, new technology, new dependencies and new conditions of reliance.

Change a customer promise and the consequences travel well beyond the team that delivers it. Very little in a business changes alone.

Yet businesses are routinely described as though it does. Strategy lives in one document and processes in another. Organisational structure is maintained apart from technology. Customers are understood through sales and service platforms, while risk, authority and performance are examined somewhere else again.

Each view may be accurate within its own boundaries. The difficulty begins when we assume that understanding each view means we understand the enterprise.

The problem with understanding things separately

Consider a business that changes who does a piece of customer work. At first glance this is a people decision, or perhaps a technology one. But what, exactly, is changing?

The work may stay substantially the same while the participant doing it changes. Or the new participant may open the way to redesigning the work itself. Either way the business still has to settle what the work requires, what information it needs, what has to be in place for it to run, what authority is appropriate and under what conditions the result can be relied upon.

Those are different questions. Answering one does not answer the others.

What an interlock is: dependencies between business concerns

Adaptive Enterprise Architecture describes one enterprise through distinct architectural concerns. They are deliberately separated, so that each keeps a precise meaning and a single owner. They are also connected, because the enterprise itself does not run as a set of independent systems.

An interlock is the relationship between those concerns. One concern can create a need that another must satisfy, and neither takes over the other’s ground. A relationship of this kind connects two things that are each owned somewhere. It never produces joint ownership.

That is why three familiar confusions matter so much:

  • Information about a thing is a different matter from the thing. A report on a capability does not own or define that capability.
  • Understanding a risk confers no authority to accept it. Knowing and deciding sit in different places.
  • Identifying a dependency changes nothing by itself. The dependent part has not moved until someone with the standing to move it does so.

Why ownership matters

Imagine an enterprise changes its strategic direction. That may require it to reconsider which capabilities it needs, how work should be performed, who or what takes part in that work, and what enabling conditions must exist.

Those consequences can be examined together. But the strategic choice does not, by itself, settle every question downstream of it. Each of those questions still has to be answered where it belongs.

This prevents one of the most common failures in organisations: a single decision being treated as though it had silently resolved a dozen questions that nobody actually considered. The relationship makes the consequences visible. Ownership keeps the answers honest.

Relationships are part of the architecture, and they move

It is tempting to think of these connections as wiring: drawn once, then left alone. They behave differently. When something changes on one side of a relationship, whatever depends on it may need to be looked at again, and the answer on the far side may change the conditions for the next choice on the near side.

So a description of an enterprise is incomplete if it only covers what is inside each concern. You also need to know what each one requires from elsewhere, what it contributes elsewhere, and what must be reconsidered if either side changes.

Change impact: six questions to ask before a change

Businesses usually assess change through projects, budgets, organisational charts or individual systems. Those views are useful, and they can miss most of what a change reaches. An architectural view adds a different set of questions.

  • What part of the enterprise is this meant to change?
  • What else depends on the thing being changed?
  • What stays the same?
  • What is known, and what still has to be determined?
  • Which consequences are possibilities, and which are established?
  • Whose authority is needed before the proposal becomes the way the enterprise actually is?

Nobody can predict every consequence. The aim is to make the basis of the assessment explicit, and to stop a proposed future being mistaken for the enterprise that exists today.

Distinct concerns. One connected enterprise.

Strategy, process, workforce design and information management have each been studied for decades, and AEA did not invent them. Its contribution is the deliberate separation of those concerns and their composition into one coherent account of the enterprise.

An interlock, then, is more than a line on a diagram. It is part of what makes the enterprise intelligible as a whole, because the real consequence of a business decision is rarely confined to the place where the decision was made.

Not yet publishedThe interlock model itself: which concerns relate, how those relationships are classified and how they are represented.

Keep readingDesign the business. Then decide how it will operate.Knowledge and research · Architecture and fulfilment →
→Continue

Where to go next.