The Vasa warship
Real storySweden, 1628No clear owner

The Vasa warship: the 1628 project that sank on its first day out

On August 10, 1628, Sweden’s newest warship set off on its maiden voyage in front of thousands of people in Stockholm. About 1,300 meters later, a gust of wind pushed it over, water poured in through its open gunports, and within minutes Vasa was on the bottom of the harbor.1 The ship was sunk by its own design, a test that was stopped halfway, and a deadline set by a king.12

  • 1,300 mHow far Vasa sailed
  • 64Cannons on board
  • ~20 minTime under sail before it began to sink
  • 333 yearsOn the sea bed before it was raised

The Vasa project on a board: as it went, and with Kanbanchi

Switch between the two states to see the same five pieces of work. As it went, the design changed hands without a record, the stability test was stopped and never closed, and the voyage went ahead anyway. With Kanbanchi, the test is a Critical card that the voyage depends on.

Open2
Stability testStopped, never closedNo ownerCritical priorityOwner: Captain
Close the gunports before sailingNo ownerNo ownerChecklist itemOwner: Captain
In progress1
Design the hullOwner changed, no notesOwner: Assistant shipwrightHandover in commentsOwner: Assistant shipwright
Done2
Fit 64 cannonsDoneOwner: Navy yardDoneOwner: Navy yard
Maiden voyageSailed anywayOwner: Vice admiralWaiting on stability testOwner: Vice admiral

As it went: the design changed hands, the stability test was stopped and left open, and the voyage was marked done anyway.With Kanbanchi: the stability test is Critical and in progress, and the maiden voyage waits in Open until it passes.

A board for a 17th-century ship, for illustration. Nobody in 1628 had a task board. The point is what the same decisions look like when everyone can see them.

The plan

In January 1625, King Gustav II Adolf of Sweden signed a contract with the Dutch master shipwright Henrik Hybertsson and his business partner Arendt de Groote to build four new ships. One of them, Vasa, was meant to be the most powerful warship in the Baltic, if not the world.1

The keel was laid in the late winter of 1626 at the navy yard in Stockholm. The ship was launched in the spring of 1627, and hundreds of craftsmen worked through the summer on the hull and rigging. Finished, it was 69 meters long and more than 50 meters tall from the keel to the top of the main mast, with ten sails, 64 cannons, 120 tonnes of ballast and hundreds of sculptures.1

Vasa would join the reserve squadron as its flagship, at a time when Sweden was at war with Poland-Lithuania.2 The king owned the navy, and he owned this ship.3

What actually happened

The designer leaves the project

Master Henrik Hybertsson was already ill when construction started. By the summer of 1626, he could no longer supervise the other shipwrights and had to hand responsibility for the new ship to his assistant, Hein Jakobsson. Barely a year later, Vasa’s designer was dead.1

Hybertsson was an experienced, well-respected shipwright who had built a number of successful warships for the Swedish Crown, but Vasa was something new for him in size and armament. There was no way to calculate a ship’s stability in advance: the mathematics we now use was more than a century in the future, so shipwrights designed from experience.2

The test that was stopped

In the summer of 1628, Captain Söfring Hansson, who was supervising the construction, was worried. He called Vice Admiral Klas Fleming down to the ship and had thirty men run back and forth across the deck. The ship rolled so badly that the admiral stopped the demonstration, afraid Vasa would sink at the quay.1

Under pressure from the king to get the ship to sea, the admiral ordered the captain to sail anyway.1 The Vasa Museum notes that the instability was suspected by some before the ship sailed.2

The maiden voyage

After many delays, frustrations with the supply of guns and a change of captain, Vasa was finally ready on Sunday, August 10, 1628. The crew had been allowed to bring their families for the first leg of the voyage.2 The ship cast off between four and five in the afternoon, was pulled along the waterfront with anchors, set four of its ten sails and fired a salute.2

A small gust made the ship heel to port, and it slowly recovered. Then a stronger gust pushed it so far over that water poured in through the open gunports on the lower gun deck.2 Vasa had sailed for only about 20 minutes.3 Within minutes it was on the sea bed, 32 meters down, still within sight of the shipyard where it was built, watched by thousands of Stockholm’s inhabitants and several foreign ambassadors.1 All but 30 of the people on board survived.2

The inquest

The Royal Council wrote to tell the king, and an inquest followed. The ship’s officers claimed innocence. The builders said they had built the ship to the design the king approved. The experts said the ship had too little hull to carry its heavy upper works. The blame fell on the designer, who had been dead for more than a year and could not defend himself.1

What happened to the ship

In 1663 to 1665, divers using a diving bell brought up almost all of Vasa’s cannons.1 The hull stayed in the mud until 1961, when it was raised after 333 years under water. It is now in the Vasa Museum in Stockholm.

What went wrong, in project management terms

Nobody owned the whole design

The person who understood the design best left the project early, and the work passed to his assistant. Nothing in the record shows how the design knowledge, or the doubts about it, moved with the hand-over.1 At the inquest, every group pointed somewhere else: the officers, the builders and the experts each had a story, and the only person left to blame was the one who could not answer.1

A failed test with no consequence

The stability test did its job. It showed, in front of the admiral, that the ship was dangerously unstable.1 But the test was stopped, not failed, and nothing linked its result to the decision to sail. A test that can be halted with no follow-up is not a gate. It is a demonstration.

The deadline won

The king wanted the ship at sea, and the admiral ordered it to sail anyway.1 Projects meet fixed dates all the time. The failure here is that the trade-off between the date and the known risk was made by one person, under pressure, with no record that anyone else could see or challenge.

The simple safeguard was not on the list

The Vasa Museum calls the decision to leave the gunports open a fateful one: if they had been closed, water could not have poured in, and the ship might have survived long enough to be rebuilt into a more stable shape.2 That is a checklist item nobody owned.

What Kanbanchi would have changed

No task board would have done the stability math for a 17th-century shipwright. But every failure above is about ownership, gates and visibility, and those are things a shared board handles well. These are the Kanbanchi features we would have put on the Vasa board.

Assignees

Give “Design the hull” one named owner. When the assignee changes from master to assistant, the card, its comments and its open questions move with it, instead of living in one sick man’s head.

How to assign a card

Card priority

Mark “Stability test” Critical. A Critical card that was stopped halfway stays at the top of the list, visible to the captain, the admiral and the yard.

How to set card priority

Task dependenciesProfessional

On the Gantt chart, make “Maiden voyage” depend on “Stability test passed.” If the test is not done, the timeline shows the voyage cannot start yet.

How to set dependencies

Checklists

Add a pre-sailing checklist to the voyage card, with “Lower gunports closed” on it and a name next to it. Simple, cheap and exactly the item that was missing.

How to create a checklist

Mentions in comments

When the captain sees the ship roll, he @mentions the admiral in the test card’s comments. The warning and the decision to sail anyway are on record, not just remembered at an inquest.

How to mention a colleague

Try it: The Vasa warship on a Kanbanchi board

Drag cards between lists with a mouse or a finger (press and hold on touch screens), or focus a card and use the arrow keys. Open a card to try the features from this article: Assignees, Card priority, Task dependencies, Checklists, @mentions in comments.

Interactive demo

Press Enter to open the card, Left or Right arrow to move it to the next list, Up or Down to go through the list, Shift F10 for the move menu.

Vasa, Stockholm navy yard
10

To Do

2
  • Operations

    Close the lower gunports before sailing

  • Operations

    Maiden voyage

    1/3
    Waits on: Stability testKF

In progress

1
  • Design

    Design the hull

    HH

Checks

1
  • Testing

    Stability test

Done

1
  • Operations

    Fit 64 cannons

    KF

What just happened

Nothing yet. Move a card or open one, and this box explains what Kanbanchi would show.

Try this

  • Drag “Maiden voyage” to Done while the stability test is still in Checks, and watch its dependency chip.
  • Open “Stability test”, set it to Critical and post the captain’s comment.
  • Open Gantt: the voyage starts before the test ends. Shift it to fix the dependency.

A simplified copy of the Kanbanchi board for this story. Cards, names and dates are illustrations, not a historical record. Nothing is saved: reload the page and the board starts over.

Honest caveat: the order to sail came from the top, under pressure from the king. No tool overrules a king. What a board does is make the failed test, the owner and the decision visible to everyone involved, so a risky call is made in the open, not on a quay.

Make your tests gate your launches

Try Kanbanchi free and link every launch card to the checks it depends on.

Start your free trial

Lessons for project managers

  1. Hand-overs need a record. When the designer left, the work moved to his assistant. Put the design, its doubts and its decisions on a card that moves with the owner.1
  2. A stopped test is a failed test. If a test is halted because it looks dangerous, treat it as failed until someone proves otherwise, and say so on the board.
  3. Link the launch to the check. Make the go-live card depend on the test card, so the date cannot quietly win over the result.
  4. Write down who decided. The order to sail anyway was made under pressure.1 A decision with a name and a reason on it is easier to question in time.
  5. Put the simple safeguards on a checklist. Closing the gunports might have saved the ship.2 The cheapest fix is the one most likely to be forgotten.

The Vasa: the numbers

DetailFigureSource
Contract signedJanuary 1625, for four ships1
Keel laidLate winter 16261
Length69 meters1
Height, keel to main mast topMore than 50 meters1
Cannons641
Men in the stability test301
Distance sailedAbout 1,300 meters1
Time under sailAbout 20 minutes3
Depth of the wreck32 meters12
People who died302
Years on the sea bed333 (raised in 1961)1

The Vasa: frequently asked questions

Why did the Vasa sink?

Vasa was top-heavy: its upper works were too tall and heavy for the small part of the hull below the waterline, so the center of gravity was too high. On its maiden voyage, a gust pushed it over, water poured in through the open lower gunports, and it sank within minutes.

Did anyone know Vasa was unstable before it sailed?

Yes. In the summer of 1628, the captain ran a test with thirty men running across the deck. The ship rolled so badly that the vice admiral stopped the test. Under pressure from the king to get the ship to sea, he ordered it to sail anyway.

Who was blamed for the Vasa disaster?

At the inquest, the officers claimed innocence, the builders said they built the design the king approved, and the experts said the hull was too small for the upper works. The blame fell on the designer, Henrik Hybertsson, who had died more than a year earlier.

What is the project management lesson from the Vasa?

Give critical work one named owner, keep a record when it changes hands, and make the launch depend on the test that proves it is safe. A test that can be stopped with no consequence is not a gate.

How would Kanbanchi have helped?

Kanbanchi would have put the hull design on a card with a named assignee and a record of the hand-over, marked the stability test Critical, linked the maiden voyage to the test with a Gantt chart dependency and added “Lower gunports closed” to a pre-sailing checklist.

Sources

  1. Vasa Museum: Timeline, Vasa Museum (Swedish National Maritime and Transport Museums). Accessed November 2, 2026.
  2. Vasa Museum: The Disaster, Vasa Museum, updated July 2, 2021. Accessed November 2, 2026.
  3. Vasa Museum: Facts about Vasa, Vasa Museum, updated March 12, 2026. Accessed November 2, 2026.

All facts come from the Vasa Museum in Stockholm, which holds the ship. The museum notes that the ship’s exact weight is still unknown, so we have not used a weight figure. We have not added a cost figure, because the sources above do not give one.

Launch only when the checks are done

Kanbanchi is a task board for Google Workspace and Microsoft 365. Give every test an owner and every launch a gate.

Start your free trial

Back to all 12 famous project failures