It started with a problem.
Before 1913, assembling a car meant workers walking to the vehicle and building sections in place. A team might spend most of its day moving between tasks and waiting for the previous step to finish. Ford's Highland Park plant tried a different arrangement: instead of moving workers to the work, they used a moving conveyor to bring parts to workers standing at fixed stations. The result was a dramatic reduction in the time to complete each vehicle. According to Ford's own records and corporate history, the Model T was eventually built in roughly ninety minutes using the moving line, down from many hours with the earlier stationary approach.
Historical sources below ↓Then something changed.
What changed was not primarily the physical machinery, but the logic of how tasks were sequenced and who was responsible for each step. Ford's approach broke a complex assembly into small repeated actions with clear handoffs. Each station received a partly finished product, added one thing, and passed it on. The $5 workday Ford introduced alongside the line addressed a second problem: repetitive work caused workers to leave. Higher wages reduced turnover and made three-shift operation possible. The product became cheaper as volume increased, which in turn expanded the market Ford was serving.
What a builder can learn.
Our interpretation: the assembly line is often remembered as a speed story, but it was also a coordination story. Making the flow of work visible—knowing which stage a product was at, how long each step took, and where delays collected—was what made improvement possible. Many small businesses have invisible assembly lines: the steps between 'customer asks' and 'customer receives' involve multiple people, tools, and handoffs. Mapping those steps, even roughly, often reveals the stage where work piles up. The problem is rarely the slowest individual; it is usually the handoff between stages that has no clear owner.
A door still open.
A hypothesis worth testing: if a small service business identified its single most time-consuming handoff and dedicated one change to reducing it, could it cut total delivery time by more than the time saved at that step? The gain might come from reduced rework, fewer clarifying questions, or earlier issue detection. The test would require measuring actual time at each step before and after the change. This is an experiment, not a promise.
Which step in your process is waiting for the step before it to finish — and does anyone own that wait?
Follow the evidence.
History is sourced below. Business lessons are editorial interpretations; future possibilities are questions to test, not predictions.
Prepared from primary-source histories. First edition: 25 Sept 2026.