The History of Lean Project Management

By Victor Hoang · Updated Oct 24, 2026

Here's a problem builders knew well. A weekly plan on a design and construction project is wrong far too often, week after week. In the 1990s, a group of researchers and builders set out to fix that. They borrowed ideas from a car company.

Lean project management has no single founding date. Its parts arrived in sequence. Toyota built the system in factories between the 1930s and 1960s. MIT researchers named it "lean" in the late 1980s. Lauri Koskela's September 1992 report started the effort to apply it to construction projects. Software followed in 2003 with the Poppendiecks' book, and startups in 2011 with Eric Ries. The Lean Construction Institute says that in traditional design and construction projects, on average only 54% of the work planned for a given week is completed within the allotted schedule.

The throughline is a change in what counts as progress. Traditional project control asks whether each task is on schedule. Lean asks whether work is flowing, whether anything is waiting, and whether the next person can rely on what they were promised. This article follows that change from the factory to the job site to the code repository. For the practice itself, see our guide to lean software development; here we trace where it came from.

Timeline at a Glance

Before the Name (1913-1963)

Ford's flow and Toyota's pull solve factory problems, not project ones

Start with a line of Model Ts. The Henry Ford museum records that Highland Park's moving assembly line began in 1913 and that by early 1914 its three continuous lines produced "a finished Model T every 93 minutes", against 12 and a half hours under the older stationary method. Flow, in other words, was a proven idea before anyone said "lean."

The Lean Enterprise Institute describes the catch. Ford's single-specification Model T meant the system could not provide variety, and the institute says Kiichiro Toyoda and Taiichi Ohno at Toyota developed a system that kept flow while offering low cost, high variety and quick throughput. Toyota's own account says Kiichiro brought chain-conveyor flow production to body assembly at the Koromo Plant, completed in 1938. Toyota's 75-year history adds that he proposed Just-in-Time production when the plant began operating, and Eiji Toyoda recalled his definition: "Just make what is needed in time, but don't make too much."

The same page says a 1939 rationing system for automobile materials made the necessary supplies impossible to get on time, so the initiatives were suspended. The concept was not fully realized until 1954, when the supermarket method was proposed: later processes take what they need from earlier ones, with the kanban as the tool. Toyota says the kanban system was adopted at all plants in 1963. Our history of the Toyota Production System and lean tells that story in full, and our history of kanban follows the card itself.

Keep the precursor and the concept apart. Ford and Toyota were solving repetitive production, where the same part is made thousands of times. Nobody was managing one-off projects with these tools yet, and nobody called any of it lean.

What this means for teams today: Flow and pull were proven on repeating work first. When you borrow them for a project, expect to adapt them, because a project is made once.

The Lean Coinage (1988-1996)

MIT researchers give Toyota's system an English name

The label came from outside Toyota. According to Mark Graban's account, John Krafcik's article "Triumph of the Lean Production System" ran in the Fall 1988 issue of MIT Sloan Management Review. Krafcik had worked with Jim Womack in MIT's International Motor Vehicle Program and had spent two years as an engineer at NUMMI, the GM-Toyota joint venture. He contrasted "lean" plants with "buffered" ones that kept large inventories to protect against downtime. Graban says the term "arguably" first appeared there, and that Krafcik presented lean as a management system rather than a set of techniques.

Two years later came the book. The Machine That Changed the World, by James Womack, Daniel Jones and Daniel Roos, was published in 1990 by Rawson Associates and, per the archive.org record, was based on an MIT five-year, five-million-dollar study of the future of the automobile. The Lean Enterprise Institute says the book thoroughly described the lean thought process. In 1996 Womack and Jones distilled it in Lean Thinking to five principles: specify value, identify the value stream, make the product flow, introduce pull, and manage toward perfection. The same institute lists later adaptations to logistics, services, retail, healthcare, construction, maintenance and government.

Notice what the word did. It made a company-specific system portable, and it invited people to take the parts they liked. That portability is why lean could move into project work at all.

What this means for teams today: When someone says "we do lean," ask which meaning they intend: the cards, the flow principles or the management system. They are not interchangeable.

Koskela's Challenge (1992-1997)

A Finnish researcher says construction runs on the wrong theory

This era overlaps the last one, because the research began before the book that made lean famous. In September 1992 Lauri Koskela, working at VTT, the Technical Research Centre of Finland, wrote Technical Report 72 in the CIFE series at Stanford, titled "Application of the New Production Philosophy to Construction." Its abstract says it compares the traditional and new production philosophies in manufacturing, criticizes the traditional conceptual basis of construction, and offers an initial new interpretation of construction based on the new philosophy. The VTT record lists it at 87 pages.

The argument was against a habit, not a tool. The report's target was the conceptual basis of construction itself, the unspoken theory behind how projects were planned and judged, before it proposed any new technique. That is why the movement it started began as research and not as a product.

A community formed quickly. The International Group for Lean Construction says it was founded in 1993, and its first conference was held in Espoo, Finland, in 1993. Glenn Ballard's biography says he co-founded the group that year. Four years later, on the practitioner side, the Lean Construction Institute was founded in 1997 by Gregory Howell, Glenn Ballard, Iris Tommelein and Todd Zabelle, originally under the name Center for Innovation in Project and Production Management, according to LCI's own timeline.

What this means for teams today: The first move was to change how people thought about the work. Before you adopt a lean tool on a project, ask whether your plan treats work as tasks to tick off or as a flow that can stall.

The Last Planner Years (1994-2003)

Ballard and Howell make weekly promises reliable

This era overlaps Koskela's, because the research and the practice ran side by side. The tool that answered his challenge was built on job sites, not in a library. LCI's timeline says that in 1994 Howell and Ballard used the Last Planner System to "save a troubled project", and that they first met on a troubled project in 1979. Ballard's own biography dates his development of the system to pilot projects over the period from 1991 to 1998. The two dates fit together: 1994 is the rescue that LCI highlights, and 1991-1998 is the span over which the method was developed.

An interview on LCI's site says Ballard and Howell used the system on a floundering construction project in Venezuela after four to five years of earlier work. They had concluded that consultants who only rescued failing projects, without changing how construction was done, would never fix the underlying problem. Their stated goal was to make clients "not need what you were brought in to provide".

The method itself is documented in Ballard's 2000 doctoral thesis at the University of Birmingham. Per the thesis record, traditional project controls mainly detect variances after they occur, while the Last Planner system aims to make plans actually get carried out, adding production management to contract management. A key measure was Percent Plan Complete (PPC): the thesis asks how to raise plan reliability above the 70% PPC level, and says the last of three case studies reached the 90% target. LCI's own description of the system gives the core idea in plain terms. The last planner is the person closest to the work, with authority to make reliable commitments for their discipline, and weekly work planning establishes the set of promises from specific people for work that will be done. The 54% figure above is the gap those promises were meant to close.

LCI's timeline records that Howell and Ballard published an update on the system in 2003 and that the first LCI Congress was held in Portland, Oregon, in 1999. The LCI interview adds that an international contracting symposium hosted by LCI in Atlanta in 2003 led to the Integrated Form of Agreement, a new kind of project contract.

What this means for teams today: Reliable promises beat optimistic schedules. Track how many weekly commitments your team actually completes, and ask why the missed ones failed.

The Software Turn (2003-2013)

Poppendiecks and Ries carry lean into code and startups

Lean reached software from a different direction. Mary and Tom Poppendieck's Lean Software Development: An Agile Toolkit was published on May 8, 2003 by Addison-Wesley Professional. The publisher's description says the authors identify seven fundamental lean principles and adapt them for software development, and its chapter titles include Eliminate Waste, Amplify Learning, Decide as Late as Possible, Deliver as Fast as Possible, Empower the Team, Build Integrity In and See the Whole. Our guide to the seven lean software principles walks through them.

Agile had been named earlier, and the lean book gave it a manufacturing vocabulary: waste, flow, value stream. The connection to boards and pull systems came a year later. As our history of kanban records, David J. Anderson designed a pull system for a Microsoft engineering team in October 2004, so the project-level use of Toyota's card owes as much to him as to the factory. For the sprint framework that many teams pair with lean ideas, see our history of Scrum.

Then lean left the project and entered the company. Eric Ries wrote that his Lean Startup grew from applying ideas from lean manufacturing to his entrepreneurial challenges at the software company IMVU, and he called it "the application of lean thinking to the process of innovation." The Wharton page is dated November 22, 2011, the year of the book. It describes the core loop of turning ideas into products, measuring customer response, and learning whether to pivot or persevere. Our article on the lean startup method explains the practice.

Neither the Poppendiecks' principles nor the Lean Startup is the Toyota Production System. Both borrowed its logic, and each reshaped it for work that has no assembly line.

What this means for teams today: Copy the question, not the factory. "What is waiting, and why?" works on a backlog as well as on a shop floor.

The Professional Era (2013-present)

Lean delivery gets staff, books, certificates and local chapters

By the 2010s lean construction had matured into an institution. LCI's timeline records that Dan Heinemeier became its first Executive Director in 2013, that Transforming Design and Construction: A Framework for Change was published in 2016, that Respect for People was added to its national events in 2021, and that it launched practitioner certifications in 2023 and 2024. It reports over 30 local Communities of Practice and more than 1,500 annual Congress attendees.

Large projects also became showcases. LCI's interview says Ballard was Technical Director for Strategic Project Solutions, which led the lean implementation on Heathrow Terminal 5, and credits the project with saving about $200 million and coming in 10 percent under cost. That is LCI's own account, not an independent audit.

Meanwhile, other fields kept the same pattern. The Lean Enterprise Institute notes that lean has spread to every country and many sectors, and says lean consciousness is only beginning to take root among senior managers. In project work today, teams mix lean flow, agile iteration and traditional control, which our history of hybrid project management describes, and many run them inside digital tools covered in the history of project management software.

What this means for teams today: Lean is not a project type. It is a set of habits applied to whatever the work is, and it lasts only when someone owns the habits.

Key People

Key Facts

Key Facts: Lean Project Management History

• Ford's line produced a finished Model T every 93 minutes by early 1914, but only one model.
• Toyota says kanban was adopted at all its plants in 1963.
• Koskela's September 1992 report applied the new production philosophy to construction.
• The first International Group for Lean Construction conference was held in Espoo, Finland, in 1993.
• Ballard's 2000 thesis aimed to raise plan reliability above 70% PPC, and one case reached 90%.
• Lean Software Development was published on May 8, 2003.

The Pattern Behind the History

We call this the Prove, Rename, Translate, Promise, Spread pattern. It is our reading of the timeline, not a research result.

1. Prove it on repeating work. Ford's line and Toyota's cards worked in factories first.
2. Rename it for outsiders. Krafcik's 1988 article and the 1990 book gave a closed system a portable label.
3. Translate the theory before the tool. Koskela's 1992 report changed how construction was understood before any new method existed.
4. Turn the idea into a promise. The Last Planner System made flow concrete as weekly commitments that could be counted.
5. Spread it by vocabulary. Waste, flow and pull moved into software and startups faster than the factory methods themselves.

What It Teaches Teams Today

• Ask what is waiting. Idle work, not busy people, is the signal lean looks for.
• Make promises small and measurable, and count how many are kept.
• Let the people doing the work make the weekly commitment.
• Borrow the question before the tool. Toyota's cards did not become Anderson's board overnight.
• Be exact about the word. Say which lean you mean: the factory system, a construction method, a software principle or a startup loop.

For the wider story, read the history of project management, the evolution of project management methodologies, and our history of critical chain, another method that treats flow as the heart of a project.

Lean came to projects as a change in question, from "are we on schedule?" to "is the work flowing?" The factory gave it a name, construction gave it a promise, and software gave it a vocabulary. What carried over each time was the same habit: look at what is waiting, and find out why.