A hefty project workload can be exhausting, so when a project comes to an end, it can be tempting to quickly close the books the second sign-off is received on final materials. But there are a number of benefits to taking the time to reflect on a project after it is complete.

The purpose of a post-project review (sometimes referred to as a post-mortem) is pretty straightforward: to understand what went well in the project as well as what could have gone better.

Here are some best practices for conducting a post-project review with your client and project team:

Seek individual feedback. You might send out a formal questionnaire or an informal email soliciting responses from the client and other team members. A questionnaire should have general questions about what went well and what was frustrating about the project. It can also include questions about specific elements such as project management, scheduling, resources and communication. Give participants some time to respond so that they can provide thoughtful and constructive feedback.

Organize a meeting to share feedback. Since you have collected individual feedback, your meeting topics can be focused, ultimately allowing for a more productive conversation. While the end product can certainly be discussed, use this time to really facilitate a discussion on how you can improve processes and reinforce best practices.

At the core of every review are two simple questions:

• What went right?
• What can we do differently going forward?

Kicking the meeting off with a positive attitude can set the tone for the overall dialogue. Ask questions such as, “What was a highlight of this project for you?” or “What was your biggest accomplishment on this project?” The post-project review is an excellent opportunity to celebrate the successes of the project and the team.

It is also important to acknowledge aspects of the project that could have been better. You don’t need to overemphasize this portion of the meeting, but admitting improvement areas and allowing your client and other team members to share their perspective is useful in learning how to prevent similar frustrations on future projects.

Although you should spend time on essential issues related to the project, avoid turning the meeting into a gripe session. Acknowledging issues is important, but a detailed rehash of the problems doesn’t necessarily provide additional value. Keeping the meeting short—30 minutes to an hour in length—can help prevent team members from dwelling on the negative.

Summarize the feedback in a written document. Like any good meeting notes, the summary is critical to ensure success moving forward. Share key takeaways from the review and be sure to note specific action items that can be taken on future projects.

Don’t forget to take action. The post-project review can be extremely valuable when the lessons learned are actually applied to future projects.

So perhaps think of the project review as a way to get your new project off on the right foot, rather than a look back.