Demand-Driven Lean Systems

From Forecast-Driven to Demand-Driven: The Power of DDMRP In today’s volatile markets, traditional MRP systems struggle to keep pace with fluctuating demand and long lead times. That is where Demand Driven Material Requirements Planning (DDMRP) steps in — a modern planning and execution methodology designed to protect flow and enhance responsiveness across the supply chain. What is DDMRP? DDMRP is an innovative approach that integrates the best of MRP, Lean, and Theory of Constraints (TOC). It focuses on decoupling points, dynamic buffers, and real demand signals rather than relying solely on forecasts. The goal? To align material flow with actual customer needs while reducing inventory volatility and improving service levels. The 5 Components of DDMRP (as shown in the image): 1️⃣ Strategic Inventory Positioning – Identify where to hold inventory within the supply chain to maximize responsiveness and minimize lead time. 2️⃣ Buffer Profiles and Levels – Establish inventory buffers (red/yellow/green zones) for different items based on demand variability and lead time. 3️⃣ Dynamic Adjustments – Continuously adapt buffer sizes based on real-time changes in demand, seasonality, and lead times. 4️⃣ Demand Driven Planning – Plan and execute replenishment based on actual consumption signals rather than forecasts. 5️⃣ Visible and Collaborative Execution – Use real-time visibility and shared information across functions to act proactively and maintain smooth material flow. Each step moves from Strategic → Tactical → Operational, ensuring agility at every level. MRP vs. DDMRP (Key Differences) 1️⃣ Driver → MRP: Forecast-driven → DDMRP: Actual demand-driven 2️⃣ Planning Logic → MRP: Push-based → DDMRP: Pull-based 3️⃣ Inventory Focus → MRP: Centralized, high levels → DDMRP: Strategically positioned buffers 4️⃣ Response Time → MRP: Slow, reactive → DDMRP: Fast, adaptive 5️⃣ Visibility → MRP: Departmental silos → DDMRP: Cross-functional collaboration collaboration 🏭 Real-Life Example In one of my projects within a manufacturing facility, we transitioned from traditional MRP to DDMRP. Before: Production orders were based on forecasts that often missed actual sales trends, leading to overstocked components and stockouts of key items. After implementing DDMRP: → Inventory dropped by 25% → Service level improved from 85% to 98% → Planners shifted focus from firefighting to proactive flow management The visibility and responsiveness achieved were game-changing. 💡 Conclusion DDMRP is not just a system tweak — it is a mindset shift toward aligning supply chains with real demand. By positioning, protecting, and pulling strategically, organizations can achieve higher agility and reliability in an unpredictable world. 👉 Have you implemented DDMRP in your organization? I would love to hear your experience and how it reshaped your planning process.

Most companies fail at Lean before they even start. The reason is simple: they begin with tools instead of the customer and the problem. After leading manufacturing transformations across global automotive operations, I keep seeing the same pattern. But Lean does not start with tools. It starts with the customer need and what is the problem.? Lean is fundamentally a way of thinking about work, people, and waste. Some lessons learned along the way: • Real quality improvement is systemic. When quality improves the right way, financial performance, safety, and morale improve together. • Copy-paste Lean rarely works. Trying to replicate Toyota or any “best practice” without understanding your own culture usually fails. • Understanding the problem is already half the solution. • Lean tools are countermeasures to minimize specific waste. • Culture and leadership matter more than tools. ⸻ A real example. At one of the largest assembly complexes in the world, the plant was competing to secure a new powertrain program. Failure would put thousands of jobs at risk. The challenge seemed impossible: • Highest operating cost in the network • Supposedly no space available But when we went to the Gemba, we discovered something surprising. Almost 40% of the plant was used to store only a few hours of inventory — in what was considered one of the leanest operations in North America. The problem wasn’t space. It was material flow design. A cross-functional team developed a progressive Electronic Kanban system to visualize several days of customer demand based on the vehicle assembly sequence — something not previously used in powertrain operations. This enabled: • Continuous small-lot deliveries • Direct flow to line racks • Synchronization between production and deliveries The supply chain became an extension of the assembly line, freeing massive space. ⸻ Another example: Operators were spending nearly 20% of their time walking just to pick up small parts. Using the Kowake principle, small-part containers were attached directly to the conveyor system, bringing parts directly to operators. The impact: • No walking for parts • Higher assembly focus → better quality • Less fatigue → better ergonomics • Less line-side inventory Combined with tools such as kitting, Minomi, Kowake, Electronic Kanban, Kamishibai, and direct delivery, the operation achieved: • ~50% space reduction • Significant cost improvement • High double-digit inventory savings Most importantly, thousands of jobs were preserved, and the plant secured the new engine program. ⸻ The lesson Lean does not start with tools. It starts with understanding the problem, the people, and the customer. Go to the Gemba. Listen. Understand. Then act. ⸻ Where do Lean transformations fail most often in your experience? • Tools • Culture • Leadership ⸻ #LeanLeadership #OperationalExcellence #Manufacturing #ContinuousImprovement #Gemba #Leadership © 2026 Yuri Rodrigues

Most attempts to 'manage demand' end up shifting it around the system – or even making it worse. What if we started with this: rising costs aren't driven by the population, but by the way our systems work? Until we address that, every new tweak or pilot will just add another layer of #complexity. After nearly thirty years in #publicservices, we've pulled together seven demand management approaches that take the whole system seriously – joining up behaviour, data, strategy, and culture. Here’s the outline: 1) Whole system predictive modelling – understand the current system and population characteristics to predict and pre-empt need 2) Prevent demand from arising – use behavioural science, social marketing, and community development to stop issues before they start 3) Early identification and intervention – target risk earlier and build capacity and self-efficacy in communities 4) More effective handling of demand – improve assessment and access, reduce rework and failure demand 5) More effective response to demand – design for outcomes, not activity; align interests across the system 6) Systems leadership – integrate budgets and shape collaborative cultures 7) Measurement, learning, evaluation – compare real to predicted impact, and adapt as you go What's needed is to move from crisis to capability - we've subtitled this 'earlier, easier, #withyou'. It's hard to speak to the world of #earlyintervention and #demandmanagement *and* the world of #strengthsbased working. But it's essential. This work connects #commissioning, #systemsthinking, #systemsleadership #leadership, data, system flow, #publicsector innovation, and the changing role of professionals. The question is: if the system is driving demand, what are we doing that unintentionally feeds it?

You break down total production demand into small, fixed-time batches instead of trying to produce everything in one long run. A large order is completed through several repeated production cycles. Each cycle has a defined duration and includes both production and the necessary change-over. This makes the workload predictable and easier to manage. By using fixed-time batches, you stabilize the production and change-over sequence. The same products are made in the same order, over and over again. This reduces variability and surprises. Change-over preparation is planned as part of normal production time, rather than treated as an exception or emergency. The goal is to keep total change-over time below 10% of total production time. Because change-overs happen frequently but in a controlled way, thy can be standardized as well so teams get faster and more consistent at them. Problems become visible quickly instead of being hidden inside long production runs. Standard work becomes possible because the process no longer changes every day. With standards in place, teams can begin kaizen activities to remove workarounds, shortcuts, and “getting by” behaviors, and steadily improve safety, quality, cost, and delivery. Small standardized batches will allow you to react better to change in mix in customer demand and not carry so much inventory. #LeanIsBetter

How to Make Supply Chains Smarter with Demand-Driven MRP (DDMRP) In today's unpredictable world, traditional supply chain planning just doesn't cut it anymore. Forecasts fail. Inventory piles up in the wrong places. Customers face delays. Enter: Demand-Driven MRP (DDMRP) A modern approach that makes supply chains agile, responsive, and resilient — based on actual demand, not unreliable forecasts. Let’s break it down into 5 core components — with real-life cues and examples to make it stick. --- 1. 📍 Strategic Inventory Positioning Place inventory where it makes the biggest impact. Think of it like water stations on a marathon route — you don’t put them randomly, you place them where runners really need them. Cue: “Where should I place my buffer stock to absorb disruptions?” 2. 📊 Buffer Profiles & Levels Use data-driven formulas to calculate how much inventory to hold. This is based on average usage, lead time, and a safety margin to absorb demand variability. Formula Example: Buffer = Daily Usage × (Lead Time + Safety Days) If you sell 10 units/day, lead time is 5 days, and you want 2 safety days: 10 × (5+2) = 70 units buffer Cue: “How much inventory should I hold to stay protected — but not overstocked?” 3. 🔁 Dynamic Buffer Adjustments Conditions change — so should your buffers. Update regularly based on new demand trends, supplier performance, or seasonality. Real-world analogy: You adjust your umbrella size depending on how hard it’s raining. Cue: “Am I adapting my stock levels as things change?” 4. ⚙️ Demand-Driven Planning Forget static forecasts. Plan using real orders and actual inventory levels. No more producing 1,000 units hoping they'll sell — produce what’s needed now. Real-life example: A food truck prepares meals based on real-time orders, not a week-old forecast. Cue: “Am I planning based on real customer demand?” 5. 👥 Visible & Collaborative Execution Everyone sees the same data. Everyone reacts fast. Use shared systems so your team can adjust production and procurement on the fly. Analogy: Like using a shared traffic app to reroute together when there's a jam. Cue: “Can my team respond quickly to demand shifts — together?” Why DDMRP Works: Reduces stockouts and overstocking Makes your supply chain responsive and stable Focuses resources where they actually matter Builds trust across teams and with customers Quick Recap: Plan by demand, not guesswork Use buffers to absorb chaos Continuously adapt and align your supply chain Real transformation happens when we stop reacting to the past and start responding to the present. #SupplyChain #DDMRP #DemandDriven #InventoryManagement #Manufacturing #SCM #SupplyChainPlanning #DigitalTransformation #AgileOperations #LeanManufacturing #SupplyChainInnovation

Something that maybe is not discussed enough in the IBP space is understanding if a company is Supply Driven or Demand Driven. A supply driven company mindset will be we produce what we can and after try to sell it. Supply-driven companies push products to market based on capacity and constraints, not demand, often leading to high inventory and misaligned customer service. 🔹 Supply-Driven industries examples: ⚡ Oil & Gas / Energy ▶️ Crude oil, natural gas ▶️ Supply driven by extraction capacity & geopolitics ▶️ Demand is volatile, but supply can’t quickly adjust 🧪 Chemicals (basic / bulk) ▶️ Ethylene, chlorine, fertilizers ▶️ Continuous high-capacity plants (economies of scale) ▶️ Push production → inventory absorbs demand swings ⛏️ Mining & Metals ▶️ Copper, aluminum, steel ▶️ Supply depends on extraction & smelting capacity ▶️ Market prices shift to balance demand vs. supply 💻 Semiconductors (historically) ▶️ Chip foundries need massive CAPEX, run “flat out” ▶️ Example: 2020–22 shortages → supply dictated allocations 👉 These industries show how supply constraints, not customer demand, set the pace of business variability. In these industries, production realities dictate planning more than demand signals. A demand driven company mindset will be that they sell what the market wants, and after they will make it or buy it. Demand-driven companies align supply to real market needs, pulling products based on demand signals to stay responsive and minimize waste. 🔹 Demand-Driven industries examples: 🛒 Retail & E-commerce (Amazon, Zara, Walmart) ▶️ Real-time reaction to POS & online sales data ▶️ Zara: designs & produces based on fast-changing fashion trends ▶️ Amazon: demand sensing drives assortment & fulfillment 🥫 Consumer Packaged Goods (CPG) (P&G, Unilever, Nestlé) ▶️ Forecasting & consumption data drive supply chain ▶️ Promotions, seasonality, shopper behavior = core drivers 💊 Pharmaceuticals ▶️ Driven by prescriptions & patient needs ▶️ Supply adjusted to demand, though constrained by regulations & batch processes 📱 High-Tech & Electronics (Apple, Dell) ▶️ Dell: classic “Build-to-Order” demand-driven model ▶️ Apple: massive demand sensing for new product launches & pre-orders 👉 These industries thrive by pulling supply in line with real market needs, staying agile, responsive, and customer-centric. In these industries, customer demand signals dictate planning more than supply constraints. Of course we have also Hybrid examples where companies straddle both worlds: 🚗 Automotive → traditionally supply-driven (plants must run efficiently, suppliers lock capacity), but shifting toward demand-driven with customization, EVs, and direct-to-consumer sales. 🥗 Food & Beverage → basic commodities (sugar, flour) are supply-driven, but branded consumer goods (snacks, beverages) are demand-driven. Why is important for SAP IBP? My answer in the comments as I ran out of space 😋

One hidden cost in many production systems is changeover time. When a machine needs hours to switch from one product to another, companies often produce large batches to compensate. But large batches create other problems: more inventory, less flexibility, and slower response to customer demand. This is where SMED (Single Minute Exchange of Dies) becomes powerful. The idea is simple: Reduce setup time so production can run smaller batches, faster, and more flexibly. A few key principles make the difference: • Analyze the current changeover process carefully. • Separate what must be done while the machine is stopped from what can be prepared in advance. • Convert as many internal steps as possible into external ones. • Simplify and standardize the remaining setup activities. • Continuously improve the process with small incremental changes. Behind this method is an important mindset: Long setup times are often accepted as “normal”. Lean thinking challenges that assumption. When setup time drops, flexibility increases, inventory decreases, and the whole production system becomes more responsive to demand. Sometimes, operational excellence does not come from doing more. It comes from changing faster and smarter. #LeanManagement #SMED #OperationalExcellence #ContinuousImprovement #Manufacturing #ProcessImprovement

Rethinking Operational Efficiency: Moving Beyond Rigid Schedules As CEOs and business leaders, we often rely on schedules—shifts, service rollouts, and predefined resource allocations—to manage our operations. While this approach provides structure, it inherently introduces inefficiencies that blow budgets & frustrate customers. Consider a grocery store with 12 aisles but only 3 open during peak hours, with long wait times and unhappy customers; or a convenience store with one register open and workers everywhere doing who knows what. How about a restroom cleaned twice a day in an airport area with minimal foot traffic, wasting labor on tasks that aren’t needed. These are clear examples of over- or under-utilization that impact both the bottom line and customer experience. The reality is, customer demand isn't static. It fluctuates throughout the day and week, with many factors affecting it -- yet many companies continue to operate on fixed schedules that can't adapt in real-time. Schedule-based operations based on snapshot survey responses are simply guesses that will almost always be wrong. Imagine a different approach—one where companies sense and analyze demand in real time, then dynamically allocate resources accordingly. This isn’t just a futuristic concept; it’s a practical strategy that can save hundreds of thousands of dollars annually. Our clients are leading the way and beating their competition with this approach today. Consider the ROI - if a business can reduce unnecessary staffing by just 20%, that’s a potential saving of tens of thousands of dollars per location each year— and hundreds of thousands overall. These are funds that can be reinvested into improving service quality, technology, or expansion. Beyond cost savings, pivoting from scheduled operations to demand-driven management enhances customer satisfaction, reduces wait times, and builds brand loyalty. The key is to harness real-time data—feedback, demand signals, environmental factors, and operational processes —and adapt accordingly. As leaders, it's time to rethink our operational models for a more efficient, customer-centric future. Let's move beyond the schedule and embrace sensing and adapting on the fly. Let me know other examples of under- or over-staffing that have frustrated you - I'd love to hear them!!! #OperationalEfficiency #CustomerExperience #SmartResources #BusinessInnovation FeedbackNow

Mixed-Model Value Stream Design is an advanced Lean technique for creating flow in environments where multiple product types (or service variants) must be produced on the same resources. Unlike a single product value stream, where flow is straightforward, mixed-model design deals with variety, shared resources and fluctuating demand and still aims to deliver at takt, with minimal waste. What It Is A value stream: the end-to-end set of activities that deliver value to the customer. Mixed-model: multiple product families or variants share the same processes, equipment and people. Design: intentionally structuring flow, scheduling and resource allocation so that all models can be produced smoothly, without excess inventory or delays. Key Principles of Mixed-Model Value Stream Design 1. Define Product Families Group products that share ~80% of process steps and have similar workloads. This reduces complexity and makes flow design manageable. 2. Calculate Family Takt Time Takt = Available Time ÷ Total Demand (for the family). Ensures the system is designed to meet aggregate demand across models. 3. Establish Production Intervals Decide how often each product in the family will be produced (e.g., every hour, every shift). Shorter intervals = lower inventory, faster response. 4. Balance Machines and Operators Use Yamazumi (operator balance charts) to distribute work evenly across operators for all models. Ensure machines and people can keep pace with family takt. 5. Enable Quick Changeovers SMED (Single-Minute Exchange of Dies) is critical. The faster you can switch between models, the shorter the production interval and the leaner the flow. 6. Design Pull Systems Kanban loops sized for mixed demand. Supermarkets or FIFO lanes to buffer shared resources. 7. Visual Management Mixed-model heijunka boards (level-loading boards) to schedule variety without chaos. Obeya dashboards to track flow efficiency across models. Example Imagine a factory producing three types of pumps (A, B, C) on the same line: Daily demand: A = 200, B = 100, C = 50 → Total = 350 units/day. Available time: 420 minutes/day. Family Takt = 420 ÷ 350 ≈ 1.2 minutes/unit. The line is designed so that every 1.2 minutes, some pump (A, B, or C) comes off the line. A heijunka schedule sequences them (e.g., A-A-B-A-C …) to level demand and avoid batching. Why It Matters Flexibility: Handles product variety without excess inventory. Responsiveness: Shorter lead times, faster reaction to customer demand. Efficiency: Shared resources are optimized, not overloaded. Scalability: Supports growth and product diversification without redesigning the entire system. Mixed-Model Value Stream Design is a perfect bridge between Lean rigor and enterprise complexity. It’s especially powerful when paired with digital Obeya dashboards, so leaders can see in real time how variety impacts flow.

Been working with Toyota Motor Corporation Production System for years. Thought I knew it cold. Then I started implementing Unified Namespace (UNS) architectures and realized something obvious that I'd completely missed. TPS isn't just about eliminating physical waste. It's about eliminating information waste too. All those data silos in your plant? That's muda. Hunting through five different systems to find one number? Also muda. Waiting three days for a report that should be real-time? Definitely muda. UNS is basically digital kaizen. Instead of workers stopping the line when they see defects, your systems automatically flag problems across the entire operation. Instead of kanban cards, you get dynamic data flows that adjust production based on actual demand. The best part? You're not throwing out Toyota's principles. You're making them work better. The companies crushing it right now aren't picking sides between lean and digital. They're using TPS philosophy to guide their data architecture decisions. Makes total sense once you see it. #LeanManufacturing #DigitalTransformation #ToyotaProductionSystem #UnifiedNamespace