PERSPECTIVES · THE CONNECTED ENTERPRISE
The Connected Enterprise in an Age of Disruption
Designing the organisation around decisions, dependencies and value
The Connected Enterprise is an architecture for making decisions across an organisation.
The Connected Enterprise is an architecture for making decisions across an organisation. It is not an organisation chart, a technology stack or simply a set of connected systems. Those things may support it, but the starting point is the business: how value is created, which decisions shape it, and what information people need to make those decisions well. Processes, roles, assets, partners and technology should connect around that logic.
At its centre is a recurring set of questions: what is happening, what might it mean, which decision does it require, who has the mandate to make it, and what outcome will show whether the assumptions were sound? The article follows one example—a manufacturer deciding whether and how to take on a large customer contract—to show how those questions connect the enterprise.
01
An organisation can become more efficient and still be unprepared
Many improvements deliver real benefits. Automation reduces manual work. Better reporting makes information easier to use. Analytics surfaces deviations sooner. Approaches such as Total Quality Management, Just in Time and Agile can help solve specific problems. AI can support analysis, forecasting and work with information.
But these gains do not answer a more fundamental question: is the organisation making the right decisions, and does its current way of operating still fit the environment? A company can become faster at producing work that is no longer needed. It can improve one function while shifting cost or risk elsewhere. Local optimisation can make a part of the business look better without strengthening the whole.
The Connected Enterprise offers a different starting point. Instead of beginning with a departmental chart or a list of applications, we ask: which decisions matter, what information do they require, who has the authority to make them, which dependencies affect their outcome, and how will the organisation learn what happened?
02
Decisions are continuous, even when change is not dramatic
An organisation does not need to wait for an exceptional event before it pays attention to its environment. Every day it makes decisions about customers, products, prices, suppliers, production, people, assets, funding and risk. It therefore needs an ongoing view of where it stands: what is changing in the market, what capacity it has, where constraints are emerging and which assumptions may no longer hold.
Consider a multi-product manufacturer that receives an offer for a large contract. The opportunity involves a new customer, a proposed volume and product mix, a price, delivery dates and payment terms. The company must decide whether to accept, renegotiate, phase delivery, acquire additional capacity, involve a partner or decline.
The offer should not be the first moment when the company tries to understand how its functions depend on one another. It is a stress test of whether the organisation already has the information, decision rights and working relationships needed to respond without improvising under pressure. Similar tests can be run in advance through scenarios. If the offer reveals a gap, it is a signal to examine readiness—not a reason to make a hurried commitment before the organisation understands the consequences.
The decision also continues after the offer is accepted. It shapes credit and payment terms, capacity allocation, purchasing, production, quality control, delivery, invoicing, collections and the cash forecast. Each step changes what is possible at the next one. A quote can look attractive and still create a weak outcome if the promise cannot be delivered as planned, if quality problems delay invoicing, or if payment terms create a funding burden the original calculation missed. A connected view follows the decision through the work and back to the result.
03
The purpose is value creation, not a single number
Return on capital, EBITDA, cash flow, margin and asset utilisation all matter. None is a complete definition of value on its own. A decision that improves this quarter's return can weaken future capability; an investment that depresses near-term profit can create a stronger position over the life of the business. The relevant question is not simply whether an initiative produces a profit, but how it affects the organisation's capacity to create value over time.
That requires a shared view of the intended outcome and the measures that make it visible. Financial results belong in that view, alongside customer outcomes, quality, resilience, risk, capabilities and the future use of capital. The measures should inform judgement, not replace it.
04
Market signals should reach beyond today's customer base
The organisation needs to listen to current customers and to people who do not yet know the company, do not choose its products or cannot find an offer that fits their needs. Marketing can help maintain this market view by analysing searches, enquiries, conversations, complaints, buying behaviour and changes in customer segments. For example, repeated searches for a product feature that the company does not offer may be a signal to investigate. It does not, by itself, prove willingness to pay.
A signal may lead to a hypothesis about a new feature, product, premium tier or customer segment. Research and Development should work close to the business and the customer while bringing its own understanding of technology, quality, cost and manufacturability. A minimum viable product or limited offer test can then establish whether the interest is real and whether the economics of delivering it make sense. The result returns to the same decision system: whether to scale the offer, refine it, or stop it, given its effect on capacity, sourcing, quality and value.
This connects market insight to operations. A feature customers will not pay for may add complexity, burden production and weaken margin. A modest product change, on the other hand, may open an attractive segment if the company can deliver it at the required scale and cost.
05
One commercial decision can change the whole system
The decision on a contract is not just a comparison between price and unit cost. Price affects demand; demand affects capacity and customer mix. The mix changes scheduling, set-up time, quality yield and scrap. Production affects material requirements, supplier availability, inventory, transport, warehousing and energy use.
Payment terms affect receivables, working capital, funding cost and liquidity. New machinery, floor space or energy infrastructure changes investment needs and asset utilisation. An order can make better use of existing resources, or it can require new costs, reduce flexibility or displace production with a higher contribution.
Pricing is therefore not an isolated commercial decision. The company needs to understand how its operating system will respond to the demand that a price may create. Full-cost margin, after allocating shared costs, does not always show the economics of an additional order. When capacity is idle, a product with a low fully allocated margin may still contribute towards costs already incurred. When capacity is constrained, the analysis must include the value of displaced production and the cost of additional capability.
Energy use and energy cost also affect the economics of production, logistics and the offer. They therefore belong in the connected view of an operating decision. The company may, for example, compare the energy impact of running an additional shift with the cost of buying power at that time. Whether it should redesign its energy model through new infrastructure, storage, fleet electrification or a different boundary between internal capability and external partner is a separate strategic question.
The output of the analysis need not be one number. Leaders may need to see the effects on customers, quality, EBITDA, cash flow, capital, risk, asset use and the organisation's future capacity to grow.
06
The architecture follows the decision
The organisation's structure should make it possible to understand and act on these dependencies. Start with the decision and the business logic behind it: for the contract, what must be true about demand, capacity, contribution, delivery and cash for the offer to create value? Then identify the information and capabilities needed to test those conditions, the people who own them, and how an outcome returns to the people who can learn from it.
The systems have different jobs. ERP may hold the approved customer terms and financial records; CRM may show the account history and opportunity; planning and manufacturing systems may show available capacity, production schedules and expected yield; procurement and logistics systems may show supply and delivery constraints. A data and modelling layer can bring together the information needed to compare contract scenarios. A workflow can then route the proposal to the right decision owner and carry the approved choice into execution. These tools support the decision; they do not define whether the underlying business logic is sound.
“One source of truth” need not mean one physical database. For the contract decision, for example, sales, finance and production need to agree what counts as committed volume, available capacity and contribution margin, and which source and owner confirm each figure. The organisation also needs to know when the information was last updated and whether it is complete enough for the decision. It does not need every data point for every decision; it needs information fit for the decision at hand.
A common data foundation is not, by itself, a connected enterprise. If many reports repeat the same data using different definitions, the first task is to establish which decisions those reports support, which source and owner are authoritative, and which outputs are genuinely redundant. A plant manager may need a shift-level capacity view, while the management team needs the contract's effect on cash, customer commitments and capital. Both views can use consistent definitions without becoming one universal dashboard. The aim is coherent meaning and traceability.
Before adding automation or AI, the organisation should examine whether the process itself has sound business logic: whether its steps, rules, hand-offs, ownership and controls support the decision it is meant to serve. For instance, automating an approval based only on unit margin could accept a contract that consumes scarce capacity, displaces a more valuable order or creates a cash gap. An application may contain AI and still automate an incoherent process or optimise for the wrong outcome. Assess the system against the business logic; do not assume the logic is right simply because it is embedded in a system.
The organisation may involve a logistics partner to fulfil this contract while remaining within its current operating model. Choosing to outsource logistics, acquire a supplier or build a new energy capability changes a more fundamental boundary: what the organisation controls, provides with partners or buys from the market. This is a strategic boundary decision, distinct from how one contract is delivered.
07
AI is cognitive support inside a designed system
AI can be embedded in operational systems to support specific tasks: demand forecasting, planning, anomaly detection in quality, transaction analysis or flow optimisation. General-purpose tools can help synthesise documents, analyse knowledge, compare scenarios and generate questions that decision-makers have not yet considered. The value depends on data quality, process logic and whether the output reaches the right decision.
Not every decision needs an advanced model. Rules or ordinary automation may be sufficient for routine, reversible actions. More analysis may be justified where the decision has high impact, uncertainty, scale or consequences that are difficult to reverse. For the contract, AI might help forecast demand or identify unusual assumptions in the proposal, while an authorised commercial or executive owner remains accountable for accepting the risk and its consequences.
This is also an economic design choice. Sending every small task through a large reasoning engine may add cost and complexity without improving the outcome. The system should direct effort where uncertainty and consequence warrant it, and use simpler methods where they do not.
09
From a decision loop to organisational learning
The five questions introduced at the beginning can be read as a decision loop. Signals and information help establish what is happening; shared interpretation asks what it may mean; scenarios clarify which decision is needed; governance identifies who has the mandate; and outcome measures show whether the assumptions were sound. In the contract example, this means testing the offer against current capacity and customer commitments, modelling alternatives, assigning an authorised decision owner, then comparing delivery, quality, margin and cash outcomes with the forecast.
Signals and data → shared understanding → scenarios → decision and mandate → action → outcome → learning
Each result should improve the next decision. Decision speed is useful feedback, not the goal. The organisation needs to know whether the decision achieved its intended result, how it affected the whole system and what it taught the business. If a supplier constraint delayed delivery, that learning should change the next scenario.
Before an offer arrives, rehearsing comparable scenarios helps reveal gaps in data, skills, processes or authority. This is the Adaptive Spiral in practice: outcomes and new signals strengthen the organisation's ability to respond, while the Connected Enterprise describes the dependencies that make that learning possible.
10
Seeing the system is the beginning
Connected Enterprise is not a fixed diagram or a promise that every change can be predicted. It is an organisational capacity: to understand dependencies, notice signals and make considered decisions in conditions of risk. Disruption does not create the need for that capacity; it makes the consequences of lacking it harder to ignore.
Its architecture emerges from questions about value, decisions, information, resources, accountability and the flow of work. Systems and AI help maintain a shared picture, anticipate consequences, detect anomalies and explore scenarios. Embedded Governance makes authority and escalation visible. The outcomes of decisions return to the learning spiral.
Seeing the current playing field also reveals its limits. When better execution within those limits is no longer enough, the organisation must decide whether to change them. The next article explores when and how to break the box.