← All playbooks
Tier 3: Dumpster Fire

What do you do when the project you led gets cancelled?

The short answer

Write a short close-out that captures what shipped, what was learned, and what's reusable, and circulate it before the team scatters. Then talk to your manager about where you land next within a week, rather than waiting to be assigned. Cancelled projects damage people who go quiet and barely touch people who document and redeploy.

What's actually at stake

  • 01Institutional memory of cancelled work disappears in about two weeks, taking your contribution with it.
  • 02The reassignment conversation is much better when you initiate it.
  • 03Bitterness in the close-out is the one thing that will be quoted later.

Do

  • · Publish a one-page close-out with outcomes and reusable assets.
  • · Thank the team publicly and specifically.
  • · Ask for your next assignment within the week.

Don't

  • · Do not litigate the cancellation decision in writing.
  • · Do not let the team hear it from a calendar deletion.
  • · Do not wait to be told where you're going.

A draft you can send now

Closing out [project]: we shipped [X], validated [Y], and [component] is reusable for [team]. Full notes at [link]. Thanks to [names] — the work was good even though the bet didn't land.
Tailor this to my exact disaster →

Questions people actually ask

How do I put this on my résumé?
By outcome and learning, not by status. 'Led X; validated Y; delivered reusable Z.'
Should I ask why it was cancelled?
Yes, once, privately, so you can answer the question when others ask you.
Is this a bad signal about my standing?
Usually not. How the next two weeks go matters much more.

Take it further

Related incidents

All CYABot tools →