Most advice on internal knowledge bases is written for companies with a department that owns documentation. If you run a team of five to fifty, nobody does, so the knowledge base has to be small, current and easy to add to, or it will be dead within a month.
What a small team's knowledge base is for
Its one job is to stop the same question from being answered twice. If a page does not answer a question someone actually asked, it does not belong. The Nielsen Norman Group says the same about FAQs: use the real questions of real users, and treat recurring questions as a signal of what is missing.
Practice 1: Organize by the questions people ask
Name each page after the question, in your team's words: 'Can I expense a client dinner?' not 'Expense policy v3'. People search with the question in their head.
Practice 2: One owner and a review date on every page
Helpdocs recommends one accountable person per article, not a team, because when everyone shares ownership no one notices when content goes wrong, and a review date on every article so no one has to remember when to check it. We would add a second date: when the answer was last confirmed.
Practice 3: Delete the old version
Helpdocs makes two points we agree with. Outdated content does more damage than missing content, because a missing answer sends someone to ask a colleague while a wrong one is trusted and acted on. And keeping an old page 'just in case' leaves two conflicting answers where neither a person nor an AI assistant can tell which is right.
Practice 4: Make adding an answer take two minutes
If adding an answer takes more than a couple of minutes, people will not do it. Use one short template: question, answer in one or two sentences, owner, last confirmed, check again by, who can see it. Our free team FAQ builder at askmystartup.com/team-faq-builder uses that template and exports Markdown, in your browser.
Practice 5: Set access in three levels
Helpdocs suggests three tiers: company-wide, department-specific, and a small restricted group for sensitive material such as compensation and security. Decide the level when you write the page, not after someone asks.
Practice 6: Check whether the same questions still come back
The test of a knowledge base is not how many pages it has. It is whether the questions stop. Each week, note which questions reached you again. A repeat means the answer is missing, wrong or hard to find, and each case has a different fix.
A starter plan for week one
- Write down every question you answer for five working days.
- Pick the ten that came up most and write one answer for each, with an owner and dates.
- Share the list with the team and ask them to look there first.
- At the end of the week, count which questions still reached you, and fix those pages first.
Where an AI clone fits
When the answers are written this way, a bot can answer from them and show the source and date, and say it does not know when nothing matches. AskMyStartup is built around that: the founder approves each answer, and the clone answers only from approved ones. It is in private beta, and you can join the waitlist from the box on our home page.
Related guides
Common questions
Start with ten answers to the questions asked most this week. Add one every time a question comes back.
No. A shared document or a simple wiki works if every page has an owner, a date and a question for a title. The habits matter more than the tool.
Put a review date on every page, give each page one owner, and delete the old version when a rule changes.
Let anyone suggest an answer, but have the owner approve it, so people can trust what they read.
Sources
- Helpdocs: How to create a knowledge base for employees: helpdocs.io
- Nielsen Norman Group: FAQs Still Deliver Great Value (Susan Farrell, December 2014): nngroup.com
Each page was opened and read on October 20, 2026. Our own numbers come from the honesty test page.