Before agile had a manifesto, the factory floor had already solved most of its problems. Lean manufacturing, refined at Toyota over decades, taught that value flows in small batches, that inventory sitting between stages is waste, that quality is built in rather than inspected in at the end, and that the worker at the machine should be able to stop the whole line when something is wrong. Agile borrowed all of it. Sprints are small batches. Work-in-progress limits are the war on inventory. Continuous integration is quality built in. The debt agile rarely repays is the last idea, the one about authority.
Lean's boards and cadences are the easy import. Its distribution of power is the hard one, and it is the part software most often leaves on the factory floor.
Flow and the line
The mechanical borrowing is well documented and it works. Forsgren, Humble and Kim's Accelerate (2018), built on four years of State of DevOps research and honored with a Shingo Publication Award for advancing lean and operational excellence, argued that specific capabilities, small batch sizes, fast feedback, limited work in progress, drive higher software delivery performance. These are lean's ideas restated for code. The subsequent DORA State of DevOps research (2024) reinforced the flow logic and added a caution: unstable organizational priorities reduce productivity and raise burnout, and that damage persists even where leadership and documentation are strong. Flow is not just a board layout. It is a promise that the work will not be yanked around every week.
So far, so faithful. The batch sizes shrank, the queues shortened, the feedback loops tightened. Software genuinely learned to move in smaller increments and to catch defects earlier, and it is better for it. Where the translation breaks is at the andon cord.
The part left on the factory floor
The deepest lean idea is that the person closest to the work has both the knowledge and the authority to act on it: to stop the line, to change the method, to solve the problem where it appears rather than route it upward. Respect for that person is not sentiment; it is the source of the improvement. Agile adopted the vocabulary of empowered teams and then, in practice, often kept decisions with a product owner, a steering committee, or a change board. The team can move cards but cannot stop the line.
Semco tested the authority idea directly, and earlier. As Semler has told it, in 1985 the company let factory workers choose their own shifts. Management predicted the assembly line would collapse; instead the workers coordinated among themselves, parents taking mornings, single people taking nights, with a single rule, talk to the person next to you. The line held because the people on it were trusted to run it. That is the borrowing agile skipped: not the schedule board, but the transfer of control to the people doing the work.
There is a related idea agile also under-borrowed: continuous improvement driven from below. On the factory floor, the people running a process are expected to change it, in small increments, as a permanent part of the job, not to file a suggestion and wait. The agile retrospective is the ceremony that gestures at this, a regular moment to reflect and adjust. But reflection produces improvement only if the team can act on what it finds. Where the authority to change the method lives elsewhere, the retrospective degrades into a complaint session with no lever attached.
The distinction shows up in outcomes. A team with lean's mechanics and none of its authority produces motion without improvement, cards flowing across a board while the actual method never changes because nobody on the team is allowed to change it. The retrospective surfaces the same problems every fortnight because the people who see them cannot act on them. This is lean stripped of its engine.
Manufacturing learned, painfully, that tooling without trust is just faster waste. A production system copied as ritual, the morning huddle, the visual board, the standardized cadence, delivers little unless the person at the machine can pull the cord. Agile inherited the huddle and the board. Whether it inherited the cord is the question that separates a genuine agile team from an assembly line with sticky notes. The mechanics were the easy half to borrow. The authority was the point.
Sources
- Forsgren, Humble & Kim (2018). Accelerate: The Science of Lean Software and DevOps. Lean-derived capabilities (small batches, fast feedback, limited WIP) drive software delivery performance; Shingo Publication Award. https://itrevolution.com/product/accelerate/
- DORA / Google Cloud (2024). Accelerate State of DevOps Report 2024 (~39,000 respondents). Unstable organizational priorities reduce productivity and raise burnout, an effect that persists even with strong leadership and documentation. https://dora.dev/research/2024/dora-report/