The Godfather as a project

Long gameBook by Mario Puzo, 1969 New York, 1945 to 1955

The Godfather as a project: Kanban board and Gantt chart

Vito Corleone heads a family business in New York after the war. He is shot, his eldest son Sonny is killed, and the business passes to Michael, the son who had wanted no part of it.

  • A family businessteam
  • About ten yearsduration (approximate)
  • Delivered at a costoutcome
  • 4handoffs, our count
  • 4re-plans, our count

Start your free trial7 days, every feature, on your Google or Microsoft account.

The Godfather as a Kanban board

The board is frozen at one moment, while Michael is in Sicily. 2 cards wait in To do, 2 are in progress, 1 is blocked and 2 are done. The card on the critical path is "Prepare the handover", owned by Vito. Blocked: "Bring Michael home", which the team cannot move on its own.

To do

  • Move the business west
  • Settle the open disputes

In progress

  • Prepare the handover
  • Hold the business together

Blocked

  • Bring Michael home

Done

  • Recover from the shooting
  • Make peace with the other families

Purple label: on the critical path. Letter: the card owner, and a question mark means nobody owns it. Blocked: stopped by something outside the team.

Run your own project on a board like this

Lists, owners, due dates and subcards, inside the Google Drive or Microsoft account your team already uses.

Start your free trial

The Godfather: the timeline as a Gantt chart

The same work on a timeline: 6 cards, 4 dependencies and the today line at 1948. 4 cards are milestones, drawn as diamonds. No arrow is red: every card waits for the one before it, as planned.

Dates are approximate: the book does not give a full timeline, so the chart uses relative steps.

Cards on the timeline
CardStartDue
The wedding1945Milestone
Vito is shot1945Milestone
Michael in Sicily19461948
Peace with the families1947Milestone
Prepare the handover19481954
Michael takes over1955Milestone

What happened, in project terms

The head of the family was shot, his eldest son was killed, and the business passed to the son who had wanted nothing to do with it. Michael spent years in patient preparation, kept his plans from almost everyone and settled every open matter on a single day. The lesson for ordinary organisations is gentler: name the successor and the handover plan before you need them.

By our count the quest has 4 handoffs, moments where work changes hands, and 4 re-plans: more re-plans than most books on this page.

Lessons for project managers

  1. Succession is a project, so plan it before the founder steps back

    In Kanbanchi, split a long plan into phases on the Gantt chart and add a milestone card for every review point. Long projects drift between milestones, so put the milestones where you will actually look.

  2. Name the successor before you need one

    Succession is a project, so plan it before the founder steps back. A sudden handover is the most dangerous kind.

  3. Keep the plan close, but not too close

    Michael told almost no one. That kept him safe, but it left his own team guessing. Decide who needs to know what.

Draw the dependencies before they bite

The Gantt chart uses the same cards your team already moves on the board.

Start your free trial

What went wrong: the risk register

Most of what went wrong was visible early. Here are three risks a project manager could have written down at the start. Switch between the plan and what actually happened.

  • The successor is not prepared

    Likelihood: highImpact: severe

    Mitigation: Name the successor and the handover plan early.

    What happened: Michael was not prepared. He spent years in patient preparation before he took over. Absorbed

  • A trusted insider will betray the family

    Likelihood: mediumImpact: severe

    Mitigation: Plan for the betrayal, and watch for the sign.

    What happened: Vito predicted that the traitor would be the one to arrange the meeting. Michael watched for it and was ready. Mitigated

  • A hot-headed acting lead

    Likelihood: highImpact: severe

    Mitigation: Pair the acting lead with someone who can hold them back.

    What happened: Sonny ran the business on anger, and was killed. Materialised

The Godfather by the numbers

BookThe Godfather
AuthorMario Puzo
First published1969
SettingNew York, 1945 to 1955
Quest typeLong game
TeamA family business
DurationAbout ten years
OutcomeDelivered at a cost
Handoffs (our count)4
Re-plans (our count)4
Dates on this pageApproximate: the book gives no full timeline, so the Gantt chart uses relative steps

Questions about The Godfather as a project

What does The Godfather teach about project management?

Succession is a project, so plan it before the founder steps back. Name the successor before you need one, and keep the plan close, but not too close. The full reasoning is in the lessons above.

How long does the quest in The Godfather take?

About ten years. The book gives no full timeline, so the Gantt chart on this page uses approximate, relative steps.

How would you set up The Godfather as a Kanban board?

Four lists: To do, In progress, Blocked and Done. At the moment shown above there are 2 cards to do, 2 in progress, 1 blocked and 2 done. The card to watch is "Prepare the handover", on the critical path. Give it two owners, and link it to the cards it waits on so the Gantt chart shows the order.

Plan your own quest on one board and one timeline

Lists for the work, two names on every critical card and the dependencies drawn before anything goes wrong, inside the Google or Microsoft account you already use.

Start your free trial