What Process Excellence really means in the Mittelstand
To the point: Process Excellence in the Mittelstand does not mean a full Black Belt programme and corporate overhead. It means four to six steering-relevant KPIs, a clearly delimited pilot process, and 90 days to the first visible FTE relief. Anyone starting with a hundred KPIs ends up measuring mainly their own initiative overhead.
Most consulting offerings on Process Excellence carry a silent corporate DNA: Belt hierarchies, multi-year roll-out plans, a dedicated staff function. In the DACH Mittelstand that does not work. A firm with 280 employees that is running three strategic initiatives in parallel cannot build an Excellence academy — and does not need to. What matters is a pragmatic cut: one pilot process with real customer value, four to six KPIs, a named process owner, a clear 90-day cadence.
Process Excellence (PEX) describes the continuous improvement of efficiency, effectiveness, and quality along a firm's value-creating processes. It combines methodologies (Lean, Six Sigma, TQM, Kaizen, BPR, DMAIC), design discipline (clear inputs, outputs, accountabilities), and a management system that sustains improvement over time. That is the textbook definition.
In the Mittelstand there is a translation layer that most sources skip. A firm with 80, 250, or 600 employees typically has dual-hatted roles, a flat hierarchy, and no dedicated process managers. Implementing Process Excellence there without adaptation imports corporate overhead. The process-oriented approach of ISO 9001:2015 requires clear inputs, outputs, KPIs, and accountabilities — but not necessarily a Belt programme.
Across more than 50 Mittelstand projects in the DACH region, PEX works when three conditions converge: first, a Business Process Owner with a mandate (not just an assignment); second, a KPI that is actually discussed in the steering committee; third, a pilot that produces a visible — not merely statistical — change. Anything else is methodological folklore.
Our take: PEX in the Mittelstand is not a method catalogue but a decision about roles, KPIs, and pilot size. Anyone who skips clarifying those three points can swap Lean for Six Sigma or Kaizen freely — the effect stays equally low.
The pragmatic cut: 4–6 KPIs, one pilot, 90 days
To the point: Three building blocks — four to six steering KPIs, one pilot process with real customer value, a 90-day cadence. No Belt hierarchy, no staff department, no multi-year roll-out plan. Typical FTE effect: 15 to 30 percent on the pilot process.
Across selection and optimisation projects we have developed a cut that runs without a Belt hierarchy and works in Mittelstand reality. It has three building blocks.
Four to six steering KPIs. Not a hundred. Typical candidates: lead time (order to delivery), first-pass yield, on-time delivery to customer, inventory days of supply, manual touchpoints per transaction, rework rate. More than six and the executive team loses focus in the steering committee. Fewer than four and goal conflicts stay invisible.
One pilot process with real customer value. Source-to-Pay, Order-to-Cash, Plan-to-Produce, or Hire-to-Retire — it does not matter which, but pick one. Not the politically easiest one, but the one where the executive team genuinely feels pain. A systematic process analysis helps as the starting point.
90-day cadence. Days 1–15: as-is recording including value stream mapping and waste identification along the seven types (TIMWOODs). Days 16–45: quick wins, target design, PDCA cycle for the first two to three measures. Days 46–75: pilot operation with weekly steering. Days 76–90: handover to the Business Process Owner, KPIs anchored in regular reporting.
What we observe empirically: with this cut, FTE effects typically land in the range of 15 to 30 percent on the pilot process. The real value, though, is not the FTE share but the freed-up capacity, which flows either into growth or into the next PEX wave. Hold the 90-day cadence with discipline for one year and you have three stable waves — plus an organisation that knows how to work with KPIs.
Practical example: south German kitchen manufacturer, 320 employees
To the point: The same south German kitchen manufacturer (€80M revenue, 320 employees) we describe in our process analysis entry ran a parallel PEX wave with five KPIs on Order-to-Cash. After three 90-day cycles: order-confirmation lead time from 13 to 5 business days, on-time delivery from 71% to 94%, FTE relief 22% on the pilot process. No Belt programme, no process-mining tool, no Excellence office.
The manufacturer wanted to set up a methodology in parallel with the process analysis — one that would permanently anchor the identified measures in the steering committee. The managing director explicitly ruled out a classical Belt programme: too much method ballast, too little time. Together with her and six process owners we defined a reduced cut — five KPIs on Order-to-Cash, three 90-day cycles over nine months, no dedicated Excellence staff role.
Wave one focused on the handovers between sales, engineering, and production planning — the three points where the process analysis showed seven of the thirteen business days were lost. Three measures were developed via A3 logic and 5-Why: a shared configuration template, an escalation rule with named deputies, a weekly 30-minute sync between the three units. Wave two addressed invoice verification jointly with finance. Wave three set up the monthly steering meeting in which the five KPIs are reviewed against agreed targets.
After the three waves — nine months total — the effects were measurable. Order-confirmation lead time down to 5 business days (from 13), on-time delivery at 94% (from 71%), rework rate on the core SKUs below 6% (from 14%), manual touchpoints per order reduced from an average of 9 to 4. FTE relief on the pilot process landed at 22%. The freed-up capacity flowed into two directions — growth (more configuration variants without headcount addition) and preparation for the ERP selection project.
Effort: 32 consulting days over nine months plus roughly 18 person-days internal effort across the six process owners. No Black Belt curriculum, no process-mining licence budget. The most effective investment was the weekly steering-committee discipline in the first three months — without it the initiative would have evaporated within 90 days, like most workshop-driven initiatives do.
Process Excellence as a prerequisite for ERP selection
To the point: An ERP system mirrors processes. If the processes are not stable, not unambiguous, and not measurable in KPIs, the ERP will paper over the gaps — typically through workarounds, Excel side-files, and manual handovers. Maturity level 3 in the core processes before selection is the honest minimum bar.
This sequence is not a method debate but economic common sense. An ERP system mirrors processes. If the processes it mirrors are not stable, not unambiguous, and not measurable in KPIs, the ERP will inevitably mask the gaps — typically through workarounds, Excel side-files, and manual handovers.
From our advisory practice there are four areas where process ambiguity makes any ERP selection more expensive or capsizes it outright. First, master data: without clean material, customer, and supplier records, every ERP function delivers fake precision. Second, workflow logic: anyone who hasn't defined escalation and approval rules ends up taking them from the system default — and fighting their own tool for years. Third, interfaces: every undocumented manual handover between two departments becomes either a customising demand or a workaround in the new ERP. Fourth, KPI definitions: without aligned metrics, reports in the new system become contested ground immediately.
The EFQM Model 2025 and the APQC Process Classification Framework provide maturity references that a mid-market firm can honestly measure itself against before an ERP selection. The question is not whether you reach maturity level 5. The question is whether you can hold maturity level 3 stably in the core processes before standing up a new system.
Our take: ERP success requires process stability. Selecting without a PEX run-up buys complexity and disguises it as a solution — the price comes due in subsequent years as customising spend and shadow-Excel.
Five anti-patterns: common Mittelstand mistakes
To the point: Five patterns that recur across our 50+ Mittelstand projects — each one preventable in the scoping conversation, not in the methodology phase.
- Software before process. Management orders a new ERP or workflow tool before the process is defined. The system then mirrors the disorderly as-is state and freezes it.
- Island optimisation. One department optimises locally without aligning with upstream and downstream units. The local effect is measurable; the global effect is often negative.
- Missing process owner. An initiative is launched but no one receives the mandate to drive it permanently. Within three months the topic peters out.
- Post-workshop yo-yo effect. A Kaizen or value-stream workshop delivers visible improvements, but without anchoring in the steering committee the baseline returns within six months.
- KPI inflation. Instead of four to six steering KPIs, 30 or 50 metrics are built up. The steering committee loses focus and the discussion shifts to data quality instead of decisions.
Our take: Three of the five anti-patterns are governance failures, not method failures. Anyone who ignores that is buying method against a leadership problem — and that never works.
Frequently Asked Questions
Process Excellence focuses on individual processes — their efficiency, quality, and controllability. Operational Excellence is broader and additionally covers culture, leadership behaviour, supply-chain performance, and asset management. In the Mittelstand the distinction matters less than in corporations because the same people carry both topics. More important than the boundary is the sequence: Process Excellence is the operational foundation on which Operational Excellence builds. Starting both in parallel with separate methodologies creates duplicate structures the Mittelstand cannot sustain.
As a full programme — usually no. From our experience a two-day Lean foundation course for the central process owners, supplemented by one or two internally trained multipliers with deeper method knowledge, is sufficient. A full Black Belt programme pays off from around 800 employees and with stable series processes at high repetition frequency. For most Mittelstand processes, A3 logic, 5-Why, and KPI discipline matter more than statistical design of experiments. Method knowledge without an application field decays into a certificate collection.
Process mining delivers hypotheses. From event logs it shows where deviations, loops, and bottlenecks emerge. It does not replace the process discussion or the decision. We typically recommend process mining from the second or third PEX wave onwards, once the organisation has learned to work with KPIs. AI functions — automated root-cause analysis or configuration suggestions — are useful amplifiers but not a substitute for roles, mandates, and steering-committee discipline. Without those foundations process mining produces reports nobody reads.
From our practice a three-stage logic works. First, hard effects on the pilot process: lead time, on-time delivery, error rate, manual interventions — measured before and after with identical definitions. Second, FTE effects: typically 15 to 30 percent relief on the pilot process, with freed capacity flowing either into growth or the next PEX wave. Third, strategic effects: stronger delivery and quality commitments become defensible in the market, ERP and digitalisation projects become cheaper and faster. The first two stages are quantifiable; the third shows up in the follow-on wave.
Next steps
If you are considering starting a Process Excellence initiative in the Mittelstand or sharpening an existing one, the pragmatic entry point is usually a two-hour situation review. Three questions are enough for a first assessment: which four to six KPIs do you actually steer today? Which process has the biggest pain from the management perspective? Which person gets the mandate to drive a 90-day cadence — with protected time and an escalation right? The conversation is free of charge and ends with an honest assessment — not a proposal with method overhead.
