In over 1,200 projects across the DACH Mittelstand we see the pattern: companies advertise a pure-form process-manager role and rarely find anyone on the market who can live that textbook version inside a Mittelstand structure. This entry is written for managing directors of Mittelstand companies.
What Is a Process Manager? — Definition and Demarcation
A process manager monitors, steers, and improves individual business processes operationally. They work with BPMN 2.0, process metrics, and improvement methods such as Lean or Six Sigma. Titles like "process manager", "business process manager", or "BPM manager" are largely interchangeable in DACH practice and describe the same task profile.
The international definition comes from the ABPMP BPM CBOK 4.0, the global industry standard. It organises the discipline into nine knowledge areas and underpins the CBPA and CBPP certifications. The regulatory baseline is set by the process approach of ISO 9001:2015. The DACH-specific reference adds the DGQ profession profile: a process manager selects suitable methods to analyse, document, and improve processes and steers them through measurable goals.
Six task areas shape the role in practice:
- Process analysis — structured capture of as-is processes, often in BPMN 2.0 or as value stream mapping.
- To-be design — modelling target processes with explicit KPI links.
- Implementation — translating process logic into ERP, workflow, or RPA configuration.
- Metrics steering — defining and monitoring cycle time, error rate, on-time delivery, and cost.
- Continuous improvement — PDCA cycles, Lean initiatives, audit preparation.
- Stakeholder coordination — aligning business, IT, quality management, and leadership.
The key demarcation versus the process owner: the owner carries strategic end-to-end accountability and defines the higher-order targets. The process manager executes tactically and delivers the metrics the owner needs for decisions. The quality manager owns the standard-compliant QMS; the operations manager runs the unit; the business analyst elicits requirements. In the corporation these roles are cleanly separated. In our experience, process manager and process owner regularly sit with one person in the DACH Mittelstand.
Why the Process Manager Role Matters in the DACH Mittelstand in 2026
Three drivers turn the process-manager role into a Mittelstand bottleneck in 2026: ERP modernisation pressure with documentation-grade to-be processes, audit demands from ISO 9001:2015, EFQM 2025 and sector-specific norms, plus a tight labour market in which the Mittelstand competes with corporations and consultancies for the same profile.
First, ERP modernisation. In our projects, an ERP rollout without documented to-be processes is the single most common driver of budget overruns. The Bitkom 2025 digitalisation study documents that 53 percent of surveyed companies with 20 or more employees report difficulty managing their digitalisation projects. Missing process documentation is, from our project experience, one of the most common delay factors in ERP initiatives.
Second, audit and compliance pressure. ISO 9001:2015 anchors the process approach together with PDCA and risk-based thinking. Consistent results are only achievable when activities are assigned to a clear owner as connected processes. Sectors such as medical devices (ISO 13485), automotive suppliers (IATF 16949), and food (IFS Food) compound the pressure. In the EFQM Model 2025 process accountability is explicitly embedded in the Execution dimension.
Third, scarce talent. Qualified process-manager profiles are scarce and strongly contested in the DACH labour market. The Mittelstand competes for the same profile with corporations building dedicated BPM departments and with consultancies that run this capability as their core business. Anyone wanting to fill the role internally needs a realistic, Mittelstand-grade profile — otherwise the position stays vacant for a long time.
Project Example: Mechanical Engineering Firm in Southern Germany, c. 200 Employees
In a Mittelstand engagement in southern German mechanical engineering we took the process-manager role ad interim and translated the CBOK 4.0 ideal into a Mittelstand-grade role cluster — one person, two hats, documented in a clear accountability matrix with four leading metrics per core process.
A mechanical engineering firm with around 200 employees, three sites, and an ERP landscape introduced in the late 1990s had advertised the role "Process Manager (Order-to-Cash and Procure-to-Pay)" for fourteen months. Two candidates reached the final round, one withdrew, the second stayed five months. The cause was the profile: the position was framed as a pure BPM CBOK 4.0 role — methods expert without process ownership, without project responsibility, without KPI definition authority. In a 200-person engineering firm with a four-person IT department, that division of labour was not constructible.
We took the mandate for the restart ad interim — coupled with the process owner role, which was equally unfilled. One person, two hats: process management for Order-to-Cash and Procure-to-Pay, process ownership for both core processes, light project coordination. We deliberately did not separate the roles, because the company sat below our pragmatic threshold. Only from around 500 employees, or with project durations beyond twelve months across more than three ERP modules, does the clean separation justify itself.
The result after seven months: two documented to-be processes with 18 to 24 BPMN activities each, a KPI dashboard with four leading metrics, a vendor-neutral shortlist of three ERP providers, and a selection decision in ten weeks. The role was subsequently filled internally — this time with a realistic profile that named the dual PM + PO role explicitly.
What Most BPM Guides Conceal About the Mittelstand Reality
Three points the BPM CBOK 4.0 and comparable corporate-oriented guides do not address in their pure-form logic — and that decide between success and failure of a process-manager engagement in the DACH Mittelstand. From over 1,200 projects in our consulting practice.
1. ABPMP Separates PM and PO Cleanly — The Mittelstand Cannot
The BPM CBOK 4.0 clearly separates process owner (strategic) and process manager (tactical). Appian documents the routinely confused roles precisely. This split holds in corporations above 1,000 employees because steering boards, BPM centres of excellence, and dedicated process-owner committees exist there. A Mittelstand with 50 to 500 employees has none of that. In our experience the PM there additionally takes process ownership for one or two core processes in around 80 percent of engagements. The realistic answer is a role cluster: PM + PO + light project coordination — one person, documented in a clear accountability matrix.
2. Tool Reality: Camunda and Signavio Are Rare in the Mittelstand
The relevant BPM guides assume work is done with Camunda, SAP Signavio, or ARIS. In roughly 70 percent of our Mittelstand engagements the PM function starts in Visio, PowerPoint, or ERP-bundled tooling. A switch to a dedicated BPM suite only pays back under three conditions: more than fifteen documented activity steps per core process, hard ISO 9001 or IATF 16949 audit obligation, or an ERP migration with process automation. Choosing the tool before clarifying the need produces a suite the team does not operate.
3. Without KPIs Before Project Start the Process Manager Fails — Even the Best One
In a corporation the process manager inherits predefined OKRs from the strategy process. In the DACH Mittelstand these KPIs simply do not exist — management expects the external PM to define them first. In our projects these are not "more efficiency" but measurable figures: cycle time per order, error rate, on-time delivery, and manual corrections per week. ISO 9001:2015 clause 4.4 explicitly requires measurable process objectives. Anyone who skips the KPI definition gets clean documentation without measurable business benefit.
Our take
The BPM CBOK 4.0 is a sound methodological frame. But it is not a job profile. Taken literally in the Mittelstand it produces vacancies nobody fills — or short-term hires who leave after five months.
How We Deploy the Process Manager Role Methodically
We deploy the process-manager role in four phases: goal clarity and KPI definition before any process capture, structured as-is analysis before to-be design, BPMN model before the tool discussion, and metrics-led improvement after go-live — vendor-neutral and tool-independent throughout.
Within our vendor-neutral ERP consulting we treat process management as the methodological core. A four-stage path has proven itself:
- Goal clarity and KPI set — before any process capture. Four to six leading metrics per core process.
- As-is process analysis — structured capture in BPMN 2.0 or as value stream mapping; bottlenecks are quantified.
- To-be design with KPI linkage — every to-be element references the metric it moves.
- Continuous improvement — PDCA cycles, monthly KPI cockpit, half-yearly audit preparation.
How we anchor the role methodically
We take the role on temporarily, ad interim, in Mittelstand mandates, couple it with the process-owner function in the same person, and hand over to an internal anchor. Anyone arriving with a fixed BPM suite documents toward the suite — not toward the business logic.
The material difference from classic BPM consulting offers: we recommend vendor-independently. More on our stance in our consulting approach.
Common Mistakes With the Process Manager Role in the Mittelstand
Four failure patterns recur in Mittelstand process-manager engagements: a pure CBOK 4.0 job profile, KPIs only after process capture, BPM tool purchase before methods clarity, and no internal handover point. Three are organisational, one is methodological — all are avoidable.
Mistake 1 — pure CBOK 4.0 job profile in a 200-person firm. The advert describes the corporate role, operationally untenable in the Mittelstand. Result: a twelve-to-fourteen-month vacancy. Fix: advertise the role cluster (PM + PO + light project coordination) explicitly.
Mistake 2 — KPIs only after process capture. Modelling runs without defining how success is measured. Result: BPMN diagrams without audit robustness. Fix: KPI set before every modelling session.
Mistake 3 — BPM tool before methods clarity. Management buys Camunda or Signavio before in-house methods capability can carry it. Result: suite on the shelf. Fix: the PM gets the mandate before tool selection.
Mistake 4 — no internal handover point. The external PM documents the to-be processes and leaves the project. Nobody maintains the metrics. Fix: an internal process anchor is named on day one — analogous to the requirements-specification handover.
Our take
Across over 1,200 projects it shows: addressing these four points before the advert cuts time-to-hire from fourteen to under six months.
Frequently Asked Questions
A process owner carries strategic end-to-end accountability for a business process — from the business goal through the value stream to customer impact — and defines the higher-order metrics. A process manager executes tactically, documents in BPMN 2.0, and supplies the metrics for steering. The ABPMP BPM CBOK 4.0 separates both roles. In the DACH Mittelstand with 50 to 500 employees both routinely sit with one person because neither a BPM centre of excellence nor a dedicated owner committee exists.
BPMN 2.0 dominates as the modelling standard. Roughly 70 percent of our engagements start in Visio, PowerPoint, or ERP-bundled tooling. Dedicated BPM suites such as Camunda, SAP Signavio, or ARIS pay back only above fifteen activity steps per core process, with ISO 9001 or IATF 16949 audit obligation, or in an ERP migration. Lean, Six Sigma, and PDCA round out the toolkit; Celonis-class process mining pays back only above roughly 500 employees and one million transactions per year.
The ABPMP cascade is the international reference: CBPA and CBPP on BPM CBOK 4.0. The BPM Institute also issues the BPMP certificate. In DACH the DGQ process-manager certificate has taken hold — especially in industries with ISO 9001, ISO 13485, or IATF 16949 obligations. Our view: DGQ for DACH practice with an audit angle, CBPP for international careers.
Next Steps
Before posting a vacancy or engaging an external process manager, a short clarification of three points pays back: which business processes should be owned? How is success measured — which four to six leading metrics per process? Which roles should be combined — PM alone or in a cluster with PO and light project coordination? To anchor the role or prepare a concrete engagement, our digitalisation services and our ERP consulting practice are the starting points. Methodologically related are our wiki articles on the process owner and the ERP system. For deeper methodological background, see our insights.
30 minutes with Dreher Consulting
A structured clarification of your process-manager role — process scope, KPI set, and the right role cluster, vendor-neutral, from over 1,200 projects in the DACH Mittelstand.
