Every project manager who has ever watched a schedule slip has heard some version of the same explanation: the team was too optimistic. They didn’t pad their estimates. They should have known better.
This diagnosis is almost always wrong, and the fix it implies (better estimation, more padding, harder accountability) makes the problem worse.
The fallacy is structural, not behavioral
The planning fallacy, first described by Daniel Kahneman and Amos Tversky, is the tendency to underestimate task duration even when we know that similar tasks have taken longer in the past. The standard interpretation is that it’s a cognitive bias. People are overconfident. They discount their own history.
But in industrial project work, the mechanism is different. The estimates are wrong not because individuals are delusional, but because the system makes honest answers impossible.
Consider what happens in a typical pre-turnaround schedule review. The scheduler has a baseline. The supervisor is asked whether the work scope fits the allotted time. Two things happen simultaneously. First, the supervisor knows that if they say “no,” they’ll be asked to explain how they’re going to fix it. Second, every other supervisor in the room is saying “yes.” Saying “no” is a career risk with no immediate upside.
The incentive is to agree, adjust privately, and hope for the best. Call that what it is: a rational response to a dysfunctional system, not optimism bias.
Commitment-based scheduling breaks the mechanism
The Boots on the Ground methodology replaces estimate-and-defend with a different structure: structured commitment with explicit conditions.
The process works like this. The people who will do the work, not their managers and not the scheduler, are brought into the Briefing Room. They look at the actual drawings and scope for their work area. They’re asked a specific question: “What can you reliably complete in the next two weeks, given your current crew, your actual material status, and the interfaces you depend on?”
The question is deliberately constrained. It is not “what does the schedule say.” It is not “what do you think the schedule should say.” It is: what do you personally commit to delivering, given what you know right now?
This changes the answer. When the person who will do the work makes the commitment, rather than the person who manages them, the estimate reflects what they believe they can control. It also surfaces dependencies and constraints that would otherwise stay invisible until they became problems.
What happens to the schedule
The first time a project team runs a Boots on the Ground exercise, the schedule almost always comes apart. Tasks that were “on track” turn out to be blocked. Work that was listed as complete isn’t. Interfaces that were assumed are actually unresolved.
That collapse is the exercise working, not failing. A schedule that reflects reality, even a difficult reality, is the starting point for recovery. A schedule that looks clean on paper but does not reflect the field is a liability.
The second and third iterations run faster. The team begins to understand what a reliable commitment looks like. They stop agreeing to things they cannot control. They surface issues earlier, because early is when you can still do something about them.
The lesson
You cannot fix optimism bias by asking people to be less optimistic. You can fix it by changing the structure of the conversation so that honest answers become the rational choice, and by giving people the framework to know what they can actually commit to.
That is what commitment-based scheduling does: instead of asking people to be better estimators, it removes the conditions that make bad estimates rational.