TOGAF® Phase B: Building a Solid, Actionable Business Architecture

In the TOGAF® ADM, Phase B — Business Architecture — is the one I consider most critical. It lays the foundation for everything that follows: information systems architecture (Phase C), technology architecture (Phase D), opportunities and migration planning (Phases E and F). Yet in most engagements I've observed, it gets rushed.

People skip ahead to applications and technology because those feel more tangible, more reassuring, more 'deliverable'. That's a costly mistake: a botched Phase B condemns the whole structure to rest on sand. Here's how I truly leverage Phase B, and the three deliverables that make it a solid foundation.

Phase B, the neglected foundation of the ADM

The temptation to rush Phase B comes from a misunderstanding: people think business architecture is 'soft', less tangible than application or technology architecture. It's the opposite. Without a shared understanding of what the enterprise does and how it creates value, the later phases optimize in a vacuum.

A solid Phase B answers three questions the technical phases presuppose without ever asking: what does the organization know how to do (capabilities)? how does it create value (value streams)? what information does it handle (business objects)? Answering them gives meaning to everything that follows.

First deliverable: the capability map

My Phase B always starts with the capability map. I work in workshops with business directors to identify level-1 and level-2 capabilities. The exercise is harder than it looks: you need to abstract above processes and org charts to find what the organization fundamentally knows how to do.

The test I apply constantly: 'Design an aircraft' is a capability; 'Fill out form X in system Y' is not. The first is stable and technology-neutral; the second is a process activity. Holding this distinction is what guarantees a map usable across all the later phases of the ADM.

Second deliverable: value streams

The value stream is the second key deliverable. It puts capabilities in motion, showing how they contribute, step by step, to creating value for the end customer. At Airbus, such a stream could run from R&D through to after-sales support.

Visualizing this end-to-end flow reveals where the organization creates the most value — and where it loses it. It's also what links Phase B to strategy: a value stream failing at a critical stage becomes a priority that Phases C and D must serve, not the other way around.

Third deliverable: business information

The third component, often forgotten, is business information modeling. What are the major objects the organization handles? A Customer, an Order, a Product, a Contract. These objects flow across processes and applications, and that's precisely why they deserve to be modeled as early as Phase B.

Modeling them at this stage lets you identify data quality issues and information silos very early — before they get frozen into the Phase C application architecture. A poorly defined business object in Phase B becomes a costly data debt three phases later.

Iterative and collaborative, never in isolation

What TOGAF® doesn't emphasize loudly enough is that Phase B must be iterative and collaborative. I never lock myself in an office to produce diagrams alone. Every deliverable is co-built with the business, challenged, adjusted across workshops.

A business architecture model that hasn't been validated by the people who live the business every day is worthless: it'll be right on paper and wrong in the field. The value of Phase B lies as much in the alignment it creates as in the diagrams it produces.

Connecting Phase B to Phases C and D

Phase B only makes sense connected to what follows. The capability map feeds Phase C's application analysis through the capabilities × applications matrix. Value streams steer priorities. Business objects guide data architecture. This top-down traceability is what makes the ADM a coherent whole rather than a series of silos.

Concretely, I keep the links in a repository (MEGA HOPEX, BizzDesign): each capability links to its applications, each value stream to its capabilities, each business object to its data entities. It's this current → target continuity that turns a documentary Phase B into a transformation engine.

What I take from the field

Phase B isn't the warm-up before the serious work: it's the foundation that determines the soundness of the whole structure. Capability map, value streams, business objects — three co-built deliverables that give meaning to the application and technology architecture that follows.

Rushing Phase B means saving a few weeks to lose months later. The rigor invested here pays off at every subsequent phase of the ADM.