Someone outside the team sets a chain of tight, interlocking deadlines for its initiative, knowing an early slip will compound and the failure will be blamed on the team's execution.
An example
The team building a new estimating platform at a general contractor had a sponsor in the chief executive and an opponent in the head of preconstruction, whose estimators would have to give up their spreadsheets. The head of preconstruction chaired the program's steering group and set its milestones: data migration in six weeks, pilot bids in ten, full cutover before the spring bidding season. Migration slipped nine days because the legacy cost codes were inconsistent, and every later date stayed where it was. Each monthly review recorded another missed gate and asked why the team was behind, and the platform lead began to sound like someone making excuses. After the third review, the lead went to the chief executive with a one-page dependency chart showing how the first slip had moved every later task, and asked for the team to re-baseline the schedule. The sponsor agreed and treated the migration slip as a scoping problem.
Why it works
Getting the outcome the opponent wants looks easy, almost free: set the dates, wait, and let the slips do the work. Continued sponsorship looks worse, because the upside can no longer arrive in the time the sponsor committed to defending, and costlier, because the sponsor has to defend each missed gate in front of peers. The schedule-setter appears to be holding the team accountable and never seems to oppose anything. It needs authority over the schedule, real technical dependencies, a sponsor who judges by milestone hit rate, and a team that cannot contest dates without sounding defensive.
The thinking behind it
Lee Ross Ross's The Intuitive Psychologist and His Shortcomings: Distortions in the Attribution Process (1977) names the fundamental attribution error: observers explain behavior by personal traits and underestimate the situation, even when situational pressures are plain. When milestones slip under a schedule designed to fail, the steering group reads the slips as poor execution. A dependency chart works because it puts the situation, the schedule's design, in front of the observers.
Jonathan Baron Baron and Hershey's Outcome Bias in Decision Evaluation (1988) found that people rate the same decision as better made when its outcome happens to be good, using outcomes as evidence about decision quality where they carry none. Missed gates are outcomes, and the sponsor reads them as proof the initiative was a poor bet. Re-baselining after the first slip breaks that link before the outcomes pile up.
Warning signs
Milestone dates are set outside the delivery team, often by someone with a stake against the initiative. Dates are never re-baselined after early slips, so every later gate is missed by construction. Reviews focus on hit rate and ask why the team is behind. Complaints about the schedule are heard as excuses. The person setting the dates never criticizes the initiative itself.
How to defend yourself
Draw the cascade. A dependency chart that traces each later miss to the first slip moves the conversation from the team's performance to the schedule's design. Raise it after the first slip. By the third, the sponsor has already begun to doubt the initiative, and anything you say sounds defensive.
- Ask the sponsor to treat early slips as scoping problems and re-baseline the whole plan.
- Ask for schedule-setting authority to return to the team, with the sponsor approving.
- Find an observer with standing, such as a program office or an outside reviewer, who can name the pattern aloud.
How a leader shuts it down
Give delivery teams real authority over their schedules, and require re-baselining after any slip in a dependent task. Watch who sets dates for initiatives they oppose. Judge programs by long-run outcomes and health alongside milestone hit rate, and assign an observer to call out schedules built to fail.