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

Change consequences in AEA by Ivory & Co.Every decision creates a different enterprise.

A proposal, an authorised decision, its assessed consequences and what actually changes are four different things. Keeping them apart lets a business see what a choice will reach before it commits, and learn honestly from what follows.

A retailer decides to introduce a thirty-day returns policy.

The idea is commercially attractive. Competitors offer similar terms, customers have been asking for more flexibility and marketing believes it will improve conversion. The executive team agrees. A new policy is approved, marketing updates the website and customer service receives the announcement.

The business now offers thirty-day returns. Except the warehouse is still working to the previous arrangements. Finance has not assessed the effect on refunds and working capital. Franchise operators have different contractual conditions. The customer service system still applies the old eligibility rules. And nobody has settled what happens when a product comes back after thirty days from a customer who never saw the new terms.

The decision has been made. The enterprise is not yet capable of delivering it consistently.

A business decision can be made in a meeting, recorded in a document and communicated in a sentence. Its consequences are rarely so neatly contained.

A decision travels further than its owner

Businesses organise responsibility through functions, departments, roles and management structures. Those arrangements are necessary. They establish accountability, allow specialisation and let work be coordinated. The consequences of a decision pay them no attention.

A pricing decision changes customer demand, revenue expectations, sales behaviour, contractual obligations and operational capacity. A technology decision alters how work is performed, what information becomes available, who needs to be involved and what the business now depends on. Entering a new market brings unfamiliar customers, suppliers, regulations and capabilities.

Consider a manufacturer that decides to reduce its product range. The commercial argument is compelling: fewer products should simplify inventory, reduce purchasing complexity and improve production efficiency. But what happens to customers who rely on the discontinued products? To supplier agreements built on minimum purchase quantities? To spare parts, warranties, sales incentives and the knowledge needed to support products already in the market?

The decision may be perfectly sound. Whether it succeeds depends on understanding what else it touches. A decision can be correct in isolation and poorly designed for the enterprise that has to absorb it.

Deciding and changing are different events

Return to the returns policy. Several distinct things are happening. Someone proposes extending the returns period. The business examines the proposal. An authorised decision-maker approves it. The organisation prepares the arrangements needed to support it. Those arrangements are introduced. The business begins operating under the new conditions.

These events may sit close together in time, and each is a different thing.

A proposal describes something under consideration. A decision establishes what has been authorised, within its scope. Implementation is the work required to give effect to the decision. Actuality is what has really changed.

A business can approve a change that has not been implemented. It can implement part of a change while the rest remains incomplete. It can find that operations differ from the arrangements it meant to establish.

This matters because organisations so often announce decisions as though they were completed changes. A board approves a new operating model and the organisation declares that it has transformed, while the underlying capabilities, work, systems, relationships and behaviour still reflect the old model. The approval was real. So was the intention. Neither establishes that the intended enterprise now exists.

Change impact: understanding what could happen before the decision

Suppose the retailer has not yet approved the policy, and the leadership team wants to understand the consequences first.

The commercial team expects more sales. Operations anticipates more returned products. Finance is concerned about cash flow. Customer service expects fewer complaints about eligibility and more enquiries about refunds.

Each view contributes something. The challenge is seeing how they relate. Extra sales may be offset by handling costs. A longer returns window may change how inventory is managed. A customer-friendly promise may carry different obligations in different sales channels. The business may need to change how it operates before it can keep the promise at all.

None of this is a reason to reject the proposal. It is what adopting the proposal would mean.

Some of it will stay uncertain. The business has reliable history on returns under the existing policy and very little evidence about behaviour under the new one. It can estimate, model scenarios and test assumptions, and what it produces is still an assessment. Examining a proposal improves the quality of the choice in front of leadership. It cannot supply certainty about the future.

A proposal deserves room to remain a proposal

Businesses generate possibilities constantly. What if we stopped manufacturing this component ourselves? What if customers could configure their own products? What if a specialist provider took over an internal function? What if an AI agent performed work that currently needs several employees?

Questions like these are commercially valuable long before the business is ready to decide anything. Turn them into formal change programmes too early and exploration narrows: the organisation starts defending a solution before it has examined the alternatives. Leave them drifting and they never become clear enough to assess or act on.

An adaptive enterprise makes room for both exploration and determination. A possibility can be investigated, challenged, refined or abandoned. Some possibilities eventually become proposals for consequential change. Most do not, and that is how it should be.

Authority changes the status of a decision

Imagine the retailer’s marketing director announces the new returns policy before the executive has approved it. The director believes the change is commercially necessary. The policy may be sensible, the evidence persuasive, and the business may go on to adopt exactly that arrangement.

The announcement still raises a separate question. Was the director authorised to make that commitment on behalf of the enterprise?

A recommendation can be well founded without being authorised. An employee can have the expertise to assess a matter without the right to determine it. An AI agent can have the technical ability to change a system without permission to make the underlying business choice.

Authority matters because decisions create obligations and consequences for other people. The business needs to know what has legitimately been determined, by whom, within what scope and under which conditions. That becomes harder, and more important, as decisions are spread across people, outside organisations and increasingly autonomous technology. Without it, activity acquires the appearance of legitimacy simply because it happened.

The consequences nobody intended

Some consequences are obvious. Others arrive through dependencies nobody could see when the decision was made.

A business introduces a new commission structure for its sales team to encourage growth. Salespeople respond with enthusiasm and revenue rises. Over time the business finds that the structure rewards new sales far more than customer suitability or retention. The team begins favouring the transactions that maximise commission. Complaints increase. Refunds increase. Some customers leave.

The commission structure achieved its immediate objective and changed behaviour elsewhere in the enterprise.

Businesses do not always behave as their designers expect. People respond to incentives, customers to experiences, suppliers to commercial terms, and technology to its configuration. A decision changes the conditions in which all of them act. Seeing the enterprise as a connected whole improves the chance of spotting these effects before they become expensive. It offers no guarantee that every consequence can be predicted.

When consequences become visible

The retailer implements the policy. Three months later sales have increased, and the commercial hypothesis looks promising. Returns have also increased, and the warehouse is running behind. Finance reports that refunds are taking longer to process. Customer service is seeing more complaints about inconsistent eligibility decisions.

What should leadership conclude? The policy may be a commercial success despite its operational problems. It may be exposing weaknesses that were already there. The additional costs may eventually outweigh the benefit.

The business needs evidence, and it needs to understand what the evidence establishes. A rise in returns does not prove the policy was a mistake. A rise in sales does not prove it worked. The enterprise has to keep apart what it expected, what it has observed and what can reasonably be concluded. That is how experience becomes useful to the next decision.

Knowing what is actually operating

A business can have several versions of its arrangements in circulation at once. The approved policy sits in a document repository. A different version is configured in the customer service system. Employees are following instructions from an earlier training session. An outside provider is still working to the previous contract.

Which one is the enterprise’s actual position? Often there is no single answer. Different parts of the business adopted the change at different times, and some of it remains incomplete or unknown.

This matters because a proposed future cannot be meaningfully compared with a present that is poorly understood. An approved design is no evidence that the business has implemented it. The enterprise needs to stay explicit about what has been established, what is operating and where its information runs out.

Every choice affects the choices that follow

Decisions also change what becomes possible next.

A retailer that invests in a highly specialised warehouse improves its existing distribution and makes other fulfilment arrangements more expensive to adopt. A manufacturer that develops a proprietary production capability opens the way to new products and markets. An exclusive supplier agreement secures favourable terms and closes off other relationships. Building operations around one technology platform brings efficiency along with dependencies that will shape future investment.

All of these may be entirely appropriate. Every strategic choice involves trade-offs, and the trade-offs mean more when leadership can see them as part of how the enterprise is evolving. A decision moves the business from one condition to another, and it expands, narrows or redirects what is available afterwards. Strategic choices deserve to be examined against the enterprise they may create as well as the outcome they are expected to deliver.

The discipline of consequential change

As businesses grow more complex, the distance between making a decision and understanding its consequences widens. A leadership team can approve a change that affects hundreds of processes, systems, relationships and participants. An AI agent can initiate actions across several applications in seconds. An operating model can be redesigned while parts of the organisation carry on under the old one.

Adaptive Enterprise Architecture gives a business a way to keep a coherent understanding of itself through that movement, by holding five questions apart.

What could we do? What have we decided? What might follow? What has actually changed? And what does that mean for the enterprise now?

The answers move as evidence arrives. A decision may need reconsidering. An implementation may reveal dependencies nobody foresaw. An outcome may differ from what was expected. The enterprise should be able to understand those differences without blurring them, and without rewriting the history of what was intended.

The returns policy was always more than a marketing decision. It was a commercial choice with implications for customers, operations, finance, technology, staffing and outside relationships. The business may still choose to proceed, and may judge the operational disruption worthwhile. That choice carries more weight when the consequences are visible and the assumptions explicit.

Risk and uncertainty remain part of business. The quality of a decision depends on how well we understand what it may change.

Not yet publishedHow AEA traces consequences through the architecture.

Keep readingWhat makes an enterprise capable of adapting without losing coherence?Knowledge and research · Adaptation →
→Continue

Where to go next.