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

Operating model design in AEA by Ivory & Co.Design the business. Then decide how it will operate.

What a business requires and how it meets that requirement are separate questions. Keeping them apart lets a business examine different ways of operating, and see the gap between what it designed and what is really happening.

Imagine a business that receives five hundred customer enquiries every day.

Some are simple. A customer wants to know whether an order has shipped, when a product will arrive or how to arrange a return. Others need judgement. A delivery has failed. A product is unsuitable. A customer has been charged incorrectly, and someone has to work out what happened and what to do about it.

The business handles these with a customer service team: twelve employees, a team leader, a CRM, a knowledge base and a set of operating procedures.

Then the CEO asks a question. Could we run this function with three people and AI agents?

It is a reasonable question. Answering it takes far more than comparing the cost of twelve salaries with three salaries and a subscription. We need to know what the business actually requires, what its current arrangements deliver, and what would have to be true for a different arrangement to work.

Operating model design starts with the requirement

A customer contacting a business has little interest in how it is organised. They want a question answered, a problem resolved or a request completed.

The business has obligations to meet. It must understand the enquiry, reach the right information, decide what action is required, take that action within the conditions that apply and communicate the result. Different enquiries call for different abilities, instructions, information, participants and levels of authority.

Those requirements exist whether the business employs twelve people, engages an outside provider or introduces AI agents. How they are fulfilled can change a great deal.

That gives business design a different starting point. We begin with what the enterprise needs to be capable of achieving, and then examine the arrangements that could achieve it.

It sounds obvious, and most management runs the other way. We inherit an organisation with its people, systems, processes and suppliers, and try to improve the business by adjusting them. Sometimes that is exactly what is needed. At other times the arrangements themselves limit our ability to imagine a different enterprise.

When the organisational chart becomes the business

A professional services company began with a founder and a handful of employees. Everyone understood the customers, the services and how the work was done. As demand grew the founder hired specialists, and over time the business acquired departments, management positions, reporting lines and procedures.

A decade later the leadership team begins a transformation programme, and its first act is to review the organisational structure. It finds duplicated roles, inconsistent responsibilities and teams that could be consolidated. A new structure is designed.

There is a question worth asking before the boxes are moved. What is the business trying to change?

Perhaps work moves slowly between departments. Perhaps customers experience inconsistent service. Perhaps the business lacks a capability it now needs, or is meeting an existing need through arrangements that no longer make commercial sense. Each problem points to a different design response. Changing reporting lines may help. It may also leave the real problem untouched.

An organisational structure shows how an enterprise is arranged. It cannot explain every requirement that arrangement exists to serve. Confuse the two and we redesign the visible organisation while the underlying enterprise stays much as it was.

One requirement. Several ways to fulfil it.

Return to the customer enquiries. The business examines three arrangements.

Employees

A customer service team receives enquiries, finds information, follows procedures and resolves matters within its authority. People can read context, exercise judgement and escalate what needs more thought. The business must supply skills, training, information, systems and supervision. The arrangement offers flexibility and direct control, and its capacity and cost follow the size of the team.

An external provider

The business engages a specialist organisation to handle some or all enquiries. The customer’s requirements are unchanged, and a new set of considerations appears. The business must settle what the provider is expected to deliver, what information it may see, how performance will be understood, what decisions it may make and how exceptions are handled. Outsourcing the activity leaves the obligation to the customer exactly where it was.

AI agents supported by employees

Agents handle routine enquiries, retrieve information and complete certain permitted actions. Employees manage exceptions, complex cases and anything that needs human judgement or specifically assigned authority. The volume and distribution of human work changes substantially, and new requirements appear for monitoring, access, escalation and assurance. Whether an agent can complete a task is only one consideration in deciding whether it should be allowed to.

What actually changed?

All three arrangements serve the same recognisable requirements. Their costs, dependencies, operating conditions and limitations differ considerably. The business may choose one, combine several or design something else.

Sometimes examining the alternatives reveals that the requirement itself should change. Perhaps proactive communication would remove whole categories of enquiry. Perhaps a recurring service problem should be fixed at its source. Perhaps the business has been funding a large customer service operation to compensate for weaknesses elsewhere.

Once the requirement and its fulfilment can be told apart, the design conversation becomes much more interesting.

Designed and actual are different questions

There is a second distinction businesses often overlook. What has been designed and what is operating may differ.

A business may have a carefully documented customer service model. Procedures specify how enquiries are classified, how long resolution should take and when a matter must be escalated. The organisational chart assigns responsibilities, the CRM holds the workflows and the staff have been trained. On paper the arrangement is complete.

In practice, employees bypass the CRM because its workflow is too cumbersome. The knowledge base contains outdated instructions. Escalation works during business hours and breaks down when the responsible manager is away. An AI agent has been configured to do something that was never in the approved design.

The designed arrangement says how the enterprise is intended to operate. The actual arrangement is what is occurring. A business needs to understand both, or its leaders will make decisions about the organisation they believe they have.

Consider what that means for the CEO’s question. If the design says twelve people do the work, and in reality four handle most complex cases while the others spend much of their time correcting upstream errors, the opportunity looks very different. It stops being a matter of swapping a number of people for technology. The business can now examine the work, the causes of demand and the arrangements that would serve its requirements better. That is a sounder basis for investment.

The economics of fulfilment: build, buy, partner or automate

Every fulfilment choice has commercial consequences. Some are visible at once: employment costs, supplier fees, software subscriptions, infrastructure, training and implementation.

Others emerge through the dependencies the arrangement creates. A low-cost provider may bring contractual constraints and extra coordination. An automated process may cut handling costs while raising the importance of information quality and exception management. An internal team may cost more directly and provide flexibility, specialist knowledge or customer relationships worth far more.

Suppose an AI agent costs a fraction of a salary. That tells us the price of one resource. It says much less about the total cost of fulfilling a business requirement, which also includes the surrounding work, information, technology, monitoring, authority, reliability and exception handling.

Equally, nothing obliges the business to preserve every existing activity when the fulfilment changes. Automation can remove work, reshape a service or make possible something that was previously uneconomical. The most valuable question may be whether the business should keep doing the work in the same way at all.

Freedom to choose requires precision

The more precisely a business understands its requirements, the more freely it can examine how to meet them. This reaches well beyond workforce design.

A business may require a technological capability without prescribing a software product. It may need specialist expertise without employing it permanently. It may need physical distribution without owning the infrastructure. It may need a commercial relationship without assuming a particular contractual form.

Some requirements do carry conditions of fulfilment. A physical service may need presence at a location. A regulated activity may be restricted to authorised participants. A customer promise may depend on a particular kind of interaction. Independence from current arrangements means establishing those constraints deliberately, so that none of them survives merely because nobody examined it.

This matters most with new technology. If the enterprise is described entirely through the systems and employees it has today, a new technology will be assessed as a replacement for something familiar. If its requirements are understood independently, the same technology can be examined as one component of a different operating arrangement. That is a much larger design opportunity.

What remains when the fulfilment changes?

Suppose the business adopts the hybrid arrangement. Three employees supervise and support a set of AI agents. Routine enquiries are handled automatically, complex matters are escalated and certain actions require explicit approval.

Some underlying requirements are exactly as they were. Others need refining, because the new arrangement brings different abilities, dependencies and constraints. The distribution of work has changed, along with the participants, the enabling technology and the conditions under which an action can be accepted. The business must also establish whether the new arrangement is performing as intended.

So architecture and fulfilment can be told apart, and they remain connected. A change in fulfilment can expose weaknesses in the original design, create new opportunities and call for further decisions. The distinction lets a business examine those consequences while staying clear about what each decision concerns.

The implications for an adaptive enterprise

Businesses have always changed how they fulfil their requirements. They have hired employees, engaged contractors, outsourced services, bought technology, formed partnerships and reorganised. What is changing is the range and speed of the alternatives.

Most businesses know in considerable detail how they currently operate. They are less practised at describing what the business requires independently of those arrangements, and that makes transformation needlessly dependent on the past.

Architecture should make a business composable and collapsible: able to assemble new capabilities quickly and exit old ones cleanly, without structural damage. For a small business, that can mean access to capabilities once available only to much larger organisations. For a complex enterprise, it offers a clearer basis for redesigning arrangements that have accumulated over decades.

For both, the question is the same. If we were designing this business today, knowing what is now possible, how would we choose to fulfil its requirements?

It is a question worth answering before the next restructure, technology investment or automation programme begins.

Keep readingWhen the workforce is no longer entirely human.Knowledge and research · Hybrid enterprise →
→Continue

Where to go next.