Imagine building a house. If every window requires a different fitting and every wall uses materials with different dimensions, builders spend time adapting parts that could have fitted together from the beginning. Common sizes and familiar methods make the work easier to repeat.
Now imagine buying that house. You might want a different layout from your neighbor, or need an entrance that works for a wheelchair. A builder who offers only one design may be efficient at producing something that does not suit you.
This is the tension that interests me in two books: The Power of Productivity by William W. Lewis and The Machine That Changed the World by James P. Womack, Daniel T. Jones, and Daniel Roos. Lewis's work makes a case for standardization. The second book explains lean production, an approach that responds to customer needs with less wasted effort.
At first, they can sound opposed: repeat a proven approach, or stay flexible. But lean also depends on standardized work. Reading the books together raises a more precise question: which things should stay the same so that other things can change?
What standardization, productivity, and lean mean
Standardization means agreeing on common specifications or a repeatable way to do something. A specification describes what a result must meet, such as a component's dimensions. A procedure describes how to do the work, such as the steps for fitting that component. Neither necessarily requires every finished house to look identical.
Productivity compares output with the resources used to produce it. For example, completing comparable building work with fewer working hours improves labor productivity. Comparisons need to account for differences in the work: building more houses is a poor measure of success if they are unsafe or unsuitable.
Lewis's The Power of Productivity, published in 2004, examines why productivity differs between countries. He was the founding director of the McKinsey Global Institute, whose research compared industries across thirteen countries over twelve years. The book's wider argument concerns competition and the spread of more productive ways of working. Standardization is one concrete part of that story, rather than a prescription to make everything identical. Book and author background.
The Machine That Changed the World, first published in 1990, grew out of an MIT study of the automotive industry. It describes lean production and Toyota's influence on the organization of manufacturing. Book and research background.
Lean is an approach to organizing work around customer value while reducing wasted resources and effort. Customer value means what helps the person receiving the product or service achieve what they need. In a factory, that includes making the right product at the required quality, rather than producing more units simply to keep machines busy. The Lean Enterprise Institute's explanation of lean.
Waste, in lean terminology, uses resources without creating customer value. Some such activity remains necessary under current conditions, including certain safety inspections. Identifying it does not authorize its immediate removal. Definition of waste.
Lewis's case: unnecessary variation can make everyone pay more
Housing gives the standardization argument a concrete setting. In a 2000 McKinsey Global Institute report coauthored by Lewis, the researchers identified the lack of standard designs, construction methods, and materials as a cause of Japan's housing productivity gap. They also identified limited price competition and barriers to larger developments. These are findings about that historical study, not a description of Japan's housing industry today. The original residential construction study.
When parts fit familiar dimensions and workers can repeat a known construction method, less time goes into resolving avoidable differences. Suppliers can serve more than one project, and workers can carry useful experience from one job to the next. Those are practical reasons to favor standards.
Customization has a cost. Sometimes the customer values the difference enough to pay for it. Sometimes the difference reflects habit or fragmented practices, and the customer pays without gaining much. The study's criticism of competition based on customization and reputation, with little price pressure, makes that question hard to avoid.
Lewis also argues that businesses can become more productive by adopting proven ways of organizing work. His article adapted from the book's first chapter uses Suzuki's operations in India as an example of transferring production methods and training. That supports the idea of learning from an effective system rather than inventing every practice again. Lewis's account.
My reading of this argument is that variation needs a justification. If five different ways of handing over an order create confusion without helping anyone, a common method is a reasonable improvement. That interpretation does not establish that every difference should disappear.
Lean's case: repeatability must still serve changing needs
The production model lean challenged was mass production: making large quantities through specialized equipment and repetitive work. Henry Ford's system combined interchangeable parts, standard work, and a moving production line. Its difficulty was offering variety and responding when customers wanted something different. A brief history of lean.
Consider a machine that takes hours to switch between two products. Making a very large batch of the first product spreads that setup time across many units. The machine looks efficient, but the factory may accumulate stock nobody currently wants while customers wait for the second product.
Lean tackles the arrangement that creates this trade-off. Quicker changeovers, smaller production quantities, and work responding to actual demand help a factory offer variety without relying on enormous batches. The Lean Enterprise Institute describes these developments in Toyota's production system; the book's publisher presents lean as a broader system spanning production, suppliers, and customers. Toyota's development of lean, the publisher's account of the book.
That flexibility requires dependable execution. In lean manufacturing, standardized work specifies the sequence of tasks, their timing in relation to customer demand, and the amount of unfinished stock needed for the process to operate. It gives people a visible baseline for training, recognizing problems, and improving the work. The standard is reviewed and updated as conditions and methods improve. Standardized work.
Lean therefore challenges inflexible production and wasteful repetition. It retains agreed methods and makes their improvement part of the job. Changing a process without shared understanding can introduce errors; refusing to change it after finding a better method can preserve errors.
Where the books meet, and where the tension remains
Lewis's housing research warns that excessive differences can make production costly. Lean warns that efficiently repeating a process can still deliver the wrong mix of products, with avoidable waiting and stock. These concerns can coexist in the same business.
It helps to distinguish what is being standardized:
| What stays consistent? | What it makes possible | What still needs room to change? |
|---|---|---|
| Component dimensions and connections | Parts fit together across projects | The design assembled from those parts |
| A shared work procedure | Reliable execution and a baseline for improvement | The procedure when evidence supports a better one |
| Information in an order or handover | People coordinate without repeated clarification | The customer's actual requirements |
| A quality requirement | Customers can rely on the result | The method used to meet it |
This table is my synthesis, rather than a framework supplied by either book. Standardization and lean are not opposites. Their useful tension concerns the boundary between variation that adds value and variation that consumes resources without enough benefit.
That boundary is debatable. A builder might find repeated layouts cheaper, while a family values a different layout. A manager might prefer a fixed script, while the person doing the work sees that it misses an unusual need. The answer depends on whose needs count, how much the difference costs, and who has authority to revise the standard.
I would use Lewis to question the cost of unnecessary customization, and lean to question whether the repeatable system serves the person receiving its output. Neither question can be answered by the number of rules alone.
Applying this at work
A customer handover is a good place to begin. Agree on the information every handover must include: the customer's goal, decisions already made, and unresolved questions. A common format prevents colleagues from having to reconstruct the situation.
Then examine the whole path the customer experiences. Does the handover sit in a queue for three days? Does the customer have to repeat the same explanation? Standardizing a form will have limited benefit if work still waits between teams.
The standardization lesson is to make recurring coordination dependable. The lean lesson is to examine how work moves from request to useful result, including delays between activities. Keep customer needs variable while making the transfer of those needs reliable.
A discovery script illustrates the limit. It can remind a new salesperson of useful questions. It becomes restrictive when finishing the script matters more than understanding the buyer. Keep shared requirements for what must be understood, and allow the conversation to follow the evidence.
Applying this to learning and creative work
A regular study session reduces the effort of deciding when to begin. A consistent way of checking understanding makes improvement easier to see. Those are useful standards.
The exercises should respond to what you discover. A language learner who recognizes vocabulary but cannot hold a conversation may need speaking practice. Repeating an easy lesson format produces completed lessons without necessarily producing the intended skill.
Writers face a similar choice. A repeatable process for checking sources can improve reliability. Requiring every essay to use the same argument structure can obscure differences between subjects. Common tools and routines can support work whose finished form remains varied.
These are personal applications of the ideas, not findings from the books' research. Learning also needs exploration whose value may take time to become visible; an activity is not wasted merely because it lacks an immediate measurable result.
Applying this to everyday routines and relationships
A packing checklist avoids rediscovering the same essentials before every trip. A fixed place for keys prevents repeated searching. These standards remove small problems without requiring each day to be identical.
Keep the useful core and adjust the rest. A checklist for a work trip needs different additions from one for a holiday. If maintaining a planning system takes more effort than the problems it prevents, simplify it.
Relationships need a different measure of success. A household chore rota can make responsibilities clear, but it needs to accommodate illness, overload, and changing circumstances. Reliability matters alongside consent and fairness.
Parenting also combines dependable boundaries with differences between people. A familiar bedtime routine can provide predictability; the support a child needs may change with age and circumstance. Consistency does not require treating every child as if the same approach must produce the same result.
Factory concepts have limits here. A slow dinner with a friend can be valuable precisely because nobody is trying to finish efficiently. Care, trust, and enjoyment cannot be reduced to output per hour.
A small experiment with a standard you already use
Choose one recurring activity and identify a problem people actually experience. For a team, it might be missing information in handovers. At home, it might be repeated disagreement about who handles a task.
Agree on one small default, then try it for two weeks. Notice whether it reduces the problem, how much effort it takes to maintain, and which exceptions people need. Give those affected a way to suggest changes.
If the same omission keeps happening, strengthen the shared method. If the rule repeatedly blocks a legitimate need, change its scope or allow a clear exception. If it creates work without helping anyone, remove it.
Reading Lewis alongside lean makes me more willing to standardize recurring work, and more demanding about what that standard achieves. The practical test is whether people can rely on the result while still responding to circumstances that deserve a different approach.