Contrary to the usual ISO 9001 framing, most BPM accounts treat the process landscape map as a QM artefact — our practice contradicts that. From over 1,200 projects across the DACH Mittelstand: architecture before software. The process landscape map is the target architecture against which the ERP selection is measured — not a deferred visualisation poster.
What Is a Process Landscape Map? — Definition and Core Characteristics
A process landscape map (German: Prozesslandkarte) is the Level-1 view of a company's business process architecture — a graphic, one-page overview of management, core, and supporting processes with their interactions. It operates at the highest level of abstraction and supplies the target architecture against which ERP selection and specification are measured.
The ABPMP BPM CBOK 4.0 defines the Enterprise Process Map as the Level-1 artefact of business process architecture, from which Level-2 process groups and Level-3 detail processes are derived. ISO 9001:2015 clause 4.4 has required since 2015 that organisations determine their processes and interactions — the process landscape map is the established graphic implementation. Five characteristics distinguish an architecture-grade process landscape map from a decorative poster:
- Three-tier structure — management, core, and supporting processes are visibly separated.
- Interfaces, not island lists — interactions between processes are shown explicitly, not just processes as tiles.
- One page, one abstraction level — Level-1 only; BPMN detail belongs at Level 3.
- Process owner per core process — no anonymous boxes; every core process has an accountable owner.
- Machine-readable bridge to the specification — every element is an anchor for later capabilities and ERP requirements.
The architectural boundary is decisive: the process landscape map is the target architecture, the Lastenheft (requirements specification) its translation into requirements, the Pflichtenheft the vendor response. Master data harmonise the data view, process owners carry accountability.
Why the Process Landscape Map Matters in the DACH Mittelstand in 2026
Three drivers act on the DACH Mittelstand at once — process complexity is growing, regulatory duties demand documented process structures, and ERP modernisation stalls without a target architecture. From our experience across DACH manufacturing and the Mittelstand the pattern is consistent.
First, the structural weakness. The Bitkom 2025 digitalisation study documents that 53 percent of companies with 20 or more employees report difficulty managing their digitalisation projects. From our project experience, many Mittelstand companies lack a documented target process landscape before ERP selection — the most common blind spot at project start.
Second, the regulatory duty. ISO 9001:2015 clause 4.4 makes the process approach mandatory for certified QM systems. The German Society for Quality (DGQ) positions the process landscape as the central visualisation of the process-oriented approach — split into management, core, and supporting processes.
Third, the architecture gap before any ERP selection. Research on process architecture — including Becker et al. — places process landscape models at the top abstraction level of a process architecture. Validated across over 1,200 projects at Dreher Consulting: a properly built process landscape map shortens the ERP project duration by up to 30 percent.
From our experience across kitchen manufacturers, machinery, and the DACH Mittelstand, many projects started without a reliable process landscape map. Over 1,200 projects confirm the pattern: without a target architecture the ERP selection becomes a blind flight — and in our projects it costs six to nine months of added implementation time, with architecture decisions deferred into the build phase.
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 process landscape map before the ERP selection. The same order-to-cash process ran in six variants in parallel; named owners consolidated them into one standard process, then translated it into a vendor-neutral specification.
The company had grown organically. Sales, engineering, production planning, and shipping each kept their own Excel view of the order-to-cash process — and nobody had ever seen the end-to-end process on one page. We insisted: no vendor talks before the process landscape map exists.
In a two-day workshop with managing directors and department heads we captured the three tiers, assigned every core process to an owner who actually decides in day-to-day operations, then set the six order-to-cash variants side by side, marked four as main variants, and defined a target process. A structured approach that the BVA Process Map Guideline also recommends.
The output was an architecture-validated Lastenheft — not a feature list, but the target architecture translated into functional requirements per core process. Six months later the S/4HANA selection was complete, vendor-neutrally evaluated. Implementation ran an estimated 25 to 30 percent shorter than comparable projects without process landscape map preparation. The lesson: the process landscape map is the prerequisite of an ERP rollout, not its outcome.
What Most Process Landscape Map Guides Leave Out
Three points that rarely surface in process landscape map guides, but in the DACH Mittelstand they decide between project success and project abort. They follow from over 1,200 projects at Dreher Consulting and consistent application of the ABPMP BPM CBOK 4.0.
1. The Process Landscape Map Is the Target Architecture — Not a Deferred QM Poster
The usual practice: the process landscape map is born after ISO 9001 certification, ends up on a hallway wall, and ages. In our view it is the target architecture against which ERP selection is measured — a blueprint used as reference in the specification, vendor talks, and implementation. Architecture before software. Treated as a QM poster, it sends software into a blank spot — and the company pays the repair in implementation, at double cost.
2. The Capability Bridge From Process to Specification Is Missing in Most Guides
The standard literature — including the process-architecture research of Becker et al. — describes the process landscape map as an architecture object but rarely jumps through to ERP selection. From over 1,200 projects at Dreher Consulting we have established the capability bridge: every core process is decomposed into business capabilities, each classified as differentiator or commodity. Differentiators land as must-haves in the Lastenheft, commodities as standard. A negotiation basis, not a feature list — the only protection against uncontrolled change requests in implementation.
3. Train-the-Trainer Methodology Keeps the Process Landscape Map Alive — Externally Built Maps Age Out
Most consultancies deliver a process landscape map as a PowerPoint deck and walk away. Six months later nobody can explain why an arrow goes where. We work in three stages: pre-modelling with subject-matter owners, handover to the process owners under coaching, then standalone operation. Those "performers" and "owner" enablers are demanded by Michael Hammer's Process Audit / PEMM (HBR, April 2007) as maturity prerequisites.
Our take
A process landscape map without an ERP-architecture role, without the capability bridge to the specification, and without train-the-trainer anchoring is a decorative QM poster — expensive to produce, ineffective in practice. Architecture before software, every time.
How We Use Process Landscape Maps in ERP Selection (Methodology)
Four phases — capture, target architecture, capability bridge, specification. Architecture first, requirements second, vendor talks last. From our experience reversing this order is where most Mittelstand ERP projects break, and where the most expensive change requests originate in the build phase.
In Dreher Consulting's vendor-neutral ERP consulting the process landscape map is part of Enterprise Architecture Management (EAM) for the Mittelstand. Four phases:
- Capture — current-state end-to-end processes, variants, media breaks, and interfaces. Three to five weeks.
- Target architecture — the process landscape map on one page. One named process owner per core process. Variants consolidated into standard processes.
- Capability bridge — each core process decomposed into capabilities, each classified as differentiator or commodity.
- Specification — architecture-validated Lastenheft. Not a feature list, but the target architecture as functional requirements. A negotiation basis, and protection against later change requests.
How we apply train-the-trainer
We do not model for the company; we model with it. Stage 1: our consultants build the first draft with the subject-matter owners. Stage 2: the process owners take over the modelling under coaching. Stage 3: they run it independently. A living target architecture, not a consultancy product.
We recommend 100% vendor-neutrally. Otherwise the company buys the consultant's favourite tool — not the right one for its business model. The process landscape map is the sober referee — the reliable reference against which every vendor is evaluated.
Common Mistakes With Process Landscape Maps in the Mittelstand
Four failure patterns in Mittelstand process landscape map projects. All avoidable if addressed before ERP selection. None has its root in the modelling software. We have documented them repeatedly across DACH manufacturing.
Mistake 1 — process landscape map as a QM compliance exercise. The map is born after the ISO 9001 audit, ends up on the wall, and is never touched again. Fix: position it as the target architecture for ERP and digitalisation from day one.
Mistake 2 — confusing detail models with the process landscape map. BPMN detail models are squeezed into the Level-1 view, and the document becomes unreadable. Fix: stay at one page, one abstraction level. Detail belongs at Levels 2 and 3.
Mistake 3 — no process owner per core process. Hammer's PEMM defines "owner" and "performers" as indispensable enablers. Fix: every core process gets a named owner with a mandate.
Mistake 4 — external consultancy models alone. Six months later the company cannot explain the map. Fix: train-the-trainer handover in three stages.
Our take
The mistakes are rarely technical. They are organisational and methodical — and that is where independent consulting has its leverage. Architecture before software, every time.
Frequently Asked Questions
The process landscape map is the Level-1 architectural blueprint — one page, three tiers, highly abstract. A process model, typically in BPMN 2.0, is the Level-3 detail view of one individual process with activities, decisions, and roles. The landscape map shows which processes exist and how they interact; the process model shows how a single process runs. Mixing the two is the most common beginner's mistake.
From our experience a serious process landscape map takes four to eight weeks, provided management frees up two two-day workshops and the process owners are named in advance. Without that mandate the timeline usually doubles, because responsibility questions resurface during modelling and need to be renegotiated. Governance is the real bottleneck, not modelling capacity.
Methodically the process owners per core process — facilitated by a staff function (process management, organisation, or QM leadership). The executive board is commissioner and ultimate owner of the architecture, because only it can make binding decisions on process consolidation, accountability cuts and investment approvals. External consulting is a midwife in the first weeks, not a permanent owner.
For the pure Level-1 process landscape map, structured slides or Visio/draw.io sketches are enough — the substance lies in the content, not the tool. For integrated architectures with Level-2 and Level-3 layers, SAP Signavio, ARIS, Adonis, or GBTEC are established. Architecture first, then tool.
It is the target architecture against which ERP selection is measured. From 1,200+ projects at Dreher Consulting: a properly built process landscape map shortens the ERP project duration by up to 30 percent. Documenting the end-to-end processes and the target process landscape before any selection means vendors are evaluated against a reliable architecture rather than a feature list.
Next Steps
Before any ERP selection, migration, or major digitalisation decision, a four- to eight-week preparatory step pays off: process landscape map as target architecture, process owners per core process, capability bridge to the specification. Skipping it risks a doubly expensive restart project after eighteen to twenty-four months. To deepen these topics, see our vendor-neutral ERP consulting and our digitalisation services. We work 100% vendor-neutrally.
We also recommend the wiki entries on process owners, the Pflichtenheft, and ERP systems. Recent case studies are in our insights; for a 30-minute conversation directly with Dr. Dreher reach us via the contact page.
30 minutes with Dr. Harald Dreher
A structured preparatory step for your process landscape map as target architecture — process owners, capability bridge, and the path to an architecture-validated specification, vendor-neutral, from over 1,200 projects in the DACH Mittelstand.
