At the 2018 Lean Construction Institute Congress, Michael Carr described an internal debate about schedule optimization. His team could build software that analyzed a plan and told people what to move. They chose to support a different process: let the people responsible for the work build the plan together, learn from it, and adjust it.
That choice came from experience. Michael said project teams made only limited changes when his earlier company presented them with computer-generated schedule improvements. The schedule could be mathematically cleaner and still lack the ownership needed for execution.
Ownership begins before the work starts
The Last Planner System puts the people responsible for the work inside the planning process. They make commitments to one another, then look ahead for the conditions that could stop those commitments from being kept.
Make-ready planning gives that look-ahead a practical purpose. A submittal, permit, unanswered question, or material delivery has to be handled before the planned start. The team is clearing the constraint before the planned start, while the sequence can still change.
When Michael Carr returned to the limits of top-down optimization, he put the lesson plainly: “the value that people bring to the process is instrumental.” The people carrying out the work need a real part in shaping it.
Live information belongs beside the plan
Michael Carr described several TouchPlan changes that were under development in 2018. Dependencies would remain visible while tickets moved. Labor totals that had required a separate report would appear in the live plan. Planned and actual start dates, crew sizes, durations, and material quantities could sit closer to the work they described.
The timing is important. A crew spike seen while the team is moving work can lead to a different decision than the same spike discovered after a report is printed. The data is useful because it arrives while the plan is still open to adjustment.
He also described releasing an 80 percent solution, listening to users, and improving it. The product process followed the planning idea: make a responsible move, see what happens, and use the feedback to shape the next move.
Automation should change the task, not erase the judgment
The robotics discussion focused on repetitive movement and layout work. Michael Carr did not present automation as a reason to remove skilled people. He said, “We're talking about augmenting them.”
In his 2018 examples, technology could reduce mundane work and leave more time for planning ahead or solving harder project conditions. Human reasoning remained necessary because buildings, sites, and the way designs are carried out are not identical.
Look for the decision window
A useful planning review begins with a recurring issue the team sees too late. Follow that issue back to the moment the people responsible for the work first could have seen it. If the answer is after a report is issued, bring the smallest useful piece of information into the planning conversation and let the team decide whether it changes the plan.
In that 2018 roadmap, the software was intended to show dependencies, labor, and performance beside the plan. The robotics example explored taking on repeated layout work. The plan becomes usable when the people carrying it forward can see the issue, shape the response, and own the next commitment.
