Why do organizations repeat mistakes despite capturing lessons learned?

In my experience, the issue is rarely capturing lessons, it is applying them. Lessons learned should be reviewed during project initiation, planning, and key stage gates, not only at closure. When teams make past insights part of decision making and governance, they become organizational knowledge instead of archived documents.

Making lessons learned easily accessible enables project professionals to review past issues, mistakes and decisions, helping them stay focused on the current scope and address challenges more effectively.
For example, maintaining a centralized repository of lessons learned, risks, issues, and decision logs as an active knowledge base rather than a historical archive is far more valuable. The repository can be queried or connected to dashboards for analysis, and integrating it with project management tools embeds it into the project workflow. This encourages project professionals to regularly reference past experiences, identify recurring patterns and apply proven solutions before similar issues arise.

Lissette, tolerance and affinity for VUCA cripple the integrity of a Lessons Learned feedback loop. Reinventing the wheel is rampant. There is so little appetite to standardize project work that unless there is an appetite to minimize VUCA, Lessons Learned feedback loops will continue to have terrible integrity.

To put a metric on the problem, I’ll title the metric “Destinations for Lessons Learned feedback.” I believe a figurative value is 100. There might as well be 100 places that Lessons Learned might land for subsequent project, because most project plans are highly unique, complex, and ambiguous.

To achieve integrity in a Lessons Learned feedback loop, your culture would have to dramatically decrease this number.

In separate threads, I have explained concepts such as Five Verbs, Finite Productivity, and Documentation Debt. To improve the integrity of your Lessons Learned feedback loop, you must reshape your culture this way. As you reshape your culture, your metric “Destinations for Lessons Learned feedback” will drop to FIVE.

1.Asset Portfolio: the titles of the documents that you govern with Five Verbs. Every Lessons Learned exercise (I recommend monthly-ish) is prone to tweaking this number through adding, removing, merging, or splitting assets.
2.Contents INSIDE each asset. For example, the Q3 2026 version of your project charter might ask 20 questions and your Q4 2026 version might ask 22 questions.
3.Interdependencies. You might change what’s sequential and what’s in parallel.
4.Assignments. Any combination of the Five Verbs is prone to be reassigned.
5.Duration estimates. Any past estimates of days or hours might increase or decrease.

That’s it. I haven’t had much feedback on this idea, but as a default, it’s worked for my past teams. Executives almost always complicate it, but as I mentioned before, the tolerance and affinity for VUCA among senior-ranking employees is high.

I welcome any nature of questions, feedback, pushback, ideas, etc.