Knowledge management for scaling companies

At 50 people, you ask the person sitting next to you. At 500, you do not know who to ask, and the person who does know has already answered that question four times this week.

Somewhere between those two numbers, knowledge sharing breaks. It breaks quietly: the product still ships, customers still get answers. But onboarding stretches from weeks to months, the same questions circle back, and decisions wait on the calendar of whoever holds the context.

The moment it breaks

No milestone announces it. The signs are consistent, though:

• The first remote colleague, or the second office. Answers that used to travel across a desk now have to travel through a system, and there is no system.
• The first departure that hurts. Employee number 12 leaves, and with them the only accurate picture of how billing really works. Knowledge walks out with people unless it is captured before the notice period.
• The same question, asked in chat for the third time this month, answered from memory each time, slightly differently each time.

Each sign looks minor. Together they mean that asking around, the system that got you to 50 people, has stopped scaling.

Why asking around stops working

Asking scales with the number of askers. Answering does not. Your ten most experienced people become the bottleneck: interrupted hourly, repeating themselves, doing their own work in the gaps.

The habit also hides its own failure. Every answered question feels like proof that the system works, while the cost lands elsewhere: on the expert's focus, on the new hire who waited a day to unblock, and on the answers that quietly diverge as each retelling drifts.

The cheap window

The price of fixing this rises with headcount, and scaling companies underestimate how fast.

At 100 people, building a writing habit costs little. There are few documents, the owners are obvious, and the culture still bends. At 500, the same change is a programme with a budget, a rollout plan and years of scattered content to untangle.

Eura Nova grew fivefold on one knowledge platform without a single migration, because it made the decision early. What that avoided never shows up as a number, which is exactly why so few companies do it: the migration you never ran, the habit you never had to rebuild.

What to put in place before 200 people

Not a knowledge department. Four habits:

1. One platform, one space per team. Each team owns what it knows; everyone searches in one place. Adding a team means adding a space, not a tool.
2. An owner and a review date on every document. Content without an owner rots, and expiry dates turn "is this still true?" from a guess into a property.
3. Write once, send the link. When a question arrives in chat, answer it in the document, then send the link. The second asker gets the same answer; the expert never types it again.
4. Onboard from the real source. New hires read the same documents the team uses, not a separate wiki that started drifting the day it was written. If your procedures need a rewrite first, start here.

Is a wiki enough?

At 80 people, often yes. A wiki stores pages, and stored pages may be all you need.

It stops being enough when the question changes from "where is the page?" to "is this page still true?". A wiki has no owners, no review cycle and no way to tell current from stale, so trust erodes page by page, and people go back to asking around. That is the point where a knowledge platform earns its cost: it manages the lifecycle, not the storage.

If you are past the point where asking around works, book a demo. Bring your five most-asked questions, and we will show you what they look like with one owner each.