#125 - 130 people, one pressure hull!
1 Oct 26
In 1991 I surfaced through the arctic ice pack at the North Pole in a Royal Navy submarine alongside USS Pargo. At the time I was too focused on qualifying as a Submariner to fully register what we were actually doing. Looking back, it stands out as one of the clearest illustrations of engineering assurance I've ever lived through.
Trial Brief
Trust in engineering is usually invisible, right up until the moment it can't be. Under the arctic ice, with no surface to escape to and no one able to reach you if something failed, that trust stops being an abstraction and becomes the only thing standing between a crew and disaster. Understanding what actually makes that trust justified is one of the clearest lessons engineering assurance has to offer.
Trial Execution
That first submarine trip was my submarine qualification voyage. Trainee submariners are, bluntly, considered passengers or oxygen thieves until they complete the full assessment required to earn the coveted dolphins badge. This is the Service's equivalent of the Royal Marines' green beret. It's a gruelling process that can take up to nine months, and it ends only with the Captain's personal recognition, based on their own and the crew's judgement of your professional capability. At the time, qualifying was all I was thinking about. I didn't fully appreciate how perilous the undertaking itself was.
Before we sailed, the submarine went through an intensive equipment fit in port: specialist sonars, communications, processing equipment and covert capabilities. All designed to let us navigate safely under the ice, surface through it, then dive and transit back to clear water once the icebergs and inverted underwater ice mountains were behind us. New equipment alone wasn't enough. We also needed new Emergency Operating Procedures built specifically around the additional hazards of that environment, because the way we'd normally respond to an emergency elsewhere in the world simply didn't apply under the ice.
What strikes me now, decades later, is how little any of us thought about that at the time. We just did our jobs. An emergency under the ice pack such as a fire, flood or collision leaves almost no room to manoeuvre and vanishingly few options to resolve it. The pressure hull was the only thing between us and the sea, and nobody was coming to help if it failed. All 130 of us on board placed our trust, without really dwelling on it, in the submarine as designed, as built, as maintained and as operated. And it delivered every one of us home.
Trial Findings
That trust wasn't earned in the moment. It was earned long before we ever went near the ice, by people most of the crew had never met and never thought about while it mattered most. Engineering assurance isn't a single decision or a single inspection. It's an unbroken chain: the shipyard that built the pressure hull to spec, the design engineers who specified the ice-capable fit, the shore support organisations who maintained every system to standard, the training organisations who built the procedures and drilled the crew until response was instinctive. Break any single link in that chain, quietly, and the crew going under the ice would have no way of knowing until it was too late to matter.
This is what makes engineering assurance different from ordinary quality control. Quality control checks whether a component meets a specification. Assurance is the confidence that the entire system as designed, built, maintained and operated, consistently, by people who will never personally witness the moment their work is tested, will hold under conditions where failure has no recovery option. The crew under the ice weren't experts in submarine assurance. They didn't need to be. Their job was to trust a system that had already done the hard thinking on their behalf, long before departure from our home port.
That's a heavy responsibility to sit with as an Engineer, and it's easy to lose sight of once a project is routine, and the stakes feel administrative rather than human. The North Pole transit is a useful reminder of what the work is actually for: not passing an audit, not meeting a spec on paper, but people trusting their lives to work they will never personally verify, done by people they will mostly never meet.
The Common Thread
Engineering assurance is invisible until it's tested, and by the time it's tested, it's too late to build. The 130 people who surfaced at the North Pole in 1991 were trusting a chain of engineering decisions made months and years earlier, by people scattered across shipyards, shore support and training organisations who each did their part without ever seeing the moment it mattered. That's the standard the work is actually held to.
Trial Sign-off
One practical action
Think about a system or piece of work your team is currently responsible for where the people relying on it will never personally verify your work. Ask whether your current assurance process would genuinely hold up if the stakes were as unforgiving as an emergency with nowhere to surface.
One question for reflection
Where in your own organisation is trust in engineering currently invisible and untested. What would it take for you to be confident it would hold if it ever genuinely had to?
Have a great week!
Steve
Find out where your next Engineering leadership development stage is here.
For short courses which target specific leadership issues, see this link.
Responses