How to Build an Onboarding Knowledge Base

The onboarding problem

New hires spend their first weeks asking the same questions: How does this process work? Who should I talk to about X? Where is the documentation for Y? Every person they ask takes 10 minutes away from their own work. Multiply that by every new hire, every year.

An onboarding knowledge base captures all of that tribal knowledge in a structured, queryable format. The new hire asks the AI instead of interrupting colleagues. The AI reads the wiki and gives specific, contextual answers. When the new hire discovers something not in the wiki, they add it — and the next person benefits.

What goes in an onboarding knowledge base

Company overview. What the company does, who the customers are, how the business model works, what the strategy is. Written for someone who just joined, not for investors.

Team structure. Who is who, what each team does, who to go to for what, and how teams work together. Include communication norms: when to Slack vs email vs meeting.

Tools and systems. Every tool the company uses, what it's for, how to get access, and where to find help. Include the unwritten knowledge: which Slack channels actually matter, which meetings are optional, which dashboards to check.

Processes. How things actually get done. Not the official process doc from 2 years ago — the real way things work today. How to submit an expense report. How to request time off. How to deploy code. How to get a decision made.

Role-specific playbooks. Different sections for different roles. What a new engineer needs to know is different from what a new marketer needs. Each role gets its own playbook with first-week priorities, key contacts, and "things I wish I knew on day 1" from people in that role.

Culture and norms. The unwritten rules. How decisions get made. How conflict is handled. What "good work" looks like here. This is the hardest section to write and the most valuable one for new hires.

Before building an onboarding wiki, run the AI team assessment to understand where your team stands. Then use our change management playbook to roll out AI tools alongside the knowledge base.

The CLAUDE.md schema for onboarding

# [Company Name] Onboarding Wiki
# Version: 1.0

## Purpose
Everything a new hire needs to get productive at [Company].
Queryable, structured, and maintained by the team.

## Structure
- /Sources — Raw onboarding docs, process descriptions, team notes
- /Wiki — Compiled, interlinked onboarding articles
- /Queries — Questions new hires ask + answers

## Categories
- Company (overview, strategy, customers, business model)
- People (team structure, key contacts, org chart)
- Tools (systems, access, setup guides)
- Processes (how things get done)
- Roles (role-specific playbooks)
- Culture (norms, values, unwritten rules)

## Article Format
- H1 title
- "TL;DR" (3-sentence summary for quick reference)
- Body with H2 sections
- "Pro tips" section (advice from tenured employees)
- Last updated date
- Related articles with [[wikilinks]]

## Rules
1. Write for someone who started today
2. No jargon without explanation
3. Include the REAL process, not the official one if they differ
4. Every article must have a "who to ask" contact
5. Flag anything older than 6 months for review
6. New hires should add things they had to figure out themselves

How new hires query it

"I'm a new [role] starting this week. What should I focus on in my first 5 days? Who should I meet with and why?"

"How do I get access to [tool]? What's the process and who approves it?"

"I need to [do specific task] for the first time. Walk me through the process step by step."

"Who should I talk to about [topic]? What team owns this and who's the point of contact?"