Featured
The Library of Alexandria began with a simple idea: gather knowledge in one place so people can find it, trust it, and build on it.
Your organization already has the raw material. Policies, training notes, past decisions, support answers, and years of experience sitting in people's heads. What it usually lacks is a shelf — somewhere a person can look and find a reliable answer without asking a colleague first.
A library is just shelves. You don't need to organize everything at once — you need to build one shelf properly, then the next. This guide walks through the first one, using a single example the whole way: onboarding new employees.
Step 1: Choose One Shelf
Pick one area where people lose time or ask the same question every week. Onboarding, customer support, internal policies, product knowledge, daily operations — any of them works, as long as you choose only one.
New employees keep asking what they need to finish in their first week, so onboarding is the first shelf.
Before you collect anything, finish this sentence:
This shelf should help people __________.
For our example: This shelf should help new employees complete everything expected of them in their first two weeks without asking a colleague.
That sentence decides what goes on the shelf and, just as importantly, what stays off it.
Step 2: Start With Questions, Not Files
Most knowledge systems are organized around documents. People arrive looking for answers.
So write down the questions first. For onboarding, the list might be:
- Which forms do I need to complete, and by when?
- How do I request time off?
- Who do I contact for technical support?
- What should I finish in my first week?
- Where are the company policies?
Five questions, and you know exactly what has to go on it.
This list does something else too: it exposes gaps. If nobody in the company can give a clear answer to one of these, that knowledge was never written down. You've just found the most valuable thing to create.
Step 3: Keep Only What You Can Stand Behind
Now go find the best source for each question. Policies, internal guides, training material, meeting notes, a recorded walkthrough, an old FAQ.
You will usually find more than one candidate. The time-off question might return an HR policy PDF, a Slack thread, and a slide from last year's orientation deck. Only one of them is current and approved. That one goes on the shelf; the rest come off.
Then give each item enough context to be trusted:
- What does it cover?
- Who is it for?
- When was it last reviewed?
- Who keeps it current?
- Is this the approved version?
Five documents with that context are worth more than fifty without it. This is the line between a file folder and a library.
Step 4: Write Down What Only People Know
Some of the most useful knowledge here has never been written down anywhere.
The person who has onboarded twenty new hires knows which form always gets rejected the first time, which system access takes three days to arrive, and what everyone misunderstands in week one. None of that is in the policy document.
Ask them:
- What do people ask you again and again?
- What do new hires only learn after getting it wrong?
- Which step is missing from the official process?
- What would be hard to replace if you left tomorrow?
Turn the answers into a short "things nobody tells you" note. It takes twenty minutes to write and often becomes the most-read page in the library.
Step 5: Test It With Someone Who Doesn't Know the Answer
A library works only if a stranger can use it.
Hand your five questions to someone who wasn't involved in building it — ideally an actual new hire — and watch. Don't help.
Can they find each answer? Can they tell it's current? Do two different people land on the same answer? Do they still end up messaging a colleague?
Wherever they hesitate, you've found the next thing to fix: a confusing label, an outdated file, or an answer that was never there. Success isn't how many documents you collected. It's how fast someone gets to the right answer.
Keep Building
Any of this goes stale. Processes change, policies get updated, new questions appear. Give each knowledge area an owner, review it on a schedule, and watch the questions people still have to ask — they tell you which shelf to build next.
This is where a platform like Metance helps: it holds different kinds of content together, lets people search with the questions they'd actually ask, and links every answer back to its source. It makes the library easier to use, but the library still gets built the same way — one purpose, real questions, sources you can vouch for, and someone responsible for keeping them true.
You can start in under an hour. Take one question people keep asking. Find the three best sources. Remove the outdated ones. Add a line of context and a name next to it.
Then ask a colleague to find the answer without your help.
That's your first shelf.
