What kills a lesson learned
- It is written for management, not for the next person with the same problem.
- It is attached to nothing: no task, no knowledge, no machine.
- Nobody validates it, so nobody trusts it.
- It is in French in a group that also works in English and Arabic.
The circuit in KnowledgeCapital
Contribution
Anyone writes what they learned, attaches a photo or a recording. A question asked in the expert network becomes a lesson learned when its answer is captured.
Validation
A committee reviews before anything becomes searchable. The diagnosis flags contributions waiting for more than 45 days: a base where people wait too long dies of discouragement.
Attachment
Each entry is linked to the knowledge and tasks concerned. It appears where people work, not in a separate folder.
Search
One search across languages, with local AI that also reads attachments. Nothing leaves the network.
Sealed meeting minutes
Team and community meetings produce minutes, including from a video-conference recording. They are sealed: you can prove they have not changed.
Measuring whether the base is alive
Entries published, views per entry, validated entries never read, attachments not analysed: the diagnosis says whether lessons learned serve, or sleep.
Lessons learned already written in a document management system or in Notion are not lost: the connectors read them read-only and link them to the knowledge they concern; new lessons learned follow the validation route.