You are signed in. Close

You are signed out. Close

Thank you. Your subscription has started. Close

Thank you. You will get an email when a new comic comes out. Close

We could not confirm your payment. If you paid, use the link "Sign in" at the bottom of the page. Close

Something went wrong on our side. Please try again in a moment. Close

Previous episode Unknown unknowns: why many small risks make a project delay likely

The planning fallacy: why projects usually take longer than the estimate

Why delays in a project add up, while time saved early gets lost

Some tasks finish late, some finish early. Over a whole project plan, shouldn't they even out? They almost never do.

  1. 1 Rono can only start the driver's screen once your map page is done. His task depends on yours, so it waits for it.youRonomap pagedriver's screenwaits for it

    Rono can only start the driver's screen once your map page is done. His task depends on yours, so it waits for it.

  2. 2 Your map page takes two days more than planned. Rono waits two days, and so does every task after his. The whole plan moves.youRono+2map pagewaitsdriver's screen

    Your map page takes two days more than planned. Rono waits two days, and so does every task after his. The whole plan moves.

The rest of this episode is for subscribers

Subscribe to read every premium episode. You can cancel when you want.

Paid yearly: $99 instead of $119.88

Next episode Hofstadter's law: why a project runs late even after you add extra time

Share this comic

More comics