Twitter/X

Assembly lines (Henry Ford model) move product through specialised stations and…

2026-08-03 · 11:18 UTC ·@Object_Zero_ ·2 min read

Brief

Object_Zero argues manufacturing choice should be driven by whether assembly steps have standard or multivariate cycle times: Henry Ford-style assembly lines suit high-volume, standard-cycle work, while parallel-batch production handles multivariate cycles at the cost of utilisation and changeover complexity. He warns bad pre-FEED sequencing (e.g., K before D) creates long-term rework and promotes atomising subassemblies and hybrid strategies.

Why it matters

Assembly lines (Henry Ford model) move product through specialised stations and require near-identical station cycle times — the whole line runs at the slowest station’s cadence — making them efficient for high unit volumes but brittle and prone to quality drift.

Key details

  • Parallel-batch production builds items in concurrent groups and accommodates multivariate cycle times, but incurs lower plant utilisation and needs changeover/re-kit planning; whether assembly is 'standard cycle time' or 'multivariate cycle time' should be decided pre-design.
  • Early systemisation and decision sequencing in pre-Front End Engineering Design is critical: closing decision K before decision D can lead to years of pain; complex products typically use hybrid approaches and several car subassemblies are themselves assembled in parallel batches.
Source evidence

Parallel Production

Some things make sense to build in assembly lines, and somethings make sense to build in parallel batches.

Everyone just presumes that Henry Ford’s assembly lines are the optimal process, and whilst that is certainly true for many things (most cars) it isn’t true for everything.

Understanding the differences:

Assembly Lines
Product moves through specialised stations, good for large unit volume, forces assembly design into many small discrete tasks.
Crucially each station needs near identical completion cadence, as the entire line moves at the cadence of the slowest station (hello whack-a-mole). Flow is efficient but brittle, quality can drift.

Parallel Batches
Items made in discrete concurrent groups, assembly steps can have multivariate cycle time (massively under appreciated!), downside is lower plant utilisation, changeover and re-kit planning.

But perhaps the foundational difference is how you need to think about assembly, is your assembly standard cycle time or multivariate cycle time? This is a pre-design basis question.

This is crucial because it should drive the systemisation of your product and your entire test and acceptance philosophy.

So many ventures tear themselves to pieces because they fumble the sequential decision closing of the pre- Front End Engineering Design, and they drop themselves into a decade of hell fighting a war all because someone closed decision K before closing decision D during the early stages.

Sadly, nobody tells you this, there are no books to read, no framework to follow. There are a lot of people with thousand yards stares who know what they had to deal with and (quite rightly) assume that pain is normal.

It is normal, but it doesn’t have to be normal! It’s a huge advantage if you have some of that insight at the table in the early stages.

A good test is how far can you atomise assembly steps. It’s also worth remembering that several of the subassemblies in a car plant are themselves assembled in parallel batches, even is final assembly is a sequential line.

So for complex products, you often end up with hybrid mixtures, but you should be able to identify these at systemisation and understand the manufacturing requirements thereof.

Anyway, enjoy the greatest airframe of all time laid out in parallel batch production…