Business Core · Technology · Module
The technology estate
What systems the organisation runs, how they connect, and the few principles that decide what may be added to them.
The idea
How it works
An estate is rarely designed from the start. It grows by purchase, each addition justified on its own terms, and the architecture that results is the unplanned sum of those justifications. Mapping it comes first because the problems that matter — duplicated functions, fragile integrations, systems nobody owns — are only visible across the whole.
Ross, Weill and Robertson argue that the estate should follow a prior choice about how standardised and how integrated the business intends to be. Without that choice each project settles it locally, and the organisation ends up with a unified estate in one division and a loose federation in the next, by accident. The per-process question of whether a tool fits its work belongs to Operational Systems under Tooling; this module holds the organisation-wide view it draws on.
Working with it
In practice
- 01
Catalogue once, at organisation level
One entry per system, with a business owner, a purpose and a criticality. Other views of technology refer to these entries and do not keep lists of their own.
- 02
Draw the lines as well as the boxes
Integrations are where estates break and where change costs most. Record each one with what it carries, how, and who answers for it.
- 03
Choose the operating model first
How much should be standardised across units, and how much should be shared? The answer shapes the architecture before any system is chosen.
- 04
Keep the principles few and applied
Five principles tested against every purchase do more than thirty consulted once. Each should reject something specific.
One level in
The components of the technology estate
A component is something that exists afterwards which did not exist before — a deliverable or a mechanism, not an intention.
System landscape
Every system the organisation runs, with its business owner, purpose, criticality and lifecycle status.
LearnIntegration map
The connections between systems: what flows along each, by what mechanism, and what fails if it stops.
LearnArchitecture principles
The short set of rules every addition to the estate is tested against, derived from the chosen operating model.
Learn
An estate nobody designed still has an architecture. It is simply the one that past purchases produced.
The other modules in technology
Build, buy or subscribe
Deciding, for each capability, whether to build it, license it or rent it as a service — and recording why, so the reasoning can be revisited.
LearnAI and automation
Where AI and automation are used, who remains accountable for what they do, how well they are shown to work, and what risk each use carries.
LearnSecurity
Protecting the estate as a capability: knowing what is worth attacking, holding a baseline of controls, managing who can get in, and being able to recover.
LearnTechnical debt and renewal
What the estate owes to decisions made earlier, which of those debts are worth repaying, and how ageing systems are replaced without stopping the business.
Learn