Project knowledge comes in two kinds. Explicit knowledge can be written down easily: an operating manual, a diagram, a procedure. Tacit knowledge lives in people's heads: the engineer's trick for getting the server to behave, or the accountant's sense of how a supplier operates. Explicit knowledge moves through documents; tacit knowledge moves through people, by working side by side, talking, and trying things.
The lessons learned register isn't a file you open only at the closing meeting. It starts at the beginning of the project, is updated whenever something worth learning happens, and is used right away to improve the rest of the same project. At the end it moves into the organization's knowledge repository so the next project benefits. In agile teams the retrospective is the natural place to find lessons and apply them in the very next sprint.
To move tacit knowledge, use pairing (two people working on the same task together), shadowing (a newcomer follows an experienced colleague), swarming (the whole team works together on one hard item), and communities of practice that connect people with the same specialty across projects. As for documents, keep them short, current, and in a place everyone knows; a document nobody reads transfers nothing.
The most dangerous form of knowledge loss is key person risk: only one person knows how an important part works, making them a single point of failure. Treat it like any risk: log it, and plan to reduce it through pairing, rotation, and documentation before that person falls ill or resigns. At the end of the project, the handover to operations isn't just handing over the keys; it means training, a period of running things together, a clear guide, and an agreed support channel.
💡 Key points
- Explicit knowledge moves through documents; tacit knowledge moves through people.
- The lessons learned register is updated throughout and used right away, not only at closing.
- Pairing, shadowing, swarming, and communities of practice transfer tacit expertise.
- One person who alone knows something critical is a risk; log it and reduce it early.
🌍 Real-life example
A contractor in Dubai is building a hospital, and only one engineer knows the settings of the smart air-conditioning system. The PM logged this in the risk register, had a junior engineer shadow him for two weeks, and asked them to write a five-page guide with photos. Two months later the senior engineer had to travel for a family matter, and work carried on without a pause. At handover, the hospital's maintenance team worked alongside the project team for a full week before formally taking over the system.
📖 Key terms
| English | العربية |
|---|---|
| Explicit Knowledge | المعرفة الصريحة |
| Tacit Knowledge | المعرفة الضمنية |
| Lessons Learned Register | سجل الدروس المستفادة |
| Pairing / Shadowing | العمل الثنائي / الملازمة |
| Community of Practice | مجتمع الممارسة |
| Key Person Risk | مخاطرة الشخص الرئيسي |