Reflection

Often we are busy, too busy! We move through the days and push on to the next one. Reflecting at the end of a project is important for two reasons: 1) to evaluate if the project actually worked, or 2) if it will be done again, managing the process better the next time.

How do we evaluate if it actually worked? First, there are a couple ways to reflect on the information. Typically, we have a measure of success for the project. We do X by Y date. Sometimes, we hit both of those marks and it is obvious. Most of the time, success is more nuanced. Is there data (i.e., quantitative or qualitative) that can inform whether what was desired was achieved? Often, if you have key stakeholders, that can also offer feedback or opinions about whether success was achieved.

Many times, projects happen cyclically. If do it all again, how can the process be improved? In the business world, we often refer to this as a post mortem. During these conversations, successes, challenges and lessons learned are defined. If a specific schedule was used for the project, discussion explores how the schedule could be refined for the next iteration.

Again, reflection is a critical element of implementing a project. Not everything goes as planned, but knowing if success was achieved and how we might improve makes the next implementation go more smoothly.

Example of post mortem framework is available here:

Free post mortem template for ambitious project managers | monday.com Blog.