I've watched the Last Planner System get rolled out on maybe a dozen jobs over the years. Some of them stuck. Most of the failures had nothing to do with the method and everything to do with the guy running the trailer. You can buy the software, print the sticky-note templates, send two people to a two-day training, and still end up with a wall of stale cards that nobody trusts by month three. The method is sound. What kills it is leadership that shows up for the kickoff and then disappears the first time the schedule and the field disagree.
So let's talk about what leadership actually has to do — not the values-poster version, but the specific behaviors that decide whether collaborative planning takes root or quietly dies on your project.
Show Up to the Meeting You Asked People to Attend
The single loudest signal a superintendent sends is where he physically stands during the weekly work plan meeting. If you call the trades together every Thursday to make and secure commitments, and then you're on the phone in the corner or you skip it entirely when the owner's in town, you've told everyone exactly how important this is. Presence isn't a soft skill here. It's the whole game in the first eight weeks.
When I say presence I mean:
- You're in the room, on time, without your laptop half-open on something else.
- You know the plan well enough to ask a real question — "Drywall, you committed to level 3 last week and it slipped, what's blocking you this week?" — not just nod along.
- You stay for the whole thing, including the part where someone raises a constraint you can't solve on the spot.
The trades read this instantly. They've all been through initiatives that the boss championed for three weeks and abandoned. Your job in the early going is to be boringly consistent until they believe it's real.
Make It Safe to Say "I Can't Hit That"
Last Planner runs on honest commitments. A crew that promises Friday because they're afraid to say Tuesday is worse than useless — it poisons every downstream trade that plans around a date that was never going to happen. The whole point of the system is that a foreman can look you in the eye and say "no, I won't be ready, my material's stuck at the supplier," and the response is "okay, good, let's re-sequence," not a chewing-out.
Here's the trap. You say you want honesty, and then the first time a foreman flags a realistic problem, you visibly deflate or push back hard in front of his peers. That foreman will never volunteer a bad number again, and neither will anyone who watched. You spent your credibility in one exchange.
The behavior that builds safety is almost dull: you thank people for early warnings. A constraint flagged three weeks out is a gift — it's a problem you can still solve cheaply. A constraint that surfaces the morning of is a fire. Reward the former loudly and the field learns to bring you problems while they're still small.
Protect the Planning Hour Like It's Concrete Placement
Everybody's busy. That's not a reason to skip planning — it's the reason planning exists. But the weekly work plan and the look-ahead review are the first things to get bumped when the day goes sideways, because they don't feel like "real" work the way chasing a delivery does.
Leadership means treating that hour as fixed. A few concrete moves:
- Same time, same place, every week. Predictability is half the battle. People plan their day around a meeting that never moves.
- Shield it from interruptions. If the owner wants a walk, it happens before or after, not during. If you break your own rule, the meeting is optional and everyone knows it.
- No-show has a consequence. Not a punishment — a follow-up. A foreman who blows off the meeting gets a call: "We committed your crew to something in there. Are you good with it or not?" Two of those and attendance improves.
The reason this matters: short-interval scheduling only works if the loop closes every week. Miss a couple of cycles and the plan drifts from reality, people stop trusting it, and you're back to firefighting off a bar chart nobody's looked at since the preconstruction meeting.
Facilitate, Don't Dictate
This is the hardest shift for a lot of experienced supers, and I include my younger self. You've been solving problems by telling people what to do for twenty years. It works, sort of. But the entire premise of collaborative planning is that the person doing the work knows the sequence and the hazards better than you do from the trailer.
The trade flow — the handoff sequence from one crew to the next — has to be built by the trades, out loud, in front of each other. When the framer, the electrician, the plumber, and the mechanical foreman argue out who needs which wall first and how much clearance the top-out needs before the drywall crew shows up, you get a sequence that actually holds. When you draw that sequence yourself and hand it down, you get a sequence that looks clean on paper and falls apart in the field because you didn't know the fire-caulk inspection had to happen before the ceiling grid.
So run the meeting with questions. "What do you need from the crew before you can start?" "What's going to make you miss this?" "Who's this handoff going to hurt if it slips?" Your job is to make the conversation happen and then get out of the way, not to have the answer.
Lead With the Numbers, Not Your Temper
Percent Plan Complete is the one metric that keeps everyone honest, and it's the one most often used wrong. PPC is the share of the week's commitments that actually got done — not a productivity number, a reliability number. A crew can be busting tail all week and still post a low PPC because they kept committing to work they weren't actually ready to start.
The mistake is turning PPC into a scoreboard for shaming. The second a foreman thinks a low PPC gets him yelled at, he games it — he commits to easy stuff, or he stops committing at all. Now your best diagnostic is worthless.
Use it the way it's meant to be used:
- Track the trend, not the point. One bad week means nothing. Six weeks stuck at 55% means your look-ahead isn't clearing constraints before work hits the plan.
- Chase the variance, not the person. Every missed commitment gets a reason code — prerequisite work, materials, information, weather, labor, whatever. After a month those reason codes tell you exactly where your project bleeds. If half your misses are "prerequisite work not complete," your problem is sequencing, not the crews.
- Say it out loud: this data is for learning. And then actually behave that way, because they'll test you.
Good scheduling software earns its keep right here — a tool like LookAheadWall keeps the commitments, the trade-flow handoffs, and the reasons for misses in one place so the pattern is visible instead of buried in someone's notebook. But the software only surfaces the pattern. What you do with it is leadership.
Develop the People Who'll Run It When You're Gone
If the Last Planner System on your job depends entirely on you, it's fragile. The good superintendents I've worked with spend real time coaching a foreman or two into running the weekly meeting themselves. It's uncomfortable to hand over the room. It's also the only way the practice survives you moving to the next job.
Start small. Let a foreman run the look-ahead review while you sit in the back. Debrief afterward — what went well, where the conversation stalled. Give them the room more often. The goal is a bench of people who can facilitate a planning session without you, because that's the difference between a method that lives on the project and a method that lives in one person's head.
Don't Quit When It Gets Ugly Around Week Six
There's a predictable dip. The first few weeks feel great — everyone's engaged, the novelty carries it. Then reality shows up. PPC is lower than anyone wants to admit, a couple of foremen are grumbling that the meeting is a waste of time, and the schedule pressure is mounting. This is the moment most implementations die, because leadership takes the low numbers as proof the method doesn't work and quietly lets it lapse.
The low numbers are the method working. It's showing you how unreliable your planning actually was all along — you just couldn't see it before. The answer isn't to abandon the process, it's to dig into why the commitments are missing and fix the upstream problem. Persistence through this dip is probably the single highest-leverage thing a leader does. Adjust the mechanics if you need to. Don't give up the discipline.
Different Chairs, Different Jobs
Leadership requirements aren't the same at every level, and pretending they are causes a lot of finger-pointing.
- Executives own the air cover — resources, consistent messaging, and not undercutting the process by demanding dates the plan says are unrealistic.
- Project managers own barrier removal. When the field flags a constraint that can't be solved on site — a design RFI, a long-lead material, an access conflict with the owner — that's the PM's to run down before it hits the week's plan.
- Superintendents own the room. Facilitation, protecting the meeting, holding the trade partners to their commitments, keeping the tone honest.
- Foremen own the frontline commitment — bringing a realistic number, flagging blockers early, and making good on what their crew promised.
When one of these chairs is empty, the others feel it. A super can facilitate beautifully and still lose, if the PM won't chase constraints or the exec keeps promising the client dates that were never in the plan.
The Warning Signs You're the Problem
A few honest gut-checks. Any of these means the process is running on fumes:
- Lip service. You talk up collaborative planning in the OAC meeting and then override the field plan the moment it's inconvenient.
- Delegation without support. You told a foreman to "run the Last Planner thing" and gave him no time, no coaching, and no backup when a trade blows off the meeting.
- Selective standards. Your favorite sub gets a pass on missed commitments while everyone else gets grilled. The room notices within a week.
- Vanishing at the dip. Attendance is optional now, the cards are two weeks stale, and you've quietly stopped bringing it up.
The Short Version
The Last Planner System, short-interval scheduling, weekly work planning — whatever you call the practice on your job — is a mirror. It reflects the quality of the leadership standing behind it. Presence, patience, protected time, honest use of the numbers, and the stubbornness to push through the ugly middle: that's the whole list, and none of it comes in the box with the software.
The tools matter — a shared, visual look-ahead everyone can see keeps the plan honest and the handoffs clear — but they're an amplifier, not a substitute. Put a disciplined super behind a good tool and you get reliable workflow. Put lip service behind the best software on the market and you get an expensive wall of stale cards. Before you roll it out, be honest about which one you're prepared to be.