Project Post Mortem

I’m currently taking a class where we explore the world of Instructional Design Project Management. For this week’s assignment, I was given the task of recalling when I worked on a project and assessing it in “post mortem”. For those of you who are new to the world of project management, post mortem is the review process where a project manager has the opportunity to assess what went well and what didn’t. Michael Greer shares,”It’s important for project managers and team members to take stock at the end of a project and develop a list of lessons learned so that they don’t repeat their mistakes in the next project “(Greer 2009). For this particular post, I am going to share my experience working on a project that involved a  learnig management system implementation. 

Project Plan

 During the project plan stage, there was a plan to roll out an enterprise wide learning management system in three phases. Overall, the plan was conservative and the deliverables were realistic. Nonetheless, there were some obstacles during the project that were quite frustrating.

1. The organization where I consulted had a policy that required an RFP to be conducted after the contract was signed. Due to this policy, the project team found that there were some modules of the system that did not fit the business model of the organization. As a result, a large amount of time was spent on identifying issues and creating work around solutions. The lesson learned, perform a RFP prior to signing a contract to ensure the software meets the business need of the organization.

Overall it was  gratifying to get the inital divisions onto the system and exicted about using it. Initially, the divisions were resistnt due to the communications that have announced the roll out of the learning management system for five years so this project raised concerns and doubt that this implementation was going to actually happen.


 The project team was relatively small but each person had a clear understanding on their role in the project. The project manager outlined a clear project plan and ensured that all deliverables were timely.


To ensure that implementation would run smoothly, my job was to create a test environment to simulate what the targeted impacted group would experience as end-users.  From the test, we were able to identify issues and find solutions with the vendor, or create the best alternate work around solution.

The feedback we received from stake holders and project drivers was of high quality. Everyone involved was comfortbale with giving feedback to ensure all concerns were addressed and all successes were celebrated as milestones.

So as you all decide to go and work on your projects. Take the time to review with your project team what went well adn what did not to ensure you do not repeat mistakes.


Greer, Michael; September 14, 2009;  Project “Post Mortem” Review Questions;  retrieved on 9/15/2011 from


One thought on “Project Post Mortem

  1. I am glad to hear of an ID project design that worked out as it was supposed to. I am sure that the fact that the project team knew their roles and worked together with the PM on the outlined project plan helped make the project run smoothly.

    And, the fact that you all took time to review what went well and what you would do differently shows that you were all committed to make future projects run smoothly as well. As a friend of mine from the Marines would say “Good On You”

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s