Every experienced project manager in Malaysia has a story about a mistake they watched happen twice. The same waterproofing detail fails at a second podium. The same authority submission is rejected for the same missing document. The same long-lead switchgear arrives late because, once again, nobody locked in the order before the design was frozen. Each time, someone in the room says, “We had this problem on the last job.” And each time, the lesson that was supposedly learned turns out to have been merely recorded.
Lessons learned are one of the most talked-about and least practised disciplines in construction project management. Almost every quality manual and project execution plan mentions them. Far fewer organisations can show how a lesson from one project actually changed the way the next one was planned, priced, designed or built. This article looks at why the loop so often stays open, and what project managers can do to close it.
Why lessons get recorded but not learned
The typical pattern is familiar. Near practical completion, or sometimes months after it, the project team is asked to fill in a close-out report. Half the original team has already moved to other sites. The people who remain are busy with defects, final accounts and handover documentation. The lessons section is completed in a hurry, often as a list of complaints about the client, the consultants or the weather. The report is approved, saved to a shared drive, and never opened again.
Several things go wrong in that pattern. Lessons are captured too late, when memories have faded and the people who knew the detail have left. They are written as stories rather than as actions, so nobody knows what to do differently. They are stored by project rather than by topic, so a planner starting a new hospital job cannot easily find what the last three hospital jobs learned about medical gas or nurse-call systems. And there is rarely an owner whose job it is to make sure a lesson changes a standard, a checklist or a tender document.
Culture matters too. In a hierarchical, relationship-driven industry, admitting that something went wrong can feel risky, especially when commercial disputes may still be open. If the lessons process feels like a hunt for someone to blame, people will contribute only safe, generic observations, and the valuable insight stays in their heads.
What good practice looks like elsewhere
Internationally, the organisations that take this seriously tend to treat lessons learned as a continuous process rather than a close-out formality. The Project Management Institute’s guidance encourages a lessons learned register that is maintained throughout the project, not only at the end. NASA, after hard experience in its space programmes, built a dedicated lessons learned information system so that engineers could search past findings by subject before starting new work. In the oil and gas sector, which has long been familiar to Malaysian engineers through Petronas and international operators, structured after-action reviews and stage-gate reviews that explicitly ask “what did we learn from previous similar projects?” are common practice.
The common thread is not a particular software tool. It is that lessons are captured close to the event, written so that they can be acted on, organised so that they can be found, and pulled into the start of new projects rather than pushed out at the end of old ones.
Capture lessons while the project is still alive
The single most useful change a project manager can make is to stop waiting for close-out. Build short lessons reviews into the rhythm of the project: at the end of each major stage, after a significant incident or near miss, after a difficult authority approval, after a commissioning test that failed and was repeated. Fifteen or twenty minutes at the end of an existing progress or coordination meeting is often enough.
A simple structure keeps these reviews focused. What did we expect to happen? What actually happened? Why was there a difference? What should we do the same way, or differently, next time? Framing the discussion this way moves the team away from blame and towards cause and action. It also works well across Malaysia’s mix of languages and working cultures, because it is concrete and practical rather than abstract.
Involve the people who did the work. Site supervisors, M&E coordinators, subcontractor foremen and document controllers often hold the most useful lessons, and they are the least likely to be invited to a formal close-out workshop.
Write lessons as actions, not anecdotes
A lesson that reads “the lift installation was delayed” is a fact, not a lesson. A useful entry explains the cause and the change: “Lift shaft handover was delayed because shaft tolerances were checked only after the structure was complete. On future projects, include a lift shaft survey hold point at each floor pour, and give the lift specialist access to inspect before the shaft is closed in.” The second version can be turned into a checklist item, a specification clause or a programme activity.
It helps to tag every lesson with a few consistent attributes: project type (for example, healthcare, high-rise residential, industrial, infrastructure), project stage, discipline, and whether the lesson is about design, procurement, construction, commissioning, contract administration or stakeholder management. Positive lessons deserve equal space. Knowing what worked well, such as an early engagement approach with a local authority or a subcontractor onboarding method, is just as valuable as knowing what failed.
Give lessons a home and an owner
Lessons scattered across hundreds of close-out reports are effectively lost. Whether an organisation uses a dedicated database, a common data environment or a well-structured spreadsheet, the lessons need to live in one searchable place, organised by topic rather than by project name. For firms already moving towards BIM and digital project delivery in line with the industry’s digitalisation agenda, the same information management discipline that applies to models and drawings can be applied to lessons.
Someone must also own the process. In larger developers, contractors and consultancies, this is often a technical or quality function that reviews new lessons regularly, removes duplicates, and decides which ones should change company standards. In smaller firms, it may simply be a senior project manager who takes responsibility for keeping the register alive. Without an owner, even the best-designed system quietly decays.
Pull lessons into the start of every project
Closing the loop means reversing the direction of flow. Instead of hoping that someone will read old reports, make the review of relevant lessons a required step at project initiation, at design reviews and before tendering major packages. A project manager starting a new data centre, school or township phase should be able to ask: what have we, and our partners, learned on similar projects in the last few years, and how is that reflected in our plan?
This is where lessons start to pay for themselves. They can shape the risk register, inform the procurement strategy, add specific items to design review checklists, adjust programme durations for activities that are consistently underestimated, and sharpen the scope and specification of subcontract packages. On public projects, where accountability and value for money are under close scrutiny, being able to show that known issues from earlier projects were deliberately addressed is a strong governance message.
Make it safe to tell the truth
None of this works if people are afraid to speak. Project leaders set the tone. When a project director openly shares a decision that did not work out and what they would do differently, it signals that honesty is expected rather than punished. Separating lessons reviews from commercial or disciplinary discussions, and focusing on systems and processes rather than individuals, makes it easier for teams to be candid.
Client organisations have a role as well. Clients who invite contractors and consultants to joint lessons sessions at the end of a project, rather than only at the end of a dispute, often find that the whole supply chain becomes more willing to share. Over time, that collaborative habit can raise the standard of the wider industry, not just individual firms.
A practical starting point
For project managers who want to begin without waiting for a corporate system, a few steps go a long way:
Set up a simple lessons register on your current project and add to it at every stage review.
Use the four questions: expected, actual, why, and what next time.
Write each lesson as a specific action that someone could implement.
Tag lessons by project type, stage and discipline so they can be found later.
Before your next project starts, spend an hour reviewing lessons from similar past projects, and record how you have acted on them.
Conclusion
Malaysian construction has no shortage of experience. Across highways, rail, hospitals, high-rise housing, industrial plants and data centres, our project teams have solved difficult problems many times over. The challenge is making sure that what one team learns does not leave with them when the project ends. Treating lessons learned as a living, owned, action-focused discipline is one of the lowest-cost improvements a project organisation can make, and one of the most rewarding. The loop only closes when a lesson changes what happens next.
The articles and technical notes published on this website are intended for knowledge sharing and professional discourse within the construction project management community. The views, opinions, and interpretations expressed are those of the respective authors and do not necessarily reflect the official policy, position, or constitutional stance of the Association of Construction Project Managers Malaysia (ACPM) or its Council.
The content should not be construed as legal, regulatory, or professional advice. Readers are encouraged to exercise their own professional judgement and seek appropriate advice where necessary



