The Death Star: a moon-sized project with a very known problem
The Empire spent years building a battle station the size of a small moon. Its lead scientist hid a weakness in it on purpose, the plans leaked, an officer warned that the rebel attack was a real danger, and the man in charge said no to evacuating. One well-aimed shot later, the project was over. Then the Empire built another one.
- 2 mWidth of the target, per the rebel briefing
- 1Shot it took
- 2Death Stars built
- 0Design reviews we see on screen
Fictional story. Everything on this page happens in the Star Wars films. The battle station is made up; the project management lessons are not.
The Death Star 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 weapon ships and every risk around it sits in Open with nobody’s name on it. With Kanbanchi, the risks have owners and a priority, and the evacuation decision is a card someone has to close.
As it went: the superlaser ships, the danger is reported, and the risk, the security review and the decision sit in Open with no owner.With Kanbanchi: every risk has an owner and a priority, and the evacuation decision is a Critical card in progress, not a remark.
A board for a fictional battle station, for fun. We do not think a task board would have stopped a rebel X-wing. We do think it would have made the risk hard to ignore.
The plan
In Rogue One, the Death Star is the Empire’s biggest project: a mobile battle station with a planet-killing superlaser. Director Orson Krennic runs construction, and the Empire forces the scientist Galen Erso to lead the work on the weapon.
The goal was simple, as these things go: finish the station, prove the weapon works, and use it to end the rebellion through fear. Leadership measured success by one thing, the weapon firing. Everything else, including what could go wrong, was somebody else’s problem.
What actually happened
A weakness built in on purpose
Galen Erso does not want the station to work. In Rogue One, he hides a flaw deep in the design, a way for a single hit to set off the reactor, and sends word of it to the rebellion through a defecting pilot. The flaw is not an accident. It is in the plans, which means it was always findable.
The plans leak
The complete plans sit in an Imperial data archive on the planet Scarif. A rebel team breaks in, finds them and transmits them to the rebel fleet at the end of Rogue One, and in the opening scenes of A New Hope, Princess Leia hides them in the droid R2-D2. Earlier, when Krennic learns that a message about the station has leaked from his engineering team, his answer is to hunt for the traitor, not to ask what the message might reveal about the design.
The rebels do the design review
In A New Hope, the rebels study the plans and find what the Empire never addressed: a small thermal exhaust port. In the pre-battle briefing, the target area is described as only two meters wide, with a shaft leading directly to the reactor system. A precise hit would start a chain reaction.
The warning, and the reply
As the attack goes on, an Imperial officer tells Grand Moff Tarkin that they have analyzed the attack and there is a danger, and asks whether he should have Tarkin’s ship standing by. Tarkin’s answer is one of the most famous lines in project history, fictional or not: “Evacuate? In our moment of triumph? I think you overestimate their chances.” A few minutes later, a single shot goes down the exhaust port, and the station is destroyed.
Then they built another one
In Return of the Jedi, the Empire builds a second Death Star. It is not finished when the rebels attack, its protection depends on a shield generator on the forest moon of Endor, and it is destroyed too. Same pattern, bigger budget.
What went wrong, in project management terms
A known risk with no owner
The weakness was in the plans. Any review of those plans could have found it, as the rebels did once they had them. On the Imperial side, nobody we see on screen is responsible for the question “what can break this station?” A risk with no owner is a risk nobody is managing.
Success measured by the wrong thing
The project was judged by whether the superlaser fired. It fired. That metric said nothing about whether the station could survive an attack by a few small fighters, which turned out to be the only question that mattered.
Information security as an afterthought
The complete technical plans of the Empire’s most important asset were stored in one archive, and the response to a leak from the engineering team was to chase the leaker. A project that assumes its documents will leak reviews them for weaknesses. A project that assumes they will not, does not.
A warning that reached a person, and stopped there
Here is the painful part. The warning did reach the commander. It was specific (“there is a danger”), it came with a proposed action (have the ship standing by), and it was dismissed on confidence alone. A warning that one person can wave away with no record and no second opinion is not really a process.
No lessons carried forward
The second Death Star had a different weak spot, but the same story: a huge project, a single dependency that could bring it down, and leaders certain it could not happen to them. Nothing suggests the Empire ever wrote down what went wrong the first time.
What Kanbanchi would have changed
We are not claiming a task board defeats the Rebel Alliance. But every failure above is the kind of thing a shared board makes visible: a risk with no name on it, a review nobody scheduled, a decision left as a remark. These are the Kanbanchi features we would have put on the station’s board.
Assignees
Give “Risk: exhaust port leads to the reactor” a named owner. An unassigned card on a shared board is easy to spot, even from the bridge.
How to assign a cardCard priority
Mark the reactor risk Critical. Critical cards stay at the top of the list until somebody closes them, which is hard to argue with in a meeting.
How to set card priorityChecklists
Add a design review checklist to the weapon card: “Every path to the reactor reviewed,” “Plans archive access checked.” The card should not reach Done with items open.
How to create a checklistTask dependenciesProfessional
On the Gantt chart, make “Declare the station operational” depend on the risk review. If the review slips, the dependency shows it.
How to set dependenciesMentions in comments
When the officer finds a danger, he @mentions the commander in the card’s comments. The warning, and the reply, stay on record for everyone on the board.
How to mention a colleagueCard templatesPremium
Turn the first station’s checklists into a card template, so Death Star number two starts with the lessons of number one.
How to use card templatesTry it: The Death Star 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, Checklists, Task dependencies, @mentions in comments, Card templates.
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.
To Do
3- Risk
Risk: exhaust port leads to the reactor
- Testing
Risk review
- Operations
Declare the station operational
Waits on: Risk reviewGT
In progress
0Done
1- Development
Main weapon
0/2EN
What just happened
Nothing yet. Move a card or open one, and this box explains what Kanbanchi would show.
Try this
- Give the exhaust port risk an owner and mark it Critical.
- Drag “Declare the station operational” to Done while the review is open.
- Use + and the template so station number two starts with the checks.
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: in the film, the commander is warned and chooses not to act. No tool forces a leader to listen. What a board does is make the warning, the owner and the decision visible to more than one person, which makes ignoring them a lot more awkward.
Lessons for project managers
- Every risk needs a name next to it. The weakness was in the plans. The problem was that nobody owned looking for it.
- Measure more than the headline feature. A weapon that fires is not the same as a station that survives. Track the things that could end the project, not just the thing that makes the demo.
- Review your own plans before someone else does. Assume your documents will be read by people who want the project to fail, and look for the weak spot first.
- Write down warnings and decisions. A warning that one person can dismiss with a one-liner is a warning nobody else ever hears about. Put it in a card’s comments.
- Carry lessons into the next project. If version two repeats the pattern of version one, nobody wrote down what went wrong. Templates and checklists are how lessons survive.
The Death Star: the in-universe facts
| Detail | What the films show | Where |
|---|---|---|
| Project lead | Director Orson Krennic runs construction | Rogue One (2016) |
| Lead scientist | Galen Erso, forced to work on the weapon | Rogue One (2016) |
| The weakness | Hidden in the design on purpose; one hit can set off the reactor | Rogue One (2016) |
| Where the plans were kept | An Imperial data archive on Scarif | Rogue One (2016) |
| The target | A thermal exhaust port, described as only two meters wide | Star Wars: A New Hope (1977) |
| The warning | “There is a danger”, with an offer to ready the commander’s ship | Star Wars: A New Hope (1977) |
| The reply | “Evacuate? In our moment of triumph?” | Star Wars: A New Hope (1977) |
| Sequel project | A second Death Star, destroyed before it is finished | Return of the Jedi (1983) |
The Death Star: frequently asked questions
Why did the Death Star fail as a project?
In the films, its lead scientist hid a weakness in the design, the plans leaked, and nobody on the Imperial side owned the risk. When an officer warned that the rebel attack was a danger, the commander refused to evacuate. A single shot into a small thermal exhaust port destroyed the station.
Was the Death Star weakness a design mistake?
No. In Rogue One, the scientist Galen Erso builds the weakness in on purpose and tells the rebellion about it. From a project management point of view, that makes it worse: the flaw was in the plans the whole time, and a proper design review could have found it.
What is the project management lesson from the Death Star?
Give every risk a named owner, measure more than the headline feature, and record warnings and decisions where other people can see them. A warning that one person can dismiss with no record is not a process.
Is this page about a real project?
No. The Death Star is fictional and appears in the Star Wars films. We use it as a light-hearted case study; the real project failures in this series, like the Mars Climate Orbiter and Knight Capital, have their own pages with sources.
How would Kanbanchi have helped?
Kanbanchi would have put the reactor risk on a card with an assignee and Critical priority, a design review checklist on the weapon card, a Gantt chart dependency between the risk review and launch, and the officer’s warning in the card’s comments with an @mention.
Where this story comes from
- Star Wars (later titled Star Wars: Episode IV – A New Hope), film, Lucasfilm, 1977
- Rogue One: A Star Wars Story, film, Lucasfilm, 2016
- Star Wars: Episode VI – Return of the Jedi, film, Lucasfilm, 1983
This is a fictional story, so there are no outside sources to check; the details come from the films above. Star Wars is a trademark of Lucasfilm Ltd. This page is not affiliated with or endorsed by Lucasfilm.
Run a project the Empire would envy
Kanbanchi is a task board for Google Workspace and Microsoft 365. Put an owner on every risk, starting today.
Start your free trial