Services

Business architecture and capability maps that drive decisions

We map what your organisation must be able to do, then use that map to settle ERP scope, operating model, integration and separation questions on evidence rather than opinion.

£13bnlargest programme delivered
19 yrssenior systems delivery
5 continentsdelivered across
£25msaving on a single programme

Delivered for and alongside

ShellBPCapitaBaringaOfgemSmart DCCInsightsFlui TechnologiesExxonMobilVodafoneConstellation SoftwareDeloittePwCEYNational GridElexon

Business architecture is a structured description of what an organisation does and how its capabilities, processes, information and systems fit together to create value. Its central tool is the business capability map, a stable picture of what the business must be able to do, used to decide where to invest and which systems should support what.

Most organisations already make architecture decisions, just not deliberately. ERP scope gets set by a vendor demo, target operating models get drawn around the current organisation chart, and integration plans follow whichever system has the loudest sponsor. A capability map puts those decisions on a common footing.

What business architecture is and why it matters

Organisations change their structures, processes and systems far more often than they change what they fundamentally do. An energy supplier will always need to bill customers, buy energy and manage debt, whatever its systems or team structure. Capabilities capture that stable core, which is why they make a better foundation for decisions than an organisation chart or a list of applications.

Business architecture is the business layer of enterprise architecture. The Open Group’s TOGAF standard, for example, treats it as one of four domains alongside data, application and technology architecture. It works best when it stays close to the decisions it is meant to inform, rather than becoming a modelling exercise of its own.

Three views do most of the work:

  • Capabilities: what the business must be able to do, regardless of who does it or which system supports it.
  • Value streams: the stages a customer or stakeholder goes through to get an outcome, and the capabilities each stage relies on.
  • Overlays: heat maps that lay performance, cost, risk, systems or teams over the capability map, so gaps and overlaps become obvious.

Capability mapping explained

Capability mapping produces a business capability model: a hierarchy of everything the organisation needs to be able to do. Level 1 gives the big blocks, usually somewhere between 10 and 20 of them. Level 2 breaks each block into its main parts, and level 3 goes further only where a decision needs it.

A few rules keep the map useful:

  • Name capabilities for what is done, not how, so customer billing rather than run the billing batch.
  • Leave out team names, system names and locations, which belong in overlays.
  • Make each capability appear once, with no overlaps between siblings.
  • Keep it stable enough that it would still be true after a reorganisation or a system change.
  • Stop at the level of detail the decision in hand needs.

Once the map exists, each capability can be scored, typically for strategic importance, current performance and how well systems and data support it. That turns a static picture into a heat map showing where money and attention should go.

Example: a level 1 business capability map for an energy supplier

The table below is a generic, simplified example rather than any real company’s map. The first two rows set direction, the next nine are the core of an energy supply business and the last four support everything else. The third column is an overlay showing where each capability is usually supported; it is not part of the map itself.

Level 1 capabilityExample level 2 capabilitiesUsual system support
Strategy and planningCorporate strategy, business planning, investment portfolio, performance reportingPlanning and reporting tools
Regulation, risk and complianceLicence obligations, regulatory reporting, industry code compliance, enterprise riskRisk and compliance tools
Product and pricingTariff design, pricing, propositions, partnershipsPricing tools and the billing platform
Sales and marketingAcquisition, renewals, broker channels, campaignsCRM
Customer serviceContact handling, account changes, complaints, support for vulnerable customersCRM or customer platform, telephony
Registration and switchingChange of supplier, change of tenancy, registration data, industry data flowsBilling platform and industry gateways
MeteringMeter asset management, smart meter installation, meter reading, meter dataMeter asset and meter data systems
BillingBill calculation, billing exceptions, statements, back billing controlsBilling platform
Payments and debtPayment methods, collections, payment plans, debt recoveryBilling platform and collections tools
Energy procurement and hedgingDemand forecasting, hedging, wholesale trading, position managementTrading and risk system
Settlement and reconciliationSettlement data, imbalance, reconciliation, industry chargesSettlement systems
FinanceAccounting, revenue reporting, treasury, management accountsERP
PeopleWorkforce planning, recruitment, learning, payrollHR and payroll system or ERP
Technology and dataData management, integration, cyber security, service managementIntegration and data platforms
Procurement and supplier managementSourcing, contracts, supplier performance, spend analysisERP

Two things stand out once a supplier puts its map on one page. The core capabilities, from registration through to settlement, are tightly linked by industry data, so a change in one ripples through the others. And the boundary between the billing platform and the ERP, usually around revenue, payments and debt, is where most scope arguments happen, which the map lets you settle capability by capability instead of vendor by vendor.

How capability maps drive investment and system decisions

We do this work for chief operating officers, finance directors, chief information officers and programme sponsors facing a decision they cannot afford to get wrong. A capability map earns its keep when it settles that decision, and these are the four we see most.

ERP scope

Mapping capabilities before talking to vendors shows which ones the ERP must cover, which belong to specialist platforms and where the interfaces sit. It stops scope drifting during demos and gives a fair basis for comparing bids. That makes it a natural first step in ERP implementation consulting.

Target operating model

A target operating model describes how each capability will be delivered in future: by which teams, processes, systems, locations and partners. Starting from capabilities stops the design simply redrawing today’s structure, which is why target operating model consulting works best when the capability map comes first. Our free target operating model template uses the same building blocks.

Mergers and integration

When two businesses combine, laying both onto one capability map shows where they duplicate each other, where one is stronger and which systems should survive. It turns post merger integration from a negotiation between two management teams into a series of capability by capability choices.

Separation and carve outs

In a separation the question flips: which capabilities must the new business stand up on day one, which can it rent from the parent for a period, and which can wait? The capability map becomes the checklist for carve outs and separation, and for the transitional services that cover the gaps.

Value streams: putting capabilities in order

A capability map shows what the business must be able to do. Value streams show the order in which those capabilities come together to deliver something a customer values. For an energy supplier, a simple set might be join, move home, use and pay, get help, and leave.

Walking each value stream across the map shows which capabilities every stage depends on and where handoffs between teams and systems cause delay or error. It also shows which capabilities to improve first, because a weak capability that sits in several value streams does more damage than one that sits in a single stream.

Value streams are not the same as a value chain analysis. Porter’s value chain looks at how the whole firm creates margin through its primary and support activities, while a value stream follows one outcome for one customer from start to finish. Both are useful, and they answer different questions.

What our business architecture work covers

We keep the work in proportion to the decision it supports. A typical engagement includes:

  • Agreeing the decisions the map must inform and the level of detail they need.
  • Building or refreshing the capability map to level 2, and to level 3 only where it matters.
  • Defining the main value streams and linking them to capabilities.
  • Heat mapping capabilities for importance, performance, cost and risk.
  • Overlaying systems, data and teams to show gaps, overlaps and dependencies.
  • Turning the findings into scope, options and a sequenced plan.

The map is built with your people in a small number of working sessions, in your own language. A first level 1 and level 2 map for a mid sized organisation usually takes a few weeks, not months. You keep the map and the method, and we show your team how to maintain it so it stays useful after we leave.

Enterprise architecture consulting without the shelfware

Many architecture programmes produce large repositories that nobody opens once the consultants leave. We take the opposite view. The test of good enterprise architecture consulting is whether a decision got made faster and better, not how many diagrams exist.

We hold no reseller agreements and take no vendor commissions, which keeps the map honest rather than shaped around a product. When it points to technology change, our IT consultancy takes the next step into platform and sourcing choices, and the same map feeds straight into your digital strategy.

Relevant experience

The questions of which capabilities a new business needs and which systems will support them sit at the heart of any separation. On the National Grid separation, where Christopher Fagan, our Managing Partner, was Project Director, the estate ran to more than 22 million assets under management. Choosing and contracting every software supplier on that programme, including the replacement of Oracle with SAP S/4HANA, sat with him until each system was implemented, and the National Grid separation case study sets out the scale.

Related services

Business architecture connects strategy to delivery. If operating models are new to you, start with our explainer on what an operating model is, then use the capability map to decide what has to change and in what order.

Frequently asked questions

What is business architecture?

Business architecture is a structured description of what an organisation does and how its capabilities, value streams, information, processes and systems fit together to deliver its strategy. It is the business layer of enterprise architecture. Its main tool is the business capability map, which is used to decide where to invest, what to change and which systems should support each part of the business.

What is capability mapping?

Capability mapping is the process of building a hierarchy of everything an organisation must be able to do, such as billing customers or managing suppliers, independent of who does it or which system supports it. Each capability can then be scored for importance, performance and system support, producing a heat map that shows where investment and attention should go first.

What is the difference between a capability and a process?

A capability is what the business must be able to do, such as customer billing. A process is how it does it: the sequence of steps, roles and systems used. Capabilities stay stable for years, while processes change with new systems, structures and regulation. That stability is why capabilities make a better basis for investment and system decisions.

What does a business capability model look like?

A business capability model is usually a one page map of 10 to 20 level 1 capabilities, grouped into those that set direction, those core to the business and those that support it. Each breaks down into level 2 capabilities, and sometimes level 3. Colour coding is often added to show importance, performance, cost or how well systems support each capability.

What is the difference between business architecture and enterprise architecture?

Enterprise architecture covers the whole design of an organisation, usually split into business, data, application and technology layers. Business architecture is the first of those layers: capabilities, value streams, information and organisation. It should come first: data, application and technology decisions are guesses until the business has said what it must be able to do.

Related reading: Target operating model design explained, Carve out separation playbook, Software procurement and selection and How to choose an ERP system.

Settle your next big decision on evidence

Whether it is ERP scope, an operating model, an integration or a separation, we can build the capability map that frames it. Tell us what you need to decide.

Book a confidential conversation