Lessons from great infrastructure projects: canals, Panama, Hoover Dam, the Snowy and the Opera House

Great infrastructure projects attract attention for their scale: canals crossing countries, dams holding back rivers, bridges spanning harbours and buildings that define cities. Their histories are also some of the richest sources of practical lessons for anyone leading projects, from a factory expansion to a new information system. Many of the hardest problems on these projects were not about calculating loads or pouring concrete. They were about choosing the right problem, understanding why earlier attempts failed, finding what really governed success, estimating honestly, keeping people safe and governing decisions when costs and politics collided.

Studying these projects is useful precisely because their lessons are so consistent. Projects that reframed the problem, investigated the ground and the risks, learned from failure and set realistic expectations tended to succeed. Projects that copied a method from a different context, underestimated complexity or were approved on optimistic numbers tended to struggle, regardless of the brilliance of their designers.

This article looks at several landmark projects: the early canals, the Panama Canal, Hoover Dam, Australia’s Snowy Mountains Scheme, the Sydney Harbour Bridge and the Sydney Opera House. It draws out lessons for project leaders and sponsors about framing, investigation, governing constraints, estimation, people and governance. It is general information for project managers, sponsors, engineers and business leaders.

Canals: why the business case worked

In 1761, the Bridgewater Canal in north-west England, engineered by James Brindley, carried coal from the Duke of Bridgewater’s mines to Manchester. Its economics were simple and compelling. A horse pulling a barge on a towpath could move many times the load it could pull in a wagon on a rough road, so the canal sharply cut the price of coal in the city. The canal paid for itself and set off a wave of canal building.

In the United States, the Erie Canal, opened in 1825, connected the Hudson River to the Great Lakes, cutting the cost and time of moving goods from the interior to New York and helping make New York the country’s leading port.

Canals were demanding to build. Water cannot climb, so a canal must hold level over long distances and change level only at locks, and it needs a reliable water supply to replace what each lock passage sends downhill. Success depended on accurate survey, earthworks and water management.

Lesson: strong projects rest on a clear, physical source of value. The canals succeeded because the cost advantage was large and easy to understand.

The Panama Canal: choosing the right problem

The French attempt to build a canal across Panama, led by Ferdinand de Lesseps, who had built the Suez Canal, began in 1881. It planned a sea-level canal like Suez. But Suez crosses flat desert, while Panama crosses a mountain divide in a region of heavy rainfall, with the Chagres River prone to violent floods. Landslides, flooding, disease and financial scandal brought the French effort to collapse by the end of the 1880s.

The United States took over the project in 1904 and completed it in 1914 by reframing the problem. Instead of cutting down to sea level, engineers dammed the Chagres to form Gatun Lake, about 26 metres above sea level, and used locks to lift ships to the lake and lower them on the other side. The river that had been the main obstacle became the water supply that operates the locks by gravity.

Two other changes were decisive:

• Health engineering. Yellow fever and malaria, spread by mosquitoes, had killed many workers during the French attempt. Under the direction of the medical officer William Gorgas, systematic drainage, screening and mosquito control dramatically reduced disease. The project’s critical path ran through public health as much as through civil engineering.
• Earthworks realism. The deep cut through the divide suffered repeated landslides, and far more material was excavated than the cut’s design volume, because slopes in wet, weak ground kept failing. Groundwater, not the strength of dry soil, governed stability.

Lessons: a method that worked in one context may not transfer; the best design move can be to turn an obstacle into a resource; investigate why previous attempts failed rather than assuming poor execution; and look for the discipline that really governs success.

Hoover Dam: when scale changes the problem

Hoover Dam on the Colorado River, completed in 1936, was one of the largest concrete structures of its time. Its most difficult engineering problem was not strength or stability. It was heat. As cement hardens it releases heat, and in a structure of that size, the concrete would have taken a very long time to cool naturally, by some estimates more than a century, cracking as it shrank unevenly.

The engineers’ solution was to build the dam as a series of separate blocks and to embed pipes through which cold water, chilled by a refrigeration plant, was circulated to cool the concrete before the joints between blocks were grouted. Diverting the river around the site through tunnels was itself a major project before dam construction could begin.

Lesson: when a project moves from large to unprecedented, the governing problem often changes. Identifying what actually governs at the new scale is the core engineering task.

The Snowy Mountains Scheme: people and nation building

Australia’s Snowy Mountains Hydro-Electric Scheme, built between 1949 and 1974, diverted water from the Snowy River and neighbouring rivers through tunnels and dams to generate hydro-electricity and provide water for irrigation inland. It involved major dams, power stations and long tunnels through difficult mountain country.

The scheme is remembered as much for its people as its engineering. Around 100,000 people worked on it, many of them post-war migrants from dozens of countries, and it played a significant part in Australia’s post-war migration and the development of its engineering and construction capability. It is widely regarded as one of the great engineering achievements of its era, and it also brought environmental costs to the Snowy River that later required remediation of environmental flows.

Lessons: major projects build workforce capability and communities as well as assets; integrating people from many backgrounds is a management challenge and an opportunity; and environmental consequences need to be considered from the start rather than corrected decades later.

The Sydney Harbour Bridge: engineering and manufacturing together

The Sydney Harbour Bridge, opened in 1932, is a steel arch bridge built by the British firm Dorman Long under a design and construct arrangement. The two halves of the arch were built out from each shore, held back by cables anchored in tunnels, until they met in the middle. Much of the steel was fabricated in workshops built on site at Milsons Point.

Lessons: construction method can be as important as design; temporary works, such as the cables holding the half-arches, carry as much risk as the permanent structure; and establishing fabrication capacity close to the work can be decisive for a project’s logistics and quality.

The Sydney Opera House: estimates, design and governance

The Sydney Opera House, designed by the Danish architect Jørn Utzon after an international competition in 1957, opened in 1973, about ten years later than planned. Its cost, commonly cited as rising from an early estimate of about A$7 million to a final cost of about A$102 million, made it one of the best-known examples of a project overrun. Construction began before the design of the famous roof shells had been resolved, and finding a buildable geometry for them took years of work by the architect and the engineers. Disputes between the architect and the state government led to Utzon’s resignation in 1966, and the interiors were completed by others.

The building is now a World Heritage–listed icon, which shows that projects judged failures on cost and time can still create great value. But the lessons for project governance are clear: starting construction before the design was resolved, approving the project on an early estimate and failing to manage the relationship between client and designer created years of cost, delay and conflict.

Lessons: early estimates for novel projects are highly uncertain; starting construction before key design problems are solved transfers risk into construction; and clear governance and relationships between sponsor and designer matter as much as technical skill.

Built to last: operating and maintaining great works

Many of these structures have served for generations: the Panama Canal for more than a century, Hoover Dam and the Harbour Bridge for close to a century, and some canals for far longer. Their long lives depend on continuous operation and maintenance that rarely makes headlines. The Harbour Bridge’s steelwork needs ongoing painting and inspection; dams need monitoring of seepage, movement and concrete condition; canals need dredging, lock maintenance and water management. Panama itself was expanded with new, larger locks a century after it opened, to accommodate bigger ships.

The lesson for project leaders is that a project’s value is realised over its operating life, not at its opening ceremony. Designing for maintenance access, durability and future expansion, documenting the asset properly and funding its upkeep are part of delivering a successful project.

Common lessons for project leaders

Research on large projects has found that cost and schedule overruns are common, and that they often stem from optimistic early estimates and underestimated complexity rather than unforeseeable events. Comparing a project with the actual outcomes of similar past projects, an approach called reference class forecasting, helps counter that optimism. The estimating project costs from cost drivers article and the how confident is that finish date article cover practical estimating and forecasting methods.

A worked example

This is an illustrative example. A manufacturer plans a new production building and process line on a brownfield site, with a base cost estimate of $20 million. The board wants to avoid the overruns it has seen on other projects.

Applying the lessons.

• Source of value: the business case is tied to specific gains in capacity and cost per unit, with the assumptions written down.
• Reference class: the project team gathers data on comparable industrial projects. In this illustration, they show a median overrun of about 15%, with about one in five overrunning by 40% or more. The board sets the project budget at $23 million, the base estimate plus 15%, and holds a further reserve up to $28 million, base plus 40%, under board control.
• Investigation: early geotechnical and contamination surveys are commissioned before design is fixed, after learning that ground conditions caused overruns on earlier projects in the area.
• Governing constraints: the team identifies the power supply upgrade, which depends on the network operator’s timetable, as the item most likely to govern the schedule, and starts it first.
• Design before construction: process layout and building structure are frozen before the main construction contract is let.
• People: a recruitment and training plan for the new line is part of the project, not an afterthought.

Result. Contamination found early is dealt with in the design stage, and the power upgrade is completed in time. The project finishes within its $23 million budget plus a modest draw on the reserve, and the business has a record of estimates and outcomes to inform its next project.

Applying these lessons in an Australian business

• State the source of value clearly and test the assumptions.
• Reframe problems before committing to a method.
• Investigate ground, sites and existing conditions early.
• Study why earlier attempts failed, internally and in your industry.
• Identify what governs schedule and cost, including in other disciplines.
• Use reference classes to set realistic budgets and reserves.
• Resolve key design problems before construction.
• Plan for people, safety and environmental effects from the start.

Questions worth considering

• What is the physical or commercial source of value in this project, and how sure are we of it?
• Is our method borrowed from a context that differs in important ways?
• Why did similar projects fail or overrun, and what are we doing differently?
• What will actually govern the schedule and cost at this scale?
• How do our estimates compare with the outcomes of comparable projects?
• Have we resolved the hardest design problems before committing to construction?

Bringing it together

Great infrastructure projects show that success depends on framing, investigation and governance as much as engineering brilliance. The early canals rested on clear value; Panama succeeded by reframing the problem and solving public health; Hoover Dam identified that heat governed at its scale; the Snowy scheme built people and capability as well as assets; the Harbour Bridge showed the importance of construction method; and the Opera House showed the cost of building before designing and estimating honestly. The same lessons apply to projects of every size.

Source: KEVOS editorial notes, drawing on an earlier KEVOS engineering history series on canals, roads, the Panama Canal, Hoover Dam and prestressed concrete, together with established histories of engineering and Australian infrastructure. Figures for historical projects are widely cited approximations. The worked example is illustrative. This article is general information.