How do you promote project learning and knowledge sharing through communication?

Share with the project team at the end of the project. Share with other project managers during a lunch and learn session. Incorporate lessons learned into risk management discussions. Categorize lessons learned and put on a shared drive. Consider how lessons learned could be effectively used and explain it prior to collection.

In knowledge management, there are two communication strategies that can support the exchange of knowledge within the organization. The push strategy supports the transfer of knowledge on an offer basis: knowledge that has been identified and assessed as valuable is actively communicated to potential knowledge users and thus offered. With the pull strategy, knowledge transfer takes place on a demand basis: existing knowledge is sought or requested in a targeted manner as required.

One thing I have found useful is to work with the project end beneficiary to tell the story. What was their situation before and how has it changed? The beneficiary describes how different actors impacted their lives. This way, we have the health worker, community worker, and administrative personnel pick the learnings they can adapt.

I have established multiple communication channels to enforce learning, these include: 1. Knowledge Sharing session between team members (various specialties) 2. Chapter meetings (iOS, Android, etc..) for reviews and knowledge transfer 3. Open communication channel for knowledge share, new tools, updates, and tricks others might find useful, on the platform of your choice. 4. One-to-ones for 2-way feedback

In my recent experiences, mainly in agile approaches, facilitating retrospectives meeting was a good way to encourage participation in raising improvements and adjustments with the teams. For example, a useful technique for encouraging participation is to pose a group question and ask for individual responses. For example, you could ask team members to think of a project success and challenge so far, and then ask each member to share their responses.

It is important that knowledge from projects is not only shared within the project group. I like to work with the peer assist method. Peer assists are structured meetings in which a project team invites experienced members of other past projects to offer support with specific new challenges. They are a targeted request for help when a project team is faced with a specific, previously unknown task for which there are already knowledge carriers in the organization who have solved similar problems and would like to share their knowledge.

once, Aa coworker told me about a very useful technique that I ended up using, the composition of a knowledge database based on records of change events, risks and highlights. However, in addition to this information serving us to consolidate real project templates, it also serves for consultation by the team and, better, as a basis for discussions. Allowing the team to feed this knowledge base and giving them credit for these contributions is very helpful as well. We ended up adjusting what was suggested to us and there was no shortage of topics for our feedback meetings.

I prefer to contextualize learning and tell the complete story, when I can. It works well because team members can easily understand WHY and HOW the knowledge is useful. They also tend to remember the story better than a line in a repository. We often see this with safety briefings in the construction industry when there are accidents. The learning is contextualized within the complete story. But we can also use the storytelling for successes...for instance, Jessica has been experimenting with a new dashboard system, and on each of her last 4 projects she has been able to deliver under budget by at least 5% and received positive feedback from stakeholders. Here are some important details on her project and what she thinks works best...

A lot of knowledge is generated in projects. It is important for others in the organization to know the learnings from the project. I work with knowledge assets that describe the most important findings and learnings from the project.