Spreadsheets are useful in assembly-line design. They help collect process times, calculate total work content, estimate labour requirements, and compare high-level options.
But mixed-model assembly lines expose a weakness in static line balances: the average can look fine while the actual flow behaves badly.
That matters when you are designing a future-state line, reducing batch size, moving toward one-piece flow, or asking operators to flex between multiple workstations. On paper, the line may appear balanced. On the floor, one product family, one station, one walking pattern, or one poorly placed buffer can change the whole result.
1. Averages hide product mix
A simple line balance often starts with average process times. That can be enough for a single product, but a mixed-model line has different products moving through the same flow.
One product may need more assembly time at station one. Another may load station three. Another may skip a process completely. If the spreadsheet collapses that into a single average, it can hide the moments where the real line becomes unbalanced.
The question is not only, "What is the average work content?" The better question is, "What happens when this specific product mix arrives in this specific order?"
2. The bottleneck can move
In a mixed-model line, the bottleneck is not always a permanent label attached to one workstation. It can move depending on product sequence, staffing, buffers, and how work is split.
A spreadsheet may show station two as slightly overloaded. But in practice, station three may become the constraint when several high-work-content products arrive close together. Or an operator who looks fine on average may become the real constraint because they are covering multiple workstations.
This is why teams often argue about line designs for hours. Everyone is looking at the same data, but nobody can quite see the behaviour.
3. Worker flexing is hard to understand on paper
Flexible-worker layouts can be powerful. More workstations than people can reduce waiting, improve utilisation, and make a line more adaptable. But the concept is difficult to trust without seeing it run.
Questions appear immediately:
- How much walking time will be lost?
- Will operators arrive at the next station when the work is ready?
- Will one operator quietly become overloaded?
- Will the line starve or block when the product mix changes?
These are not just calculation questions. They are flow questions. A static spreadsheet struggles because it is not showing movement over time.
4. Buffers can help, or just hide the problem
Buffers are another area where spreadsheets can be misleading. Adding a buffer between workstations may protect a bottleneck and improve flow. It may also disguise a mismatch between station capacities and create excess work in progress.
The key is not simply whether a buffer exists. It is how often it fills, how often it empties, and whether it keeps the constraint working or just stores the evidence of an unbalanced line.
That behaviour is much easier to understand when you can watch the line run.
5. Confidence matters before changing the floor
Physical line changes are expensive. Moving benches, changing work allocation, retraining operators, and disrupting production all carry cost and risk.
Before doing that, teams need confidence. Not perfect certainty, because no model has perfect data. But enough confidence to know which version is worth trying first.
That is where simulation helps. It turns the spreadsheet from a static calculation into a working scenario. You can test three workstations versus four, one line versus two, different operators, different product mixes, and different buffer strategies before touching the real floor.
What to test before committing to a mixed-model line
If you are designing a mixed-model assembly line, useful experiments include:
- Run the current-state line first so you have a baseline.
- Test the proposed future-state layout against the real product mix.
- Try different product sequences, not just the cleanest possible order.
- Compare fixed operators against flexible-worker layouts.
- Add buffers deliberately and check whether they improve throughput or just increase WIP.
- Move work between stations and watch whether the bottleneck shifts.
Flowcell was built for this exact problem
Flowcell helps lean teams and consultants turn process-time data into a visible mixed-model assembly line simulation. It is not a crystal ball. It is a faster way to understand what to try first.
Try the live demoRelated pages: mixed-model assembly line simulator, lean consultant simulation tool, and why Flowcell was built.