" Times of rapid change and increasing complexity require a shift from optimization towards innovation. Forcing workers to blindly execute the upfront plans and sequential processes of the “waterfall model” turns out not to be the one best way. But we do it anyway. Taylor’s obsession with time, order, and efficiency has been absorbed into the fabric of our culture. We share his faith in reductionism. We divide projects into phases into tasks. We separate people into teams into roles. We split work into steps and silos. Then things fall through the cracks. Figure 1-6. The Waterfall Model. It’s not that waterfall is wrong. In many contexts, it’s a useful model. The problem is that, all too often, we apply it without realizing it’s not the only way. Again, it helps to know history. In the 1950s, Toyota figured out how to avoid the pitfalls of Taylorism by embracing what’s now called Lean. In design, all relevant specialists were involved at the outset, so conflicts about resources and priorities were resolved early on. And in production, managers learned that by making small batches and giving every worker the ability to stop the line, they could identify, fix, and prevent errors more quickly and effectively. [40] Rather than serving as cogs in the machine, workers were expected to solve problems by using “the five why’s” to systematically trace every error to its root cause. Similarly, suppliers were expected to coordinate the flow of parts and information within the just-in-time supply system of kanban. "
― Peter Morville , Planning for Everything: The Design of Paths and Goals
![Peter Morville quote : Times of rapid change and increasing complexity require a shift from optimization towards innovation. Forcing workers to blindly execute the upfront plans and sequential processes of the “waterfall model” turns out not to be the one best way. But we do it anyway. Taylor’s obsession with time, order, and efficiency has been absorbed into the fabric of our culture. We share his faith in reductionism. We divide projects into phases into tasks. We separate people into teams into roles. We split work into steps and silos. Then things fall through the cracks. Figure 1-6. The Waterfall Model. It’s not that waterfall is wrong. In many contexts, it’s a useful model. The problem is that, all too often, we apply it without realizing it’s not the only way. Again, it helps to know history. In the 1950s, Toyota figured out how to avoid the pitfalls of Taylorism by embracing what’s now called Lean. In design, all relevant specialists were involved at the outset, so conflicts about resources and priorities were resolved early on. And in production, managers learned that by making small batches and giving every worker the ability to stop the line, they could identify, fix, and prevent errors more quickly and effectively. [40] Rather than serving as cogs in the machine, workers were expected to solve problems by using “the five why’s” to systematically trace every error to its root cause. Similarly, suppliers were expected to coordinate the flow of parts and information within the just-in-time supply system of kanban.](/image/1191364.jpg)