Read time: 5 minutes

👉 Why Read This Edition: You will learn how to shut down a dead project when a powerful sponsor is keeping it alive, without blowing up your career in the process.

ON THE CALENDAR

Fri, Apr 24 — The 4-Phase AI Framework Every Project Manager Needs. 30 minutes. Live on Zoom. Register here

Thu, May 7 — Reclaim Your Time: Run Your Week on Autopilot with Claude Cowork. 4-hour live workshop. SAVE $100 for the pre-launch. Use code launch100. (Sold out. Next cohorts May 14 and May 21.)

Fri, May 8 — Turn Numbers Into Decisions: Data Analysis with Claude. SAVE $100 for the pre-launch. Use code data100. (Sold out. Next cohort May 29.)

Mon, May 11 — AI-Powered Project Management. 4-week cohort. SAVE $100. Use code PROJECT at checkout.

Mon, May 11 — Project Management That Actually Works. 4-week cohort. SAVE $100. Use code EXECUTE at checkout.

Tue, May 12 — Project Management Foundations. 3-hour workshop. SAVE $100 for the pre-launch. Use code project100. (Sold out. Next cohort May 28.)

Wed, May 13 — Execution Sense: When AI Gives Everyone the Same Tools, This Is What's Left. SAVE $100 for the pre-launch. Use code launch101.

Thu, May 14 — Reclaim Your Time: Run Your Week on Autopilot with Claude Cowork. Next open cohort. SAVE $100 for the pre-launch. Use code launch100.

THE PROBLEM

Every company has one. The project that will not die.

You know the one. The numbers do not work. The team stopped believing a year ago. The deadline has moved four times. But the project keeps running. Why? Because a senior leader put their name on it. And no one wants to be the person who says it is over.

So the project lives. It eats budget. It eats head count. It eats the best hours of your best people, who now spend their days faking energy for work they know is dead. And every week, the company pays the bill.

Most leaders handle this in one of two ways. Both are weak.

The first type does the slow starve. They cut the budget a little. They pull one person off. They hope the project quietly dies on its own. It does not. It just suffers longer. Now you have a half-staffed team trying to ship a thing no one wants. That is not leadership. That is waiting for someone else to do your job.

The second type forms a committee. They call it a "strategic review" or an "evaluation working group." Six weeks of meetings. Reports filed. Slides made. Everyone in the room knows the answer on day one. But the committee gives them cover. No one has to face the sponsor. The project keeps breathing while the committee writes more reports.

Both moves share the same root. The leader cares more about their own comfort than the health of the company. They let a bad project live because killing it feels risky. That is backwards. The risk is keeping it alive.

Andy Grove had a line that stuck with me years ago. He said there is no such thing as a bad team, only bad leaders. I would add one more. There is no such thing as a project that cannot be killed. Only leaders who will not do it.

THE FRAMEWORK

THE PROJECT SUNSET FRAMEWORK
(download a free copy of this framework here)

I have killed projects inside Fortune 500 companies. I have done it as a consultant brought in to clean up a mess. I have done it on tiger teams and recovery teams. The pattern is always the same. When you do it right, the sponsor thanks you. When you do it wrong, you make an enemy for life. The difference is in how you run the play.

Part 1: Build the case on the sponsor's terms, not yours

Here is where most people get it wrong. They build a case that proves they are right. Charts. Data. A clean list of why the project is a waste. Then they walk into the sponsor's office thinking logic will win.

It will not. The sponsor does not care about your logic. The sponsor cares about their name, their story, and their standing in the company. If your case makes them look bad, they will fight you. Even if you are right. Especially if you are right.

You have to build the case on their terms. What does winning look like for them? What is the story they want to tell their boss at year end? What do they need to walk away with?

Then you frame the kill around that. You are not ending their project. You are helping them free up money to win somewhere else. You are not saying they were wrong. You are saying the market moved. You are not making them lose. You are handing them the next win.

Here is what you do not do. You do not walk in with a slide deck called "Why Project X Should End." You do not list every missed milestone. You do not make it a trial. That is how you turn a sponsor into an enemy.

I once helped a VP end a product line he had championed for two years. We did not lead with the failures. We led with a new market we had spotted. We showed him how the team, the budget, and the story he had built could shift into the new space. He killed the old project himself in the next leadership meeting. He got credit for the pivot. Everyone won.

Part 2: Have the conversation in private first, never in a room

Most people try to kill projects in meetings. Big mistake. You never put a senior sponsor in a room with other leaders and ask them to admit their project is dead. They will defend it. They have to. Their standing is on the line.

The kill has to happen one on one. Before any meeting. Before any deck. You sit down with the sponsor, alone, and you walk them through what you are seeing. You ask them what they are seeing. You listen.

Then you tell them the truth. Not with a speech. With one clear line. "I think we need to talk about whether this is still the right bet." Then you stop talking.

What happens next is the real work. The sponsor will push back. They will defend. They will tell you about the work already done. Let them. Do not argue. Just listen. Most sponsors already know the project is dead. They just need someone to give them room to say it out loud.

Here is what you do not do. You do not surprise them in a group setting. You do not send a memo. You do not let your boss deliver the news for you. That is cowardice dressed up as process. You own it. You walk into their office. You have the talk.

Colin Powell used to say leaders should never let their ego get so close to their position that when their position goes, their ego goes with it. Your job in this conversation is to protect the sponsor from that exact trap. Give them space to step away from the project without stepping away from themselves.

Part 3: Give the sponsor a graceful exit

This is the part most people skip. They get the sponsor to agree the project should end, then they walk away. Weeks later, the project is still running. Why? Because no one gave the sponsor a clean way out.

Your job is to write the story the sponsor will tell. What did we learn? What did we prove? What is the next bet we are placing with this team and this budget? Write it for them. Hand it to them. Make it easy to say.

The best sponsors I have worked with wanted to kill their own projects. They just did not have the words. When I handed them the words, they moved fast. A project that had been limping for six months ended in a week. The team got reassigned. The budget went somewhere useful. And the sponsor walked away with a win.

Here is what you do not do. You do not make them say the word "failed." You do not rub their face in the bad bet. You do not tell the team the sponsor finally saw the light. You protect the sponsor's name on the way out. Always. Because the next time you need to kill a project, you want that sponsor on your side.

THE REAL TEST

Here is the question you ask yourself to know if you did it right.

Six months from now, does the sponsor still take your call?

That is the test. Not whether the project ended. Not whether you saved the company money. Those things matter. But if the sponsor feels like you beat them, you did not kill the project well. You just won a fight. And you will pay for that win every time you try this again.

The best project killers I know are the ones senior leaders trust to deliver bad news. They get called in on purpose. Not because they are mean. Because they are clean. They do the hard thing without making it personal. They protect the room on the way out. And the sponsors they worked with still take their calls years later.

Here is your action step for this week. Pick one project you know should end. Just one. Write down what the sponsor wants to walk away with. Not what you want. What they want. Then ask yourself if you can build a kill that gives them that.

If you can, you have the start of a plan. If you cannot, you need more information before you move.

Either way, you are doing the work most leaders will not. And that is how you become the person the company trusts with the hardest calls.

If this helped you, send it to someone who could use it this week.

Until next time,
Justin

✍️ From the Desk of Justin Bateh, PhD
Simple tactics. Real results. No fluff.