A Business Capability Map (BCM) is the one-page, business-facing view of what a company must be able to do — Sales, Procurement, Service, Production, Finance — structured by differentiators versus commodities. From over 1,200 projects across the DACH Mittelstand we know: in the Mittelstand it decides not graphics, but the target architecture against which the later ERP selection is measured. Treat it as a consultant poster and you buy software into an unclarified capability structure — architecture before software, every time.
What is a Business Capability Map? Definition and core characteristics
A Business Capability Map is the highly abstract, one-page view of all business capabilities — from Level 1 main capabilities like Sales, Procurement and Service down to Level 3. It answers the question "what must the business be able to do", and supplies the target architecture against which ERP selection and the Lastenheft are measured.
The TOGAF Business Capabilities Guide (G211) from The Open Group defines a business capability as "a particular ability that a business may possess or exchange to achieve a specific purpose" and positions the BCM as a core artefact of TOGAF Phase B (Business Architecture). The BIZBOK Guide from the Business Architecture Guild requires a BCM to deliver a "concise, non-redundant, complete, business-centric view of the enterprise". Five characteristics distinguish an architecture-grade BCM from a decorative poster:
- Business view, not system view — capabilities such as "Configure Order" or "Plan Material Requirements", not IT systems or org-chart units.
- Hierarchical structure — Level 1 main capabilities, Level 2 sub-capabilities, Level 3 operational capabilities.
- Clear accountability — every capability has a named Capability Owner, no anonymous tiles.
- Differentiators visibly marked — what sets us apart from competitors is recognisable; everything else is commodity.
- Machine-readable bridge to the Lastenheft — every capability anchors a functional requirement, not a feature list.
The boundary in the architecture document is decisive: the BCM is the target architecture, the Lastenheft its translation into requirements, the Pflichtenheft the vendor response. The process landscape map shows the value-creation view; process owners carry the operational accountability.
BCM vs. Capability Map: the business view against the umbrella view
The Business Capability Map is the business-facing partial view of the broader Capability Map — it answers "what must the business be able to do", while the umbrella Capability Map adds IT, data and technology capabilities. In the DACH Mittelstand the business BCM on a few pages is usually enough — not 200 corporate pages.
Forrester explicitly distinguishes Business from IT capabilities across multiple levels in its Reference IT Capability Map (May 2024) — explicitly complementary, not a replacement for the BCM. From our experience in numerous EAM pre-analyses across the DACH Mittelstand the separation is indispensable: first clarify what the business should be able to do, then ask which systems carry it.
Three boundaries that often blur in the literature:
- BCM vs. process model — the BCM shows capabilities ("Handle Complaint"), the process model shows the flow. Capabilities are stable, processes change.
- BCM vs. org chart — capability-oriented instead of hierarchical; Capability Owners need not be department heads.
- BCM vs. IT capability map — business view, not system view. Both are interlocked with value streams, not mixed.
The EAM Initiative at the University of St Gallen calls the BCM a "common language between executive board and IT" — which is exactly what it becomes in our Mittelstand projects.
Why the BCM matters in the DACH Mittelstand in 2026
Three drivers act on the DACH Mittelstand at once — the digitalisation gap is becoming structural, SAP investments are tightening, and every ERP selection without a documented capability structure falls into the feature trap. We have seen this in numerous ERP projects of the past 24 months — across machinery, kitchen manufacturers and medical technology.
First — the structural weakness. The Bitkom study "Digitalisation of the Economy 2025" shows: 53 percent of German companies report problems handling digitalisation; 82 percent describe the current economic crisis as also a crisis of hesitant digitalisation. Without a BCM, companies buy standard packages instead of differentiating capabilities.
Second — investment discipline. The DSAG Investment Report 2026 (around 198 SAP customers across D/A/CH) shows: 42 percent plan investments in S/4HANA on-premises, 22 percent in Private Cloud, only 6 percent in Public Cloud — investments follow viability and integration capacity, not visions. The BCM makes viability operational.
Third — the architecture gap before every ERP selection. The Trovarit study "ERP in Practice 2024/2025" (over 1,700 D/A/CH users) reports declining satisfaction with vendor service — driven by requirement gaps. From over 1,200 Dreher Consulting projects we know: a properly built BCM noticeably shortens the ERP project duration.
From our experience in numerous projects of the past 24 months — across DACH machinery, kitchen manufacturers and medical technology — the dependable BCM was missing at project start in many cases. Without a capability structure, ERP selection becomes a feature exercise flown blind.
Project example: DACH kitchen manufacturer (anonymised, c. 2,000 employees)
At a southern-German kitchen manufacturer with around 2,000 employees and a major order for 1,500 kitchens, we built a Business Capability Map before the ERP selection. In the capability "Configure Order" six process variants ran in parallel — four of them main variants. The BCM with clearly marked differentiators consolidated this into a manageable target architecture.
At this DACH kitchen manufacturer with around 2,000 employees, Sales, Engineering and Shipping each ran their own view on order processing — no one had ever seen, on a single page, which capabilities set the company apart from competitors. We have diagnosed this pattern in numerous projects of the past 24 months: no vendor talks before the BCM stands.
In a two-day workshop with the managing directors we captured the Level 1 capabilities — Sales, Engineering, Procurement, Production, Service, Finance. In the second step we named one Capability Owner per capability. In the third step we classified each capability on the differentiator-versus-commodity axis — exactly what the BIZBOK Guide requires.
The output was an architecture-validated Lastenheft — not a feature list, but the BCM expressed as functional requirements per differentiator capability. Six months later the ERP selection was complete and vendor-neutrally evaluated; the implementation ran an estimated 25 to 30 percent shorter. The lesson: the BCM is the prerequisite, not the result, of an ERP rollout.
What most BCM guides leave out
Three points rarely surfaced in German-language BCM guides and vendor pitches, but in the DACH Mittelstand they decide between project success and project abort. They follow from over 1,200 Dreher Consulting projects and from the consistent application of TOGAF G211 and BIZBOK.
1. The BCM is the target architecture — not a deferred consultant poster
Contrary to common framing, the BCM is not purely a corporate tool. From the Dreher view it is the target architecture against which ERP selection is measured — an architectural drawing that serves as reference in the Lastenheft and in vendor talks. Architecture before software. Demote it to a slide attachment and you buy software into a blank spot, then repair it at double the cost.
2. Differentiators vs. commodities — the axis most guides omit
German-language standard literature describes the BCM as an architectural object but rarely bridges through to ERP selection. From over 1,200 Dreher Consulting projects we have established the differentiation axis: differentiators land as must-requirements in the Lastenheft, commodities are accepted as standard processes. That is a negotiating basis instead of a feature list — the only protection against uncontrolled change requests.
3. Train-the-trainer methodology keeps the BCM alive — externally built maps decay
Most consultancies deliver a BCM as a PowerPoint appendix and leave. Six months later no one can explain why a given capability sits at a given level. We work in three stages: pre-modelling with the subject experts, handover of the modelling to the Capability Owners under coaching, then autonomous management. Exactly these "Performer" and "Owner" enablers are demanded by Michael Hammer's Process Audit / PEMM (HBR April 2007) as maturity prerequisites. A BCM without this ownership model stays a consultant product.
Our take
A BCM without an ERP architecture function, without a differentiation bridge to the Lastenheft, and without train-the-trainer anchoring is a decorative slide poster — expensive to produce, ineffective in practice. Architecture before software, every time.
How we use Business Capability Maps in ERP selection (methodology)
We run Business Capability Maps in four phases — capture, target architecture, differentiation bridge, Lastenheft. The order is not arbitrary: architecture first, then requirements, then vendor talks. From our experience, every ERP project that skips this order fails right here.
In Dreher Consulting's vendor-neutral ERP consulting the BCM is part of Enterprise Architecture Management (EAM) for the DACH Mittelstand. The TOGAF Business Capability Planning Guide supports this methodically — capabilities are mapped onto organisation, value streams and systems. Four phases:
- Capture — actual capabilities per area. Business capabilities at Level 1 and Level 2 from interviews, workshops and document analysis. Duration: three to five weeks.
- Target architecture — the BCM on one page. Sales, Procurement, Production, Service, Finance, HR, IT. One named Capability Owner per main capability.
- Differentiation bridge — classify every capability. Differentiator versus commodity. Here it is decided what the ERP must carry and what may remain standard.
- Lastenheft — architecture-validated requirements specification. The BCM expressed as functional requirements per differentiator capability. Protection against later change requests.
Train-the-trainer in practice: we model with the company, not for it. Stage 1 — together with the subject experts. Stage 2 — Capability Owners under coaching. Stage 3 — autonomous operation.
The difference from most consulting offers: we recommend vendor-neutrally. The BCM here is the sober referee, supported by methodology standards such as the SAP LeanIX BCM templates and research such as Springer PoEM 2024.
Common BCM mistakes in the DACH Mittelstand
Four error patterns recur in Mittelstand BCM projects. All four are avoidable — if they are addressed before ERP selection. None has its root in the modelling software. We have documented them repeatedly across DACH machinery and the Mittelstand.
- Mistake 1: Treating the BCM as an IT tool. The map is built in the IT department and contains systems instead of capabilities. Fix: the BCM is the business view — executive board and subject areas model, IT is co-pilot.
- Mistake 2: Confusing detail models with the BCM. Processes and use cases are squeezed into the Level 1 view; the document becomes illegible. Fix: keep the BCM at clear abstraction levels; detail belongs in process models.
- Mistake 3: No Capability Owner per main capability. The map shows tiles without ownership. Fix: every main capability gets a Capability Owner with a mandate — named, not a function placeholder.
- Mistake 4: External consultancy models alone. Six months later the company cannot explain the BCM. Fix: train-the-trainer methodology — handover in three stages, from pre-modelling to autonomous operation.
Our take: the mistakes are rarely technical. They are organisational and methodical — and that is exactly where vendor-neutral consulting has its leverage. Architecture before software, every time.
Frequently asked questions about the Business Capability Map
The Business Capability Map shows what the company must be able to do (capabilities like "Configure Order", "Handle Service") — independent of systems. The process landscape map shows the value-creation view: management, core and supporting processes with their interactions. Capabilities are stable, processes change frequently. In Dreher Consulting's ERP consulting we use both: the BCM to classify differentiators, the process landscape map to model the end-to-end flows.
From our experience a serious BCM at Level 1 and Level 2 takes four to six weeks — provided leadership reserves two workshops and the Capability Owners are named. Without this mandate the duration commonly doubles, because accountability questions are renegotiated during modelling. Adding Level 3 takes another two to four weeks.
It is the target architecture against which ERP selection is measured. Every capability is classified differentiator versus commodity; differentiators become must-requirements in the Lastenheft. From over 1,200 Dreher Consulting projects, a properly built BCM noticeably shortens the ERP project duration. The TOGAF Business Capability Planning Guide confirms the methodology as a standard for binding strategy to IT architecture.
Next steps
Before any ERP selection, ERP migration or major digitalisation decision, a four-to-six-week pre-clarification step pays off: Business Capability Map as target architecture, a Capability Owner per main capability, the differentiation bridge to the Lastenheft. Skip this step and you risk a doubly expensive re-setup project after eighteen to twenty-four months.
If you want to dig deeper, see our vendor-neutral ERP selection and our process management. We also recommend the wiki entries on the Capability Map (umbrella view), the process landscape map and the Lastenheft. Current case studies are in our insights; arrange a 30-minute conversation via the contact page.
30 minutes with Dreher Consulting
A structured pre-clarification of your target architecture — Business Capability Map on one page, a Capability Owner per main capability, and the differentiation bridge to the Lastenheft, vendor-neutral and drawn from over 1,200 projects across the DACH Mittelstand.
