Skip to content
Bevean TownSmart Office

A good manager answers the same question only once

"How do I request a reimbursement?" "What’s the Wi-Fi password in the meeting room?" "Who approves software purchases?" The same person answers the same questions several times a week. They’re kind, but every answer interrupts what they were doing. And when they go on vacation, the questions go unanswered.

The team doesn’t ask out of laziness. They ask because the answer isn’t anywhere they know of.

What an internal knowledge base is

An internal knowledge base is the place where the answers the team needs day to day live: processes, policies, rules, contacts and the way things get done. It works when it’s the first place someone looks, not the last.

Six practices help build one like that.

1. Start with the questions that repeat

Don’t start by writing a complete manual. List the questions that come in most, in channels, direct messages and hallway conversations. Each repeated question is a page to write. That way, the knowledge base is born useful, because it answers what people really look for.

2. Write for whoever is searching

Use the words people use when they ask. "How do I request time off?" is a better title than "Paid leave policy". Short answers, with the step by step and what to do when something is out of the ordinary, work better than long texts.

3. One topic, one place

If the same information appears in three documents, they’ll soon say different things, and nobody will know which one counts. Each topic should have a single page. Other places point to it instead of copying it.

4. Give each area an owner

Every knowledge base ages. Define who looks after each area, such as finance, HR or tools, and agree on a review from time to time. A page with an owner stays trustworthy. A page with no owner ends up ignored, and with it the whole knowledge base.

5. Make the knowledge base the first place to check

When someone asks something that’s already in the knowledge base, reply with the link. It seems small, but that’s how the habit changes. And make search easy: if finding the answer is harder than asking a colleague, people will keep asking.

6. Use unanswered questions as an agenda

Each question that found no answer shows what’s left to write. Track those gaps and turn the most frequent ones into new pages. Over time, the knowledge base grows toward what the team needs, and it also keeps the knowledge that would otherwise walk out the door with whoever leaves.

Why many knowledge bases get abandoned

The ones nobody uses tend to have the same problems:

  • They were written all at once. A big initial effort and, after that, no updates.
  • They sit far from the work. Consulting means leaving what you’re doing and going to search.
  • Nobody knows if they’re up to date. One wrong piece of information makes the team distrust all of it.
  • Search finds nothing. If you need to know the exact name of the document, it’s faster to ask.
  • Nobody knows what’s missing. The questions left unanswered never reach whoever writes.

Checklist: the knowledge base the team uses

Use it to build or review your team’s knowledge base:

The content

The upkeep

The use

How this looks in Bevean Town

In Bevean Town, the knowledge base lives in the same office where the team chats and works.

  • Team pages: Notes holds processes, policies and manuals, with Procedure, Policy and Onboarding templates, comments and version history. From the Town plan up, teams write together in shared Notes spaces.
  • Search that finds: Notes search finds a title or a piece of the text, ignores accents and capitalization and shows only the pages the person can read.
  • A question instead of an interruption: on the Capital plan, when the office turns on the Assistant, the team asks in natural language and gets the answer with its sources, from the knowledge base built by whoever administers, which can include pages, links and files.
  • Who sees what: each source in the Assistant’s knowledge base can apply to the whole office or only to some teams.
  • What’s missing, in view: on the Assistant’s Quality tab, whoever administers sees the questions left without a source and the answers the team rated badly, to know what to write next.

Create yours now, free for up to 3 people. In a minute you’ll be talking on the map.

Create my free office

Content

Frequently asked questions

What goes in an internal knowledge base?

Start with the questions that repeat most: processes, policies, rules for using tools and who to go to on each topic. Then add what comes out of the questions that went unanswered.

How do you keep the knowledge base up to date?

Set an owner for each area, agree on periodic reviews and fix the page as soon as someone finds an error. A knowledge base used every day tends to stay up to date.

How do you get the team to use the knowledge base?

Make search easy, use the words of whoever asks and answer repeated questions with the page link. Over time, checking the knowledge base becomes faster than asking.