Skip to content
BENIBIX Learn

Knowledge Silos and Wikis

Level 4 · Notes for a team

Why know-how gets stuck in one team or one head, and what it costs. How a wiki and a community of practice let a group share what it knows.

Course contentsLesson 5 of 6

Level 1 · What you are saving

  1. Tacit and Explicit Knowledge

Level 2 · Taking notes

  1. Cornell Notes and Mind Maps

After this lesson you can

  • Spot a knowledge silo
  • Explain how a wiki is written and kept up
  • Say what a community of practice does

11 mincovers 4 glossary entries

Worth reading first: Zettelkasten Method

Why does a team keep losing what it knows?

Knowledge management is how a group captures, shares and reuses what its people know. Without it, know-how gets stuck in one team or one head. That is a knowledge silo. Other people cannot reach it, so they solve the same problem again, or wait for the one person who knows.

Silos form for ordinary reasons. Teams are busy, writing things down takes time, and each team keeps its notes in its own place. Nobody decides to hoard. The cost shows up later, when the one person who knows leaves, or a customer gets three different answers.

A wiki is a website a group writes together. Anyone allowed in can add or edit pages. The first wiki went online in 1995, and the name is a Hawaiian word for quick. Its strength is that the person who learns something can write it down at once, without asking anyone.

Its weakness is the same freedom. Pages go stale, two pages say different things, and nobody owns the mess. A wiki works when each section has an owner who checks it, and when people are thanked for fixing pages, not just for writing new ones.

A community of practice is a group of people who share a craft, across teams. All the designers in a company might meet once a month, or keep a shared channel. They swap problems and fixes. Much of what passes between them is tacit, which no page could hold.

The two work together. The community is where people learn from each other. The wiki is where the best answers are written down so the next person can find them. Notes alone miss the tacit part. Talk alone is forgotten.

The common mistake is to buy a tool and think the job is done. A shared space nobody writes in is just a new silo. What matters is the habit: when someone answers a question twice, the answer goes on a page.

Walled teams each keep their own notes. A shared place lets each team read and write what the others know.

Worked example

Three offices, one fix

A firm's three offices each spend a week solving the same printer fault, one after another. Nobody knew the others had seen it.

The firm starts a wiki page for every fix that takes more than an hour. In the first year it holds 120 fixes, and repeat faults drop by half.

The words for this lesson4

Check yourself

What usually makes a wiki fail?

Finished this lesson?

Marking it complete also marks its 4 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.