Lessons learned without learning?

Why experiential knowledge is often lost in projects

Does this sound familiar from your own projects? A critical problem arises and suddenly someone on the team says: “We had exactly the same thing two years ago.”

Or a project fails due to the same coordination issues as its predecessor. Even though lessons had already been learned back then. And yet the next project starts almost from scratch again.

The reason is not that employees don’t want to learn. The reason is that experiential knowledge is inadequately reflected upon, shared and passed on in many organisations. Learning from experience and the reuse of lessons learned are often not firmly integrated into regular project processes.

Yet valuable knowledge is generated in projects every day: teams improvise under pressure, resolve conflicts, make difficult decisions and develop creative solutions. This is precisely where experiences arise that could make future projects more successful and efficient. And yet many of these insights disappear again. Not out of malice, but because in day-to-day project work there is often a lack of time, structure and sometimes even the culture needed to learn from them collectively.

Documentation is not the same as learning

Perhaps you have experienced this yourself: once a project is completed, a ‘lessons learned’ document is quickly drawn up. Everyone adds their input, the document is filed away, and after that hardly anyone talks about it anymore.

Formally speaking, insights have been documented. But in practice, a different reality often emerges: insights are documented, but not really understood, developed further or utilised in the next project. This is because what is stored there is mostly information, but not yet collectively reflected experiential knowledge.

Real learning does not come from filing documents. It arises when people jointly make sense of experiences, understand connections and can apply insights to their own practice.

This is precisely where the challenge lies. Perhaps you are familiar with situations where it only suddenly became clear during a conversation why a decision was actually made at the time. Not because of the official project status, but because of time pressure, uncertainty or a lack of coordination between those involved.

It is precisely such experiences that are rarely found in project documentation. And yet they often influence future decisions more strongly than any process description.

Experiential knowledge is never purely factual. It arises from individual perceptions, decisions, relationships and specific situations within projects. Employees often know far more than they can spontaneously explain or document. [1] And that is precisely why it is not enough simply to archive project knowledge.

Why experiential knowledge is so hard to access

Many important experiences remain unspoken. This is because they are difficult to pin down. Critical situations, in particular, often provide especially valuable learning opportunities:

• Why was a risk underestimated?
• Why did collaboration work particularly well at one stage, or suddenly break down completely?
• What implicit assumptions influenced decisions?
• What would those involved do differently today?

Yet such insights rarely emerge at the flick of a switch. Perhaps you are familiar with ‘lessons learned’ workshops, where initially only superficial statements are made, such as:

• “Communication could have been better.”
• “We should have escalated the issue sooner.”

And yet everyone involved feels that there is actually much more to it than that.

This is precisely why such discussions require appropriate questions and often also facilitation. Because experiential knowledge is not simply ‘retrieved’. It emerges through joint reflection, storytelling and contextualisation of situations.

There is also another crucial factor: a culture of learning from mistakes.

Empirical knowledge becomes particularly evident where people can speak openly about uncertainties, mistakes and problems. Yet this is precisely what many organisations find difficult. Anyone who shares negative experiences makes themselves potentially vulnerable. That is why critical insights often remain unreflected upon and unshared, even though they are precisely what hold the greatest learning value.

An effective knowledge culture therefore needs more than just processes and tools. It needs trust and psychological safety. Research on psychological safety and organisational learning shows that sustainable learning occurs particularly where reflection, knowledge exchange and a culture of open discussion free from fear are encouraged. Only when employees can speak without fear of rejection, sanctions or embarrassment do mistakes and doubts become opportunities for learning. [2]

The real problem: lessons learned have no fixed place in day-to-day project work

In many organisations, learning is expected to happen ‘on the side’.

Perhaps you’ve experienced this yourself: between deadlines, status reports and operational pressures, there’s hardly any room for conscious reflection. In traditional waterfall projects, lessons learned are often only scheduled at the very end, when those involved are already mentally focused on the next task.

No wonder, then, that many lessons learned seem more like a compulsory exercise than a genuine learning opportunity. The problem is therefore rarely a lack of knowledge. The problem is a lack of priority given to reflection.

Organisations that take learning seriously therefore consciously create spaces for it:

• regular debriefings,
• retrospectives,
• learning formats within day-to-day project work,
• cross-functional exchange formats
• or communities of practice.

Not as an additional task, but as an integral part of successful collaboration. Some companies are now deliberately creating dedicated spaces for reflection. For example, Union Investment also emphasised in an interview with Handelsblatt how important structured learning and exchange formats have become for sustainable organisational learning. [3]

Learning requires repetition, exchange and social embedding – only then do individual experiences become collective knowledge.

Knowledge management is not an end in itself

Perhaps you have experienced this yourself: new platforms or tools were introduced in the hope of finally managing knowledge more effectively. Initially, there was a great deal of enthusiasm. Yet after a few months, whilst things were being documented, they were hardly ever read, reflected upon or taken further.

This is precisely where a common misconception in knowledge management comes to light: knowledge is treated like an object – to be collected, stored and managed. Yet knowledge does not realise its value in an archive.

Knowledge management should therefore not be seen as an end in itself. Its purpose is not to introduce as many tools or platforms as possible. Its purpose is to effectively support the actual value-creation processes within the organisation.

Or to put it more simply: knowledge must help where decisions are made, problems are solved and projects are managed. Only then does real value emerge.

In principle, almost every recurring problem in organisations can be attributed, at least in part, to a lack of knowledge sharing, insufficient reflection or inadequate learning. Moreover, this also changes the role of the PMO. A modern PMO does not merely manage processes and standards. It creates the conditions in which learning becomes possible:

• through established reflection routines,
• through exchange formats,
• through networking
• and through a culture in which experiences can be openly shared.

In learning organisations, ‘reflecting on and sharing knowledge’ is not seen as an additional task. It becomes part of normal collaboration. And that is precisely where a sustainable knowledge culture begins.

Why stories are more effective than reports

Do you remember the content of tables? Probably, if you saw them just last week. But the risk table from the project before last has most likely already been forgotten. Situations, on the other hand, stay with you much longer.

That is precisely why storytelling plays such an important role in knowledge management. Stories convey not only information, but also context, emotion and meaning.

When someone recounts

• how a project nearly failed,
• how a decision was made under pressure
• or what small change suddenly led to a breakthrough,

something emerges that mere documentation rarely achieves: relatability.

Other teams can put themselves in the situation. They grasp connections more quickly and apply insights more easily to their own practice.

Storytelling does not mean ‘embellishing’ experiences. It is about making knowledge understandable, comprehensible and relatable. This offers enormous potential, particularly for PMOs: lessons learned are no longer static documents; they become living learning opportunities.

AI cannot replace a culture of learning

Artificial intelligence is currently transforming the way organisations handle knowledge. Perhaps you are already experimenting with AI tools yourself to process information more quickly or summarise content more efficiently.

In fact, AI can help to

• structure insights,
• summarise content,
• identify patterns
• or present case studies in a more accessible way.

This can significantly ease the burden on teams. But AI cannot replace trust or dialogue. The real challenge remains a human one: how do organisations create spaces where experiences can be openly shared and reflected upon together?

Only when this foundation is in place can technology truly fulfil its potential.

So that knowledge spreads

Knowledge has an impact when it is put into motion. When experiences are reflected upon, shared and passed on, learning takes place on several levels:

• individually,
• within the team
• and across the entire organisation.

This is precisely why communities of practice are so valuable. They create safe spaces where people can learn from one another – voluntarily, in a practical way and across project boundaries.

There, knowledge is not merely stored, but constantly developed further together. And that is precisely what many organisations need today more urgently than ever: not more information, but greater connection between people, experiences and learning.

For every project contains insights that can be valuable to others. The crucial question is simply this: do these experiences remain isolated, or are they allowed to spread?

Notes (partly in German):

[1] Michael Polanyi: The Tacit Dimension
[2] Amy C. Edmondson: Die angstfreie Organisation: Wie Sie psychologische Sicherheit am Arbeitsplatz für mehr Entwicklung, Lernen und Innovation schaffen
[3] Sonja Albers von Union Invest bei Handelsblatt live: Lernende Organisation: Der Schluessel zur Zukunftsfähigkeit

If you’d like to explore experiential knowledge in greater depth and are interested in how it can be made visible, shared and put to practical use in everyday life, we recommend the free, German-language webinar by Victoria Koestner on 22 September 2026. During the webinar, she will provide further valuable insights, practical examples and approaches to reflection. You can also find additional information and free resources on her new website.

Would you like to discuss lessons learned as an influencer or thought leader? Then please share this post across your networks.