KnowledgeCapital

KnowledgeCapital › Docs

What setting up really takes: half a day

Start knowledge management from a blank space: the order of the steps, what you get at the end, and the example followed from start to finish.

In short. This guide takes a blank space from your first click to day-to-day running, screen by screen and in the order you meet them. A single example runs through it, Atelier Nord, small enough to type in by hand. Allow half a day for a first department, and no technical skills.

This guide takes you from your first click in a blank space to the day-to-day running of the system: every button, every field, in the order you come across them, with a screenshot taken at the exact moment you will see each screen. The numbered orange frames on the screenshots (1, 2, 3…) are referred to by the same numbers in the text.

What you will have once setup is complete. Your org chart, your people, your first knowledge items named in your own words, the tasks that require them, and a map that already shows — with figures to back it up — the knowledge you cannot afford to lose. Then your SharePoint, DMS, Notion or intranet documents connected to it. Allow half a day for a first department; no technical skills are needed.

Why a blank space is disorienting

The demo space is full: hundreds of people, dozens of knowledge items, years of history. You grasp the logic in ten minutes. Then you open your own space and everything looks different: the lists are empty, the add buttons sit alone on the page, the drop-down lists offer nothing, the system status is orange. It is the same product, just not yet filled with your data. But an empty screen does not look like a full one — that is exactly where people get lost, and it is why every step of this guide was redone on a genuinely blank space.

The rule that explains almost everything. When a drop-down list is empty, a previous step has not been done: no structure → nothing to choose in “Attachment”; no position → nothing in “Position”; no skill → nothing in “Grouped under”. Go back one step: nothing is broken.

The example: Atelier Nord

A single example runs through every page. It is small enough to type in by hand, and realistic enough to show the risk the system is designed to reveal:

WhatWhat this guide creates
Org chartAtelier Nord (North Workshop), with two departments under it: Maintenance and Production
PositionsResponsable maintenance (maintenance manager) · Technicien de maintenance (maintenance technician) · Chef d'équipe (team leader) · Opérateur de ligne (line operator)
PeopleAwa Diallo (maintenance manager, 38 years in the trade, born in 1964) · Karim Benali (technician) · Sofia Rahal (team leader) · Youssef El Amrani and Léa Martin (operators)
SkillsMaintenance des presses (press maintenance) · Conduite de la ligne (line operation)
Knowledge itemsRedémarrage de la presse P-12 après arrêt d'urgence (restarting press P-12 after an emergency stop) · Réglage du couple de serrage des matrices (setting the die clamping torque) · Diagnostic du bruit anormal du réducteur (diagnosing abnormal gearbox noise) · Changement de format de la ligne 2 (line 2 format changeover) · Contrôle qualité au démarrage de série (quality check at the start of a production run) · Consignation électrique avant intervention (electrical lockout before any work)
ProcessesMaintenir les presses (maintaining the presses, 2 tasks) · Conduire la ligne 2 (running line 2, 2 tasks)
What the guide will revealOnly Awa has mastered restarting P-12, and she is nearing retirement. Nobody had written it down; the map will show it.
Your names instead of ours. Every screen accepts your structures, your people and your knowledge in place of Atelier Nord. If you would rather rehearse first, keep the example: you can then reset the space (next page) without losing your account or your progress in the academy.

The order, and why it is not negotiable

1
The org chart — everything else is attached to it.
2
Positions, then people — without people, a mastery level has no one to measure.
3
The repository: skills, then knowledge items — without them, there is nothing to assess.
4
Processes and their tasks, and what each task requires — this is what makes a knowledge item relevant.
5
Mastery: who knows what, from 0 to 5 — the only data the machine cannot invent.
6
Objectives and the criticality grid — what tells you why a knowledge item matters.
7
Accounts, then the validation circuit and test campaigns — once there is something to see.
8
Connectors — once there are knowledge items to link your documents to.

Skipping a step saves no time: it comes back two screens later, in the form of an empty drop-down list.

What to have on hand

Read the guide in order. The second half — day-to-day running, situations and what to do, tests, keeping the repository up to date, AI and reporting — is what you will use every day after that.

Half a day for a first department.By the end: your org chart, your people, your first knowledge items named in your own words, and a map that already shows what you cannot afford to lose. The trial lasts 14 days and asks for no card. Start a free 14-day trial (no card needed) or request a demo.

See also: Step 0 — Getting your blank space, signing in, securing your account · Step 1 — The org chart, starting from a single structure · End of setup: the check, line by line · How to build a knowledge management system from scratch

Frequently asked questions

Where do you start when mapping your organisation's knowledge?

With the org chart: everything else is attached to it. Then come the positions and the people, the repository, the processes and their tasks, then mastery.

How long does it take to set up a blank space?

Allow half a day for a first department. No technical skills are needed.

What should you prepare before you start?

The list of your departments, the people of a first department with their positions (an Excel export from HR works as is), and five to ten knowledge items per department, named in the words of the trade.

Docs