Last Planner remains a craft. And that’s exactly why it sometimes fails – not because of the system, but because of the way we use it. When weekly, daily, lookahead, and PPC reviews become normal meetings, there is more communication but less reliability. This article highlights typical misconceptions and provides concrete steps for returning LPS rituals to their intended purpose: an operating system for commitments, troubleshooting, and learning.

The fallacy: “More meetings = more control”

Meetings are often designed for information exchange. This can be useful, but Last Planner was built for something else: flow.

LPS rituals are not “meetings” but mechanisms that control behavior:

• Work is prepared in such a way that commitments are realistic.
• Obstacles are made visible and actively removed.
• Deviations are not only explained but translated into improvements.

When we treat rituals like meetings, a paradox occurs: there is more talk, but the plan still falls apart.

Symptom vs. cause

Symptoms (frequent):

• Weekly takes longer but provides less clarity
• Lookahead is a “light version” of the schedule
• Daily becomes a problem-sharing circle
• PPC is a number without consequence
• The main energy goes into “Who is to blame?” rather than “What are we changing?”

Cause (almost always):

The rituals lose their character as a commitment and learning machine.

A meeting often ends with: “We’ll take care of it.”

An LPS ritual ends with: “I will deliver X by date Y – and the prerequisites are secured.”

Four misconceptions that you can recognize immediately

1) Weekly work planning becomes a status round instead of a promise round

The weekly meeting is used to report on what has happened – instead of making concrete promises about what will be finished next week.

2) Lookahead becomes bar shifting instead of constraint radar

Deadlines are postponed, but obstacles (approvals, materials, access, planning) remain.

3) Daily huddle becomes a brief meeting instead of a cycle reset

Problems are discussed, but no quick decisions are made about what needs to be done differently today.

4) PPC review becomes reporting instead of a learning loop

Reasons are listed – without any real change to the system that causes these reasons.

Stabilize: First execution, then improvement

In unstable projects, LPS sometimes seems “too small” for the chaos. That’s exactly when a clear focus is needed:

first stabilize, then improve.

HSC is not a standard consulting firm, but a project stabilizer with leadership and lean DNA: We bring order to complexity, first stabilize execution, and then improve sustainably – in a practical and people-focused way.

5 measures you can implement starting tomorrow

1) Make ritual rules visible (on the board, not in your head)

Examples as working agreements:

• Weekly: “Only commitments that are prepared.”
• Daily: “10 minutes – decisions, no stories.”
• Lookahead: “Every constraint has an owner + date.”

2) Introduce a “definition of ready” for commitments

A task is only committed to if the prerequisites are clarified (typically):

• Plan/details clear
• Approval available
• Materials scheduled or available
• Access/space available
• Team/equipment scheduled

3) Constraint log with ownership and deadline

No owner = no constraint. Then it’s just a wish.

Tip: Actively manage max. 5–10 top constraints in the weekly meeting, don’t manage 50.

4) PPC review: Max. 15 minutes – plus 1 system change per week

Don’t collect 20 reasons. Define one improvement that reduces the most common reason.

Examples:

• Simplify/standardize the approval process
• Organize material provision as pull
• Interface rule for handovers (“definition of done”)

5) Leadership protects focus: Timebox + clear moderation

Rituals are short, regular, and sharp. Digressions are brought back to the topic in a friendly but consistent manner. This is respect for the team – not harshness.

Measurement: 4 metrics that really mean something

1. PPC (Percent Plan Complete) – only useful with clear commitments
2. Constraint Removal Rate (proportion of constraints resolved per week)
3. Plan stability (how often commitments are overturned)
4. Adherence to deadlines at the commitment level (e.g., “finished on the promised day”)

Risks/trade-offs

• Excessive ritual discipline without explanation can generate resistance (“control instead of help”).
• The “constraint-free” rule feels slower at first – but reduces later escalations and rework.

Conclusion

When Last Planner “doesn’t work,” it’s rarely because of the system. Most of the time, we treat its rituals like meetings – and lose exactly what makes LPS powerful: commitments, troubleshooting, learning.

FAQ

FAQ 1: What is the difference between a meeting and an LPS ritual?

A meeting often involves the exchange of information. An LPS ritual generates commitments, removes obstacles, and closes a learning loop.

FAQ 2: Does PPC always have to be high for LPS to work?

PPC is a sensor. The decisive factor is whether deviations are systematically used to derive improvements.

FAQ 3: What is the fastest lever when LPS “doesn’t work”?

Definition of Ready for commitments + constraint ownership in the lookahead. This usually increases plan stability noticeably.

Note

This article is based on practical experience from Lean Construction/LPS implementations and project stabilization