Lean Construction: Principles, the Eight Wastes and Pull Planning
By Kush Agarwal, President and CEO, YelloSKYE. Published .
Executive Summary
- The Question: What is lean construction, what are the eight wastes it targets, how does pull planning work, and what does a project team need to make it stick?
- The Answer: Lean construction organises a project around the value the client is paying for and steadily removes everything else: waiting, rework, double handling and unreliable plans. Its main tools are the eight wastes as a diagnostic, pull planning and the Last Planner System for reliable commitments, and a routine of measuring and learning from missed work.
- The YelloSKYE Angle: Lean depends on everyone seeing the real state of the site. Construct IQ provides a dated, located record from drones, fixed cameras and 360° walks, so constraints, completed work and hand-offs can be checked without another site walk.
Lean construction is an approach to planning and delivering projects that concentrates effort on what the client values and systematically removes work that adds nothing to it. It treats a project as a flow of tasks passed between trades, and it improves that flow by making plans reliable, exposing waste and fixing the causes rather than the symptoms. It is less a single tool than a set of habits shared by the whole project team.
This guide covers where lean thinking came from, the five principles behind it, the eight wastes with examples from real sites, how pull planning and the Last Planner System work, and the role of site visibility. That last point is where Construct IQ, YelloSKYE's construction monitoring service, fits in: lean planning only works when the team agrees on what has actually been built.
Where lean construction comes from
Lean began in car manufacturing. Taiichi Ohno and colleagues at Toyota developed a production system after the Second World War that aimed to make exactly what was needed, when it was needed, with as little waste as possible. Western researchers later described it as "lean production", and James Womack and Daniel Jones set out its principles for a general audience in their 1996 book Lean Thinking.
Construction took longer to adopt the ideas because a building is not a production line. Every project is a prototype, the factory moves to the site, and the workforce is a temporary alliance of separate companies. In 1992 the Finnish researcher Lauri Koskela published an influential report arguing that construction should be managed as flows of work and information, not only as a list of activities. Glenn Ballard and Greg Howell then developed the Last Planner System, and in 1997 they founded the Lean Construction Institute in the United States to spread the practice.
The motivation has not gone away. The McKinsey Global Institute's 2017 report Reinventing Construction found that labour productivity in construction had grown by about 1 per cent a year over the previous two decades, against 2.8 per cent for the world economy as a whole. Lean is one of the main responses the industry has developed to that gap.
The five principles on a building site
Womack and Jones described lean in five principles. Each one translates into a practical question a project team can ask.
| Principle | The question on site | Example |
|---|---|---|
| Value | What does the client actually need from this work? | A hotel operator values rooms finished to a consistent standard on the opening date, not the earliest possible frame |
| Value stream | Which steps, hand-offs and approvals does each element pass through? | Mapping a bathroom pod from design approval to installation exposes four separate waits for sign-off |
| Flow | Can work move from one trade to the next without stopping? | Floors released in a steady rhythm so each trade follows the last without gaps or overlaps |
| Pull | Is work started because the next trade needs it, or because a crew is available? | Partition boards delivered to a floor the week the boarding crew is due, not when the supplier has stock |
| Perfection | How does the team learn from each cycle and improve the next? | Reasons for missed weekly tasks reviewed every week and acted on |
The fifth principle sounds abstract, but it is what keeps lean from becoming a one-off workshop. Improvement has to be a routine with an owner.
The eight wastes, with construction examples
Lean calls anything that consumes time or resources without adding value "waste". Ohno identified seven types; an eighth, unused talent, was added later. The acronym DOWNTIME is a convenient way to remember them.
| Waste | What it looks like on site | A common root cause |
|---|---|---|
| Defects | Walls reboarded because services behind them were not tested, slabs broken out for a missing sleeve | Work covered before it was checked |
| Overproduction | A trade completes an area weeks before the next trade can use it, then the area is damaged or redesigned | Crews kept busy instead of following the sequence |
| Waiting | Ceiling fixers idle while a services inspection is rebooked; a crane waiting for a delayed pour | Constraints not removed before work was planned |
| Non-utilised talent | Foremen excluded from planning; site engineers spending days compiling reports | Planning done for crews instead of with them |
| Transportation | Materials moved from the gate to a laydown area, then to a hoist, then to another floor | No delivery plan tied to installation dates |
| Inventory | Pallets of fittings stored on every floor, exposed to weather and theft | Buying ahead of need to secure prices or avoid shortages |
| Motion | Operatives walking the length of the site for tools, drawings or answers | Poor workplace organisation, information held off site |
| Extra processing | The same progress information typed into three reports; approvals that pass through unnecessary layers | No single agreed source of information |
Defects deserve special attention because they compound: a mistake that is built over becomes rework for several trades. Our guide on how to reduce rework in construction sets out practical steps for that specific waste, so we will not repeat them here.
The other wastes are easier to miss because they rarely appear in a cost report. A crew waiting for an area does not generate an invoice line, and a manager driving between sites to check progress looks like diligence. Learning to spot them is the first lean skill a team needs.
Pull planning and the Last Planner System
Traditional programmes push work: a central planner sets dates and trades are expected to meet them. The Last Planner System instead gives planning responsibility to the people who direct the work, the "last planners" such as trade foremen, and builds commitments from the bottom up.
The levels of planning
- Master schedule. Sets the key milestones and overall logic for the project.
- Phase schedule built by pull planning. For each phase, the trades work backwards from a milestone, usually with sticky notes on a wall or a shared board, agreeing what each one needs from the others and when.
- Lookahead plan. Typically covering the next several weeks, it lists upcoming tasks and the constraints that must be cleared first: drawings, materials, access, inspections, equipment and the preceding work.
- Weekly work plan. Trades commit only to tasks that are free of constraints, so a promise means something.
- Daily check-in. A short meeting to confirm the day's work and raise new problems before they stop a crew.
Running a pull planning session
A good session starts with a clear milestone and its definition of done. The last activity before the milestone goes on the board first. Each trade then asks what it needs to start its task and places the preceding tasks to the left, until the chain reaches today. Durations are agreed by the people doing the work, and any buffer is held openly as a shared allowance rather than hidden in individual estimates.
Measuring reliability
At the end of each week, the team records which committed tasks were completed and calculates percent plan complete (PPC). PPC is not a measure of progress; it measures how well the team keeps its promises. The useful part is the list of reasons for every missed task, grouped and reviewed so that the same constraint does not stop work twice. If you want to measure physical progress instead, our guide to percent complete in construction covers those methods.
Why lean depends on site visibility
Every step of the Last Planner System relies on an accurate picture of the site. A constraint can only be cleared if someone knows it exists. A weekly commitment can only be checked if someone can see whether the work is done. A hand-off between trades only works if both sides agree on the condition of the area. When that picture comes from memory and phone photos, lean meetings drift into debates about what is true.
Regular visual capture gives the team a shared factual starting point:
| Lean need | The question | How capture answers it |
|---|---|---|
| Constraint removal | Is the area actually ready for the next trade? | A recent 360° walk or fixed-camera view of the zone |
| Commitment check | Was last week's committed work completed? | Dated imagery of each task area compared with the plan |
| Flow between trades | What condition was the area in when it changed hands? | A located record captured at release |
| Waiting | Has work stopped in a critical zone? | Fixed cameras with activity alerts |
| Transportation and motion | Do managers need to travel to see progress? | Remote review of the latest captures |
| Extra processing | Is progress being retyped into several reports? | One record that every party opens |
Construct IQ provides this through DEX, where drone flights, fixed cameras and 360° walks sit on one dated record and actual progress is compared with the planned schedule in 4D. On our fixed-camera monitoring projects, the platform can alert the team when activity stops in a high-priority zone, which turns hidden waiting into something visible the same day. In the interior fit-out use case, working from navigable 360° records cut coordination time by 70 per cent and made the cycle from snag to closure five times faster, and the capture did not need a specialist technician.
The time saved on reporting matters for lean too, because it returns skilled people to planning and problem-solving. In our aerial progress capture use case, weekly drone flights saved site managers more than 15 hours a week of manual reporting and shortened stakeholder meetings from two hours to 30 minutes. For teams spread across several sites, our guide to remote construction site monitoring explains how this reduces travel without losing control.
Visibility does not replace the gemba walk, the lean habit of going to see the work in person. It makes those walks more useful, because people arrive already knowing what changed and can spend their time on the conversation with the crew.
Why lean efforts stall
- Treating it as a scheduling technique only. Pull planning without constraint removal and weekly learning produces nicer charts and the same delays.
- Commitments made under pressure. If foremen are pushed to promise tasks that are not ready, PPC becomes fiction and trust drains away.
- No agreed definition of done. When "complete" means different things to different trades, every hand-off becomes a dispute.
- Subcontractors brought in too late. The people with the best knowledge of how work flows are often appointed after the plan is fixed.
- Arguing about facts. Meetings spent debating what is on site leave no time to remove constraints. A shared, dated record settles those questions quickly.
Getting started: the first month
- Pick one phase or area. Start where flow problems are visible, such as fit-out of repeated floors.
- Hold a pull planning session for the next milestone, with every trade foreman in the room.
- Set up a lookahead and constraint log, reviewed weekly, with a named owner for each constraint.
- Agree definitions of done for the main tasks and hand-offs between trades.
- Start measuring PPC and recording the reason for every missed commitment.
- Put a capture routine in place so each weekly review starts from current, located evidence of the site.
- Review the top three reasons for missed work at the end of the month and change one thing about how the next month is planned.
Frequently asked questions
What is lean construction in simple terms?
Lean construction is a way of planning and running projects that focuses on what the client actually values and removes the effort that does not contribute to it, such as waiting, rework and unnecessary handling. It borrows ideas from lean manufacturing, especially the Toyota Production System, and adapts them to one-off projects with many trades. In practice it changes how work is planned, how trades commit to tasks and how problems are surfaced.
What are the eight wastes in lean construction?
The eight wastes are defects, overproduction, waiting, unused talent, transportation, inventory, motion and extra processing, often remembered by the acronym DOWNTIME or TIMWOODS. On a building site they show up as rework, work done before the next trade is ready, crews standing idle, materials moved several times, excess stock, long walks for tools and duplicated reporting. Every one of them consumes time or money without adding anything the client will pay for.
What is the difference between pull planning and the Last Planner System?
Pull planning is one technique inside the Last Planner System. In a pull planning session, the trades work backwards from a milestone and agree the hand-offs each one needs from the others. The Last Planner System wraps that phase plan in a lookahead process to remove constraints, weekly work plans built from tasks that are genuinely ready, daily check-ins and a measure of how reliably commitments are kept.
What is percent plan complete (PPC)?
Percent plan complete is the share of tasks committed in a weekly work plan that were actually completed as promised. It measures how reliable the planning is, not how far the project has progressed. Recording the reason for each missed task is what makes PPC useful, because the reasons point to the constraints the team needs to remove.
Can lean construction work on small projects?
Yes. The core habits, such as planning backwards from milestones with the people doing the work, checking that tasks are ready before committing to them and reviewing why commitments were missed, need no special software or dedicated staff. Small teams often adopt them faster because fewer parties need to agree. Larger projects benefit from a lean coordinator to keep the routine going.