It's easy to get a project started – everyone's excited, there's money, and lots of energy. But when it's time to end a project, things often get complicated. Sometimes, leaders keep projects going for too long, which wastes money and makes the team feel down.
But the really smart leaders know how to skillfully end projects. They see it as a smart move, not a failure. Ending a project just means you're focusing on what's really important.
So, how do you end a project smoothly? Gerald Leonard (courtesy: HBR) has a simple "4 R's" plan to make sure project endings are clear, respectful, and useful. Let's look at them:
1. Retire – Finish it properly.
Don't just let a project slowly disappear. Officially close it out: save all the files, stop spending money on it, and tell the team clearly why it's ending. This helps everyone feel like it's truly done. Our brains like to have clear endings; otherwise, people can stay stuck on old, unfinished tasks.
2. Redirect – Use your people and money elsewhere.
Old projects can tie up your best people and your budget. By redirecting, you free up your team, money, and tools for better, new opportunities. Companies that regularly move resources around often do much better than those that don't. Show your team how their next job fits into bigger company goals – it builds their trust.
3. Repackage – Save the good stuff.
Even if a project didn't fully succeed, not everything from it is worthless. You can often reuse things like code, designs, ideas, or even training materials. For example, Microsoft took parts of its old Windows Phone and used them in products like Surface devices and cloud tools. Think of reusing as being innovative, not just recycling.
4. Reflect – Learn and keep going.
Finally, take some time to look back. Have meetings to review what happened, thank your team, and share what everyone learned. Reflecting helps reduce any bad feelings and builds confidence. It shows everyone: "This project might be over, but here's what we gained for next time."
