Capturing Project Knowledge
By Greg Bailey, VP WorldWide Sales at ProSymmetry
As the saying goes, “failure teaches us more than success”. But when we consider the number of projects that fail, and project managers’ struggles to capture learning as they implement projects, it seems project management may be an exception.
A 2013 survey found that 50 percent of businesses had an IT project fail during the previous year. What’s more worrying, however, is that not much changed in the following three years. A 2016 survey by the same company found that the statistics have in fact gotten worse: with 55 percent of businesses reporting they had worked on a project that had failed. While project managers are clearly working hard, there appear to be systemic problems in how common issues are being resolved across the industry.
The key differentiator is that learning from failure implies learning from our mistakes. To do that, we must identify and acknowledge challenges, obstacles and human mistakes during the project lifecycle. And to do that, we must consistently capture project knowledge. Without capturing the mistakes (as well as everything else) we encounter along the way, how can we as project management professionals learn from them?
Failure is a result of mistakes
It is highly valuable to understand how mistakes arise, so you can then do something about them. Common issues that arise include:
- Adding more people to a late project. When a project is behind, it’s tempting to add more people to the project to speed up completion. But filling new additions in on the situation will likely take more productivity away from existing team members than will be added by new ones.
- Overestimating savings from new tools or methods. Productivity is rarely improved in giant leaps, no matter how many new tools or methods are adopted. It is a gradual process, yet the project aims do not reflect this.
- Insufficient risk management. Failure to proactively assess and control the things that might go wrong with a project can cause projects to fall behind and go over budget.
- ‘Silver-bullet syndrome’. After finding initial success, project teams latch onto a single practice or new technology and expect it to solve all their problems from there on out.
- Switching tools mid-project. Often a result of making snap decisions, the learning curve and inevitable mistakes that accompany implementation of a new tool can void any benefits when in the middle of a project.
The power of hindsight is a wonderful thing. For many project managers, they will address any problems they encountered after the project’s completion—usually by way of a project summary. The following are the most common activities and approaches Project Management organizations use to capturing project knowledge, per the Project Management Institute (PMI)® study on Capturing the Value of Project Management through Knowledge Transfer:
- Lessons learned/post-mortem debriefings (81%)
- Subject matter experts (77%)
- Copying documents to a centralized repository (72%)
- Company Intranet (68%)
Post-project debriefings are the most common form of capturing knowledge. But the reality is, by waiting until after the dust has settled to address these problems, you risk forgetting the problems themselves or how you solved them. If project knowledge is not captured or shared, you risk ‘reinventing the wheel’ and failing to learn from (and therefore repeating) your mistakes.
Capturing project knowledge through developing a culture of continuous improvement should be the ideal goal for a project manager—where your team members will proactively decide to immediately record the lessons they’ve learned or directly mention them to you. But it will take a lot of time and dedication before this becomes a reality. So how do you get started?
Capture project knowledge at all times
- Constant improvement
In other words don’t wait until your next project to do things differently, but act immediately and plan ahead. It requires learning lessons as you encounter them. This is difficult, especially when your focus is on the project at hand. But it can be done.
- Documenting both the positives and negatives you and your team members experience
It is the individual responsibility of every project team member to take the opportunity to learn—documenting this as soon as possible. Project Managers and team members should participate together in sessions—both during and after projects—where these experiences are reviewed to make decisions on how to improve on future and current projects.
- Reporting and analyzing the lessons you have learned
From your failures and your successes, are the next steps you should take to implement a culture of continuous improvement. By analyzing lessons in full, you can develop practices to improve on future projects and ensure you don’t become another failed project statistic.
Greg Bailey is Vice President WorldWide Sales at ProSymmetry, the company behind the state-of-the-art resource management tool, Tempus Resource