Built to Change the World

How far should an engineer's responsibility extend beyond the drawing, the contract and the project boundary?

In this final episode of Series One, I return to a childhood ambition: wanting to invent something that could save the world. As I look back across the series, that idea feels more complicated. Engineering can change lives, but the things we build also use resources, alter landscapes and affect people in ways that may not be visible from the project boundary.

From Smeaton's Eddystone Lighthouse and the Rainhill Trials to the Tay and Forth bridges, we revisit the achievements and failures that shaped civil engineering. Along the way, we meet the people and systems behind the famous structures, and consider what these stories teach us about evidence, public benefit, safety, wellbeing and trust.

Four questions bring those lessons together: Is it sound? Will it work as a whole? Who does it affect? Can people trust it? I explore how they apply to the next wave of technology, including AI, and to infrastructure such as HS2 and the Thames Tideway Tunnel. New tools can expand what we are capable of doing, but they cannot decide what should be built or replace the judgement needed to understand who benefits and what consequences remain.

We cannot each take responsibility for every outcome alone. But we can make important consequences visible, raise concerns, connect people across organisational boundaries and give decision-makers clear advice. Sometimes that means challenging an assumption; sometimes it means listening when someone challenges ours.

The series began by asking what we should build next. We end with a better sense of what that question involves. We are the engineers whose decisions future generations will inherit. How far should we go? Far enough to understand the consequences of our work, act within our influence and help people make decisions they have good reason to trust.

Key takeaways:

Ground ambition in evidence. Understand the problem, test important assumptions and let evidence change your mind.

Think in systems and focus on public benefit. Follow the connections that allow infrastructure to work and deliver value.

Make care part of achievement. Include safety, wellbeing, fair treatment and environmental responsibility in how success is judged.

Earn trust through honest advice. Explain uncertainty, distinguish measured results from forecasts and make the public value clear.

Use the past to inform what comes next. Historical lessons can guide everyday decisions as well as major projects.

Support:

If you have enjoyed this series, please share it with a colleague, follow the podcast and leave a review. Your support helps bring these engineering stories and conversations to more people.

Coming next:

Series Two brings the conversation into the present. I'll speak with civil engineering leaders about their experiences, the challenges facing the profession and what we should build next.

Listen and follow:

Listen to Built to Change the World wherever you get your podcasts: https://podfollow.com/6790092627

Discover more from the podcast host: https://linktr.ee/michaelfisher88

Historical accuracy disclaimer:

Built to Change the World is based on historical and contemporary research and is created with the intention of presenting events, people, engineering achievements and infrastructure programmes as accurately and fairly as possible.

Historical sources, project forecasts and policy positions can differ or change over time. Some details may be simplified or interpreted to support the storytelling format.

Any inaccuracies or omissions are unintentional and are not intended to mislead. Corrections, additional context and constructive feedback are warmly welcomed at [email protected].

How can Britain deliver extraordinary engineering while struggling to sustain the ambition and public confidence behind it?

In this episode, we imagine bringing Isambard Kingdom Brunel into the modern world. We show him digital models, modern construction safety and a tunnel boring machine developed from the tunnelling shield pioneered by his father, Marc Brunel.

The engineering capability would be extraordinary to him. But when we explain that the machine is helping to build High Speed Two, a more complicated story emerges. HS2 began as a national network connecting London, the West Midlands, Manchester and Leeds. Over time, routes were reduced or cancelled, costs increased and expected opening dates moved further into the future.

We then turn to the Lincoln Eastern Bypass, a project I remember studying during my engineering training. Its original dual carriageway proposal was reduced to a single carriageway after the funding position changed. The completed road delivers real benefits, but it also raises questions about what might have been achieved if the original ambition had been sustained.

Both projects show that change and delay rarely have one cause. Funding decisions, safety concerns, contractor failure, archaeological discoveries, extreme weather and delivery challenges require different responses.

Britain has not stopped attempting bold engineering. The capability, machinery and people are still here. The deeper challenge is whether we can carry ambitious ideas through to useful public outcomes with enough honesty, continuity and credible decision-making for people to trust what comes next.

Key takeaways:

Protect the outcome, not only the project. When scope changes, explain which benefits remain and which needs are left unresolved.

Communicate uncertainty honestly. Credible estimates depend on transparent assumptions, risks and limitations.

Understand the cause of delay. Safety scrutiny, funding decisions, contractor failure and poor delivery require different responses.

Protecting people is part of progress. Physical safety, mental wellbeing and the confidence to speak up are essential measures of successful engineering.

Connect achievement with public experience. Ambitious engineering earns trust when people can understand and experience its value.

Support:

This episode includes discussion of mental health and suicide within the construction industry.

If you need someone to talk to, Samaritans can be contacted free on 116 123 from anywhere in the UK and Ireland, day or night.

Coming next:

In Episode 12, "How Far Should We Go?", we reach the final episode of the first series of Built to Change the World.

I return to an ambition I had as a child: wanting to invent something that could save the world.

But what does that ambition mean when you become an engineer?

Technical capability can tell us what is possible. It cannot decide what should be built, who should benefit or what consequences future generations should inherit.

As our technology becomes more powerful, our responsibility to exercise judgement, challenge assumptions and protect the public interest becomes even greater.

Episode 11 asks whether Britain can sustain the ambition and public confidence needed to deliver major infrastructure.

Episode 12 asks where that ambition should take us.

From whether we can still build boldly, we move to the responsibility that comes with deciding what should be built next.

Listen and follow:

Listen to Built to Change the World wherever you get your podcasts:

https://podfollow.com/6790092627

Discover more from the podcast host:

https://linktr.ee/michaelfisher88

Historical accuracy disclaimer:

Built to Change the World is based on historical and contemporary research and is created with the intention of presenting events, people, engineering achievements and infrastructure programmes as accurately and fairly as possible.

Historical sources, project forecasts and policy positions can differ or change over time. Some details may be simplified or interpreted to support the storytelling format.

Any inaccuracies or omissions are unintentional and are not intended to mislead. Corrections, additional context and constructive feedback are warmly welcomed at [email protected]

What is the true cost of progress when the people who build it are left out of the story?

In this episode, we turn from the engineers and infrastructure featured throughout Built to Change the World to the people whose labour made those achievements possible.

We begin beside a railway cutting in the 1840s. Before passengers could cross the country at speed, workers had to excavate the route, move spoil, manage water, build embankments and lay the track. Many of them would never see their names recorded alongside the finished railway.

Among those workers were the navvies, a mobile workforce with hard-earned skills in earthworks, tunnelling and heavy construction. They worked alongside local labourers, miners, masons, brickmakers, carpenters and others. Families and temporary communities followed the work too, sustained in part by women whose contribution rarely appears in accounts of engineering history.

Navvies were often described as rough, reckless and difficult. Some accounts of disorder reflected real harm, but the stereotype tells us little about the conditions in which people lived and worked. Employment was uncertain, accommodation could be poor, the work was physically punishing and injury could threaten a family's income. If we want to understand a workforce's culture, we also have to examine the system around it.

The physical price could be severe. Explosions, collapses, falls, disease and exhaustion were among the hazards faced by those building Britain's railways and other infrastructure. Historical records do not always give us a complete account of those injured or killed. That absence is itself part of the story.

This led me to a question that reaches beyond the nineteenth century: what do we measure when we call a project successful? A railway can connect communities and create opportunity while its construction places the greatest burden on people with the least influence over its decisions. The finished asset may be an achievement, but it cannot tell us everything about how that achievement was delivered.

We also consider the wider consequences of industrial progress. Britain's infrastructure grew within networks of trade, finance, resources and empire whose benefits and costs extended far beyond a project site. Those histories are not interchangeable with the experience of paid construction workers, but they remind us that the boundary of a project is rarely the boundary of its impact.

From there, we bring the conversation into construction today. Physical safety has improved enormously, yet mental health, fatigue, isolation and financial pressure remain serious concerns. Long hours, time away from home, uncertain contracts, late payment and pressure passed through supply chains can accumulate in ways that are difficult to see on a project dashboard. Mental health is complex, and no single working condition explains an individual experience. We still need to ask what our systems repeatedly demand of people.

Support services, trained colleagues and open conversations matter. But leaders must also look at the design of the work itself: programmes, procurement, staffing, travel, accommodation, supervision and whether people can speak honestly without fearing for their next shift or contract.

This episode is a tribute to the workers whose hands turned earlier designs into reality, and to those working across construction today. Remembering the people behind progress should change more than the way we tell the story.

It should change the next programme, contract, conversation and decision.

Content note:

This episode discusses suicide, mental health, injury and death at work. Please take care while listening. Support details are included below.

Key takeaways:

The workforce is part of the engineering story. Drawings and calculations matter, but infrastructure becomes real through the skill and labour of the people who build it. Their contribution deserves to be recognised alongside the finished asset.

Look beyond stereotypes to understand working conditions. Accounts of navvy behaviour can obscure the effects of insecure employment, poor accommodation, physical danger and separation from established communities.

The labour model shapes the outcome. Programme, procurement, payment, supervision and welfare influence behaviour, quality and safety. They belong within the delivery system, not outside it.

Ask who benefits and who carries the cost. Infrastructure can create lasting public value without distributing its benefits and burdens equally. A fuller definition of success must consider the people affected during delivery.

Treat historical records with care. The experiences of many workers, particularly those with little power to record their own stories, are incomplete or filtered through the views of others. Uncertainty should encourage careful judgement, not indifference.

Take psychological health seriously. Construction has made substantial progress on physical safety. Stress, fatigue and isolation also require attention to the conditions of work and the support available to those affected.

Support people and change the system. A helpline or awareness campaign can help somebody in difficulty. Prevention also means addressing unrealistic programmes, harmful pressure, insecure work and cultures that make it hard to speak up.

Listen where power is lowest. Leaders may see a healthy project report while workers and subcontractors experience a very different reality. Honest conversations must be safe, and what people say must be acted upon.

Coming next:

In Episode 11, we ask why Britain has found it so difficult to build boldly.

Earlier generations delivered railways, bridges, sewers and other infrastructure that reshaped daily life. Today, the need for ambitious engineering remains, yet major projects can become caught between changing decisions, uncertain funding, fragmented responsibility and rising costs.

We explore whether Britain has lost the ability to deliver, or whether the system around delivery has made sustained ambition harder. We also ask how engineers can challenge that system without repeating the hidden human costs explored in this episode.

Episode 10 asks us to see the people behind progress.

Episode 11 asks what it would take to build with purpose and confidence again.

Listen and follow:

Listen to Built to Change the World wherever you get your podcasts: https://podfollow.com/6790092627

Discover more from the podcast host: https://linktr.ee/michaelfisher88

Support:

If this episode has affected you, Samaritans can be contacted free, at any time, on 116 123: https://www.samaritans.org/how-we-can-help/contact-samaritan/

The Construction Industry Helpline offers confidential support to construction workers and their families. Call 0345 605 1956 in the UK or 1800 939 122 in Ireland: https://www.constructionindustryhelpline.com/

If you or someone else is in immediate danger in the UK, call 999 or go to A&E.

Historical accuracy disclaimer:

Built to Change the World is based on historical research and is created with the intention of presenting events, people and engineering achievements as accurately and fairly as possible. Historical sources can differ, and some details may be simplified or interpreted to support the storytelling format.

Any inaccuracies or omissions are unintentional and are not intended to mislead. Corrections, additional context and constructive feedback are warmly welcomed at [email protected].

What responsibility do engineers carry for the infrastructure the public rarely sees, but depends upon every day?

In this episode, we explore the engineering beneath our feet and how evidence, public health and long-term thinking transformed Victorian London.

By the middle of the nineteenth century, London had become the largest city in the world. But its infrastructure had not kept pace with its population. Human waste accumulated in cesspits, entered local water supplies and flowed through overcrowded streets into the River Thames.

Cholera repeatedly swept through London, killing thousands. At the time, the widely accepted explanation was that disease spread through foul-smelling air. During the 1854 outbreak in Soho, physician John Snow challenged that belief. By investigating where people had died and mapping the cases around the Broad Street water pump, he built a compelling evidence-based case that contaminated water was spreading the disease.

Snow's work demonstrated the importance of observing what is happening in the real world rather than relying solely on established opinion. He did not have access to modern laboratory science or a complete understanding of bacteria, but he followed the evidence and was prepared to question what respected authorities believed to be true.

Four years later, the Great Stink of 1858 made London's sanitation crisis impossible for Parliament to ignore. During an exceptionally hot summer, the smell rising from the polluted Thames became so severe that urgent action was finally authorised.

Joseph Bazalgette, Chief Engineer of the Metropolitan Board of Works, was given responsibility for delivering one of the most important infrastructure programmes in British history. His system of intercepting sewers redirected waste away from central London, while pumping stations, embankments and associated works helped reshape how the city functioned.

Bazalgette also recognised that designing only for the immediate problem would leave London vulnerable to future growth. By increasing the capacity of the system beyond the original calculations, he created infrastructure that continued serving the city for generations.

The work came at a considerable human cost. Bazalgette carried enormous responsibility throughout the programme, and the pressure contributed to periods of serious exhaustion. His story reminds us that major infrastructure depends not only on technical competence, but also on the resilience, judgement and wellbeing of the people leading it.

We then bring the story into the present through the Thames Tideway Tunnel, a modern response to the continued pressure placed on London's sewerage system. It demonstrates that infrastructure is never truly finished. Cities grow, environmental expectations change and the systems inherited from previous generations eventually require the next generation of engineers to adapt them.

For modern engineers and construction leaders, the lesson is that the value of infrastructure is not determined by how visible it is. Some of the most important engineering works are those people rarely notice because they quietly protect public health, support daily life and prevent crisis.

The best infrastructure does not demand attention.

It creates the conditions in which society can function.

Key takeaways:

Follow the evidence, even when it challenges established belief. John Snow did not begin with complete scientific certainty. He observed patterns, gathered information and tested the accepted explanation against what was happening in the real world.

Make complex information visible. Snow's mapping helped reveal a relationship that could not be seen by examining individual cases in isolation. Engineers must present evidence in ways that allow patterns, risks and consequences to be understood.

Prevention rarely receives the same attention as crisis. London's sanitation problems had been developing for years, but decisive action came only when the Great Stink directly affected Parliament. Responsible leadership means acting before failure becomes impossible to ignore.

Design for the future, not only the immediate requirement. Bazalgette recognised that infrastructure designed solely around existing demand would quickly become inadequate. Good engineering considers growth, uncertainty and the needs of generations who are not yet represented in the decision.

Invisible infrastructure still carries enormous public value. Sewers, drainage systems, utilities and buried structures may attract little attention, but they support public health, economic activity and the everyday functioning of communities.

Engineering is part of a wider system. Public health, political decision-making, funding, scientific understanding, construction and long-term operation all shaped London's response. Complex challenges cannot be solved by technical design in isolation.

Look after the people carrying responsibility. Bazalgette's exhaustion reminds us that resilience should not mean expecting individuals to absorb unlimited pressure. Sustainable delivery requires capable teams, shared responsibility and space for recovery.

Infrastructure must continue to evolve. The Thames Tideway Tunnel shows that even exceptional engineering has limits. Future generations must maintain, adapt and sometimes extend the systems they inherit.

Coming next:

In Episode 10, "The Hidden Cost of Progress", we turn from the infrastructure that protected Victorian society to the people whose labour made Britain's transformation possible.

Railways, canals, tunnels, bridges and docks are often remembered through the names of the engineers who designed them.

But they were built by thousands of labourers whose names rarely appear in the history books.

The navvies worked in dangerous conditions, moved extraordinary quantities of material and travelled wherever the next major project took them.

Their communities were frequently treated with suspicion, while accidents, disease, poor accommodation and physical exhaustion were accepted as part of the cost of construction.

We also look beyond the construction site to consider the wider consequences of industrial progress, including the communities disrupted by development, the resources consumed and the global systems that supplied Britain's growth.

Progress created prosperity, connection and opportunity, but those benefits were not shared equally and their costs were often carried by people with the least influence over the decisions being made.

Episode 9 explores the infrastructure that quietly protected society.

Episode 10 asks who paid the hidden price of building it.

From the engineering beneath our feet, we move to the people history too often left behind.

Listen and follow:

Listen to Built to Change the World wherever you get your podcasts:

https://podfollow.com/6790092627

Discover more from the podcast host:

https://linktr.ee/michaelfisher88

Historical accuracy disclaimer:

Built to Change the World is based on historical research and is created with the intention of presenting events, people and engineering achievements as accurately and fairly as possible. Historical sources can differ, and some details may be simplified or interpreted to support the storytelling format.

Any inaccuracies or omissions are unintentional and are not intended to mislead. Corrections, additional context and constructive feedback are warmly welcomed at [email protected]

What responsibility do engineers carry when the public has no choice but to trust what we build?

In this episode, we explore how iron transformed nineteenth-century bridge building, allowing engineers to create structures that were lighter, longer and more ambitious than anything that had come before.

We begin with the Iron Bridge at Coalbrookdale, before looking at how Thomas Telford advanced the use of cast iron at Buildwas. These bridges demonstrated the enormous potential of a new material, but they also revealed an important truth. New materials do not simply replace old ones. Engineers must understand how they behave, where they are vulnerable and how design needs to change around their properties.

That lesson becomes tragically clear in the story of the Tay Bridge. Designed by Thomas Bouch and opened in 1878, the bridge was celebrated as an extraordinary engineering achievement. But on the night of 28 December 1879, during a violent storm, its high girders collapsed as a passenger train crossed the River Tay. Everyone aboard was lost.

The disaster exposed failures in design, assumptions, workmanship, quality control, inspection and oversight. It also raised deeper questions about professional responsibility. Bouch was an experienced and respected engineer, but reputation could not compensate for a structure that had not been adequately designed, manufactured, constructed and assured against the forces it would face.

Public confidence in engineering had been broken. Across the Firth of Forth, the response was a bridge designed to make its strength visible. Benjamin Baker and John Fowler used steel, redundancy, rigorous calculation and an unmistakably robust cantilever form to create a structure capable of restoring trust. The Forth Bridge was not simply another crossing. It was an engineering response to failure.

For modern engineers and construction leaders, the lesson is that public trust cannot be claimed through reputation, confidence or technical language. It must be earned through competence, evidence, transparency and the willingness to challenge decisions before failure makes those questions unavoidable.

Public responsibility begins long before something goes wrong.

Key takeaways:

Understand the material, not merely its potential. Iron allowed engineers to build lighter and longer structures, but its different forms had different strengths, weaknesses and failure behaviours. Adopting a new material requires a corresponding change in design knowledge, testing and assurance.

Question the assumptions beneath the calculation. A design can appear technically complete while still being based on incomplete loads, misunderstood behaviour or optimistic assumptions. Engineers must ask whether the model reflects the conditions the structure will face in service.

Quality cannot be inspected into a finished structure. The Tay Bridge inquiry exposed poor castings, defective connections and inadequate workmanship. Quality must be designed, specified, manufactured, constructed and verified throughout delivery.

Reputation is not assurance. Experience and professional standing should never prevent challenge. Strong engineering organisations create space for assumptions, calculations and decisions to be questioned regardless of who made them.

Pressure does not reduce responsibility. Financial, programme and commercial pressures may explain why poor decisions are made, but they do not remove their consequences. Engineers must recognise when pressure is beginning to compromise safety, evidence or professional judgement.

Design for public confidence as well as technical performance. The Forth Bridge demonstrated its strength through its form, material, redundancy and scale. When trust has been damaged, reassurance must be supported by visible evidence and disciplined engineering.

Learn before disaster forces the lesson. The most important time to challenge a design, material, assumption or process is before failure. Professional responsibility means speaking up while there is still time to change the outcome.

Coming next:

In Episode 9, "The Engineering Beneath Our Feet", we turn from the structures everyone can see to the infrastructure most people rarely think about.

By the middle of the nineteenth century, London had become the largest city in the world.

But beneath the wealth, industry and expansion was a growing public health crisis.

Human waste flowed into streets, cesspits and the River Thames.

Disease spread through crowded communities.

In 1858, an exceptionally hot summer created a stench so severe that Parliament could no longer ignore what became known as the Great Stink.

But years earlier, physician John Snow had already challenged the accepted belief that cholera spread through bad air. His investigation of the Broad Street outbreak showed the importance of evidence, mapping and the courage to question established thinking.

Joseph Bazalgette would then lead one of the most important infrastructure programmes in British history, creating London's system of intercepting sewers and helping transform the health and functioning of the city.

His engineering saved lives on an extraordinary scale, yet much of it remains unseen beneath the streets.

Episode 8 asks what happens when engineering breaks public trust.

Episode 9 explores the engineering that quietly protects the public every day.

From visible strength, we move to invisible infrastructure.

Listen and follow:

Listen to Built to Change the World wherever you get your podcasts:

https://podfollow.com/6790092627

Discover more from the podcast host:

https://linktr.ee/michaelfisher88

Historical accuracy disclaimer:

Built to Change the World is based on historical research and is created with the intention of presenting events, people and engineering achievements as accurately and fairly as possible. Historical sources can differ, and some details may be simplified or interpreted to support the storytelling format.

Any inaccuracies or omissions are unintentional and are not intended to mislead. Corrections, additional context and constructive feedback are warmly welcomed at [email protected]

What does real innovation look like when the new idea does not work?

In this episode, we explore Isambard Kingdom Brunel, one of the most famous engineers in British history, but not through the familiar story of the top hat, cigar and engineering genius.

Instead, we look at the experiments, failures, risks and difficult decisions behind that reputation. We begin with the enormous Great Eastern refusing to launch in front of thousands of spectators, before going back to the Thames Tunnel, where a young Brunel learned about engineering in an environment of water, ground, machinery, workers and very real danger.

Across the episode, we explore Brunel's willingness to challenge conventional thinking through the Great Western Railway, broad gauge, the atmospheric railway and the Great Eastern. We also look at a very different Brunel project, the modular hospital at Renkioi, which shows that innovation does not always mean building something bigger. Sometimes it means radically simplifying how something is designed, manufactured, transported and assembled around the people who need it.

But innovation comes with responsibility. Brunel's career includes extraordinary successes, commercial failures, experiments that did not survive real operating conditions and projects where the human consequences of engineering cannot be separated from the technical story.

For modern engineers and construction leaders, the lesson is not that we should copy Brunel or celebrate failure for its own sake. It is that progress sometimes requires someone to challenge the accepted answer, while still respecting evidence, safety, workers, operators and the public.

Responsible innovation requires both rebellion and restraint.

Key takeaways:

Challenge assumptions, not evidence. Understand why a standard, precedent or accepted solution exists before deciding there might be a better answer.

Create space for different thinking. Organisations cannot say they want innovation while making it professionally dangerous for people to challenge established approaches.

Bound the experiment. Define the hypothesis, success criteria, failure criteria, consequences and stop point before testing a new idea. Good governance should make experimentation safer, not prevent it.

Design for the real operating environment. Brunel's atmospheric railway demonstrated that an elegant technical concept is not enough if it cannot survive maintenance, weather, operations and everyday use.

Innovation does not always mean greater complexity. Brunel's Renkioi Hospital shows how modular design, manufacture, logistics and assembly can be reconfigured around a clear human outcome, an idea that remains highly relevant to modern MMC and DfMA.

Build organisations that do not need a hero. Great technical leadership is not about one exceptional person having every answer. It is about creating teams that can challenge, learn, experiment and continue functioning without depending entirely on one individual.

Coming next:

In Episode 8, "The Bridge That Broke Trust", innovation meets consequence.

During the nineteenth century, iron transformed what engineers believed was possible.

Bridges became lighter, longer and increasingly ambitious.

But adoption sometimes moved faster than understanding, quality and assurance.

On the night of 28 December 1879, a train entered the high girders of the Tay Bridge during a violent storm.

The bridge collapsed.

Everyone aboard was lost.

The disaster damaged public confidence in engineering and forced difficult questions about design, materials, workmanship, inspection and professional responsibility.

But the story does not end at the Tay.

Across the Firth of Forth, engineers would eventually create one of the most recognisable bridges in the world and attempt to rebuild confidence through engineering that made its strength impossible to ignore.

Episode 7 asks when engineers should challenge convention.

Episode 8 asks what responsibility we carry when the public has to trust the things we build.

From innovation, we move to consequence.

Listen and follow:

Listen to Built to Change the World wherever you get your podcasts:

https://podfollow.com/6790092627

Discover more from the podcast host:

https://linktr.ee/michaelfisher88

Historical accuracy disclaimer:

Built to Change the World is based on historical research and is created with the intention of presenting events, people and engineering achievements as accurately and fairly as possible. Historical sources can differ, and some details may be simplified or interpreted to support the storytelling format.

Any inaccuracies or omissions are unintentional and are not intended to mislead. Corrections, additional context and constructive feedback are warmly welcomed at [email protected]

What happens when a successful engineering project stops being a project and becomes part of something much bigger?

In this episode, we follow Britain's railways beyond the success of the Liverpool and Manchester Railway and watch as individual lines begin spreading across the country. New companies, new routes and new stations appear, but with that growth comes a much more complicated engineering challenge.

Building one railway is difficult. Building hundreds of railways that eventually need to connect, interact and operate together is something else entirely. Different companies made decisions about routes, gauges, stations, signalling and operations, often based on what worked best for their own railway. But those individual decisions created consequences far beyond individual project boundaries.

We explore the Railway Mania of the nineteenth century, the battle over railway gauge, the operational problems created when different systems met, and the development of signalling, telecommunications and standardised time. We also look at the modern parallels, including HS2, and ask whether major infrastructure can ever really be understood as a single isolated project.

For modern engineers and construction leaders, this is ultimately an episode about systems thinking. We divide infrastructure into projects, disciplines, contracts, organisations and packages because we need boundaries to manage complexity. But the infrastructure itself does not experience those boundaries.

A passenger experiences one railway. A city experiences one transport system. A river experiences everything entering its catchment. An electricity network experiences the combined demand placed upon it.

The boundaries are ours.

The system does not have them.

Key takeaways:

Systems thinking does not mean understanding everything. It means understanding what your decisions connect to and recognising where consequences extend beyond your immediate scope.

Project boundaries are management tools, not necessarily system boundaries. People, water, power, traffic, data, maintenance and risk continue beyond the red line on a drawing.

Interfaces often determine whether the wider system succeeds. Different teams, organisations, standards and assets may work perfectly independently but still fail when they have to connect.

Optimising one part can make the whole system worse. A technically superior solution can still create additional cost, complexity or operational problems somewhere else.

Engineering decisions can have consequences for decades. We need to ask who will operate, maintain and eventually modify what we create, and how changes in technology, climate and demand might affect those decisions.

The biggest infrastructure challenges cannot be solved one isolated project at a time. Transport, energy, housing, water, digital infrastructure and communities increasingly depend upon one another.

Coming next:

In Episode 7, "Brunel and the Price of Innovation", we meet perhaps the most famous civil engineer of the Industrial Revolution.

But this is not simply the story of the top hat, the cigar and the engineering greatest hits.

Isambard Kingdom Brunel constantly questioned accepted answers.

Sometimes he was right.

Sometimes he was spectacularly wrong.

From the Thames Tunnel and Great Western Railway to the atmospheric railway, the Great Eastern and his remarkable modular hospital at Renkioi, Brunel's career shows both the extraordinary potential and the real cost of pushing engineering beyond what already exists.

Episode 6 is about understanding the system.

Episode 7 asks a more dangerous question.

When should an engineer be brave enough to challenge it?

Listen and follow:

Listen to Built to Change the World wherever you get your podcasts:

https://podfollow.com/6790092627

Discover more from the podcast host:

https://linktr.ee/michaelfisher88

Historical accuracy disclaimer:

Built to Change the World is based on historical research and is created with the intention of presenting events, people and engineering achievements as accurately and fairly as possible. Historical sources can differ, and some details may be simplified or interpreted to support the storytelling format.

Any inaccuracies or omissions are unintentional and are not intended to mislead. Corrections, additional context and constructive feedback are warmly welcomed at [email protected]

What happens when a radical new idea finally has to prove that it works in the real world?

In this episode, we travel to Rainhill in October 1829, where engineers, investors and spectators gathered to watch a series of trials that would help decide the future of the new Liverpool and Manchester Railway.

The Rainhill Trials are often remembered as a race between early steam locomotives, particularly George and Robert Stephenson's famous Rocket. But the real question was much bigger. Could locomotive power move beyond workshops, collieries and experiments and become part of a reliable transport system between two major cities?

To understand why that mattered, we step back from Rocket and explore the extraordinary civil engineering required to create the railway beneath it. We look at George and Robert Stephenson, the failed parliamentary attempt to secure the railway, the challenge of surveying a route suitable for locomotives, and the enormous construction effort required to cross Chat Moss, drive cuttings and tunnels, and build the bridges, viaducts and infrastructure needed to connect Liverpool and Manchester.

Rocket may be the machine history remembers, but the railway was the bigger experiment. The locomotive could only succeed because an entire infrastructure system had been designed around the outcome it needed to achieve.

For modern engineers and construction leaders, that lesson remains highly relevant. Innovation is easy to celebrate when it is presented as a prototype, demonstration or new technology. The real test comes when that idea has to be constructed, operated, maintained and relied upon in conditions that are rarely perfect.

Because reality does not care how innovative an idea sounds.

It has to work.

Key takeaways:

Innovation has to solve a real problem. Liverpool and Manchester did not need a locomotive because steam engines were exciting. They needed a faster, more reliable way of moving goods and people between two rapidly growing economic centres.

The most visible innovation is not always the most important one. Rocket gets much of the attention, but without the alignment, earthworks, tunnels, bridges, track and infrastructure beneath it, the locomotive had nowhere useful to go.

New technology needs the right environment around it. The performance of the locomotive influenced gradients and alignment, which in turn created major civil engineering challenges including Chat Moss, cuttings, tunnels and viaducts.

Uncertainty needs to be treated honestly. Engineers will never know everything before construction begins. The challenge is to observe what reality is telling us, respond intelligently and avoid allowing confidence in a design or model to replace engineering judgement.

Proof needs to represent the real world. Rainhill was not simply looking for the locomotive capable of producing the most impressive moment. The trials tested repeated useful performance, reliability and the ability to keep operating.

Coming next:

In Episode 6, "From Line to Network", the success of the Liverpool and Manchester Railway creates an entirely new engineering challenge.

One railway had proved that the concept could work.

Now everyone wanted one.

New companies appeared. New routes spread across Britain. Different gauges competed. Stations, junctions, signalling systems and timetables began interacting with one another.

The engineering problem was no longer whether one railway could work.

It was whether hundreds of individual projects and decisions could eventually become one functioning network.

Episode 5 is about proving one system in reality.

Episode 6 is about understanding the bigger system around it.

Because a successful project is not automatically a successful network.

Listen and follow:

Listen to Built to Change the World wherever you get your podcasts:

https://podfollow.com/6790092627

Discover more from the podcast host:

https://linktr.ee/michaelfisher88

Historical accuracy disclaimer:

Built to Change the World is based on historical research and is created with the intention of presenting events, people and engineering achievements as accurately and fairly as possible. Historical sources can differ, and some details may be simplified or interpreted to support the storytelling format.

Any inaccuracies or omissions are unintentional and are not intended to mislead. Corrections, additional context and constructive feedback are warmly welcomed at [email protected]

What happens when the problem is not finding resources, but moving them?

In this episode, we leave the exposed rocks of Eddystone and return inland to explore how the Bridgewater Canal helped transform the movement of goods during the Industrial Revolution.

By the middle of the eighteenth century, Manchester was growing rapidly and demand for coal was increasing. Francis Egerton, the Duke of Bridgewater, owned significant coal reserves at Worsley, but getting that coal to market was slow and expensive. The challenge was not the resource itself. It was movement.

Working with John Gilbert and James Brindley, the Duke developed a canal that connected the Worsley mines with Manchester and created a far more efficient way of transporting heavy goods. Along the way, the project produced remarkable engineering, including Barton Aqueduct, where canal boats were carried above the River Irwell, and an underground canal system that connected directly into the mines.

But this episode is about much more than canals.

The Bridgewater Canal shows how infrastructure works as a complete system. Route, water management, structures, mining, logistics, operations and commercial purpose all had to work together. When they did, the result was not simply an impressive piece of engineering. It changed the economics of moving coal, helped reduce transport costs and demonstrated the wider value that infrastructure could unlock.

For modern engineers and construction leaders, the lesson remains highly relevant. Projects are increasingly divided into disciplines, packages and contracts, but the infrastructure itself does not experience those boundaries.

Great engineers understand their technical discipline, but they also understand how their work connects to the wider project, how the asset will be built and operated, and what value the client is ultimately trying to create.

Because infrastructure only works when the whole system works.

Key takeaways:

Infrastructure unlocks trapped value. The Duke of Bridgewater already owned the coal. The engineering challenge was creating an efficient connection between the resource and the market.

Great infrastructure depends on systems thinking. The canal, mines, aqueduct, water management, transport operation and market all had to work together. The visible asset was only one part of the system.

Engineers need to understand the whole project, not only their technical package. Design, construction, operations, maintenance, commercial purpose and interfaces are all connected.

Coming next:

In Episode 5, "The Railway That Changed Time", Britain faces the next transport challenge.

The canals had transformed the movement of heavy goods.

But they were still slow.

At Rainhill in October 1829, engineers gathered to test whether a radically different technology could provide the answer.

Among the competitors was a locomotive called Rocket.

But the story of the railway revolution is much bigger than one machine.

It is the story of George and Robert Stephenson, the extraordinary civil engineering challenge of building the Liverpool and Manchester Railway, and what happens when an ambitious new idea finally has to prove that it works in the real world.

The canals taught Britain to move weight.

The railways would teach Britain to move time.

Listen and follow:

Listen to Built to Change the World wherever you get your podcasts:

https://podfollow.com/6790092627

Discover more from the podcast host:

https://linktr.ee/michaelfisher88

Historical accuracy disclaimer:

Built to Change the World is based on historical research and is created with the intention of presenting events, people and engineering achievements as accurately and fairly as possible. Historical sources can differ, and some details may be simplified or interpreted to support the storytelling format.

Any inaccuracies or omissions are unintentional and are not intended to mislead. Corrections, additional context and constructive feedback are warmly welcomed at [email protected]

How do you design for survival when the sea has already destroyed one lighthouse and fire has consumed another?

Welcome to Episode 3 of Built to Change the World, a 12-part podcast series exploring the engineers, infrastructure and decisions that helped shape modern Britain.

In this episode, we leave Britain's muddy roads and travel out to the Eddystone Rocks, a dangerous reef around 14 miles from Plymouth.

The first Eddystone Lighthouse, built by Henry Winstanley, was destroyed during the Great Storm of 1703. The second, built by John Rudyerd, survived for decades before being destroyed by fire in 1755.

The challenge was no longer simply to replace the lighthouse. It was to understand why the previous structures had failed and build something capable of surviving the sea.

Robert Weston sought advice from George Parker, the Earl of Macclesfield and President of the Royal Society, who recommended a 31-year-old mathematical instrument maker and experimenter named John Smeaton.

Smeaton did not begin with the tower.

He began with the rock.

He studied the reef, waves, materials, tides, access constraints and previous failures. His solution combined an oak-tree-inspired stone form, hydraulic lime, accurately cut granite blocks, dovetailed connections and marble dowels that helped the structure behave as one.

However, the design was only part of the challenge. The stones had to be prepared onshore, transported in the correct sequence and assembled during the limited periods when the tide and weather allowed work to take place.

Smeaton understood that buildability was not something to consider after design. It was part of the design itself.

The Eddystone Lighthouse demonstrates that great engineering rarely depends on one clever idea. It comes from many connected decisions about materials, form, foundations, connections, logistics, sequencing and long-term performance.

The episode also asks what Smeaton's approach means for engineers today.

We now have standards, software, guidance, digital models and technical information that Smeaton could never have imagined. These tools are valuable, but they cannot replace engineering judgement or a deep understanding of the problem.

Learn the standards, but do not hide behind them.

Use the software, but understand what it is doing.

Follow the process, but do not lose sight of the problem.

Because civil engineering is not only about producing a compliant answer.

It is about understanding reality well enough to protect people and build infrastructure that lasts.

Key takeaways:

Engineering begins with the real conditions of the problem. Smeaton started with the rock, the sea, the previous failures and the practical constraints of construction.

Resilient infrastructure is created through connected decisions. Form, materials, foundations, connections, logistics, sequencing and buildability all had to work together.

Standards, software and processes are valuable tools, but they cannot replace engineering judgement, responsibility or a deep understanding of the consequences of failure.

Coming next:

In Episode 4, "The Canal Kings", we return inland and explore how the Bridgewater Canal helped transform the economics of moving coal and other heavy goods.

From stone and open sea, we move to controlled water, industrial ambition and a new transport system.

The same horse.

A different system.

A different future.

Listen and follow:

Listen to Built to Change the World wherever you get your podcasts:

https://podfollow.com/6790092627

Discover more from the podcast host:

https://linktr.ee/michaelfisher88

Historical accuracy Disclaimer:

Built to Change the World is based on historical research and is created with the intention of presenting events, people and engineering achievements as accurately and fairly as possible. Historical sources can differ, and some details may be simplified or interpreted to support the storytelling format.

Any inaccuracies or omissions are unintentional and are not intended to mislead. Corrections, additional context and constructive feedback are warmly welcomed at [email protected]