Business Core · Object
The organisation’s tools and systems taken as a whole: what exists, how it connects, how each part was sourced, how it is protected, and what it will take to keep it working.
The term
Technology in the Business Core is what the organisation has to work with in systems: the applications, platforms, integrations, devices and services it runs on. Each was acquired to solve a particular problem, and the object exists because the sum of those solutions has properties none of them has alone — dependencies, overlaps, exposure and cost that only appear when the estate is looked at in one piece.
Two neighbours are easy to confuse with it. Operational Systems asks whether a given tool fits the process it serves; Technology asks what the whole collection amounts to and where it is heading. Data Core owns the data itself — its ownership, meaning, access and retention — while this object owns the systems that hold and move it.
Since general-purpose AI became widely available, the object has also had to carry AI. Models that draw on an organisation’s own documents and act inside its systems are technology decisions with unusual properties: their behaviour is probabilistic, their quality has to be measured, and regulators have begun to classify them by risk. The framework places them here, with the rest of the estate, and not as a separate strategy.
Why it earns a place
Every purchase and integration adds to an architecture. Left to accumulate, it takes the shape of past decisions made one at a time, and the cost of that shape arrives later as integration work nobody budgeted for.
Integration, support, security patching, licence growth and eventual migration outweigh the initial price in most estates. A sourcing decision judged on acquisition cost is judged on the smallest part of it.
Both can be deferred, and both accumulate interest while deferred. The choice is between paying on a schedule the organisation sets and paying on one set by an incident or an unsupported system.
One level in
Five working areas: what the estate consists of, how each part is sourced, where AI and automation are used, how the whole is protected, and what it still owes to its own past.
The systems the organisation runs, the integrations between them, and the few principles that decide what may be added. Kept once, for the whole organisation, so that every other view of technology can refer to the same entries.
LearnDeciding for each capability whether to build it, license it or rent it as a service, with the whole cost over time and the cost of leaving counted before the commitment is made.
LearnWhere AI and automation are used, who stays accountable for what they do, how their quality is measured, and how each use is classified by risk. The home in the framework for AI as something the organisation adopts and operates.
LearnWhat the estate owes to earlier decisions, which of those debts are worth repaying, and how ageing systems are replaced without stopping the business while it happens.
LearnAcross the framework
Beyond the framework
The Omnigoal says where this belongs and what it touches. It does not tell you how to think about it — other people have done that, and done it well. These are theirs.
Also known as TAM (technology acceptance)
Whether people use a new system depends mainly on whether they think it will help them and whether they think it will be easy.
Davis separated perceived usefulness from perceived ease of use and found usefulness to be the stronger of the two: people will put up with a difficult system that clearly helps, but not an easy one that does not. For anyone introducing technology it shifts the question from features to what the user believes the system will do for their own work.
Fred D. Davis, “Perceived Usefulness, Perceived Ease of Use, and User Acceptance of Information Technology”, MIS Quarterly, 1989.
Also known as NIST CSF
A common structure for managing cyber risk, organised around what an organisation must be able to do before, during and after an incident.
It groups security work into a few functions — identifying what needs protecting, protecting it, detecting attacks, responding and recovering — and the 2024 revision added governing as a function of its own. Its main value is as a shared map: it lets management, technical staff and suppliers describe their position and their gaps in the same terms.
National Institute of Standards and Technology, Framework for Improving Critical Infrastructure Cybersecurity, 2014; The NIST Cybersecurity Framework 2.0, 2024.
Also known as TOGAF, The Open Group Architecture Framework
A method for describing how a business, its information and its technology fit together, and for changing that fit deliberately.
At its centre is a repeating cycle for developing an enterprise architecture: understanding the business, then data and applications, then technology, then planning how to move from the current state to the target one. Its value is in making the connections explicit, so a technology decision can be traced back to a business need and forward to what it will affect.
The Open Group, TOGAF, first version 1995; The TOGAF Standard, 10th edition, 2022. TOGAF is a registered trademark of The Open Group and is named here only to refer to its work.
Also known as Wardley maps
Map what a user needs, the components that serve it, and how far each component has evolved from novel to commodity.
Components are placed by how visible they are to the user and by how mature they are — from newly invented, through custom-built and product, to utility. The insight is that the right way to handle a component depends on where it sits: invent the novel parts, buy or rent the commodities, and expect everything to drift towards commodity over time.
Simon Wardley, Wardley Maps: Topographical Intelligence in Business, published openly under a Creative Commons licence from 2016; developed from 2005.
These are other people’s models, named here so you can go to the source and use them properly. The Omnigoal is not affiliated with their authors and is not endorsed by them; nothing of theirs is reproduced here — no canvas, no diagram, no wording. Each is described in our own words, with the originator credited, because the framework is a place to put thinking, not a replacement for the people who did it. Model names and trademarks belong to their respective owners and are used here only to refer to the work itself.
Every model in the framework, and where each one belongsDraw the integration map before approving the next system. Most of what an estate costs to change sits in the connections between the boxes, and those are the parts nobody bought.
The people the organisation has, the people it needs, and how the gap between them is closed through planning, hiring, development and retention. Capability is usually the slowest constraint on a plan to move.
LearnWhat the organisation offers, stated in terms of what it does for someone rather than what the product is. Who the customer is comes from the Market Core; what they are offered is settled here.
LearnHow what is offered turns into money: what is charged for, on what basis, how often and by whom. Whatever the pricing metric rewards is what the organisation will end up producing.
LearnThe few things the organisation does better than most, that customers value and competitors struggle to copy. What counts as core decides what is kept in-house and what goes to partners.
LearnWhat the organisation owns and can put to work, from premises and equipment to intellectual property and accumulated data. The intangible assets are usually the most valuable and the least often listed.
LearnThe processes and standards that let the organisation do the same work twice without deciding how each time. A process that is routinely worked around is worse than none.
LearnThe organisations the business relies on for capability it has decided not to build. The decision is the substance, and the exit terms are best agreed while the relationship is still good.
LearnEveryone with a claim on the organisation or a stake in what it does, including groups it never chose. The market asks who will buy; this object asks who has standing.
LearnWhether the business is profitable, whether it has cash, and whether it can fund what it intends to do next — three questions that are often confused. It also covers how capital is raised, how investments are appraised, and how tax bears on both.
LearnEverything between a supplier and a customer: sourcing, moving, holding and delivering. It is where the trade-off between efficiency and resilience is made, usually without anyone deciding it.
LearnWhere things are actually made: capacity, flow, quality and the maintenance that keeps all three possible. A production system runs at the speed of its slowest step.
LearnThe obligations the organisation has no choice about — legal, regulatory, financial, health and safety, and data protection — and the controls that show they are being met. Commitments made above the legal minimum are held under Responsibility in the Vision Core.
LearnHow the organisation is structured and led: who decides what, how work is divided and coordinated, and how people take up change. HR covers the people; this object covers the arrangement they work in.
LearnWho owns the organisation and how it is overseen: the board, enterprise risk, succession and, eventually, exit. It is where decisions about the organisation itself are taken, rather than decisions within it.
LearnWhere new offers and new ways of working come from, how they are tested, and how the decision to scale or stop them is taken. An idea nobody is able to stop is a commitment rather than an experiment.
Learn