← CDO Compass
Foundations

Where Business Architecture Meets Data

Why business architects and the data office work best as one team, and how the capability map joins them.

Executive summary

For business architects, CDOs and heads of data governance in Switzerland

  1. Most organisations keep two maps of themselves. Business architecture maintains the capability map. The data office maintains data domains, owners and the inventory of critical data. The two rarely share a model.
  2. Business concepts such as client, account or portfolio connect the two maps. Each capability creates, changes or uses them. Each concept needs one system of record and one owner.
  3. FINMA Circular 2023/1 asks Swiss banks to identify critical data systematically and to manage it over its full lifecycle. A capability map linked to data shows where critical data is created and where it flows.

For your next architecture board: pick one capability and ask which application is the system of record for each concept it creates.

Ask a business architect to describe the organisation and you get a capability map. Ask the CDO and you get data domains, a glossary and a list of owners. Both describe the same organisation. In most organisations the two work in different teams, with different tools, for different committees. They have more to gain from each other than either side usually sees. This briefing looks at that alliance: what each brings, where their work meets, and how to make them work as one team. The examples come from Swiss banking, where FINMA sets clear expectations for critical data. The approach applies to any organisation that runs on data.

Two Maps That Rarely Meet

The capability map is the business architect's main tool. It is stable over time, because what an organisation does changes much more slowly than how it does it. Business architects use it to link strategy to change: they map value streams and processes onto capabilities, place applications on them, spot overlaps and design the target state.

The data office works from another angle. It defines data domains, writes business definitions, names owners and stewards, sets quality rules and, in Swiss banks, maintains the inventory of critical data.

Business architect

What the organisation does

Capabilities, applications, interfaces, target state, roadmap. Reviewed in the architecture board.

CDO and data office

What the organisation knows

Domains, definitions, owners, quality rules, critical data. Reviewed in the data governance forum.

When the two maps live apart, the gaps show up in familiar ways:

  • Two applications both claim to hold the master client record, and nobody has decided which one wins.
  • A project changes how a capability works and nobody checks which critical data it touches.
  • Owners are named per data domain, while architecture decisions are taken per capability, so the owner is rarely in the room when a decision affects their data.
  • The critical data inventory lists tables and fields with no link to the business activity that creates them.

Each side does its own job well. The organisation still ends up with two partial pictures of itself, and each side misses what the other knows.

The Bridge: Business Concepts

The two maps meet at the level of business concepts. Every capability creates, changes or uses some of them. Every data domain groups some of them. Once both teams use the same list of concepts, a simple chain links a capability to the person who decides about its data.

From capability to ownerSelect a link in the chain to see what it holds, who maintains it, and the question it answers.

A reading frame proposed by DataEdgePro. Names of artefacts vary between organisations and tools.

What FINMA Asks

For Swiss banks and securities firms, FINMA Circular 2023/1 "Operational risks and resilience – banks", in force since 1 January 2024, includes a section on critical data risk management (chapter IV, letter D).1 Two of its provisions connect directly to the capability map.

Banks · FINMA 2023/1 · Margin no. 73

Identify systematically

Critical data must be identified in a systematic and comprehensive way, categorised by criticality, with clear responsibilities.1

Walking the capability map, one capability at a time, is a systematic method.

Banks · FINMA 2023/1 · Margin no. 74

Manage the lifecycle

Critical data must be managed throughout its entire lifecycle.1

The lifecycle starts in the capability that creates the data and runs through every capability that uses it.

A map that shows these links gives the bank a clear answer to both requirements: where each critical data element comes from, where it goes, and who is responsible at each step.

Proportionality applies. Banks and securities firms in FINMA supervisory categories 4 and 5 are exempt from margin nos. 73 and 74, among others.1

Who Does What

The business architect and the CDO each keep their role. What changes is a small set of artefacts they use and maintain together, and the habit of asking each other before a decision.

Business architect

Draws and connects

Maintains the capability map, value streams and process maps, and the functional map of the information system. Allocates capabilities to applications. Proposes a system of record for each business concept and checks data flows in solution designs with solution architects.

CDO and data office

Defines and decides

Names owners and stewards and writes business definitions. Classifies critical data and sets quality rules. Confirms, with the owner, the system of record proposed by the business architect.

Shared

One list of concepts

One name, one definition and one identifier per business concept, used in both the glossary and the capability map.

Shared

One review point

Data impact is a standing item in the architecture board, and the data office has a seat at it.

Example: Client Onboarding in a Private Bank

Client onboarding is a good first capability, because almost everything downstream depends on it. The same reasoning works for patient admission in a hospital or supplier onboarding in industry.

One capability creates, others useClient onboarding creates the core client concepts. Other capabilities depend on them.
Client onboarding capability CREATES BUSINESS CONCEPTS Client Account Risk profile Investment profile USE Portfolio management Compliance monitoring Client reporting

Generic illustration. Capabilities and concepts are simplified and do not describe any specific bank.

Each concept created by onboarding needs one system of record. If the CRM and the core banking system both hold client data, the bank has to decide which one is authoritative for which attributes, and write that decision down.

Several attributes are likely to be classified as critical: client identification data used for anti-money laundering checks, the risk profile used for suitability, the domicile used for tax and cross-border rules. Each has an owner, usually in the business line that runs onboarding.

The benefit shows when change arrives. A project to replace the onboarding tool can see, before design starts, which critical data it creates, which capabilities depend on it, and which owners must sign off.

An Unlinked Map Is Data Debt

Data debt is the future cost of past shortcuts in how data is managed. Borrowed Debt looked at the debt an organisation takes on when it pledges data to a supplier. Two unlinked maps create another kind, built up from inside.

Each time a project goes live without saying which business concepts it creates, which system is authoritative and which critical data it touches, the organisation takes on a little debt. The interest is paid every day: reconciliations between systems that both claim the client, manual fixes in reports, definitions argued again in every project.

How the debt builds up

  • A second masterA new application stores client data with no decision on which copy wins.
  • A silent changeA capability changes and the critical data inventory is not updated.
  • A missing ownerA new concept appears and nobody is asked to own it.

How it is kept small

  • One decision per conceptThe system of record is recorded with a date and an owner.
  • One question per changeEvery design states which concepts it creates, moves or retires.
  • One mapThe inventory of critical data points to the capabilities behind it.

The due date usually comes from outside: an audit, a migration, a merger, an incident. On that day the organisation needs to know where its critical data is born and where it goes. A linked map is how that answer is prepared in advance.

Making the Link

Move 1

Start with one capability

Pick a capability that creates critical data and is under change. Map it fully, from concepts to owners, before extending to others.

Move 2

Agree the list of concepts

The hardest step and the most useful. One name and one definition per concept, used by the glossary and the capability map alike.

Move 3

Record the system of record

The business architect proposes, the owner confirms. Where two systems compete, the decision is written down with a date and an owner.

Move 4

Tag critical data on the map

Link each critical data element to the capability that creates it and to the capabilities that use it.

Move 5

Ask one question in every review

Which business concepts does this change create, move or retire, and have their owners agreed?

Move 6

Give the data office a seat

Data impact becomes a standing item in the architecture board, with the data office present to answer it.

Are Your Two Maps Connected?

Tick each statement that is true in your organisation today. The result shows where to start.

Self-check for the business architect and the CDOTick what is already in place.
Tick what is already in place to see where to start.

One Organisation, Two Allies

The business architect knows what the organisation does. The CDO knows what the organisation knows. Each sees half the picture alone. Working from one list of business concepts and one capability map, they can show where critical data is created, who decides about it and what a change will touch. The business architect gets better designs, the CDO gets owners who are in the room when it matters, and the organisation gets one clear view of its critical data. In a Swiss bank, that is also what FINMA expects.

Sources & references

  1. FINMA, Circular 2023/1 "Operational risks and resilience – banks", 7 December 2022, in force 1 January 2024. Chapter IV.D on critical data risk management (margin nos. 71 to 82), in particular margin nos. 73 and 74; exemptions for FINMA categories 4 and 5 (chapter III). finma.ch