System of record
Lessons learned stop at the register
A lessons learned register is a written statement that something you already approved is wrong. It sits in a log nobody queries, while the procedure it corrects keeps its approved status and answers every question.
Cognatum Team · Oct 23, 2026 · 6 min read
A lessons learned register is an unusual document. It is a written statement that something your company already approved is wrong. Somebody ran the project, saw what went badly, and wrote it down. The register now holds the correction.
Cognatum governs the entry
source · version · approver · permissions
Then the project closes. The procedure it was about keeps its approved status, its version number and its place in the system everyone searches. The lesson sits somewhere else, in a log nobody queries. Both are live. Only one of them answers questions.
The process has five steps
The shape of this work is settled and old. The Project Management Institute published a paper two decades ago setting out five steps: identify, document, analyze, store and retrieve. Modern guides use the same five. Capture the insight, write it up, look for patterns, put it in a repository, then go and look for it next time.
Step five is where it ends
The PMI paper is honest about what happens next. In less mature organizations, lessons are stored with the other project documents on a shared drive, with no easy means of retrieving them. The retrieve step, it says, is rarely used. Success depends on somebody choosing good key words, and on somebody else thinking to search for them.
The professional bodies say it plainly
The Association for Project Management is blunter. Many organisations report that although lessons may be documented, they are not reliably learned, and practices are not adjusted to capitalise on the learning. The same guidance adds that closing the project and writing the report is not enough. The report has to reach people in a form that makes them want to read it.
Capture is not the part most people worry about. APQC surveyed a thousand professionals and found that 92 percent of organizations do not consistently capture knowledge from soon-to-be retirees, and 85 percent have not operationalized AI for knowledge management. The register is the piece everyone believes is already handled.
A lesson is defined by what it should change
Look at how the term is defined. NASA, the European Space Agency and JAXA share a definition used widely across engineering. A lesson must be significant, valid, and applicable, where applicable means it identifies a specific design, process or decision that reduces the chance of the failure happening again.
Read that last part again. The definition requires the lesson to name a process. It does not require anything to happen to the document that describes that process. Nothing in the register points at a clause. Nothing in the procedure points back.
Three things a register cannot do
It never supersedes anything
A register is append-only by design. You add a row, you do not retire a document. So the procedure keeps its approved status while a note elsewhere says it led to a bad outcome. In change control terms, nothing has been superseded. In practice, something has.
It is not where the question gets asked
People do not search the lessons log. They search the policy, the procedure, the handbook, the shared drive. The register is a parallel record. It is kept for a different reason and read at a different moment, usually at the start of a project rather than in the middle of a working day.
It has no route to the document
A row in a register has an author and a date. It rarely has a target. Which procedure, which section, which version. Without that link, no reviewer can tell whether the lesson was acted on, and no system can tell that two of its records now disagree.
Now put an assistant on top of it
Point a retrieval assistant at your document estate and one of two things happens. The register is out of scope, so the assistant answers from the procedure and the lesson has no effect at all. Or the register is in scope, and two passages now contradict each other.
Similarity is not authority
Retrieval ranks passages by how closely they match the question. The superseded procedure often wins, because it is written in the formal language of the question. The lesson is written in project language, after the fact. Neither passage carries an approver, a status or an effective date, so nothing in the ranking can prefer the one that is right.
A worked example you can check today
ISO 9001:2015 has been withdrawn and replaced by ISO 9001:2026. Any lesson your team wrote against the 2015 clause numbers is now a note about a withdrawn document. Any answer quoting those clauses is a copy of one. The edition changed on a date you can look up. Your register did not notice.
Regulated industries already named this
Pharmaceutical quality guidance has circled this for years. ICH Q10 names knowledge management as one of two enablers of a quality system, alongside quality risk management. It says product and process knowledge should be managed from development through to product discontinuation. EU GMP asks that product and process knowledge is managed throughout all lifecycle stages.
Utilised is the load-bearing word
The ICH Q9(R1) questions and answers go further. There is no regulatory requirement for a formal knowledge management system. However, it is expected that knowledge from different processes and systems is appropriately utilised. A register nobody reads is captured knowledge. It is not utilised knowledge.
The AI rules point at the system
The EU AI Act writes a feedback loop into law. Article 72 requires providers of high risk systems to collect, document and analyse data on the performance of those systems throughout their lifetime. Read the object of that sentence. It is the system. A lesson your own team learned about your own procedure sits outside it.
What a lesson would need to count
Four fields turn a note into something a system can act on. The entry it concerns. The version of that entry. The named person who accepted or rejected the change. The date they did it. With those four, a lesson is a proposed revision. Without them, it is a row in a spreadsheet.
Once entries carry that record, the condition of the whole library becomes visible. Items split into healthy and at risk, where at risk is wider than overdue for review:
- duplicates, where more than one entry answers the same question
- conflicts, where an approved entry and a recorded lesson disagree
- gaps, where no approved entry exists at all
Those are counts. Somebody can be asked why the conflict count went up last quarter.
Where Cognatum sits in this
Cognatum governs the knowledge rather than the model. AI runs seven of the eight steps in the Cognatum Knowledge Loop, and Approve is the one it does not: a named person signs off, and the entry carries that approver, the date and the source from then on. Information stays where it lives, in the repositories each department already uses. When a source changes, dependent entries are flagged and routed for re-check.
A conflict is routed, not resolved
Where a procedure and a recorded lesson disagree, both are held and the disagreement is shown to a person, rather than settled by recency or by averaging. A legitimate difference between two divisions is linked rather than retired. None of this confers compliance with any framework. It produces the trail your reviewers ask for.
A test for your own register
Open your register and pick one lesson from last year. Find the procedure it was about, and check whether that procedure changed. Then ask your assistant the question that lesson was written to answer, and ask it for the entry, the approver and the date. The lesson is in the building. It just is not in the answer.
Your company's knowledge isn't missing. It's unusable. Cognatum changes that. The eight steps and the single human gate are documented in full on the Cognatum Knowledge Loop.
Sources
- Lessons learned: taking it to the next level (pmi.org)
- What is lessons learned in project management? (apm.org.uk)
- Lessons learned in project management: 5-step process (asana.com)
- Lessons learned, definition and application (wikipedia.org)
- APQC study warns of looming Great Retirement crisis (apqc.org)
- ISO 9001:2026 Quality management systems, requirements (iso.org)
- Is knowledge management a part of the pharmaceutical quality system? (gmp-compliance.org)
- EU AI Act Article 72: Post-market monitoring by providers (europa.eu)
- The Cognatum Knowledge Loop (cognatum.ai)
Common questions
Questions this raises.
What is a lessons learned register?
A log of documented insights from a completed project or phase, usually covering what went well, what went badly and what to improve next time. It is a record of learning. It is not a change to the documents the learning was about.
Why do lessons learned rarely change anything?
Because the register is append-only and has no route to the document it concerns. The lesson names a process, but nothing retires or revises the procedure that describes that process, and nobody searches the register when they have a question.
Will an AI assistant read our lessons learned log?
Only if the log is in scope, and even then retrieval ranks passages by how closely they match the question rather than by authority. A formally worded superseded procedure usually outranks a project note. Neither passage carries an approver or an effective date.
Is a lessons learned process a regulatory requirement?
In pharmaceutical quality, ICH Q9(R1) states that there is no regulatory requirement for a formal knowledge management system, but that knowledge from different processes and systems is expected to be appropriately utilised. Capture on its own does not meet that expectation. No software confers compliance with any framework; it supplies evidence toward your own obligations.
What should we measure instead of lessons captured?
Measure the condition of the knowledge itself. Count entries past their review date, unresolved conflicts between an approved entry and a recorded lesson, and gaps where no approved answer exists. Those are counts a governance forum can set a threshold against.