Short answer
Knowledge management AI and living memory are overlapping descriptions, not mutually exclusive software categories. A useful comparison distinguishes two jobs: retrieving information that is already approved, and maintaining context or actions that need a later review. Check how any proposed system supports sources, ownership, updates and permissions for each job rather than assuming its label determines its capabilities.
The difference is not “documents versus people”
Knowledge management does not become better merely by recording more conversations. Many questions need an approved policy, a procedure owner and a current document. Many work accounts should remain limited to the people and purpose for which they were shared.
Here, living memory describes the continuity job; it is not a standard product category or a capability exclusive to one supplier. A knowledge base or AI platform may support both jobs. Compare the responsibility model:
| Need | Retrieval-focused work | Continuity-focused work |
|---|---|---|
| Main question | What approved information can I retrieve? | What context or action needs to be revisited? |
| Useful source | Controlled document, record or article | Dated account, approved brief, described practice or action |
| Freshness control | Version, document owner and review date | Context, owner, review condition and correction route |
| Common failure | A fluent answer outruns its source | Old context is treated as a permanent fact |
| Human role | Own the source and resolve gaps | Check relevance before reuse or action |
The National Archives cautions that knowledge capture is not the same as knowledge management and that captured knowledge needs ownership and refreshing. Its guidance is useful here: capture only what has enough potential value and make responsibility explicit.
A freshness and responsibility card
For each item that should remain useful after a conversation, make a small card:
- Context: the work situation, location or period in which it was described.
- Source: the approved record or brief that supports it.
- Use: the question it may help answer, and who may use it.
- Owner: the role responsible for checking it.
- Review condition: a date, changed process, or next work event that triggers a check.
- Correction: where someone can challenge, amend or retire it.
This is deliberately less ambitious than a universal organisational profile. It gives a later reviewer enough information to ask: is this still relevant, and does the source support using it now?
Use the platform evaluation pack to test whether a changed or withdrawn record reaches the next answer, including for users with different access.
Fictional example: a practice becomes stale
Fictional example: an experienced shift lead describes a three-step handover that worked during a seasonal peak. The account is stored with its store, role, date and the operational owner who checked it. Four months later, a new returns process changes the exception route. The next team does not reuse the old handover automatically. It asks the owner whether the steps still apply, records the change and links the revised practice to the current procedure.
The value is not that a system “remembers everything.” It is that the original context makes a responsible update possible.
A practical capture-to-review sequence
The UK government's Lessons Management guidance describes a useful sequence of capture, analysis, validation, reporting and sharing. Adapted to ordinary operational learning, that becomes:
- Capture one concrete observation or practice with its setting.
- Separate what happened from the explanation offered.
- Ask an accountable work owner to check relevance and exceptions.
- Record the practical action or reusable guidance that is agreed.
- Return to it after the next relevant work event and revise, retain or retire it.
This is a method, not a claim that every observation proves a broader pattern or cause.
Where Lontra fits
Lontra's Living Memory organises permitted, dated context across employee conversations so a later campaign can revisit themes, commitments, described practices and open questions. Its product description states that managers receive action-oriented briefs rather than raw employee responses. The system does not replace an HRIS, a document repository or human interpretation. Explore the product.
Frequently asked questions
What makes organisational memory useful?
Useful memory keeps a source, context, owner and review condition, so a later team can check whether it still applies.
Does living memory replace a knowledge base?
No. A knowledge base remains useful for approved documents. A governed memory adds continuity for contextual work accounts and actions that need later review.
