The problem that Operational Excellence addresses in SMEs
To the point: Inefficient processes eat up profits, time and employee motivation - at the same time there is a lack of resources for expensive management consultancies.
We repeatedly see the same pattern in SMEs in the DACH region: cycle times are longer than necessary. Error rates are not falling, even though employees are working hard. Inventories grow while supplier demand remains chaotic. The cause is often not a lack of commitment, but fragmented processes, a lack of transparency and IT systems that are older than the implementations on which they run. Our experience with companies with between 50 and 1,200 employees shows that operational excellence is not optional for SMEs. It is essential for survival when competitors are becoming faster, supply chains more uncertain and personnel costs are rising.
The problem is not the idea of OpEx itself. The problem is that many approaches come from large corporations - Six Sigma black belts, complex controlling departments, certification programs that take years. SMEs need something different: pragmatic, quickly measurable improvement without bringing operational work to a standstill.
An overview of the methodology (5 phases, without corporate overhead)
To the point: OpEx success for SMEs follows a clear, iterative pattern: analysis, redesign, enablement, rollout, operationalization - in parallel, not serially.
Phase 1: Diagnosis & data collection (weeks 1-3). We do not document all possible processes - we select. The focus is on the most painful area: order-to-cash, make-to-order, supply chain planning or customer service. We use simple measurements (lead time, error rate, resource utilization) to create a baseline. AI-supported process analysis tools help to identify bottlenecks more quickly. Data analysis in the best sense - systematic, not speculative.
Phase 2: Process redesign & target state (week 3-8). Here we work with subject matter experts from your team - not with consulting theory, but with practical know-how. We define a lean target state (not perfect, but measurably better) and identify which ERP support is required. When inventories grow chaotically, it is often not due to people, but to a lack of planning transparency in the ERP. The solution is not a new tool, but process logic that makes better use of the existing system.
Phase 3: System configuration & enablement (week 6-12). ERP parameters are adjusted, workflows are configured. This is not a new implementation - this is intelligent reconfiguration. Parallel: Training, but no lectures. We train with real scenarios that employees will see tomorrow. Change management is essential here: those who are not taken along become a risk.
Phase 4: Pilot rollout & monitoring (week 10-16). We introduce the new process in a department or plant. Measurement begins immediately. If it doesn't work, we readjust - not after three months, but daily. Iterative, not waterfall.
Phase 5: Scaling & operationalization (week 14+). As soon as pilot KPIs are green, we roll out to other areas. At the same time, we establish governance: Who measures? Who escalates in the event of deviations? Who is responsible for improvement? Without clarity here, OpEx gains are quickly lost.
Our classification: These phases are not a dogmatic waterfall model. They overlap. Pilot and scaling can start in parallel, depending on risk tolerance. The key is measurability from phase 1.
Practical example: South German mechanical engineering company with measurable outcome
To the point: Theory is valuable. Practice is everything.
A mechanical engineering company with 320 employees from Baden-Württemberg was faced with a classic challenge: order-to-delivery time of 14 weeks, competitors managed 8-10 weeks. Margins were falling. In over 1,200 projects, we have seen that the cause is usually not poor design, but fragmented processes between sales, engineering, production and logistics.
Diagnosis: Sales drafted requirements in Word and email. Engineering modeled in CAD systems that were not automatically linked to ERP. Production saw changes too late. Stocks of semi-finished products proliferated.
Redesign: Structured requirements management (requirements specification standard), coupled with CAD metadata and automatically transferred to ERP. Production planning gained real visibility. Speed was achieved through parallelization, not by increasing speed.
Result after 14 weeks:
- Order-to-delivery: 14 weeks → 9 weeks (36% reduction)
- Rework: 12% → 3% of production costs
- Employee satisfaction: decreased during the upheaval, increased by 22% afterwards - less crisis management required
ROI: Amortized in 18 months. The mechanical engineering company did not expand its team; it optimized its resource utilization. This is OpEx for SMEs.
Common mistakes when applying operational excellence
To the point: Good intentions without structure lead to standstill instead of optimization.
1. Perfectionism instead of pragmatism. Many SMEs want to do everything right - ISO 9001 certification, implementation by the book. This takes two years and the competition is gone. "Good Enough OpEx" measurably reduces throughput times and creates fast ROI. Perfect can come later. Often it never comes because the business is over in the meantime.
2. IT without process logic; process logic without IT. Some companies buy a new ERP and think that solves OpEx. Others optimize processes without checking whether the ERP can map the new logic at all. Both approaches fail. ERP is an enabler, not a solution - the solution is the process itself.
3. Underestimating change management. If employees are not involved, they unconsciously torpedo the new processes - or they leave. In times of skills shortages, attrition is expensive. Change management is not HR sentiment; it is business risk.
4. Projects that are too broad. "We are optimizing the entire value chain!" will almost certainly fail. OpEx needs focus: order-to-cash or procurement or production, one after the other. Success creates momentum for the next module.
5. No governance after rollout. New processes quickly fall into disuse if it is not clear who is monitoring them. KPIs become routine measurement, not strategic navigation tools. Dedicated process owners are not optional.
Application in DACH SME sectors
To the point: Operational Excellence is not industry-specific magic. But the priorities shift depending on the industry.
Mechanical engineering & production technology: focus on lead time reduction, error rates in production and assembly, stock levels of components and semi-finished products. CAD systems must be linked to ERP and production planning. Successful projects show 20-40% lead time gains and 50-80% quality improvement.
Medical technology & pharma: Focus on compliance without operationalization sacrifices, batch transparency, traceability. Master data governance is critical, especially with regulatory requirements. ROI is measurable, but longer term (12-18 months).
Food & logistics: focus on throughput optimization, supply chain flexibility, waste reduction. WMS systems and transport optimization are core levers. Sustainability (ESG integration) is not positioned here as a separate compliance obligation, but as a cost-saving opportunity: Less waste = less cost.
Service & Professional Services: Focus on project execution, resource utilization, time-to-invoice. Process owners for PMOs and CRM integration are central. Interface efficiency (APIs, data exchange) is just as important as process design.
Next steps
Operational excellence is not a one-off project. It is cultural maturity. The first step is always an honest diagnosis: Where is it hurting? Where does inefficiency cost the most euros or weeks? That's where we go first - not everywhere at the same time, but in a focused way. Momentum is created from there. If you would like to know whether Operational Excellence is right for your situation, we invite you to a brief analysis meeting. No selling, just clarity: Where are the levers? In what order? Realistic effort and ROI.
