We tend to spend lots of time talking about project set up, having a fully-thought through business case, or all the stuff you have to do while the project work is being done. But there’s another area that is arguably as important, if not more so than those: how to close a project.
If you don’t finalise and hand over the project to the operational teams effectively, you risk:
- Support and operational teams not knowing what they are supposed to be doing with what your project has delivered
- Ineffective benefits tracking
- Poor levels of training and support for users or customers
- High learning curves for users, which affects their ability to work in the new environment.
There is a big prize at stake: the project’s benefits. Wasn’t that why you did the project in the first place? If your project customers can’t understand or work with what you have given them, they won’t use it. If they don’t use it, the organisation doesn’t receive the planned benefits. And if the planned benefits aren’t delivered, the whole project was kind of pointless, right?
Here’s an infographic on how to close down a project effectively so you don’t leave anyone hanging. If you’d like a version to download, it’s available as a PDF inside the Resource Library.
Let me into the Resource Library!
Get access to over 30 project management templates, ebooks, checklists and more. The secret password is in your confirmation email!