Value stream mapping is not software. It is a four-phase approach. We have held the sequence in our projects across more than 30 years — the same shape carries a two-day workshop and a six-week sprint.
Phase 1 — product family and scope. A product family is a set of articles with a similar process route. From our experience defining the family too broadly maps three value streams at once and identifies none. Rule of thumb: one family per map, ideally with 60–80 per cent of the process route shared. The REFA Lexikon — Wertstromanalyse anchors this boundary as the first methodological step.
Phase 2 — capturing the as-is on the floor. The value stream is captured live, not in the conference room. We walk the shop floor and the back office with the operative team, time cycle durations, and record information breaks at every handover. The Fraunhofer IPA Wertstromdesign programme has worked with the same approach for over twenty years.
Phase 3 — symbol system and to-be value stream. The as-is map uses the standard symbol system. From it the to-be value stream is built with KPIs: lead time, value-add ratio, inventory per station. We set quantitative targets — qualitative to-be pictures rarely get implemented in the Mittelstand.
Phase 4 — translation into the requirements document. Every information break is translated into a functional ERP requirement — testable and prioritised. The VDMA — Industrie 4.0 meets Lean framework extends the concept of waste from material flow to information flow.
Practical example: a pragmatic short VSM at a Mittelstand manufacturer
Anonymised case from specialised mechanical engineering in Baden-Württemberg: 180 employees, two plants, legacy ERP system 14 years old. Goal: an ERP selection grounded in real value streams rather than current screen masks. Outcome: 31 prioritised requirements out of two workshop days and an ERP selection that finished in seven months instead of the planned eleven.
We have observed across more than 30 years in DACH Mittelstand engagements a recurring pattern: value stream mapping works as soon as the operative line dominates. Concrete example: a specialised equipment manufacturer in Baden-Württemberg, classic Mittelstand, 180 employees, two plants and a legacy ERP from 2012. The brief: an ERP selection based on real value streams — not the screen masks of the legacy system.
We captured the value stream over two days — with production leadership, sales support, planning, dispatch, and IT leadership at a brown paper. Day one: product family “Standard Platform Specialised Equipment” defined, as-is value stream recorded with a stopwatch. Result: 38 process boxes, 17 information breaks, real lead time of 41 working days against value-add time of 4.2 days. Value-add share: 10 per cent.
Day two: to-be value stream with KPI targets (lead time below 22 days, information breaks below seven) and translation into 31 prioritised requirements. From our experience this pace is only reachable when the core team carries decision authority. The ERP selection ran in seven months instead of the planned eleven — because the requirements document came out of the value stream, not out of 200 individual interviews.
Common mistakes in VSM execution
Five patterns sort Mittelstand value-stream projects reliably into success or failure: scope too broad, wrong product family, no operative line involvement, no to-be value stream with KPIs, and no connection to a requirements document or change programme. All five are visible before the first workshop day — if anyone is willing to look.
We have identified five patterns in our projects that predict Mittelstand failure — independent of any methodological dogma.
Mistake 1 — scope too broad. Three plants and seven value streams in parallel is not a workshop, it is a strategy project. One product family per map.
Mistake 2 — wrong product family. A product family defined by revenue rather than by process route leads almost always into a dead end. We cluster in our projects by shared processing route, not by accounting view.
Mistake 3 — staff functions instead of operative line. Value stream mapping with Lean officers and controllers, but without production and sales support, produces a methodologically clean picture without operative commitment. The REFA standard anchors operative involvement as a core requirement.
Mistake 4 — no to-be value stream with KPIs. Many initiatives stop after the as-is capture. Only the to-be value stream with lead-time, inventory and information-flow targets makes the method effective.
Mistake 5 — no connection to a requirements document or change programme. Value stream mapping without a downstream connection evaporates. In the context of an ERP selection that means: every bottleneck is translated into a testable requirement.
What VSM textbooks won't tell you
Three gaps between textbook VSM and Mittelstand reality that the standard sources rarely address: information-flow waste is under-represented, the question of when process mining is the better method, and the fact that most Mittelstand VSMs fail not at the capture but at the translation into requirements.
The standard literature explains how to draw a value stream map. It is silent on three points that decide impact in the DACH Mittelstand — visible also in the IT&Production analysis on the Value-Stream-4.0 target architecture, which names the translation step as the missing bridge.
1. Information-flow waste is under-represented
The classic symbol system from Learning to See concentrates on material and order flow. In the Mittelstand, the most expensive waste sits in information breaks: Excel sheets instead of master data, manual order confirmations, duplicate entries between CRM and ERP. The VDMA — Industrie 4.0 meets Lean framework extends the concept of waste to information flow — this extension carries the translation into the requirements document.
2. When process mining is the better method
Not every process belongs on brown paper. With fewer than 20 variants and a single system, a value-stream workshop is efficient. With five systems and over 50 variants, process mining delivers the more precise view. The Celonis — VSM Guide documentation positions both methods as complementary.
3. Most VSMs fail at the translation
From our experience Mittelstand value streams almost never fail at capture. They fail at phase four — the translation into testable requirements. This step appears in no textbook because it sits outside Lean methodology. We anchor it in every ERP selection — it is the actual value of the exercise.
Our take
Value stream mapping is not a symbology problem. It is a connection problem — and the connection is called a requirements document, a change programme, or a to-be architecture.
How we use VSM methodically for ERP selection
We use value stream mapping as mandatory preparation for every Mittelstand ERP selection — not because Lean is elegant, but because a requirements document without a validated as-is value stream very probably digitises the inefficient processes of the legacy system. The method supplies the requirements base our SCOReX®-supported evaluation then condenses into a measurable selection decision.
In the DACH Mittelstand we observe the same anti-pattern again and again: the new ERP is selected before anyone has a defensible picture of the current value stream. The outcome is the most expensive form of digitalisation — the digitalisation of inefficient processes, followed by a change backlog the project never closes.
We therefore treat value stream mapping as mandatory preparation for every ERP selection. Sequence: first the to-be value stream, then the requirements document, then the market. From the to-be value stream we derive between 30 and 80 prioritised requirements — testable, with acceptance criteria.
These requirements feed into our selection methodology, which weights every value-stream segment and measures it against vendor responses. The value stream supplies the requirement; the evaluation procedure supplies the decision. On the practice side under process management and in our overview of independent ERP consulting we describe this integration in detail.
Application in manufacturing and service-Mittelstand verticals
Value stream mapping works reliably in manufacturing with clear product families, but also delivers measurable leverage in the service Mittelstand and across administrative processes. We deploy the method in mechanical engineering, furniture and kitchen manufacturing, logistics complaint handling and order-based services.
We have deployed value stream mapping across industries. Read-out from more than 30 years of Mittelstand practice.
Mechanical engineering and specialised equipment. Core use case: many variants, long lead times, multiple stations. Typical leverage: 20 to 35 per cent lead-time reduction.
Furniture and kitchen manufacturers. At a Mittelstand kitchen manufacturer in the DACH region we analysed the configuration-to-delivery chain: 47 process boxes, six information breaks between configurator, ERP and dispatch. The translation into 22 functional requirements became the basis for an S/4HANA selection.
Logistics and trade. Complaint and returns handling are ideal value-stream candidates: many touch points, visible waiting times. In our projects we have seen 25 to 40 per cent lead-time reduction repeatedly.
Service and administration. Order-to-cash, purchase-to-pay and record-to-report are prime value-stream candidates — especially as preparation for an ERP selection. The Fraunhofer IPA Wertstromdesign programme has confirmed this breadth of application for over twenty years.
Frequently asked questions
How long does a pragmatic value stream mapping engagement take in the Mittelstand?
In practice we have seen one to two operative workshop days are enough for a defensible as-is and to-be value stream of one product family, provided the core team from the operative line is on site together. The academic textbook variant with Green-Belt certification and a multi-week project delivers about 20 per cent additional insight for Mittelstand decisions at three times the effort.
Value stream mapping or process mining — which fits when?
From our experience the methods are complementary, not competing. Value stream mapping fits physical material and order flows with a manageable variant count. Process mining is the better choice when a process runs through five or more systems, shows over 50 variants, and several hundred cases per month — then event logs deliver depth that brown paper cannot. Most Mittelstand ERP selections start with value stream mapping.
Why should I do VSM before, not after, the ERP selection?
Because an ERP requirements document without a validated as-is and to-be value stream very probably digitises the inefficient processes of the legacy system. We recommend in our projects placing the value stream as the first preparatory step — from it emerges a requirements document with 30 to 80 testable items. Whoever runs the value stream after the selection builds a change backlog the project never leaves.
Who from the company needs to be in the workshop?
At least 60 per cent operative line: production leadership, planning, sales support, dispatch and IT leadership. Staff functions supplement but do not dominate. We have observed across more than 30 years that the most valuable observations come from the people who run the process daily. Managing-director presence at the end of day two is mandatory: without decision authority even the best to-be value stream evaporates.
What does a pragmatic value stream mapping realistically cost?
For a pragmatic two-day value stream mapping with methodology, facilitation and translation into a prioritised requirements document, consulting costs in our projects sit between 15,000 and 35,000 euros — depending on complexity, number of product families and depth of the requirements translation. Whoever asks only for an as-is capture without a to-be value stream and without a requirements-document connection stays at the lower end, but forfeits the actual value of the method.
Next steps
Value stream mapping works when it connects to something downstream — usually an ERP selection or a change programme. We examine three points with you: is the product family clear? Is an operative core team available? Is managing-director presence at the end of day two confirmed? When two of the three answers are “not yet”, that is where the work begins — not in the workshop calendar. Background on our methodology in our Insights and under digitalisation services.
30 minutes with Dr Dreher
A structured assessment of your value stream and the connection options — vendor-independent, based on 30+ years of project practice.
