Chapter 27 — Further Reading

Twelve pointers. Everything here is either a source you can go and verify yourself or a well-established institution's published material. Where I am not certain of an exact title, edition, or document number, I describe the source instead of inventing a citation — go to the organization's own site and search from there.

A warning specific to this subject, and please take it seriously. Lean construction has more marketing attached to it than almost any other topic in this book, and the marketing runs heavily on numbers that nobody can source. You will be shown percent-plan-complete benchmarks, productivity improvements, schedule-compression figures, and "typical" waste percentages presented as findings. Before you repeat any of them, ask three questions: measured by whom, on how many projects, and defined how? PPC in particular is not measured consistently enough across projects, companies, or trades for one job's number to be comparable to another's — which is why this chapter refuses to give you a benchmark and tells you instead to trend your own. The only defensible number in this chapter is the one you measured on your own job. Read the list below in that spirit, and be at least as skeptical of a claim that flatters lean as of one that attacks it.

1. The Lean Construction Institute (LCI)

Why: LCI is the nonprofit at the center of lean construction practice in the United States. It publishes practitioner guidance, glossaries, and training on the Last Planner System, pull planning, make-ready work, and the surrounding toolkit, and it runs the congress where most working practitioners first encounter this material. "Last Planner" is a registered trademark of LCI — worth knowing before you print it on a form or a proposal. Start with its published description of the system's levels and terminology, because the vocabulary in the field is inconsistent and having one authoritative reference for the terms will save you an argument a month.

For whom: Anyone implementing this for the first time, and anyone who has to explain to a skeptical superintendent that this is a defined method rather than a consultant's improvisation.

2. The International Group for Lean Construction (IGLC) — the annual conference proceedings

Why: This is the single most useful item on the list, and it costs nothing. IGLC is the research community for lean construction, and its annual conference proceedings are freely available online going back to the early 1990s. It is where you go to find out whether a claim about lean is actually supported or merely repeated — including claims about PPC, takt planning, and productivity. The papers vary in quality, as conference papers do, but they show their methods, their sample sizes, and their limitations, which is exactly what a consultant's slide deck does not.

For whom: Anyone who is about to quote a lean statistic to an owner, a boss, or a subcontractor. Search the proceedings for the claim first. Half the time you will find it was one case study on one project, and that is genuinely useful to know before you stake your credibility on it.

3. Taiichi Ohno on the Toyota Production System

Why: Ohno was the Toyota engineer most closely associated with developing the production system that the West later named "lean," and his own account of it — published in English translation and widely available — is short, plain, and much stranger than the tidy version taught in seminars. Read it for two things: the origin of the waste categories, and the repeated insistence that the system is a way of seeing problems, not a set of tools to install. That is the idea most lean training loses in translation, and it is the reason §27.7 insists that making work ready is a job function rather than a meeting.

For whom: Anyone who wants the source rather than the summary. Read it alongside §27.2's caveat: construction is not a factory, the product is fixed and the workstations move through it, every project is a prototype, and the workforce is assembled from twenty separate companies. Import the ideas — waste, flow, pull — not the factory.

4. The Machine That Changed the World (Womack, Jones, and Roos, 1990) and its successor on lean thinking

Why: This is the book, out of MIT's International Motor Vehicle Program, that put the word "lean" in front of a general audience and triggered everything downstream — including construction's interest in it around the same time. Its successor volume by Womack and Jones generalized the ideas out of automotive manufacturing into the five-principle framework (value, value stream, flow, pull, perfection) that most lean training still uses. Read them as history and as framework, and read them knowing that the automotive comparisons do not transfer cleanly to a construction site.

For whom: Readers who want to understand where the vocabulary came from and why it carries manufacturing assumptions that keep causing trouble on job sites.

5. Lauri Koskela on transformation, flow, and value

Why: Koskela's argument in the early 1990s is the intellectual door through which lean entered construction: that construction management theory recognized only transformation — turning inputs into outputs — and had no concept of flow (how work moves between transformations) or value (what the customer actually receives). His technical report and later doctoral work developing what became known as the transformation-flow-value view are widely cited and readily findable; search his name plus "transformation flow value" rather than trusting a secondhand summary.

For whom: Students, and anyone who wants a rigorous answer to "why isn't a good CPM schedule enough?" that goes deeper than this chapter's practical one. It is also the best available inoculation against people who say CPM is obsolete — Koskela's argument is that the theory was incomplete, not wrong.

6. Glenn Ballard and Greg Howell on the Last Planner System, and UC Berkeley's Project Production Systems Laboratory (P2SL)

Why: Ballard and Howell developed the Last Planner System and went on to co-found LCI; Ballard's doctoral work is the formal treatment of the system this chapter describes practically — the should/can/will/did structure, the shielding of production through the readiness screen, and percent plan complete as a measure of planning reliability rather than production. P2SL, the research laboratory at the University of California, Berkeley associated with Ballard and Iris Tommelein, publishes ongoing research on production planning, takt, and project production systems.

For whom: Anyone who wants the primary treatment rather than the practitioner distillation — particularly the argument for why the screen shields production, which is the part practitioners most often implement without understanding and therefore abandon first.

7. Takt planning — read it from more than one source, deliberately

Why: "Takt" is simply German for beat or rhythm, and takt-based scheduling has two distinct lineages: the manufacturing concept of takt time, and a long European — particularly German — practice of rhythm-based scheduling in repetitive building construction. It entered the English-language lean construction literature relatively recently, and the terminology is genuinely unsettled: what one source calls a wagon another calls a train car or a trade package, and zone-balancing methods differ substantially. This is a topic where I would explicitly send you to compare two or three sources rather than adopt one. The IGLC proceedings, LCI's material, and P2SL's research are the three places to look, and the arithmetic in §27.8 — total takts equals zones plus wagons minus one, and always round down — is stable across all of them even where the vocabulary is not.

For whom: Anyone with repetitive floors: hospitals, hotels, multifamily, student housing, offices, parking structures. Do not adopt it for irregular space, and read at least two sources before you size your first zone.

8. Factory Physics (Hopp and Spearman) — for the mechanism, not the setting

Why: The 🔍 Why this works passage in §27.2 rests on a claim that deserves a rigorous source: that variability, not slowness, is what destroys throughput, and that buffers appear wherever variability is not removed. Factory Physics is the standard graduate treatment of exactly that — the relationships among variability, work-in-process, capacity, and cycle time, worked with real mathematics. It is about manufacturing, and this chapter has already told you construction is not a factory. Read it anyway, because the mechanism generalizes even where the setting does not, and because the mathematics of why a chain of individually reliable handoffs compounds into an unreliable chain is done properly there and hand-waved almost everywhere else.

For whom: Quantitatively inclined readers, schedulers, and anyone who has to explain to a skeptical executive why 0.9⁵ = 0.59 is the most important arithmetic in this chapter.

9. Eliyahu Goldratt on the theory of constraints

Why: Goldratt's business novel about a struggling plant, and his later work applying the same thinking to project scheduling, popularized two ideas this chapter uses without attribution: that a system's throughput is governed by its constraint, and that individually protected task durations aggregate into a schedule far longer than the work requires. His project-scheduling work is where the argument for pooling buffers rather than hiding them in every duration is made most forcefully — which is precisely what Renny Kovach did when he traded five days of private float for a guaranteed continuous elevation.

For whom: Readers who want a second, independent lineage of the same insight. Two honest caveats: the books are written as advocacy and the case for the project-scheduling method is more contested in practice than the books suggest; and the manufacturing setting carries assumptions — a fixed plant, a single employer, repeated production — that a job site does not.

10. The Associated General Contractors of America (AGC) — lean construction education

Why: AGC of America publishes a structured lean construction education program aimed at working practitioners, delivered largely through its local chapters. It is the most accessible formal training route for a project engineer or superintendent in the United States, it is written for contractors rather than for researchers, and completing it gives you a defensible vocabulary when you propose any of this to a boss who wants to know where it comes from.

For whom: Project engineers and superintendents who intend to actually implement this rather than read about it, and companies deciding how to train a field staff. Check the current program structure with AGC or your local chapter directly.

11. Integrated Project Delivery contract documents — the AIA and ConsensusDocs multi-party agreements

Why: §27.9 argues that lean's central commercial problem is that the benefits and the costs of reliability land on different parties, and that IPD's structure is the cleanest answer to it. Both the AIA and ConsensusDocs publish multi-party collaborative agreements in which owner, designer, and builder share a risk-and-reward pool, and the AIA publishes an accompanying guide describing how integrated delivery is intended to work. Read the mechanism — how the pool is funded, how profit is placed at risk, what is waived among the parties, and how decisions get made — because that mechanism is the entire reason the incentives line up. Then read Chapter 3 again with it in mind.

For whom: Anyone considering IPD, and — more usefully — anyone running lean on an ordinary CM-at-risk or design-bid-build job who needs to understand precisely which incentive they do not have. Most lean practice happens without IPD, Northgate included, and that is survivable only if you know what you are missing and who is paying for it.

12. Jim Suhr on Choosing By Advantages, and your own subcontract scope sheet

Why: Two very different documents, paired because they are the two places a lean program most often dies quietly. Choosing By Advantages is the decision method named in §27.8 — comparing alternatives by the importance of their advantages rather than by pro-and-con lists or weighted scoring, with cost considered last, after the advantages are understood. Suhr developed and published the method, and it is worth reading properly before you facilitate a contested multi-stakeholder decision, because a half-understood version of it is just a slower vote. And your subcontract scope sheet is where participation in pull planning, weekly planning, and look-ahead reporting either does or does not become an obligation. If it is not in the subcontract, it is a request; by month four a request is a suggestion; by month six it is a thing three foremen no longer do. Put it in the scope sheet during buyout (Chapter 16), price it, and make sure the subcontractor knows it was priced.

For whom: The first one for anyone facilitating design or phasing decisions. The second one for every project manager who has wondered why attendance decayed, and it is free to read tonight.