Large infrastructure projects have a dubious record – rarely is a project delivered on or before the original planned due date. Analysis of every failed project reveals that the delays are due to uncertainties, apparently, outside managers’ direct locus of control. Is that really the case? Are we sure that no wastage is created due to dysfunctional management practices? The wastage of time and capacity in projects emanates from the following erroneous paradigms of management:Assumption of (In) Adequate ResourcesMost of the large infrastructure projects are actually many independent sub-projects, almost executed in parallel with integration at the end. The managerial and technical bandwidth and even the direct resources (civil labour, fabricators, engineers, etc.) required to manage it, are significant. But, in most cases, there is always a scarcity of resources. But at the same time, to complete a project on time, it is considered imperative to work on all work fronts sooner rather than later. This, in turn, leads to bad multi-tasking in engineering and procurement. Delays creep in, and almost every sub-project is delayed in the pre-erection phase. Civil work invariably starts without complete drawings, leading to further interruptions. At the same time, when many civil work fronts are started simultaneously, progress slows down due to the thin assignment of resources. <figure class="image"><img style="aspect-ratio:1080/1080;" src="https://new-stage-be.vectorconsulting.in/storage/editor_uploads//1_1715232237.png" width="1080" height="1080"></figure>Almost every manager in every key area attributes delays to ‘inadequate resourcing’ and all efforts go into recruiting experienced or skilled resources, which seem ever elusive. However, what gets ignored is the rampant wastage of limited resources due to multi-tasking in various support departments, leading to inadequate preparations before the start of the site job or poor issue resolution due to stretched management bandwidth. Conflict of cost and timeLarge projects invariably involve huge procurement budgets with significant scope for negotiations for a price reduction. Typically, using multiple vendors and aggregating various parts in different modules (or sub-projects) are considered as the best way to reduce the costs of bought-outs. But, at the same time, such aggregations also create a ‘batching effect’ in design and procurement. This leads to a situation where work has to be done in parallel on all sub-projects at the site. In the end, one reaches a stage where commissioning not only has to be done independently for each sub-project but also for the larger integration between sub-projects for going live on entire operations. This invariably leads to rework and cascading delays. <figure class="image"><img style="aspect-ratio:1080/1080;" src="https://new-stage-be.vectorconsulting.in/storage/editor_uploads//2_1715232277.png" width="1080" height="1080"></figure>Management by milestonesIn such projects, it is considered that task detailing and scheduling is good for the overall project. Scheduling of minor tasks is usually done up to level 4 and even level 5. This level of detailing in task scheduling leads to buffering and higher overall lead time. When the task milestones are converted to a deadline, it invariably leads to adding buffers in plans while most of it is wasted in execution. Surprises are revealed only close to milestones when delays are not recoverable. Issue resolution slows down, blame games become rampant, and plans are rescheduled to follow the execution. Execution drives plans rather than the other way out. <figure class="image"><img style="aspect-ratio:1080/1080;" src="https://new-stage-be.vectorconsulting.in/storage/editor_uploads//3_1715232295.png" width="1080" height="1080"></figure>The way outThe <a href="https://www.vectorconsulting.in/en/scientific-system-thinking/">‘Theory of Constraints’</a> way of managing large projects is to first acknowledge the limitations in resourcing and management bandwidth. Once this limitation is accepted, the focus shifts to exploiting the limited bandwidth rather than wasting it by bad multitasking. So, the way ahead is to visualize the large project as a portfolio of small sub-projects and stagger them considering the limitations in resources. The rules of WIP (work in progress) control are put in place in design/procurement with clear prioritization of different modules. Work on a module is activated not based on a planned start date but based on a module completed from allowed WIP. The staggering of work fronts in pre-erection leads to staggered execution in civil. <figure class="image"><img style="aspect-ratio:1080/1080;" src="https://new-stage-be.vectorconsulting.in/storage/editor_uploads//4_1715232335.png" width="1080" height="1080"></figure>The conflict of cost and time is resolved by organizing work for collective simultaneous decision-making. The procurement contracts are designed to get aggregation benefits without having to aggregate and batch work modules.Similarly, daily management becomes the guiding management mantra rather than milestone management. The buffers are shifted from the tasks and aggregated at the project level to provide maximum safety at a point where it is needed the most.

Key Takeaways

Most large infrastructure projects, which actually are a collection of many independent sub-projects executed in parallel with integration at the end, often get delayed. Conflict is between 'inadequate resources' and balancing cost v/s profit. There is a way to avoid delays without increasing costs.

Improving flow in large infrastructure projects

Large infrastructure projects have a dubious record – rarely is a project delivered on or before the original planned due date. Analysis of every failed project reveals that the delays are due to uncertainties, apparently, outside managers’ direct locus of control. Is that really the case? Are we sure that no wastage is created due to dysfunctional management practices? The wastage of time and capacity in projects emanates from the following erroneous paradigms of management:Assumption of (In) Adequate ResourcesMost of the large infrastructure projects are actually many independent sub-projects, almost executed in parallel with integration at the end. The managerial and technical bandwidth and even the direct resources (civil labour, fabricators, engineers, etc.) required to manage it, are significant. But, in most cases, there is always a scarcity of resources. But at the same time, to complete a project on time, it is considered imperative to work on all work fronts sooner rather than later. This, in turn, leads to bad multi-tasking in engineering and procurement. Delays creep in, and almost every sub-project is delayed in the pre-erection phase. Civil work invariably starts without complete drawings, leading to further interruptions. At the same time, when many civil work fronts are started simultaneously, progress slows down due to the thin assignment of resources. <figure class="image"><img style="aspect-ratio:4000/1558;" src="https://backend.vectorconsulting.in/storage/editor_uploads//ec-article-12-img-1_1735539755.png" width="4000" height="1558"></figure>Almost every manager in every key area attributes delays to ‘inadequate resourcing’ and all efforts go into recruiting experienced or skilled resources, which seem ever elusive. However, what gets ignored is the rampant wastage of limited resources due to multi-tasking in various support departments, leading to inadequate preparations before the start of the site job or poor issue resolution due to stretched management bandwidth. Conflict of cost and timeLarge projects invariably involve huge procurement budgets with significant scope for negotiations for a price reduction. Typically, using multiple vendors and aggregating various parts in different modules (or sub-projects) are considered as the best way to reduce the costs of bought-outs. But, at the same time, such aggregations also create a ‘batching effect’ in design and procurement. This leads to a situation where work has to be done in parallel on all sub-projects at the site. In the end, one reaches a stage where commissioning not only has to be done independently for each sub-project but also for the larger integration between sub-projects for going live on entire operations. This invariably leads to rework and cascading delays. <figure class="image"><img style="aspect-ratio:4000/1558;" src="https://backend.vectorconsulting.in/storage/editor_uploads//ec-article-12-img-2_1735539768.png" width="4000" height="1558"></figure>Management by milestonesIn such projects, it is considered that task detailing and scheduling is good for the overall project. Scheduling of minor tasks is usually done up to level 4 and even level 5. This level of detailing in task scheduling leads to buffering and higher overall lead time. When the task milestones are converted to a deadline, it invariably leads to adding buffers in plans while most of it is wasted in execution. Surprises are revealed only close to milestones when delays are not recoverable. Issue resolution slows down, blame games become rampant, and plans are rescheduled to follow the execution. Execution drives plans rather than the other way out. <figure class="image"><img style="aspect-ratio:4000/1558;" src="https://backend.vectorconsulting.in/storage/editor_uploads//ec-article-12-img-3_1735539779.png" width="4000" height="1558"></figure>The way outThe <a href="https://www.vectorconsulting.in/en/scientific-system-thinking/">‘Theory of Constraints’</a> way of managing large projects is to first acknowledge the limitations in resourcing and management bandwidth. Once this limitation is accepted, the focus shifts to exploiting the limited bandwidth rather than wasting it by bad multitasking. So, the way ahead is to visualize the large project as a portfolio of small sub-projects and stagger them considering the limitations in resources. The rules of WIP (work in progress) control are put in place in design/procurement with clear prioritization of different modules. Work on a module is activated not based on a planned start date but based on a module completed from allowed WIP. The staggering of work fronts in pre-erection leads to staggered execution in civil. <figure class="image"><img style="aspect-ratio:4000/1558;" src="https://backend.vectorconsulting.in/storage/editor_uploads//ec-article-12-img-4_1735539786.png" width="4000" height="1558"></figure>The conflict of cost and time is resolved by organising work for collective simultaneous decision-making. The procurement contracts are designed to get aggregation benefits without having to aggregate and batch work modules.Similarly, daily management becomes the guiding management mantra rather than milestone management. The buffers are shifted from the tasks and aggregated at the project level to provide maximum safety at a point where it is needed the most.

<h4>Improving flow in large infrastructure projects</h4>

Download PDF

A few simple steps can drastically reduce project completion lead time in large infrastructure projects. Read to know more.

Let's Empower Growth