50-WORD SUMMARY: Executive hubris sank the Vasa before it reached open water. In 1628, Sweden’s king demanded a second gun deck, ignoring the engineering trade-offs. The lesson for modern leaders is clear: unchecked scope creep, silenced warnings, and arbitrary deadlines can make project failure inevitable. Build psychological safety, test assumptions, and respect evidence.
On a sunny afternoon in August 1628, thousands of people gathered around Stockholm harbour to watch the maiden voyage of the Vasa. She was meant to be the jewel of the Swedish Navy: a colossal warship, covered in gilded sculptures and built to project military dominance across the Baltic Sea.
Less than twenty minutes after setting sail, a modest breeze caught her sails. The vessel listed sharply to port, righted herself briefly, then tipped again. Water poured through the open lower gun ports. Within minutes, in full view of the crowd, the Vasa sank barely a mile into her first voyage.
The Vasa remains one of history’s clearest warnings about executive hubris. Hubris encourages leaders to treat technical constraints as objections to overcome, rather than facts to understand. In this case, King Gustav II Adolf demanded a ship beyond the limits of Swedish naval design. His ambition did not create a stronger warship; it created a vessel that could not safely sail.
The Royal Mandate: When Ambition Overrides Engineering
When the Vasa contract was signed in 1625, master shipbuilder Henrik Hybertsson had designed a conventional single-deck warship. Then reports reached the Swedish court that Denmark was building a larger vessel with two gun decks.
The King reacted. Under pressure to outmatch a rival, he intervened directly in the specifications. The Vasa would be lengthened and fitted with an additional gun deck carrying sixty-four heavy bronze cannons.
The decision looked decisive from the palace. On the shipyard floor, it changed everything.
During construction, Hybertsson became ill and died. His assistant, Hein Jacobsson, inherited a design that had expanded far beyond its original proportions. The extra guns made the ship dangerously top-heavy. Shipwrights placed heavy stone ballast in the hull to lower its centre of gravity, but they faced a hard physical limit: add enough ballast to stabilise the ship and the lower gun ports would sit perilously close to the waterline.
The design had become a compromise with no safe answer. Yet stopping the work was not a realistic option in an environment shaped by royal hubris. The King wanted the ship. The fleet needed it quickly. The people closest to the risk had the least room to challenge the decision.
Hubris rarely announces itself as vanity. It arrives as urgency, competitive pressure, strategic ambition, or a leader’s confident belief that the team will “find a way”. Ambition is not the problem. The problem begins when ambition is treated as a substitute for feasibility.
Ignored Signals: The Stability Test at the Quay
Months before launch, Admiral Klas Fleming ordered a simple stability test. Thirty sailors ran back and forth across the Vasa’s deck to simulate the forces of a rolling ship.
After only three runs, the Vasa rocked so violently that Fleming stopped the test. He feared she would capsize while still tied to the quay.
The warning could not have been clearer. The ship had failed before it reached open water.
Yet the project continued. Fleming reportedly said he wished the King had been there to see the test, but he did not halt the launch. Gustav Adolf was abroad fighting in Poland and sending impatient letters demanding that the Vasa join the Baltic fleet.
Why did experienced naval officers and shipbuilders allow a visibly unstable warship to sail?
Because hubris changes the conditions in which other people make decisions. When senior authority signals that a goal is non-negotiable, raising concerns can feel career-limiting, disloyal, or futile. Silence starts to feel safer than candour.
The Vasa did not sink because of an unforeseeable storm. It sank because leadership refused to accept the trade-offs created by its own demands. The ship was put to sea with insufficient stability, and no safe margin for error.
How Executive Hubris Creates Modern Project Failure
The Vasa’s story plays out in modern businesses whenever leaders impose major changes without reassessing capacity, risk, budget, or time.
Executive hubris shows up when a leadership team adds features late in development, shortens a delivery timetable, changes a product’s strategic purpose, or announces a launch date before consulting the people responsible for delivery. The request may sound manageable in isolation. Combined with existing commitments, it can destabilise the whole project.
A platform becomes “just one more integration”. A product launch gains “just a few essential features”. A team is asked to deliver the same scope with fewer people because the deadline has already been announced.
Each instruction may be well-intended. Together, they can make the plan impossible.
The Boeing 737 MAX crisis showcases the consequences of commercial pressure overriding engineering safeguards and open escalation. Competitive urgency does not remove risk; it often makes the need for independent challenge more important.
Top-down hubris blinds leaders to three execution realities:
- The illusion of control: Executive authority cannot bend physical, technological, financial, or human limits.
- The sunk-cost trap: Leaders continue with a flawed initiative because admitting a change of course feels more costly than carrying on.
- Asymmetric risk exposure: Senior leaders may receive the credit for a successful gamble, while project teams carry the operational burden when it fails.
When arbitrary deadline pressure overrides technical verification, failure stops being a distant risk and becomes the most likely outcome.
A Due-Diligence Regimen to Neutralise Hubris Before Launch
To counteract executive hubris, you must institute formal, non-negotiable operational reviews that evaluate projects against empirical metrics before launch. To do that, you require a structured due diligence regimen to separate genuine strategic vision from reckless ambition.
1. The Pre-Mortem Analysis
Before any major commercial initiative receives final sign-off, assemble the project team for a pre-mortem workshop. Direct the team to operate under a specific premise: “It is twelve months from today, and this initiative has failed. What specific operational factors caused the collapse?“ This exercise counteracts organisational hubris by legitimising pessimism and unearthing structural flaws that early optimism conceals.
2. The Operational Stress Test
Just as the Swedish Navy ran sailors across the deck of the Vasa, you must also stress-test your operational limits. Define clear operational boundaries (such as system load capacity, supply chain bandwidth, or team overtime caps) and test them in controlled conditions before full rollout. If the system fails the stress test, executive preference must not be permitted to override the empirical data.
3. The Scope-Budget-Time Triad Audit
Whenever the management requests an expansion in project scope, you must adjust one of two parameters: delivery timeline or allocated budget. Enforce a rule where any scope addition automatically recalculates project timelines, effectively curtailing executive hubris before commitments are finalised.
Build Psychological Safety Before You Need It
Hubris thrives where bad news has a personal cost.
Admiral Fleming saw evidence that the Vasa was unsafe. But the culture around the project made it easier to launch a compromised ship than to challenge royal authority. Modern teams can fall into the same pattern, even without a king at the top.
A psychological safety net ensures that people can raise risks, admit uncertainty, and challenge assumptions without being punished, ridiculed, or sidelined. When teams cannot, problems remain hidden until they become expensive, public, and difficult to reverse.
Nokia’s decline in the smartphone market illustrates this danger. Engineers and middle managers understood that the company’s software capability was falling behind competitors. Yet a culture of pressure and leadership hubris made it difficult to communicate those weaknesses openly. By the time the organisation responded, the market had moved.
To make risk reporting routine, you should build these habits:
- Reward the messenger: Publicly thank people who identify material flaws early, even when their findings disrupt a preferred plan.
- Separate identity from ideas: Assess evidence and assumptions, not the seniority or confidence of the person presenting them.
- Decouple deadlines from vanity: Treat operational readiness, not an executive’s public commitment, as the release gate.
- Ask before telling: Before announcing a decision, ask the delivery team what must be true for it to succeed safely.
- Record unresolved risks: If you choose to proceed despite a warning, document the risk, mitigation, owner, and decision rationale.
The last point matters. It prevents hubris from hiding behind vague optimism. A recorded risk creates accountability and gives teams a legitimate route to escalate when conditions worsen.
The VOICE Risk-Mitigation Framework
To make open challenge part of normal operations, use the VOICE framework. It gives you a repeatable way to turn risk reporting into a management practice rather than a last-minute rescue effort.
V – Validate Technical Realities
Anchor strategic objectives in feasibility evidence. Require written input from technical leads, operations teams, finance, and customer-facing teams before confirming external commitments. This does not weaken leadership; it protects leaders from making promises on incomplete information.
O – Open Anonymous Escalation Channels
Give employees a safe route to raise serious concerns when normal reporting lines are blocked. Anonymous channels should not replace direct conversation, but they are a necessary safeguard where power dynamics or executive hubris make speaking up difficult.
I – Institutionalise Red Teams
Create an independent group whose job is to challenge major assumptions. A red team should test the plan as a sceptical customer, regulator, engineer, competitor, or operator would. Its purpose is not to delay delivery. Its purpose is to find the weak points while they can still be fixed.
C – Clarify Non-Negotiable Launch Gates
Set measurable standards for security, stability, quality, compliance, and operational readiness. If a project fails a gate, the launch pauses automatically. This removes the temptation to negotiate with evidence when a senior leader wants to press ahead.
E – Establish Post-Initiative Accountability
After a launch, review the decisions as well as the results. Focus on what the organisation knew, when it knew it, and how it responded. Avoid scapegoating individual contributors. The aim is to improve the system that allowed the risk to develop.
Steer Away from Hubris
The Vasa shows how quickly bold ambition can become public failure when leaders ignore the constraints of the work. A second gun deck made the ship more impressive on paper, but it also made it incapable of surviving a modest breeze.
The same pattern applies to business. When leaders add scope without changing resources, demand certainty where uncertainty remains, or silence the people closest to the work, they create projects that look impressive until they meet reality.
The alternative to hubris is not timid leadership. It is operational humility: the discipline to test assumptions, hear unwelcome evidence, and change course before a small problem becomes a costly one.
Before approving your next major initiative, ask a simple question: are you strengthening the ship, or merely adding more guns to the deck?
Invite the people doing the work to identify the risks. Test the structure before launch. Make the trade-offs visible. That is how leaders protect both ambition and the organisations asked to deliver it.
If you found this perspective useful, consider subscribing to my blog by sharing your email below. You will receive regular insights on strategy, leadership, and building sustainable systems.
Stay Connected: For short-form thoughts and business storytelling, follow me on X and Facebook for regular updates.
Beyond the Blog: If stories of power, ambition, and passion interest you, explore my books on Amazon. They examine the fine line between success and surrender, and the choices that define both.
Leave a Reply