Blog
How to keep a team knowledge base current
Why team wikis go stale, which knowledge belongs on a page and which in a shared memory, and how Cedric keeps the answers current where the team asks them.
Benjamin Ben HattarEvery team wiki starts the same way. Someone spends a week writing the onboarding guide, the pricing rules and the how-we-ship page. For a month it is the best thing in the company. Then the product changes, the refund window moves from 14 days to 30, a new tool replaces an old one, and none of that reaches the pages.
Six months later a new hire reads the onboarding guide, follows it, and gets told in chat that nobody does it that way anymore. After that they stop reading the wiki and ask in chat. So does everyone else. The wiki gets fewer readers, which means fewer people notice when it is wrong, which means it gets more wrong.
This post is about breaking that loop. Better writing does not fix it, because the writing was fine. The trouble is where the changes happen and who is supposed to carry them back.
- Wikis go stale because decisions happen in threads and meetings, and carrying them back to the page is nobody's job.
- Long, structured material belongs on a page. Short rules and corrections belong in a shared memory the team can ask.
- The test for a page is whether a person would read it top to bottom. The test for a memory is whether it fits in one sentence.
- Cedric reads the pages, keeps the one-line rules in the company brain, and flags a page when a later decision contradicts it.
- Deciding what is true, and who owns each page, stays with people.
Why team wikis go stale
Look at the last five things your team changed its mind about. I would bet most of them were settled in a thread or on a call. Someone said "let's do 30 days for annual plans", two people reacted with a thumbs up, and the conversation moved on. The wiki page that says 14 days did not hear about it.
Updating that page is a second task, done later, in another tab, by someone who has to remember which page it was. It loses to everything. Nobody is lazy here. The wiki asks for a separate trip every time something changes, and most changes are too small to feel worth the trip.
The other half is trust. A page does not tell you it is out of date. It looks exactly as confident as it did the day it was written. Once a reader has been burned by a stale page, every page is suspect, and asking a colleague feels safer. That colleague then answers from memory, and the wiki loses one more reader.
What to keep in writing, what to keep in a shared memory
Most teams put everything on pages. Some of it reads better as one sentence the team can ask about.
| Knowledge | Where it belongs | With Cedric |
|---|---|---|
| The onboarding guide | A page. People read it start to finish. | He reads the page and answers from it, cited. |
| A product spec | A page, with its history. | He searches it and names the section and date. |
| "Hardware goes under equipment" | Shared memory. One sentence. | Said once in the channel, followed in every draft. |
| The customer naming rule | Shared memory. | Kept for the workspace, listed on the Brain page. |
| "I prefer short replies" | A personal preference. | An only-me instruction that never touches a teammate's work. |
| The travel policy | A page, or a document you teach him. | Saved as a memory with the file's name, quoted when it applies. |
If it fits in one sentence and changes often, it is a memory. If people need to read it in order, it is a page.
Two places, two jobs
A page is for material with an order to it. Onboarding, a spec, a process with steps. People read it when they have time, and it needs headings.
A shared memory is for the short rules a team says out loud. Which category a purchase goes under. That the Keller account is always addressed to Priya. That the weekly note leads with signups. These rarely earn a page, so they live in people's heads, and they leave when those people go on holiday.
The mistake is forcing one into the other. A wiki full of one-line rules becomes a junk drawer nobody searches. A memory holding a twelve-page policy turns into guesswork. Keep each in its place and let one assistant read both.
The page that fell behind
Answered, with the stale line flagged.
Nadia Haddad9:14 AM
@Cedric what's our refund window for annual plans?
CedricAPP9:15 AM
30 days. Grace saved that for the workspace on 12 September. The Billing FAQ in Notion (Support / Policies, last edited 4 March) still says 14 days, so the page is behind. I can change that line and leave the rest of the page as it is.
Both sources read
The page for what was written, the shared memory for what was decided since.
The gap named
Which page, which line, and when it was last edited. Checkable in seconds.
The fix proposed
One line changed in Notion, and only after someone says yes.
How Cedric's company brain works
Cedric keeps one memory for the workspace, and every memory is either shared with the team or visible only to the person who made it. The Brain page on the dashboard lists all of them, one line each, with where each was learned. Workspace rules and personal preferences sit above the memories. One click deletes a memory, and a deleted memory stops shaping any later task. The company brain doc covers the privacy rules in full, and teach him once shows the first week of using it.
For the wiki itself, connect it. With Notion connected, Cedric searches the workspace, queries the databases and reads or writes pages. When someone asks a question in the channel, he answers from the page and names where it lives. When a memory or a newer page contradicts an older one, he says so and offers the edit. Every write waits for a yes.
So the wiki gets corrected the moment someone asks the question it answers wrong. Most of the time that is the first moment anyone would have noticed.
An afternoon that fixes most of it
No migration, no new tool for the team to learn.
- 01
Collect the questions people ask in chat
Scroll back through a month of your busiest channel and write down the questions that got answered from someone's head. You will find ten or so, and most repeat.
- 02
Sort each answer into a page or a sentence
If the answer needs headings, it belongs on a page. Check the page exists and says the right thing. If the answer is one sentence, it is a memory.
People often write a page for a one-line rule. Nobody will ever open that page.
- 03
Say the one-line rules to Cedric, once
"@Cedric annual plans get a 30-day refund window. Remember that for the workspace." He asks whether it is for the workspace or only you, then lists it on the Brain page.
- 04
Connect the wiki and ask your ten questions
Ask each question in the channel. Where he cites a page that is wrong, approve the fix he proposes or write it yourself. That is your stale-page list, found in ten messages.
- 05
Put the check on a schedule
"On the first of every month, check the Support pages in Notion against what we decided in #support and list anything that disagrees." He states the job back to you before it exists. See recurring work.
What still needs a person
Someone decides what is true. When two pages disagree, Cedric flags it. He does not pick a winner and silently rewrite the loser.
Structure and permissions stay yours. He edits a page on approval. He does not reorganize the workspace or change who can see what.
The memory keeps durable facts and rules. It is not a transcript of everything said, so a fact nobody taught him and no page holds is still a question for a colleague.
FAQ
Because decisions are made in threads and meetings, and copying them back to the page is a separate task that belongs to nobody. Put the reader and the updater in the same place and the gap closes.
Material people read in order belongs on a page: onboarding, specs, processes. One-sentence rules that change often read better as shared memory the team can ask about.
Yes. He proposes the edit in the thread, names the page and the line, and saves it only when someone says yes.
Shared memories are visible to the workspace on the Brain page. Only-me memories, including what he learns in a direct message, are visible to their owner alone.
No. The pages stay where they are. Cedric reads them where they live and keeps the one-line rules in his own memory.
100,000 free credits, no card. Connect Notion and ask the question people keep asking in chat.