Discussions about assembly line design usually start with volume. How many units must the line deliver, and how much growth should it accommodate? Those requirements soon become questions about operators, layout, square metres, and investment. To connect them, however, we first need to translate volume into takt: the available production time divided by the required
In a previous article, “Productivity or Kosu: Faster or in Less Time?”, I introduced kosu as a more honest way to talk about labour productivity. The core idea was simple: instead of counting pieces per person per hour, kosu measures how much direct labour time you actually consume per good unit. That earlier piece showed
Machine-heavy operations and job shops are often difficult to control. Customer requirements shift, capacity is limited, technical constraints are real, and scheduling becomes a constant balancing act. In practice, flow is often elusive, and there always seems to be something that has to give. A customer urgently needs product, but the machine is tied up
Assembly lines are expected to absorb demand changes smoothly. They rarely do. When demand increases, operators feel it first. They struggle to finish before the takt pulse, idling the next station, or they move with the unit to catch up. Overtime is used to recover arrears, or extra people are added after the fact, not
If you manage a mixed‑model assembly line, you’ve likely asked the questions that surface when the line stutters, when takt compliance falters, and when the neat precision of the balance chart feels worlds away from the reality on the floor. The instinct is to look harder at the balance chart: to re‑do task assignments and
Most of the problems observed on the shop floor are symptoms of underlying problems in the layout, the material flow, or the way the line was originally designed. When these fundamentals are no longer aligned with production demand, operators are forced to compensate for system shortcomings rather than being supported by a stable and capable
AI is appearing more frequently in discussions about assembly line design. Over the past months, several examples have circulated on LinkedIn showing how quickly an AI model can generate a small application that draws a PERT network, proposes a task allocation, or even runs a Monte‑Carlo simulation. These demonstrations are often presented as evidence that
In my earlier article on constraint‑aware line balancing, I explored how real‑world assembly lines rarely behave like the tidy line balance charts and yamazumi’s we sketch during design. Task dependencies, operator interference, spatial constraints — they all complicate the balancing process. Yet even when the balance looks right, another layer of complexity emerges: ensuring operators
Line balancing is often described as the theory and relatively simple act of more or less evenly loading operators and stations with work. This Lean principle creates flow, limits overproduction, reduces work-in-process, and creates a balanced workload across all operators – without exceeding takt time. Most introductions to line balancing, therefore, start with the same
Joel Barker’s quote—”Action without vision merely passes the time”—always stops me in my tracks. Nelson Mandela cited it often, and in my years working with organizations on strategy and Lean deployment, I’ve seen exactly why. Companies without a clear future state don’t just drift—they clash internally, chase local priorities, and burn energy on counterproductive efforts.
