Jurassic Park
Fictional storyJurassic Park (1993)No clear owner

Jurassic Park: they spared no expense, except on a second programmer

John Hammond built a theme park on a remote island and filled it with living dinosaurs. The park’s fences, doors and cameras all ran through one computer system, built and understood by one programmer, Dennis Nedry. When Nedry switched the security off to steal dinosaur embryos for a rival company, nobody else could get it back on in time. The rest, as the film puts it, is history with teeth.

  • 1Programmer who understood the system
  • 3Outside experts on the test tour
  • 1Storm on the night of the visit
  • 0Days the park was open

Fictional story. Everything on this page happens in the film Jurassic Park (1993). The park is made up; the project management lessons are not.

Jurassic Park 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, one name is on every critical system card, and nobody notices. With Kanbanchi, the work is split, a second person can run the system, and the risks have owners.

Open2
Fix the known system bugsStill being debuggedOwner: ProgrammerCritical priorityOwner: Chief engineer
Open the park to the publicDate setOwner: FounderWaiting on sign-offOwner: Founder
In progress1
Expert safety sign-offVisit during a stormOwner: Investors’ lawyerChecklist before openingOwner: Investors’ lawyer
Done2
Park control systemOne person knows itOwner: ProgrammerDocumented, 2 ownersOwner: Chief engineer
Fence and door securitySame ownerOwner: ProgrammerSubcard, own ownerOwner: Game warden

As it went: the programmer’s initials are on the control system, the security and the bug fixes, and nobody else can step in.With Kanbanchi: the work is spread across people, the bug fixes are Critical, and opening waits on the safety checklist.

A board for a fictional dinosaur park, for fun. We do not think a task board stops a velociraptor. We do think it shows when one person holds the keys to everything.

The plan

In the film, Hammond’s company has cloned dinosaurs from ancient DNA and built a park for them on an island off Costa Rica. After an accident with one of the animals, the park’s investors are nervous, and their lawyer, Donald Gennaro, insists that outside experts visit and endorse the park before it opens.

The visitors are paleontologist Alan Grant, paleobotanist Ellie Sattler and mathematician Ian Malcolm, joined by Gennaro and Hammond’s two grandchildren. The plan is a test run of the park tour, and a sign-off, so the opening can go ahead. Hammond’s favorite phrase during the tour says a lot about the project’s priorities: he “spared no expense.”

What actually happened

One man runs the computers

The park is run from a control room. The tour vehicles, the electric fences, the door locks and the security cameras all depend on the computer system Nedry built. The film shows the system still being debugged during the visit, and Nedry as the only one who really knows how it works.

Nedry is also unhappy. He complains to Hammond about money, and Hammond waves him off. Meanwhile, Nedry has made a deal with Lewis Dodgson of a rival company: steal frozen embryos and smuggle them off the island.

The night of the storm

A tropical storm is coming in, and most of the staff leave the island on the boat to the mainland. The test tour goes ahead anyway. Nedry picks his moment: he runs a program that shuts down security systems across the park so he can get to the embryo storage, and the fences go dead along with the cameras and door locks.

Nedry gets lost in the storm on the way to the dock and never comes back. The program he left behind is locked, and when the chief engineer, Ray Arnold, tries to get in, the screen answers with Nedry’s taunt, “Ah ah ah, you didn’t say the magic word.”

Turning it off and on again

With nobody able to undo what Nedry did, Arnold decides to shut the whole system down and restart it. The restart works only partly: the main power has to be switched back on by hand in the maintenance shed. The fences that held the most dangerous animals are among the things that went down.

In the end, the person who gets the door locks back on is not an engineer. It is Hammond’s granddaughter Lex, who sits down at a terminal and recognizes the system.

No park

By the end of the film, the experts are not signing anything. They leave the island by helicopter with Hammond and the children, and the park never opens.

What went wrong, in project management terms

A single point of failure with a name

Every critical system depended on one person’s knowledge and access. When that person left, accidentally or on purpose, the project could not run. Nobody in the film seems to have asked what happens if Nedry is not there.

Known problems, parked

The system is still being debugged while the experts are already on the island. A list of known problems that belongs to one overloaded, unhappy person is a list that will not get shorter.

A disgruntled key person, ignored

Nedry tells Hammond he is unhappy, and Hammond dismisses him. That is not just a people problem. When the one person who controls the system is unhappy and nobody acts on it, that is a project risk.

The test happened at the worst time

The test tour runs while a storm comes in and most of the staff have left. A sign-off visit is exactly the moment to have the full team, the full checklist and the fallback plans in place.

What Kanbanchi would have changed

No task board stops a dinosaur. But every failure above is about who holds the work, who can step in and what has to be done before opening day, and a shared board makes those things visible. These are the Kanbanchi features we would have put on the park’s board.

Team Workload viewProfessional

Team Workload view shows how much work sits on each person. When one name is on every critical system card, it is your cue to spread the load before that person becomes the whole project.

See plans

SubcardsPremium

Split “Park control system” into subcards for fences, doors, cameras and tour vehicles, each with its own assignee. Knowledge spreads when the work does.

How to create a subcard

Card priority

Mark “Fix the known system bugs” Critical, so it stays at the top of the list before anyone books a sign-off visit.

How to set card priority

Checklists

Give the sign-off card a checklist: “Full staff on site,” “Weather checked,” “Second person can restart the system.” The visit waits until every item is ticked.

How to create a checklist

Mentions in comments

Keep decisions and system notes in card comments and @mention the people who need them, so how things work is written down, not only in one programmer’s head.

How to mention a colleague

Try it: Jurassic Park 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: Team Workload view, Subcards, Card priority, 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.

Island park opening
20

To Do

1
  • Risk

    Fix the known system bugs

    DN

In progress

4
  • Development

    Park control system

    2/4
    DN
  • Development

    Fences

    Park control system
    DN
  • Development

    Tour vehicles

    Park control system
    DN
  • Operations

    Sign-off visit

    0/3
    GW

Done

2
  • Development

    Doors

    Park control system
    DN
  • Development

    Cameras

    Park control system
    DN

What just happened

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

Try this

  • Open Team Workload: one name sits on almost every system card.
  • Open a subcard such as “Doors” and give it to someone else.
  • Mark “Fix the known system bugs” Critical before the sign-off visit.

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, Nedry sabotages the park on purpose. No tool stops a determined insider. What a board does is make the dependency on one person visible early, so the team can spread the knowledge and access before it is too late.

Find your single point of failure

Try Kanbanchi free and see whose name is on every critical card.

Start your free trial

Lessons for project managers

  1. Look for the name on every card. If one person owns every critical system, you do not have a team, you have a hostage situation.
  2. Always have a second person who can run it. Knowledge that exists in one head disappears with that person.
  3. Fix known problems before the big test. A sign-off visit is not the time to still be debugging.
  4. Treat an unhappy key person as a risk. It is a project issue, not just an HR one, when the person with all the access is unhappy.
  5. Run your tests in good conditions. Full staff, good weather and fallbacks ready. Otherwise you are not testing the park, you are testing your luck.

Jurassic Park: the in-universe facts

DetailWhat the film showsWhere
FounderJohn Hammond, who “spared no expense”Jurassic Park (1993)
Who ran the computer systemOne programmer, Dennis NedryJurassic Park (1993)
Why Nedry shut security downTo steal dinosaur embryos for a rival companyJurassic Park (1993)
Reason for the expert visitInvestors wanted outside experts to endorse the parkJurassic Park (1993)
Weather that nightA tropical storm; most staff leave on the boatJurassic Park (1993)
How the system came backA full shutdown and restart, with power switched on by handJurassic Park (1993)
Who restored the door locksHammond’s granddaughter, LexJurassic Park (1993)
Opening dayNever happenedJurassic Park (1993)

Jurassic Park: frequently asked questions

Why did Jurassic Park fail as a project?

In the film, the park’s whole computer system depended on one programmer, Dennis Nedry. He shut down security to steal embryos, and nobody else could restore it in time. The test visit also took place during a storm, with most of the staff gone.

What is the single point of failure in Jurassic Park?

Dennis Nedry. He built the park’s computer system, and the film shows that nobody else fully understood it. When he locked others out, the chief engineer had to shut everything down and restart it.

What is the project management lesson from Jurassic Park?

Do not let critical work depend on one person. Spread knowledge and access, fix known problems before a big test, and treat an unhappy key person as a project risk.

Is this page about a real project?

No. Jurassic Park is a 1993 film, based on Michael Crichton’s novel. We use it as a light-hearted case study; the real project failures in this series, like the Vasa warship and Knight Capital, have their own pages with sources.

How would Kanbanchi have helped?

Kanbanchi would have shown in Team Workload view that one person held every critical card, split the control system into subcards with different owners, marked the bug fixes Critical and put a pre-visit checklist on the sign-off card.

Where this story comes from

  1. Jurassic Park, film, directed by Steven Spielberg, Universal Pictures, 1993

This is a fictional story, so there are no outside sources to check; the details come from the film above. Jurassic Park is a trademark of its owners. This page is not affiliated with or endorsed by Universal Pictures or Amblin Entertainment.

Never let one person hold the keys

Kanbanchi is a task board for Google Workspace and Microsoft 365. Spread the work, and the knowledge, across your team.

Start your free trial

Back to all 12 famous project failures