Why most organisations collect lessons… but never actually learn from them.

Every major project finishes with a lesson’s learnt workshop.  Flip charts appear.  People discuss what worked well.  Everyone agrees the conversation was valuable.  The report gets written.  Then it quietly disappears into SharePoint.  Six months later, the next project makes many of the same mistakes.

At BRS, we’ve found that the problem isn’t that organisations fail to identify lessons. The problem is that they don’t have a system for embedding them.

Recently, we facilitated a comprehensive lesson’s learnt programme for one of New Zealand’s largest infrastructure projects. Rather than treating it as a single workshop, we designed a structured process that gathered insights from across the entire project ecosystem and translated them into practical actions for the organisation, future projects and the wider industry.

The experience reinforced an important principle:

Lessons learnt are not an event. They are an organisational capability.

The organisations that consistently deliver outstanding projects don’t simply reflect on the past—they systematically use experience to improve the future.  Here’s how to approach it.

Step 1 – Start Before the Workshop

Many organisations begin with a workshop.  We believe that’s the wrong place to start.  People arrive with different perspectives, incomplete information and often the loudest voices dominate the discussion.  Instead, begin by building evidence from multiple sources.  Our process typically includes:

• Reviewing background and project documentation
• One-on-one stakeholder and partner interviews
• Confidential surveys using a combination of Likert scoring questions and open-ended questions
• Small group discussions
• Facilitated workshops
• Consolidated reporting and action planning

Each stage builds upon the previous one, allowing themes to emerge before people come together to solve problems.   The result is a far richer, more objective and evidence-based conversation.

Step 2 – Listen to Every Part of the Ecosystem

Projects are delivered by ecosystems—not organisations.  That means the best insights don’t just come from the project team.  They come from:

• Clients
• Delivery partners
• Designers
• Contractors
• Consultants
• Advisors
• Governance groups
• Supply chain partners
• Stakeholders
• Communities
• Traditional owners and other key partners

Everyone experiences the project differently.  When these perspectives are combined, recurring patterns begin to emerge that no single organisation can see on its own.  The richer the diversity of perspectives, the richer the quality of the lessons.

Step 3 – Look for Patterns, Not Individual Issues

Good lessons learnt processes don’t produce hundreds of disconnected actions.  They identify a small number of systemic themes.  In our recent review, hundreds of comments consistently pointed towards recurring issues including:

• Governance clarity
• Decision-making discipline
• Stakeholder integration
• Role clarity
• Commercial capability
• Relationship quality

Conversely, the strongest positive themes were:

• High trust
• Psychological safety
• One-team culture
• Collaborative leadership

These themes consistently emerged across interviews, surveys and workshops.   When multiple sources tell the same story, leaders can be confident they are addressing root causes rather than symptoms.

Step 4 – Convert Insights into Organisational Change

Capturing lessons is only the halfway point.  The real question becomes:

What changes tomorrow?

The most successful organisations convert lessons into improvements across multiple areas, including:

• Governance and assurance frameworks
• Decision-making processes
• Operating models
• Commercial systems and processes
• Capability development
• Leadership expectations
• Project management methodologies

A lesson only creates value once it changes how future work is delivered.  Reflection without implementation is simply documentation.

Step 5 – Develop an Implementation Plan, Not Just a Report

This is where many lessons learnt exercises fail.  The report gets endorsed.  Everyone agrees with the recommendations.  Then the project moves into the next phase exactly as before.  If a lessons learnt review is undertaken midway through a project, which is where we believe it creates the greatest value, the most important output is not the report itself.  It is a practical implementation plan for the next phase.

Think of the lessons learnt report as the diagnosis.  The implementation plan is the treatment.  Without a structured implementation plan, even the best insights are gradually overtaken by delivery pressures, competing priorities and new people joining the team losing this important tacit knowledge.

An effective implementation plan should identify a small number of guiding principles that define how the next phase will operate. Beneath each principle should sit specific actions, accountable owners, realistic timeframes and regular progress reviews.  Rather than creating hundreds of disconnected recommendations, the implementation plan should organise improvement into a series of strategic workstreams.

These may include:

• Establishing a clear project operating model
• Strengthening governance and decision-making
• Building capability as an intelligent client
• Improving project controls and commercial disciplines
• Strengthening leadership, culture and wellbeing
• Enhancing stakeholder and supply chain integration
• Sharing lessons across the wider agency and industry

Each principle then becomes a workstream with practical deliverables such as developing governance charters, decision registers, DARCI models, stakeholder and partner integration plans, capability development programmes, succession plans and agency roadshows to transfer knowledge across future projects.

This transforms lessons learnt from a retrospective exercise into a forward-looking delivery strategy.

Step 6 – Use the Implementation Plan to Reset the Next Phase

One of the strongest recommendations from our recent review was to conduct a formal project reset before commencing the next phase.   This reset is where the implementation plan comes to life.  Rather than assuming improvements will happen organically, project leaders deliberately revisit:

• Project outcomes
• Governance arrangements
• Roles and responsibilities
• Decision-making frameworks
• Ways of working
• Stakeholder strategies
• Project controls
• Team culture and behaviours

The implementation plan provides the roadmap for these discussions and ensures the lessons identified are translated into tangible improvements before delivery recommences.  Embedding lessons at the beginning of a new phase is significantly easier than trying to change behaviours once the project is back under delivery pressure.

Step 7 – Share Beyond the Project Team

Perhaps the biggest missed opportunity in infrastructure is that lessons often remain within the project that generated them.  Every major project invests millions and often billions of dollars building knowledge.  Yet much of that knowledge disappears when teams disband.

Leading organisations deliberately share lessons across:

• Future projects
• Business units
• Executive leadership
• Project Directors and Sponsors
• Delivery partners
• Government agencies
• Industry forums
• Supply chain organisations

This creates organisational memory rather than project memory.  It also improves capability across the entire infrastructure ecosystem.   The most mature organisations recognise that every project has a responsibility to leave the industry stronger than it found it.

Step 8 – Build an Intelligent Client

One of the most significant findings from our review was that lessons learnt should contribute to something much bigger than improving a single project.  They should help organisations become more mature and intelligent delivery clients.  As infrastructure projects become larger, more complex and increasingly dependent on multiple agencies and partners, owners need capabilities that extend well beyond traditional project management.

These include:

• Systems leadership
• Governance excellence
• Commercial acumen
• Programme integration
• Ecosystem management
• Strategic decision-making

The future belongs to organisations that can orchestrate complex delivery ecosystems, not simply manage contracts.   Developing these capabilities is one of the greatest long-term benefits of a well-executed lessons learnt programme.

The Biggest Lesson of All

Perhaps the greatest insight from this work is that projects don’t improve because people work harder.  They improve because organisations learn faster.  The infrastructure sector often speaks about continuous improvement.  True continuous improvement requires much more than collecting feedback.  It requires a disciplined process that captures experience, identifies systemic patterns, embeds change into governance and operating models, develops an implementation plan, and deliberately shares knowledge across organisations, agencies and industry.

The most mature organisations no longer see lessons learnt as the end of a phase—they see them as the beginning of the next one.  Every lessons learnt exercise should conclude with an implementation plan that is actively managed by the project leadership team, reviewed alongside project performance and continuously updated as improvements are embedded.  That is how organisations move from documenting experience to systematically building capability.

Over time, every project leaves the organisation stronger than it found it.  At BRS, that’s what we believe a modern lesson’s learnt process should achieve.  Not simply documenting the past.  But systematically improving the future.

Final Thought

One of the greatest compliments a project can receive is not that it was successful.  It is that the projects that follow including their own if the lessons learnt review is midstream are even better because of it.  That’s when lessons learnt become more than a report.  They become a lasting competitive advantage.