Owning an early input on a tightly coupled program, one team delays it with process explanations, knowing the slip will compound downstream and sink a rival team's final delivery.
An example
Shared certification of a new sensor module belonged to the compliance group of a medical device maker's surgical division, and the cardiac division could not start production tooling until it cleared. The surgical division's general counsel was competing with the cardiac division's president for the next chief operating officer role. Certification was due in March. In March compliance asked for an extra round of biocompatibility review. In April a test lab had a scheduling problem, and in May compliance wanted a revised risk file. Each reason was plausible on its own. Tooling started ten weeks late, the cardiac team squeezed validation into half the planned time, and the launch missed the year's largest trade show. At the quarterly business review, executives saw only the missed launch and asked the cardiac president what had gone wrong.
Why it works
A late input in a tightly coupled program costs far more than the length of the delay. Each downstream phase inherits less slack than the last, so a two-week slip upstream can become a missed launch, and the rival's eventual output, even if complete, is worth much less. The rival also pays in compressed phases, overtime, scope cuts, and explanations to sponsors. Cover comes from process explanations that look legitimate (review rigor, vendor problems, regulatory caution). Beyond that, the upstream owner needs downstream phases with little slack, no program function tracking the root cause of delays across team boundaries, and executives who look only at final delivery.
The thinking behind it
Thomas C. Schelling In Arms and Influence (1966), Schelling describes salami tactics: a line can be defeated by crossing it in slices, each too small to justify a response. A cascading delay arrives the same way, one plausible slip a month, none worth escalating alone. A dependency log that adds the slips up, and escalation the week each one happens, removes the cover the small increments provide.
Oliver E. Williamson Williamson's Markets and Hierarchies: Analysis and Antitrust Implications (1975) assumes bounded rationality, so contracts are always incomplete, and some opportunism, which he later described as including incomplete or distorted disclosure. An internal dependency with no written milestone is an incomplete contract that leaves the upstream owner free to read review rigor generously. Written commitments on each upstream milestone are the safeguard.
Lee Ross Ross's fundamental attribution error, from The Intuitive Psychologist and His Shortcomings: Distortions in the Attribution Process (1977), is the tendency to blame people and overlook their circumstances. Executives who see only the missed launch hold the downstream team responsible for a situation produced upstream. Presenting the delivery date with the dependency record beside it shows them the circumstances they would otherwise skip.
Warning signs
Upstream milestones owned by another team slip repeatedly, each time with a process-shaped explanation: more review, a vendor issue, caution about compliance. Each explanation is plausible alone. Downstream slack shrinks with every slip. The upstream owner competes with the downstream team's leader for a role, a budget, or credit, and executive reviews look only at final delivery dates.
How to defend yourself
Make the dependency chain visible before the end date is the only thing anyone sees.
- Get written commitments on every upstream milestone your delivery depends on, with owners and dates.
- Keep a dependency log that records each slip, its stated cause, and its downstream effect in days.
- Escalate slippage the week it happens, to the people who will judge your final delivery, with the log attached.
- Build slack into your own plan where you can, and ask for contingency paths (a second test lab, parallel work) on the most fragile inputs.
When the final review comes, present the delivery date with the dependency record beside it.
How a leader shuts it down
Put a program manager in charge of dependencies across team boundaries, with a mandate to attribute the root cause of each delay. Give upstream milestones the same attention as final delivery. When the owner of a critical input competes with the team that depends on it, move the input or watch it closely.