[When company memory is missing]
You need your team to find the answer without asking one person
The answer lives in an old email. A former staff member knows the reason. The new person asks the same question again.
The answer is already somewhere
It may be in a shared drive a ticket a meeting record or a person’s head.
We map the sources before we add a chat box. The system should show its source and stop when the evidence is weak.
Build memory around one question
The first use should answer a question your team asks often.
- The source files and their owner
- The person allowed to see the answer
- The source link and review step
- The update and deletion path
- The rule for saying I do not know
Make the answer worth trusting
We test the system against real questions. A person stays in the loop when the evidence is weak or the decision matters.
The first step is a focused knowledge review. You can start with one source and one question.