10. Lean Operations, JIT and Agile Systems

Introduction and Context

Operations managers are required to deliver value with fewer resources, shorter lead times, dependable quality and greater responsiveness to customers. These demands have made lean operations, just-in-time (JIT) systems and agile operations central to contemporary operations and logistics management. Although the terms are often used interchangeably, they describe related but distinct approaches. Lean focuses on eliminating activities that do not create customer value. JIT coordinates the flow of materials and information so that resources arrive when needed, in the required quantity and at the required quality. Agility concerns the ability to respond rapidly and profitably to volatile demand, product variety and unexpected disruption.

The origins of lean thinking are strongly associated with the Toyota Production System (TPS), but its logic extends beyond automobile manufacturing. Hospitals, warehouses, ports, retailers, software firms and professional services organisations have adapted lean principles to their own processes. In logistics, lean thinking can reduce inventory, handling, waiting, transport and errors; however, excessive cost reduction without risk analysis may weaken resilience. The managerial challenge is therefore not to pursue minimum inventory or maximum speed in isolation, but to design an operating system that balances efficiency, quality, flexibility and continuity.

Learning Objectives

After studying this chapter, students should be able to:

1. Explain the meaning and relationships among lean operations, JIT, agile and leagile systems.

2. Identify the principal forms of operational waste and diagnose their causes.

3. Apply takt time, pull systems, Kanban, 5S, cellular operations, kaizen and setup-reduction methods.

4. Distinguish push, pull, lean, agile and leagile responses to different demand conditions.

5. Evaluate the managerial, technological, ethical and supply-chain implications of lean implementation.

6. Design improvement priorities for manufacturing, warehousing, transport and service operations.

Lean Thinking: Value, Flow and Discipline

Lean begins with value as defined by the customer. An activity is value-adding when it changes a product or service in a way for which the customer is willing to pay and when it is performed correctly the first time. Activities that consume resources but create no customer value are waste, or muda. Some non-value-adding activities may nevertheless be necessary under current conditions—for example, regulatory inspection or a safety check. These should be reduced or redesigned rather than automatically eliminated.

A widely used lean logic consists of five linked ideas: specify value, identify the value stream, make value flow, establish pull and pursue perfection. The value stream includes all activities and information flows required to deliver a product or service, from supplier to customer. Mapping this stream reveals queues, rework, hand-offs, excess inventory and delays that departmental measures may conceal. Flow means that work proceeds with minimal interruption, batching and waiting. Pull means that upstream activity is authorised by actual downstream demand rather than by forecasts alone. Perfection refers to continuous, disciplined improvement rather than a belief that a process can become permanently perfect.

Lean is not simply a collection of tools. It is an operating philosophy supported by standards, employee involvement, problem-solving and respect for people. Tools such as Kanban or 5S are ineffective when managers use them as isolated cost-cutting programmes while ignoring unstable processes, poor maintenance, inadequate training or fear of reporting problems.

The Eight Wastes

The traditional seven wastes are often expanded to eight by including unused human capability:

• Defects: errors, damage, incorrect documentation, rework and returns.
• Overproduction: producing earlier or in greater quantity than required.
• Waiting: idle labour, equipment or materials caused by delays and imbalances.
• Non-utilised talent: failing to use employee knowledge, creativity and problem-solving ability.
• Transportation: unnecessary movement between facilities, departments or locations.
• Inventory: raw materials, work-in-process or finished goods beyond immediate requirements.
• Motion: unnecessary movement by people, such as searching, walking or reaching.
• Over-processing: extra approvals, duplicate data entry, excessive packaging or specifications beyond customer need.

These categories are diagnostic rather than mutually exclusive. For example, a defect may generate rework, additional transport, waiting and excess inventory. Managers should therefore investigate the system causes of waste rather than blame individual operators.

JIT and the Architecture of Pull

JIT aims to make materials and information available in the right quantity, at the right place and at the right time. Its purpose is not merely to reduce stock; inventory is treated as a signal of problems such as unreliable suppliers, long setups, uneven production or poor quality. When inventories are reduced, these problems become visible and must be solved.

A pull system authorises production or replenishment in response to consumption. In a basic two-bin system, the empty container or card signals the need to replenish the quantity associated with that container. A push system, in contrast, releases work according to a schedule or forecast, often regardless of downstream capacity. Push systems remain useful where demand is highly predictable, processes are continuous or customer lead times require advance production. Pull systems are particularly effective when work can be paced and replenishment quantities are controlled.

Kanban

Kanban is a visual signalling mechanism that limits work in process and coordinates replenishment. A Kanban may be a card, electronic message, barcode, container or space on a rack. A simple calculation for the number of Kanban containers is:

Number of containers = (Demand during replenishment lead time × (1 + safety factor)) / Container capacity

The result is normally rounded upward. Demand during lead time must reflect the relevant usage rate, and the safety factor should be based on variability and risk rather than habit. Too many cards conceal excess inventory; too few may cause frequent shortages if the process is unstable. Electronic Kanban can connect warehouse, production and supplier systems, but digitisation does not correct inaccurate master data or unreliable processes.

Kanban works best when quality is stable, replenishment lead times are known, containers are standardised and work-in-process limits are respected. It is less suitable as the sole control mechanism for highly customised, very low-volume or unpredictable work. In such situations, capacity planning and careful scheduling may be required alongside pull signals.

Takt Time, Capacity and Flow

Takt time expresses the pace of customer demand. It is calculated as:

Takt time = Available production time / Customer demand during that time

If a process has 420 available minutes per day and demand is 210 units, takt time is two minutes per unit. Takt time is not the same as cycle time. Cycle time is the time actually required to complete one unit at a process. For sustainable flow, the effective cycle time at each required operation should be at or below takt time, after considering breaks, changeovers, downtime and quality losses.

Takt time is a demand-based planning measure, not a target to be achieved by unsafe acceleration. If cycle time exceeds takt time, the operation may need additional capacity, improved methods, work redistribution or demand-leveling. If cycle time is far below takt time, resources may be underutilised unless the difference is deliberately used to provide flexibility or support other operations. Takt calculations should be revised when demand patterns, working time or product mix change.

Unevenness (mura) and overburden (muri) are closely related to waste. Producing in large batches may create peaks followed by idle periods, while excessive workload can produce defects, accidents and equipment failure. Heijunka, or production leveling, seeks to smooth volume and mix where customer requirements permit. Leveling does not eliminate variability, but it reduces avoidable fluctuations imposed by the operating system.

Workplace Methods for Lean Improvement

5S and Visual Management

5S is a workplace organisation method: sort unnecessary items, set needed items in order, shine and inspect, standardise the improved condition, and sustain the discipline. Its value is operational, not cosmetic. A well-designed workplace reduces search time, reveals abnormal conditions and supports safe, repeatable work. Red-tagging can identify items for removal or review, while location markings, shadow boards, status lights and standard labels make deviations visible.

Visual management enables a person unfamiliar with a process to understand its normal condition quickly. Examples include inventory min–max markings, colour-coded routes, safety boards, production status displays, standard work charts and escalation signals. Visual controls should communicate actionable information; excessive signs create visual noise and may hide important abnormalities.

Standard Work and Kaizen

Standard work documents the best currently known method, sequence, timing and quality checkpoints for a task. It provides a baseline for improvement and training. A standard is not a restriction against innovation; it is the reference point against which a proposed improvement can be tested. If every operator follows a different method, performance variation becomes difficult to analyse.

Kaizen means continuous, incremental improvement. Effective kaizen uses direct observation, data, root-cause analysis and experiments. The Plan–Do–Check–Act cycle supports this discipline: define the problem and plan a change, implement it on a controlled basis, check results against evidence, and standardise or revise the change. Five-Why analysis, cause-and-effect diagrams, Pareto analysis and process observation are common supporting methods. Kaizen events can accelerate focused improvement, but continuous improvement requires follow-up, ownership and measurement after the event.

Cellular Operations

A cell groups equipment, people and activities according to product or service families so that work moves through a compact sequence with less transport and waiting. Cellular layouts may use U-shaped arrangements, cross-trained operators and balanced work content. They can shorten lead time and improve accountability, but they may require duplicated equipment, careful product-family analysis and flexible staffing. Cells are most effective when product routes are sufficiently similar and demand is not so volatile that equipment becomes a severe constraint.

Setup Reduction and SMED

Long changeovers encourage large batches, which create inventory and delay responsiveness. Single-Minute Exchange of Die (SMED) is a structured approach to reducing setup time. It distinguishes internal activities, which require the machine to stop, from external activities, which can be completed while it is running. The improvement sequence commonly includes separating internal and external work, converting internal tasks to external tasks, simplifying and standardising remaining activities, and using parallel work where appropriate. Quick clamps, preset tools, standard settings and checklists can reduce both time and error. Setup reduction is strategically important because it makes smaller batches economically and operationally feasible.

Lean, Agile and Leagile Responses to Demand

Lean and agile should not be treated as competing labels with universally superior outcomes. Lean is strongest when demand is relatively stable, waste can be systematically removed and efficiency is a major priority. Agile is designed for high variety, short market windows, volatile demand and the need to respond rapidly. Agile operations emphasise postponement, modular design, flexible capacity, rapid information sharing and close customer or market sensing.

A lean system seeks smooth flow and low total cost. An agile system accepts that some flexibility, capacity buffers or postponement resources may be economically justified. Agile does not mean disorganised or permanently expedited; it requires disciplined visibility, fast decision-making and the ability to reconfigure resources.

A leagile system combines lean upstream operations with agile downstream response. The decoupling point separates forecast-driven activity from demand-driven activity. Standard components may be produced efficiently in advance, while final configuration, packaging or allocation is postponed until customer demand becomes clearer. In logistics, inventory may be positioned strategically at a postponement centre, cross-dock or regional fulfilment node. The correct position depends on product modularity, demand uncertainty, lead-time expectations, transport economics and the cost of obsolescence.

| Condition | Suitable emphasis | Typical practices |

|---|---|---|

| Stable volume and variety | Lean | Leveling, standard work, flow, low inventory |

| Highly uncertain demand and short life cycles | Agile | Flexible capacity, postponement, rapid information |

| Predictable components but uncertain final demand | Leagile | Modular production, strategic decoupling stock |

| Severe disruption risk | Resilient hybrid | Alternative sources, selective buffers, visibility |

The distinction is not absolute. A firm may use lean practices within an agile network, or agile practices for a specific customer segment while maintaining lean replenishment for standard products.

Application in Logistics and Service Operations

In warehouses, lean analysis can identify excessive travel, repeated scanning, poor slotting, congestion, mispicks and waiting at receiving or dispatch docks. Product placement based on velocity, standard work for picking, visual replenishment signals and cross-docking can improve flow. Yet a warehouse should not remove all safety stock or handling capacity merely to appear lean. Seasonal peaks, supplier unreliability and service-level commitments require explicit risk decisions.

In transport, waste includes empty kilometres, waiting for loading, repeated documentation, inefficient route sequences and avoidable handling. Pull-based replenishment and milk-run collection can synchronise deliveries from several suppliers. Digital visibility can support dynamic routing, but frequent schedule changes may increase emissions or operational instability if they are not governed by clear priorities.

In services, the customer often participates in the process and demand is difficult to store. Lean service methods may reduce queue time, duplicate data entry, unnecessary approvals and hand-offs. Examples include appointment leveling in healthcare, standardised claims processing and self-service information for routine requests. Service quality must be defined broadly: speed is not an improvement if it reduces accuracy, accessibility, privacy or professional judgment.

Digital Enablement and Contemporary Developments

Digital technologies strengthen lean and agile systems when they improve the quality and speed of information. Warehouse management systems, enterprise resource planning, Internet of Things sensors, electronic Kanban, RFID, process mining and real-time dashboards can reveal location, status, consumption and bottlenecks. Predictive analytics can anticipate equipment failure or demand shifts, while artificial intelligence can support forecasting, slotting and exception prioritisation.

Technology introduces its own risks. Poor data quality can create false signals; excessive alerts can cause alarm fatigue; opaque algorithms may allocate work unfairly; and cyberattacks can interrupt connected supply networks. Automation should therefore be evaluated through total cost, maintainability, worker safety, resilience and service impact—not only labour reduction. Human expertise remains essential for interpreting abnormalities, managing exceptions and making ethical trade-offs.

Current practice increasingly combines lean with resilience and sustainability. Firms are questioning whether lowest inventory is always appropriate when geopolitical disruption, climate events or supplier concentration threaten continuity. Circular logistics adds reverse flows, repair, reuse and recycling to conventional value-stream analysis. Green kaizen examines energy, emissions, packaging and material waste alongside time, quality and cost. The emerging objective is not “lean at any cost,” but an efficient, adaptive and responsible operating system.

Implementation: From Diagnosis to Sustained Practice

A sound implementation begins with a strategic problem, not with a fashionable tool. Managers should define customer value and service requirements, select a representative value stream, observe actual work, collect baseline data and identify constraints. A current-state map can then show lead time, processing time, queues, inventory and information signals. The future state should specify the desired flow, pull points, standards, capacity and measures.

Implementation should proceed through manageable experiments. Stabilise safety, quality, equipment availability and data before aggressively reducing inventory. Train employees in problem-solving and involve those who perform the work. Establish visual daily management with a small number of meaningful measures, such as on-time completion, first-pass yield, lead time, work-in-process, changeover time and safety incidents. Audit standards without turning audits into blame exercises. Leaders must remove barriers, respond to abnormal conditions and protect the right to stop a process when quality or safety is threatened.

Common failure modes include copying Toyota practices without understanding their conditions, treating 5S as housekeeping, reducing inventory before solving instability, measuring local utilisation instead of end-to-end flow, using Kanban with inaccurate quantities, and rewarding output that creates downstream congestion. Another error is confusing employee pressure with employee involvement. Lean requires respect, learning and transparent escalation; it should not be used to intensify work beyond safe limits or to conceal workforce reductions behind improvement language.

Illustrative Case: Leagile Replenishment in a Regional Spare-Parts Network

Background

The following fictional case concerns Northstar Equipment Services, a regional distributor of industrial pumps. It holds standard seals, bearings and fasteners for many customers, but final service kits vary by pump model and maintenance requirement.

Situation and Problem

Northstar promised next-day delivery but experienced frequent stockouts of popular kits, excess inventory of obsolete configurations and long picking queues. Forecasts were unreliable because emergency maintenance demand varied considerably. The warehouse operated a push system based on monthly forecasts. Staff also travelled long distances because related components were stored in separate zones.

Analysis

A value-stream study showed that actual picking time represented a small portion of total order lead time. Waiting for replenishment, searching for locations, correcting inaccurate records and assembling kits in large batches created most delays. The company also discovered that standard components were common across many kits, while final kit composition was uncertain until the customer order arrived.

Approach

Northstar adopted a leagile design. High-volume standard components were replenished through two-bin Kanban signals with electronic consumption records. Components were re-slotted by demand velocity and product family. A small postponement area was created near dispatch, where final kits were configured only after the order was received. Standard work and visual controls defined the picking and verification sequence. A daily board tracked order lead time, stock accuracy, first-time picking accuracy and urgent orders.

The firm reduced batch sizes for kit assembly after using setup-reduction techniques on label printing and packaging. It retained a deliberately calculated buffer for critical components whose supplier lead times were long, rather than applying a blanket zero-inventory rule. Employees participated in weekly kaizen reviews, and changes were tested in one product family before wider implementation.

Outcome

The case organisation reported shorter order lead times, fewer obsolete finished kits and improved inventory accuracy. The improvement did not result from eliminating all inventory. Instead, inventory was repositioned and differentiated: lean replenishment was used for predictable components, while postponement and flexible final assembly addressed demand uncertainty. The organisation also gained clearer visibility of exceptions and supplier risks.

Learning Points

The case demonstrates that the appropriate operating model may vary within the same network. It also shows why demand information, product modularity and process stability matter when selecting lean or agile practices. Most importantly, service improvement required a combination of physical redesign, information discipline, employee involvement and selective buffers.

Ethical, Governance and Professional Considerations

Lean decisions affect employees, suppliers, customers and communities. Managers have a duty to protect health and safety, provide adequate training and avoid setting takt-based expectations that encourage unsafe shortcuts. Supplier synchronisation should not transfer all inventory and financial risk to small suppliers without fair contracts and realistic lead times. Customer data used for demand sensing must be handled lawfully and securely.

Governance requires clear ownership of Kanban parameters, master data, automation rules and exception decisions. Performance measures should prevent local optimisation—for example, a transport department should not maximise vehicle utilisation if doing so causes missed customer commitments. Sustainability reporting should account for total system effects, including expedited freight, packaging, energy consumption and product returns.

Chapter Summary

Lean operations seek customer value, continuous flow, pull-based replenishment and systematic elimination of waste. JIT exposes process problems by reducing unnecessary inventory and synchronising material and information flows. Takt time translates demand into a pace, while Kanban controls replenishment and work in process. 5S, visual management, standard work, kaizen, cellular layouts and setup reduction create the stability required for flow.

Lean is most effective under relatively stable conditions, whereas agile systems emphasise flexibility and rapid response to uncertainty. Leagile systems combine efficient upstream operations with downstream postponement or flexible configuration at a decoupling point. In logistics and services, these principles can reduce travel, waiting, errors and unnecessary handling, but inventory and capacity buffers may remain necessary for resilience. Successful implementation depends on data quality, employee involvement, ethical leadership, safety, appropriate technology and end-to-end measures rather than isolated cost reduction.

Key Terms

Agile operations: Operations designed to respond rapidly and profitably to volatile demand, variety and disruption.

Andon: A visual or electronic signal indicating an abnormal condition and requesting attention.

Cellular operations: Arrangement of resources into compact groups that process a product or service family through a related sequence.

Cycle time: Actual time required to complete one unit or task at a process.

Decoupling point: Location separating forecast-driven activities from demand-driven activities in a leagile system.

Heijunka: Production leveling by volume and product mix to reduce unevenness.

JIT: An approach that provides materials and information in the required quantity, place and time.

Kaizen: Continuous, incremental improvement involving systematic problem-solving.

Kanban: A visual signal authorising replenishment or movement of work.

Lean operations: An operating philosophy focused on customer value, flow, pull and waste elimination.

Muda: Waste or resource consumption that does not create customer value.

Mura: Unevenness or inconsistency in workload, demand or production.

Muri: Overburden placed on people, equipment or systems.

Pull system: A system in which downstream consumption authorises upstream replenishment or production.

SMED: A setup-reduction method that separates and converts internal and external changeover activities.

Standard work: The documented best currently known method, sequence and timing for performing a task.

Takt time: Available operating time divided by customer demand for that time period.

Value stream: The complete set of activities and information flows required to deliver value.

Visual management: Use of visible signals and displays to communicate normal conditions and abnormalities.

Waste: Activity or resource use that fails to create customer value, including defects, waiting and excess inventory.

Review Questions

Short Answer Questions

1. What is the difference between takt time and cycle time?

2. Define a pull system and explain how Kanban supports it.

3. Identify the eight commonly recognised forms of lean waste.

4. What is the purpose of standard work?

5. State one condition in which an agile system may be preferable to a purely lean system.

Long Answer Questions

1. Explain the five linked ideas of lean thinking and show how they apply to a logistics value stream.

2. Discuss how JIT reduces inventory while simultaneously exposing operational problems.

3. Explain 5S, visual management, kaizen and setup reduction as a connected improvement system.

4. Compare lean, agile and leagile systems in terms of demand conditions, inventory, flexibility and risk.

5. Evaluate the managerial and ethical challenges involved in implementing lean operations.

Analytical / Application Questions

1. A warehouse has 480 available minutes per day and demand for 160 orders. Calculate takt time and explain what managers should investigate if the average process cycle time is 4 minutes per order.

2. A firm faces predictable demand for standard components but highly uncertain demand for final product configurations. Design a leagile operating arrangement and justify the location of its decoupling point.

3. A company plans to cut all inventory by 30 percent after installing electronic Kanban. Analyse why this decision may fail and propose a safer implementation sequence.

22. Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes takt time from cycle time?

A. Takt time is based on customer demand, while cycle time is the actual process completion time.

B. Takt time measures setup duration, while cycle time measures inventory.

C. Takt time is always shorter than cycle time.

D. Takt time applies only to transport operations.

Correct Answer: A. Takt time is based on customer demand, while cycle time is the actual process completion time.

Question 2

A downstream warehouse consumes one standard container and sends an electronic signal for replacement. This is an example of:

A. Forecast-driven push production

B. A pull system using Kanban

C. Overproduction control through batching

D. A decoupling point based only on capacity

Correct Answer: B. A pull system using Kanban

Question 3

Which action most directly supports SMED?

A. Increasing batch sizes

B. Producing to the monthly forecast

C. Converting machine-stopped activities into activities performed while the machine runs

D. Adding finished-goods inventory

Correct Answer: C. Converting machine-stopped activities into activities performed while the machine runs

Question 4

A company postpones final product configuration until a customer order is received, while producing common components efficiently in advance. This is primarily:

A. A purely push system

B. A leagile system

C. A preventive maintenance system

D. A 5S audit

Correct Answer: B. A leagile system

Question 5

Which situation is most likely to justify an agile rather than a purely lean response?

A. Stable demand for a standard product

B. Highly predictable replenishment requirements

C. Short product life cycles and volatile customer demand

D. A repetitive process with fixed specifications

Correct Answer: C. Short product life cycles and volatile customer demand

Question 6

What is the principal operational purpose of 5S?

A. To increase product variety regardless of demand

B. To organise the workplace, expose abnormalities and support standard work

C. To replace all employee training with automation

D. To eliminate every form of inventory

Correct Answer: B. To organise the workplace, expose abnormalities and support standard work

Question 7

If available production time is 420 minutes and daily demand is 210 units, the takt time is:

A. 0.5 minute per unit

B. 1 minute per unit

C. 2 minutes per unit

D. 210 minutes per unit

Correct Answer: C. 2 minutes per unit

Question 8

Why can reducing inventory too quickly create operational problems?

A. Inventory always increases defects

B. It may expose instability before quality, supplier and equipment problems are solved

C. It automatically converts a pull system into a push system

D. It prevents the use of standard work

Correct Answer: B. It may expose instability before quality, supplier and equipment problems are solved

Question 9

Which of the following is an example of non-utilised talent waste?

A. An employee’s improvement suggestion is ignored despite repeated process problems

B. A forklift travels between two warehouse zones

C. A customer order waits for approval

D. A damaged item is reworked

Correct Answer: A. An employee’s improvement suggestion is ignored despite repeated process problems

Question 10

In a leagile network, the decoupling point primarily separates:

A. Safety activities from production activities

B. Forecast-driven operations from demand-driven operations

C. Employees from managers

D. Quality inspection from maintenance

Correct Answer: B. Forecast-driven operations from demand-driven operations