5 Lessons From E Sreedharan on Finishing Work When Everyone Expects a Delay

E Sreedharan once said that the difference between a project that finishes on time and one that doesn't is decided in the first week, not the last. He was describing the Delhi Metro, but the principle applied equally to the Pamban Bridge he rebuilt in 46 days after a cyclone, and to the Konkan Railway carved through the Western Ghats when most engineers said the terrain made the schedule impossible. What he built was not just infrastructure. It was a working argument against the institutional habit of managed delay.

When Sreedharan was handed the Pamban Bridge reconstruction in 1964, the estimate from the Railways was six months. He committed to 46 days before he had drawn up the full execution plan. This is not recklessness, it is sequencing. A deadline set after the plan absorbs every contingency the planner can imagine, then a few more. It arrives padded. A deadline set first forces the plan to be leaner than comfort allows, and that pressure is exactly what removes the slack that delays hide inside. Chanakya wrote in the Arthashastra that a task expands to fill the time allotted to it. Sreedharan's method was to allot less time than felt safe, then build the plan to match.





One of the structural reasons large projects drift is that responsibility is distributed across committees, approvals, and review bodies until no single person can be held to account for a missed date. Sreedharan consistently refused this arrangement. On the Delhi Metro, he held individual engineers responsible for individual sections and individual milestones. The reporting was not to a committee, it was to him, directly, and he was on site often enough that the reporting was not abstract. When accountability has a face, the conversation about why a milestone slipped is immediate rather than retrospective.


Projects rarely fail at the end. They fail at the first deadline that was quietly renegotiated, which made the second easier to renegotiate, and so on until the accumulated drift becomes the new reality. Sreedharan's reputation for delivery rested partly on a refusal to normalise the first slip. On the Konkan Railway, when a section fell behind, the response was not to adjust the overall timeline, it was to identify what had caused the delay and correct it before it compounded. The instinct in most organisations is to absorb a small delay into the buffer and move on. That instinct is where the larger delay begins.



Institutional delay is often approval delay. A decision that requires sign-off from five bodies will take longer than one that requires sign-off from two, regardless of the urgency attached to it. Sreedharan was known for pushing hard on the organisational structure around his projects, not to bypass accountability, but to shorten the chain between a problem on the ground and a decision that resolved it. On the Delhi Metro, he had enough authority concentrated in the project body that contractors did not wait weeks for answers. Speed of decision-making on-site is not a personality trait. It is an organisational design choice made before the project begins.

A project that is 95 percent complete and sitting there is, for all practical purposes, incomplete. Sreedharan understood that the final phase of any large project, the commissioning, the testing, the handover, is where delay most often lives, because the pressure to finish has already been released by the near-completion. He drove projects through that final phase with the same intensity as the middle. The Delhi Metro's Phase 1 opened ahead of the date that had been publicly committed, which meant the visible finish matched or exceeded the promise. That matters beyond optics: it changes what the next project's stakeholders believe is possible. The lesson is not about reputation. It is that finishing completely and finishing on schedule are two separate disciplines, and both require deliberate attention at the end.