Why SAP standardization isn't enough

Most SAP S/4 programs fail long before go live. But the steering committee never sees it until the factory shows the bill.   If you’ve ever delivered an S/4 rollout into a real plant, you already know the pattern. The program dashboard is green, design is locked, UAT is acceptable enough and everyone is gearing up for cutover… while the factory quietly braces for impact.   Here’s the reason. The KPIs that matter, the ones senior leaders judge success on, don’t originate in ERP. They surface in the plant.   Inventory turns, schedule adherence, ECO cycle time, OEE, FPY, scrap, batch release, line flow, continuity of change, are all shaped by PLM truth, APS feasibility and MES execution. ERP records the intention. Execution determines the outcome.   The trouble is simple. S/4 programs keep treating execution as Wave 3 instead of Wave 0. > APS gets deferred. > MBOM gaps get ignored. > Routings are assumed, not validated. > MES is treated like a future enhancement. And by the time the plant is asked to adopt the “new process,” the program has already locked in decisions that don’t match how the factory runs.   When that happens, the symptoms roll in fast: • Schedule chaos • Inventory drift • Quality disruption • Change delays • Firefighting • Rising cost-to-serveS • A blame game that points fingers at ERP   The real issue isn’t ERP. The real issue is missing manufacturing execution intelligence.   Tie ERP, PLM, APS, MES, Quality and IIoT together in a way that respects factory physics, and everything stabilizes. Ignore that layer and the plant is left improvising.   If this sounds familiar inside your own S/4 programs, you’re not alone. We’re seeing the same patterns across Defense, Automotive, Industrial, Med Device and Pharma. And we’re helping GSIs turn this recurring pain into a capability that protects margin, improves KPIs and strengthens client relationships.   Happy to compare notes with anyone facing these symptoms right now.

Stop customizing your S/4HANA implementation. Seriously. Stop. I just had a client insist they needed custom Z-codes for their "unique" business processes. They wanted to recreate all their ECC customizations in S/4HANA. I explained that customizations are severely limited in modern SAP environments. They didn't believe me. Here's the reality: clean core isn't optional anymore. SAP, Oracle, and Workday all require process standardization. You fit your business to the application, not the reverse. Custom development creates technical debt that compounds over time. This client had hundreds of Z-codes in their ECC system. Each one represented a process that didn't fit standard SAP functionality. Each one required maintenance, testing, and updates. Each one increased their total cost of ownership. In S/4HANA, those customizations become roadblocks. They prevent you from accessing new functionality. They complicate upgrades. They create integration problems with third-party tools. The clean core approach forces process discipline. Instead of customizing the system to match broken processes, you fix the processes to match best practices. Instead of building technical workarounds, you implement business solutions. Companies that embrace clean core get faster implementations, lower ongoing costs, and access to new capabilities. Companies that insist on customizations get expensive implementations that limit their future options. Your business processes aren't as unique as you think. Standard SAP functionality handles 90% of business requirements across industries. Are you planning to fit your processes to S/4HANA or force S/4HANA to fit your processes?

𝗚𝗲𝗿𝗺𝗮𝗻 𝗦𝘂𝗽𝗲𝗿𝗠𝗮𝗿𝗸𝗲𝘁 𝗖𝗵𝗮𝗶𝗻 𝗟𝗶𝗱𝗹 𝗷𝘂𝘀𝘁 𝘄𝗿𝗼𝘁𝗲 𝗼𝗳𝗳 €𝟱𝟬𝟬 𝗠𝗜𝗟𝗟𝗜𝗢𝗡 𝗼𝗻 𝗮 𝗳𝗮𝗶𝗹𝗲𝗱 𝗦𝗔𝗣 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻. Seven years. 1,000 employees. Hundreds of consultants. Zero ROI. The German retail giant had to scrap their entire eLWIS project and revert to legacy systems. What went catastrophically wrong? ➤ Refused to adapt processes to SAP standards (insisted on purchase price vs retail price inventory valuation) ➤ Massive over-customization that broke system integrity ➤ Executive turnover killed project continuity (CEO + Head of IT both left mid-project) ➤ Inadequate change management despite massive investment The kicker? SAP awarded Lidl a "best customer" prize in April 2017... then Lidl killed the project 15 months later. 𝗛𝗲𝗿𝗲'𝘀 𝘁𝗵𝗲 𝗯𝗿𝘂𝘁𝗮𝗹 𝗿𝗲𝗮𝗹𝗶𝘁𝘆: 𝟱𝟱-𝟳𝟱% 𝗼𝗳 𝗘𝗥𝗣 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻𝘀 𝗳𝗮𝗶𝗹. 𝗧𝗵𝗲 𝘁𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝘆 𝘂𝘀𝘂𝗮𝗹𝗹𝘆 𝘄𝗼𝗿𝗸𝘀 𝗳𝗶𝗻𝗲. 𝗧𝗵𝗲 𝗼𝗿𝗴𝗮𝗻𝗶𝘇𝗮𝘁𝗶𝗼𝗻𝘀 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗶𝗻𝗴 𝗶𝘁? 𝗡𝗼𝘁 𝘀𝗼 𝗺𝘂𝗰𝗵. 𝗞𝗲𝘆 𝗹𝗲𝘀𝘀𝗼𝗻𝘀 𝗳𝗼𝗿 𝗳𝗶𝗻𝗮𝗻𝗰𝗲 𝗹𝗲𝗮𝗱𝗲𝗿𝘀: ✅ Set hard budget escalation limits (50%, 100%, 150% triggers) ✅ Limit customization to TRUE competitive differentiators ✅ Ensure leadership stability during multi-year projects ✅ Change management isn't optional - it's survival ERP success isn't about buying the best software. It's about executing the best transformation strategy. #ERP #DigitalTransformation #CFO #ProjectManagement #SAP Key lessons for finance leaders:  Set hard budget escalation limits (50%, 100%, 150% triggers)  Limit customization to TRUE competitive differentiators  Ensure leadership stability during multi-year projects  Change management isn't optional - it's survival ERP success isn't about buying the best software. It's about executing the best transformation strategy. What's the most expensive implementation mistake you've witnessed? #ERP #DigitalTransformation #CFO #ProjectManagement #SAP

🚫 SAP Alone Is Not Enough I’ve spent 20 years working with SAP, and I’ll tell you something many consultants won’t: 👉 SAP doesn’t win the digital transformation battle alone. Modern companies are no longer running on a single platform — they run on ecosystems: • SAP S/4HANA for the digital core • Salesforce or HubSpot for CRM • Microsoft Power Platform for workflows and quick apps • Specialized tools for logistics, HR, compliance, or customer experience But here’s the problem: ➡️ These systems often don’t talk to each other. ➡️ Data is duplicated, delayed, or misaligned. ➡️ Business processes suffer — and nobody takes full ownership. The future of IT leadership isn’t about choosing the “best tool.” It’s about designing an integrated digital core — where SAP works with other systems to enable real-time, end-to-end visibility and agility. Integration is no longer a technical afterthought. It’s a strategic pillar of digital success. If you’re a CIO, Head of IT, or transformation leader, here’s the question you should ask: Do our systems enable flow — or create friction? #SAP #DigitalTransformation #IntegrationStrategy #ITLeadership #Salesforce #PowerPlatform #S4HANA #CIO #BusinessProcessTransformation

"I get why it’s right for SAP. But it’s not right for us." Ever heard a customer say this? I have. More than once. And they’re not talking about bugs or broken processes. They’re talking about something harder to measure — fit. ✔️ The system works ✔️ The design follows best practices ✔️ Every box is checked But still… something feels off. Why? Because in our push to deliver standard, we sometimes erase what made the business special. 🚫 Decision-making feels slower 🚫 The workflows don’t match how teams actually operate 🚫 The system works, but the people don’t love it This is the quiet cost of “fit-to-standard” — when you fit the business into the system instead of fitting the system around the business. SAP should enable the business — not reshape it. As consultants, our job isn’t to enforce the model. It’s to protect what makes our customers competitive. Standard only works when it fits. #SAP #ERP #DigitalTransformation #ConsultingLife #CustomerVoice #BusinessDesign #FitToStandard