The KVP process — Kontinuierlicher Verbesserungsprozess, the German adaptation of Kaizen — anchors continuous improvement as a PDCA cycle in DACH quality-management systems. From over 1,200 Dreher Consulting projects we know the pattern: KVP is routinely misused in the Mittelstand as a deflection from hard architecture decisions before ERP go-live — „we'll fix that later in KVP" — and fizzles within two years. We recommend a reduced toolkit and starting KVP only once the process map, process owners and KPIs are in place. That yields a durable improvement engine instead of workshop theatre.
What Is the KVP Process? Definition and Demarcation
The KVP process is the systematic, employee-driven improvement of processes, products and services in small steps. Its backbone is the PDCA cycle (Plan-Do-Check-Act). ISO 9001:2015 and IATF 16949 make continuous improvement a mandatory part of the quality-management system.
KVP stands for Kontinuierlicher Verbesserungsprozess — the German adaptation of Kaizen (Masaaki Imai, 1986). Where Business Process Reengineering demands radical breaks, KVP relies on incremental improvement in small steps, carried by those who run the process daily.
Its methodological backbone is the PDCA cycle — Plan-Do-Check-Act, after Shewhart and Deming. A hypothesis is planned, piloted, measured, and standardised on success. ISO 9001:2015 (clause 10.3) anchors PDCA and continuous improvement as a core requirement of quality-management systems; Amendment 1:2024 adds the climate-action reference.
Three terms must be kept apart to grasp the KVP process precisely:
- KVP vs. Kaizen — Kaizen is the original Japanese philosophy from the Toyota Production System; KVP is the German, more formal adaptation with its own roles (KVP officer, process owner).
- KVP vs. Six Sigma DMAIC — Six Sigma addresses large, statistically measurable quality problems via Black Belt structures; KVP runs continuously, broadly carried, without a belt hierarchy.
- KVP vs. Business Process Reengineering — BPR is a radical redesign of a process; KVP is the incremental upkeep of an existing process against a clean target model.
The Deutsche Gesellschaft für Qualität (DGQ) maintains the KVP-officer profile and its certification; under VDA 6.3 and IATF 16949 a documented KVP mechanism has been an audit requirement for years.
Why the KVP Process Matters in the DACH Mittelstand in 2026
Digitalisation pressure, ERP modernisation, and tighter CSRD and climate-action requirements raise the stakes for structured improvement. At the same time, from our experience most KVP programmes in the Mittelstand fizzle within two years — because they stand on no documented target process.
First, digitalisation pressure rises. The Bitkom Digitalisation of the Economy 2025 study reports that 53 percent of 603 firms surveyed struggle with their digitalisation (2024: 48 percent), and 82 percent see a crisis of hesitant digitalisation in the current economy. KVP closes the operational gaps after each roll-out wave — provided it stands on a clean target process.
Second, the ERP landscape is changing. In the DSAG Investment Report 2026, process optimisation and ERP modernisation are consistently among the top investment drivers in the DACH Mittelstand. This is exactly where the anti-pattern sits: in our projects — typically 80 to 500 employees per mandate — hard ERP architecture questions are regularly deferred into a later KVP circle.
Third, the survival rate is unforgiving. From our experience a large share of Mittelstand firms launch KVP programmes with energy, but only a minority keep them alive beyond two years. The top success factor is a documented target process — not the charisma of the KVP officer.
The method itself is not at issue — Imai established Kaizen in 1986; the KVP adaptation has been standard since the first ISO 9001 wave. From our experience, what is at issue is where in the value chain it is deployed.
PDCA Cycle and KVP Toolkit — What Really Works in the Mittelstand
For Mittelstand firms with 50 to 500 employees, five tools are enough: Ishikawa, 5-Why, 5S, PDCA sheet, Pareto. From our experience Six Sigma DMAIC and Black Belt structures rarely pay off in smaller Mittelstand firms. The reduced toolkit dominates practice.
PDCA is the standard frame of every KVP process. Plan: formulate an improvement hypothesis grounded in data — cycle time, defect rate, on-time delivery. Do: pilot it, cleanly separated from regular operations. Check: test the effect against the defined metric. Act: on success, standardise and carry the improvement into the process documentation; on failure, discard the hypothesis and plan again.
From over 1,200 projects we have learned: Six Sigma DMAIC and Black Belt structures rarely carry in 50-to-500-employee firms. Training Black Belts without a target process map pays for consulting revenue, not improvement potential.
For the Mittelstand, we recommend five tools that carry the load in practice:
- Ishikawa diagram — cause-and-effect analysis along Man, Method, Machine, Material, Milieu, Measurement. Delivers the likely levers in two hours.
- 5-Why — ask „why" five times until the structural cause rather than the symptom surfaces. Invaluable in master-data clean-up.
- 5S audit — Sort, Set in order, Shine, Standardise, Sustain. Entry-level tool, visible, low barrier.
- PDCA sheet — a one-page standard form per improvement idea. The discipline of documentation, not of creativity.
- Pareto analysis — the 80/20 rule on defect classes, complaint causes, master-data error rates. Keeps the right topics on top.
VDI 2870 Part 1 on Integrated Production Systems names KVP and PDCA as a central design principle and remains the binding reference for production operations.
What KVP Textbooks Leave Out — the Architecture Trap
Three points that most KVP textbooks and consulting decks do not state plainly, but that decide success or abandonment in DACH Mittelstand programmes. From over 1,200 Dreher Consulting projects we know the recurring pattern well.
1. „We'll fix that later in KVP" is the most expensive sentence in the ERP project
Contrary to the textbook framing of KVP as a universal improvement mechanism, we observe a clear anti-pattern: KVP is misused as a deflection from hard architecture decisions before ERP go-live. Master-data logic, variant structure, document flow — „we'll sort it out later in KVP". The result: architectural debt runs as a permanent theme through the KVP circle. In the majority of our recent KVP engagements with DACH Mittelstand firms, this exact pattern turned the improvement engine into a repair shop.
2. KVP without a target process ends in the yo-yo effect
From our experience: whoever enters the KVP workshop without a documented target process optimises symptoms instead of causes — and sees the old patterns again months later. We call it the yo-yo effect of process optimisation. Process map first, then process owner, then KPI, then KVP — the sequence is non-negotiable.
3. Six Sigma belts and corporate method stacks are overhead in the Mittelstand
Black Belt training, champion structures, and the full DMAIC stack come from corporate worlds with dedicated quality staff. In a 200-employee firm the structural prerequisites are missing — and the toolkit becomes a consulting-revenue machine.
Our take
A KVP initiative without clean architecture decisions, without a target process model, and without five-tool discipline is workshop theatre. The three prerequisites belong before the method — first the architecture, then KVP as the discipline that keeps it alive.
How We Set Up the KVP Process in the Mittelstand (Four Phases)
We set up KVP programmes in the DACH Mittelstand in four phases: target process and owner, toolkit and KPI anchoring, pilot wave, standardisation. Typical set-up: six to ten weeks, then continuous operation on a quarterly cadence.
In our vendor-neutral ERP and process consulting we treat KVP not as an isolated quality topic but as part of post-go-live process architecture. The following four-step approach has proved itself:
- Target process model and process-owner model. Identify three to five end-to-end core processes, assign one owner per process, keep the target model in BPMN or a comparable notation. A firm without a process map builds it here — otherwise KVP will not carry. We often combine this step with value stream mapping from the Lean tradition.
- Toolkit and KPI anchoring. Train the reduced five-tool stack (Ishikawa, 5-Why, 5S, PDCA sheet, Pareto) in the pilot team and define a handful of metrics per core process — cycle time, defect rate, complaint rate, on-time delivery. Process mining helps when the ERP provides clean document logs; process analysis gives the as-is reference point.
- Pilot wave and quick wins. Run three to five KVP initiatives through PDCA sheets in the pilot area, with monthly review and visible quick wins. From over 1,200 projects we know: without visible wins in the first ten to twelve weeks, sponsorship erodes.
- Standardisation and roll-out. Carry successful improvements into the process documentation, institutionalise KPI tracking, appoint a KVP officer, take the next area into the wave. Connect with process excellence as the umbrella.
The difference from corporate-style offerings: we do not build a Black Belt staff that structurally overwhelms a Mittelstand firm. We deliver the reduced toolkit and the KPI anchoring that keep the improvement engine viable beyond 24 months — pragmatic, not corporate overhead.
Case Study: Southern German Machine Builder After ERP Go-Live (Anonymised)
A southern-German machine builder with around 230 employees launched a KVP programme three months after ERP go-live. After twelve months: master-data error rate cut by two-thirds, order-cycle time shortened, programme still alive — against the usual two-year fade.
The builder of bespoke industrial machines had called us because three months after ERP go-live master-data quality was crumbling: duplicates in the article master, inconsistent variant logic, document flows that did not run through. Leadership wanted to „finally start KVP" — we held the reflex back.
In six weeks we set the prerequisites. Three core processes were already documented from the ERP implementation: order-to-cash, procure-to-pay, hire-to-retire. For each we agreed two to three metrics with the named process owner — master-data error rate, cycle time, on-time delivery. The reduced toolkit was trained in the sales and master-data pilot team.
The first three PDCA initiatives ran in the pilot wave: deduplication of the article master, standardisation of variant creation, 5S in the sales back office. After twelve months: master-data error rate cut from around 14 percent to under 5 percent, order-cycle time shortened by roughly a fifth. More importantly, the programme is alive.
The decisive difference lay in the sequence: target process before method, process owner before workshop, metric before idea. Had we begun with the first workshop, we would have produced the same yo-yo effect within about a year.
Common Mistakes in KVP Programmes in the Mittelstand
We see four failure patterns again and again in Mittelstand KVP programmes. All four are avoidable — if they are addressed before method selection. Three are organisational, one is purely methodological. Fixing them costs less time than waiting them out.
- Mistake 1: KVP as architecture deflection. The firm pushes hard ERP architecture decisions before go-live into the later KVP circle. Master data, variants, document flow are „to be clarified later in KVP". From our practice: the dominant anti-pattern in the majority of our recent engagements. Consequence: architectural debt runs through the KVP circle, the improvement engine turns into a repair shop.
- Mistake 2: KVP without a target process model. Workshops start without the core processes documented. The team optimises symptoms instead of causes, and the yo-yo effect sets in after six to nine months. Solution: process map and process owner first, then KVP.
- Mistake 3: a corporate method stack in the Mittelstand. Black Belt training, champion structures, and the full DMAIC stack introduced in 200-employee firms. From our experience these structures rarely carry in the Mittelstand. Solution: the reduced five-tool kit.
- Mistake 4: KVP without KPI anchoring. Ideas are collected but not measured against a metric. After about a year effectiveness erodes. Solution: two to three metrics per core process before the first workshop.
Our take: the mistakes are rarely methodological. They are organisational and architectural — and that is exactly where vendor-neutral consulting has leverage. We recommend starting KVP only once architecture, target process and metrics are in place.
Frequently Asked Questions on the KVP Process
The KVP process relies on incremental, broadly carried improvements with a reduced toolkit — Ishikawa, 5-Why, 5S, PDCA sheet, Pareto. Six Sigma addresses larger, statistically measurable quality problems via DMAIC and Black Belt structures. From our experience Black Belt structures rarely carry in 50-to-500-employee Mittelstand firms. We recommend KVP as the continuous operation and Six Sigma only for bounded major issues above the 500-employee threshold.
After the go-live — not before, not in parallel. In the majority of our recent KVP engagements with DACH Mittelstand firms, KVP was misused as a deflection from hard architecture decisions („we'll fix it later in KVP"). Architectural debt then runs through the KVP circle, and the engine becomes a repair shop. We recommend KVP two to four months after go-live — once the target process is documented, process owners are named, and KPIs are in place.
In automotive supply chains under VDA 6.3 and IATF 16949 a documented KVP mechanism is an audit requirement, and a DGQ KVP-officer certification helps. Outside automotive the certification is nice-to-have, not a must. More important than the certificate is organisational anchoring — one process owner per core process, a KVP officer with mandate and time budget, monthly review with management. Without that anchoring even a certified officer cannot carry the programme past 24 months.
Next Steps
Before launching a KVP programme, a short clarification step is usually worthwhile: which architecture decisions are open? Which core processes are documented? Who carries the process-owner role? Anyone who skips this builds a programme that fizzles in the yo-yo effect after about a year.
For depth, see our process-management services and our ERP consulting. We work vendor-neutrally and assess requirements along process, cost and system architecture.
Related entries: process mining, value stream mapping, process analysis and process excellence. Arrange a first conversation via the contact page or browse our Insights.
References: ISO 9001:2015, DGQ KVP materials and VDI 2870 Part 1.
30 minutes with Dreher Consulting
A structured pre-clarification of your KVP plan — the open architecture decisions, documented core processes, the process-owner model and KPI anchoring before the first workshop, vendor-neutral and drawn from over 1,200 projects in the DACH Mittelstand.
