Back to Blog Home

How to Structure Internal Knowledge Base: The Ultimate Guide

How to Structure Internal Knowledge Base

Build your internal knowledge base from the questions your teammates keep asking, and set the top-level folders to match your team structure: Company, Human Resources, Marketing, Sales, Customer Support, Product, Design and Engineering.

What should be included in the internal knowledge base?

  • What are the things that everyone in your team should know? Those are usually the things that you will walk through new hires when they first join your company. These likely include company mission, employee guidelines such as holiday policy and office essentials such as wifi password.
  • What are the frequently asked questions in the team? The best way to keep building your team knowledge base is to add information whenever a teammate asks a question that the knowledge base cannot answer yet.
  • Team guidelines and best practices: for example, to help sales reps close more deals, share the sales playbook, demo best practices and scripts, email templates, and sales reviews covering key customer pain points and how your product solves them, common objections and lost reasons.
  • Team meeting notes: keep meeting notes in the knowledge base too, so teammates can look up what was discussed, the decisions made and the rationale behind them, and the action items they need to follow up.

For more ideas on what to document, see Kipwise’s use cases page or our template gallery.

How to structure your internal knowledge base

We believe the best way to structure your internal knowledge base is to set the top folders according to your team structure (you can take out your organizational chart to use it as a reference). Not only does it make the navigation easy to follow, it also makes setting permissions (i.e. who can view and/or edit content inside those folders) much easier.

Generally, we recommend companies to start with these top level folders:

  • Company
  • Human Resources
  • Marketing
  • Sales
  • Customer Support
  • Product
  • Design
  • Engineering

Then divide each top-level folder by the functions of that team.

Treat the sample sub-folders below as a menu. A knowledge base built from real questions has the right shape, while one built from a template fills up with empty folders that make the whole thing look unmaintained. We recommend creating a sub-folder only when the third page for it appears.

Most team folders end up with the same four sub-folders: a welcome folder (how the team is structured, its onboarding items and how it works with the rest of the organization), goals and stats (quarterly and monthly goals plus the documents that track progress), a tech stack folder (the tools the team uses and how each is used) and meeting notes.

Internal knowledge base examples: sample structure and templates for each functional team

Marketing Team

For example, for marketing, you can further divide the top level folders into

  • Welcome to Marketing: How the marketing team is structured, its onboarding items and how it works with the rest of the organization.
  • Marketing Team Goals and Stats: Quarterly and monthly goals, plus the documents that track progress and performance.
  • Marketing Tech Stack: An overview of the tools the team uses, with a doc on how each is used.
  • Style Guides & Marketing Assets: Include style guides and useful marketing assets such as videos, visuals, logos, customer testimonials, etc. to help your marketing team craft better and more consistent messages and copies.
  • SEO: Include things related to SEO such as keyword research, strategies and tactics, etc.
  • Content Marketing: Include content calendar, drafts for blog posts, whitepapers and any tips and skills that your content marketers should know.
  • Website Pages: Include landing page drafts, A/B testing plans, etc.
  • Outbound Marketing: Include strategies and planning, campaign docs, etc.
  • Marketing Team Meeting Notes: Notes for internal meetings.

Sales Team

Then for sales team, sub folders that you can create include:

  • Welcome to Sales: How the sales team is structured, its onboarding items and how it works with the rest of the organization.
  • Sales Team Goals and Stats: Quarterly and monthly goals, plus the documents that track progress and performance.
  • Sales Tech Stack: An overview of the tools the team uses, with a doc on how each is used.
  • Sales Processes: Explain how the sales process works at your organization, e.g. include docs to explain how you qualify leads, what to do as a deal move through the sales process and how to document learnings along the way.
  • Market Overview
  • Customer analysis: Include documentation to help your sales reps understand the ideal customer profile and their usual pain points
  • Competitor analysis: Include an overview of the competitor landscape and include individual docs for each of the major competitor
  • Pitch Resources
  • Demo scripts and email templates: Include sample scripts for demos and email templates for different stages to help your sales close more deals.
  • Sales decks: Use this folder to ensure all sales reps have the most up-to-date and accurate sales decks.
  • Battle Cards: Include battle cards such as competitive battle cards, tips to handle objections to help increase win rates.
  • Sales Call Notes: A centralized place to house your sales call notes so managers can review and share learnings accordingly.
  • Sales Team Meeting Notes: Notes for internal meetings.

Customer Success Team

For customer support team, some recommended sub-folders include:

  • Welcome to Customer Success: How the CS team is structured, its onboarding items and how it works with the rest of the organization.
  • CS Team Goals and Stats: Quarterly and monthly goals, plus the documents that track progress and performance.
  • CS Tech Stack: An overview of the tools the team uses, with a doc on how each is used.
  • User Onboarding: Explain how the user onboarding process works for your product, how to identify users who are at risk and need more help with useful resources such as demo scripts and email templates.
  • Support Processes: Explain how the support process works at your company. Such as how to determine priority and how to report issues and file feature requests from clients.
  • Product FAQs: Include canned responses for questions that are frequently asked by your customers.
  • Troubleshooting Guides: Include guides to help customer troubleshoot issues in your product.
  • CS Team Meeting Notes: Notes for internal meetings.

Product Team

For product team, consider creating the below sub-folders:

  • Welcome to Product: How the product team is structured, its onboarding items and how it works with the rest of the organization.
  • Product Team Goals and Stats: Quarterly and monthly goals, plus the documents that track progress and performance.
  • Product Tech Stack: An overview of the tools the team uses, with a doc on how each is used.
  • Product Roadmap: Include an overview of what is planned for your product with more detailed docs for short term roadmaps.
  • Product Requirements Docs: Gathering all your product requirements docs in one place helps your team find the requirements of planned features more easily.
  • Sprint Planning + Retrospectives: This is the home for your sprint planning docs plus the take-aways that you get from your sprint retrospective meetings.
  • Feature Launches: Include templates for launch checklists so your team won’t miss any important steps for feature launches.

Design Team

For design team, these are some sub-folders that you can create:

  • Welcome to Design: How the design team is structured, its onboarding items and how it works with the rest of the organization.
  • Design Team Goals and Stats: Quarterly and monthly goals, plus the documents that track progress and performance.
  • Design Tech Stack: An overview of the tools the team uses, with a doc on how each is used.
  • Style Guides and Design Assets: Include style guides and useful design assets such as frequently used visuals, logos, etc. to help your design team maintain a consistent branding in their design.
  • Design Projects: Include planning and notes for your design projects.
  • Design Team Meeting Notes: Notes for internal meetings.

Engineering Team

For engineering team, sample sub-folders include:

  • Welcome to Engineering: How the engineering team is structured, its onboarding items and how it works with the rest of the organization.
  • Engineering Team Goals and Stats: Quarterly and monthly goals, plus the documents that track progress and performance.
  • Engineering Tech Stack: An overview of the tools the team uses, with a doc on how each is used.
  • Engineering Processes: Explain how the different processes such as code reviews, QA testing, deployment work in your company.
  • Engineering Retrospectives: Document learnings that are shared in your engineering retrospective meetings.

Human Resources

For HR team, some common sub folders are:

  • Welcome to HR: How the HR team is structured, its onboarding items and how it works with the rest of the organization.
  • HR Team Goals and Stats: Quarterly and monthly goals, plus the documents that track progress and performance.
  • HR Team Tech Stack: An overview of the tools the team uses, with a doc on how each is used.
  • HR Processes: Explain how the different processes such as hiring, payroll handling, employee benefits work in your company.
  • HR Team Meeting Notes: Notes for internal meetings.

Company-wide

Other than having a top level folder for each functional team, it’s useful to have a company-wide folder to house important information that everyone should know:

  • Meet The Team: Include items such as how your team is structured and each individual teammate’s profile to help new hires get to know your team better.
  • Company Mission and Visions: Share your company mission statement to make sure everyone is aligned. You can also include any interesting stories of how the company was started, etc.
  • Founders / CEO Updates: Here you can gather all the monthly/quarterly updates by management so your teammates can refer to them easily.
  • Important Announcements: This is the home for any important announcements that the whole company should know.
  • Company Tech Stack: An overview of the tools the whole company uses, with a doc on how each is used, such as your chat tool, video conference tool and holiday management tool.
  • New Hire Onboarding: Share the general onboarding plan and onboarding checklist templates to help managers onboard new employees more efficiently.
  • Employee Handbook: Company policy, overview of employee benefits, useful forms, etc.
  • Office Essentials: Include common office FAQs such as wifi password, mailing address, how to use the coffee machines/printers, etc.
  • All-hands Meeting Notes: Notes for internal meetings.

Keep processes that cross teams in one place. A feature launch, for example, involves product, marketing, sales and customer success, so give it a single page with one named owner in the folder of the team that runs it and link to it from the others, rather than copying it into four team folders where the copies drift apart.

Folders with limited access for some sensitive topics

Most team folders can be shared with the whole team or even the whole organization, but sensitive topics need private folders, shared with only a few teammates. These might include:

Best practices when writing internal knowledge base articles

Use numbered headings and subheadings

Divide each article into sections with headings and subheadings, and number them (for example “A, B, C…” in front of Heading 1s and “1, 2, 3…” in front of Heading 2s). Structured headings make an article easy to scan, and many internal knowledge management tools, Kipwise included, generate a table of contents from them automatically. Numbered headings also let you point a teammate to a specific place when answering a question, such as “see point A2 of this documentation”.

Include keywords to optimize search

Besides a naming convention for article titles, include the keywords your teammates are likely to search for, synonyms included. When a teammate searches for a term and finds nothing, add that term to the article that should have matched.

Related posts

Your team’s knowledge, answered in Slack

Add the Kipwise Agent. It answers from your pages with the source, and asks before it changes anything. 7-day trial, no card needed.