Do we learn from history? Today’s article focuses on learning from our history and the importance of project closure. This is the second article in our series on:
A customer problem and how we solve it via the UrukPlatform.
Background
As we build the Uruk Platform, we reflect on decades of experience on real projects worldwide and in different industries. These projects ranged from micro to mega, simple to incredibly complex. During these decades, we have learned from the good, bad, and even ugly practices. One day, we will share many of these stories.
The Problem
One area we observed as a weakness was project closeout. why is this a weakness? Some (if not many organizations do not properly close a project. They might ignore, forget, or rush project closure. Further, once the implementation team hands over the product (e.g., facility) to the operation team, the implementation team is demobilized (disbanded), and their project history is likely lost as they leave the project.
In today’s post, we will not explain the importance of proper closure; I think many PM guides make that case. We will say it is vital for continual organizational learning.
Most of us have probably heard a variation of this
“Those who do not learn from history are doomed to repeat it.”
Project Closure is one mechanism for learning from history.
Solving the Problem
How are we solving this problem in the UrukPlatform?
We have many features to counter this problem, and we will briefly share them here:
Digital Solution: The Uruk Platform is a digital solution. Therefore, the default is that all project information is automatically stored in the system and NOT lost.
Closing Stages: Instead of waiting to close the project at the end (after handover), we included a process for closing every stage BEFORE the stage team members leave the project. The image shows the close process for each stage.
Completion Report: In the last stage of the project, we insist on generating a completion report (the closeout report will be in the future, after the final success assessment). The Project Completion Report includes many steps. By the way, we insist on closing every project, even those terminated before completion.
Captured Lessons Learned: The Uruk Platform includes a module for capturing and using lessons learned on a project. Lessons are captured throughout the project; there is no need to wait for closure. Accordingly, each project contributes to learning and improving future projects. In addition, while planning each stage in the current project, the team can review the lessons from past projects and embrace the learning.
The Uruk Platform, Executive Dashboard, Portfolio View, Captured Lessons Learned
Project Success: We also incorporated project success in the Uruk Platform with a dedicated module using the Uruk Way Four Dimensions of Project Success. Project Success supports the learning from history and facilitates the project closure.
Exit Report: Every team member leaving the project will complete a project exit report to capture their thoughts before disappearing.
There are many other subtle features throughout the Uruk Platform. The cumulative benefits of these features include:
Ensure project completion and closure actions are carried out promptly and not lose history.
We are ensuring quality information to support organizational learning.
Closing Comments
As you can see from these articles, we are not business/tech people building software. We are project management practitioners with decades of global experience. It was natural for us to build the Uruk Platform using our learned history!
Remember:
Success can be predetermined, cultivated, and achieved!
If you like what you read, please share!
The post Do we learn from our history? appeared first on Applied Project Management Blog.
