Reading Time: 12 minutes

Quick Answer: Documenting tribal knowledge at work means turning what experienced people know, but have never written down, into a record other people can act on. It works best when someone other than the expert writes it from a conversation, each entry is shaped around the moment it is needed, and a newcomer tests it by doing the task from the page.

When three surgeons at the University of Southern California were filmed teaching a procedure, a 2014 study found they left out about half the action steps and around seven in ten of the decisions. Prompted with structured questions in a follow-up interview, they covered 66 per cent of the steps, against 44 per cent when they recalled the procedure unprompted. Three experts and one procedure make it a small study, but the pattern holds well beyond surgery, and it is the central problem in documenting tribal knowledge at work: the people who know a job best are badly placed to write it down on their own.

Tribal knowledge is the know-how a team runs on that sits with one or two people: which client needs a phone call, the workaround that stops a report breaking, the reason a step exists. The right questions draw it out, and why a wiki alone fails because documents go unused is well covered. Less attention goes to the record itself: who writes it, what shape it takes, how it is tested and how it stays true.

Why Tribal Knowledge Stays in a Few Heads

Concentration is normal, not a failure. Researchers in Brazil estimated how exposed 133 popular open-source software projects were to people leaving: 65 per cent would be in serious trouble if two or fewer key developers left. Open-source software is not a typical business, so treat the figure as a benchmark, but teams that lean on one long-serving colleague look much the same. Four things keep the knowledge there:

  • The expert no longer notices the steps. Practice turns decisions into habit, which is why the surgeons skipped theirs without meaning to.
  • The record keeps the steps and drops the reasons. Without the reason, nobody knows when a step can be skipped, and the document drifts towards what people believe happens rather than what does.
  • It is filed by topic, not by moment. “Client onboarding” is a heading; “when the identity documents do not match” is the moment someone needs help.
  • Asking is quicker than reading. Colleagues go straight to the expert, so the document is never tested.

Documenting tribal knowledge at work has to get around all four, rather than asking the expert to try harder.

A Handover Document or a Working Record

Most organisations meet tribal knowledge at a rushed handover, when the person leaving writes down what they can in their last weeks. A working record is built differently.

 A handover documentA working record
What it starts fromA list of the leaver’s tasksA moment in the work: “when this happens”
Who writes itThe expert, in their last weeksSomeone else, from a conversation the expert corrects
What each entry keepsThe stepsThe steps, the reason and the exception
Where a reader meets itIn a folder they have to go looking forInside the checklist, form or ticket where the moment happens
How it is checkedThe author reads it backA newcomer does the task from it
When it changesWhen the next person leavesWhen the work changes, or when someone still has to ask

The handover document still has a job: access, passwords and open items. It cannot carry judgement. Turning employee knowledge into process documentation people use means building the working record while the expert is still in the role, and treating documenting tribal knowledge at work as normal work, not an exit task.

Documenting Tribal Knowledge at Work, One Entry at a Time

Britain’s safety regulator sets out much the same approach where a bad procedure can cost lives. HSE guidance for major-hazard sites tells employers to base procedures on how tasks are actually done, write them with users from different teams and shifts, have people explain or show the task, ask whether they rely on their own “black books”, and keep safe informal aids rather than ban them. It is safety guidance, not a rule for offices, but it is a useful standard for documenting tribal knowledge at work anywhere.

Write Each Entry Around the Moment It Is Needed

An entry answers the question someone has when they are stuck, so it starts with the situation, not a topic:

  • When: the situation that triggers it.
  • Do: the steps, in order.
  • Because: the reason, so people know when the step matters.
  • Unless: the exception the expert handles without thinking.
  • Ask: the role to go to when the case does not fit.

Keep one moment per entry, so readers find it by recognising their situation.

Let Someone Else Write It, Then Have the Expert Correct It

Talking produces far more than writing. In a study of AI-led interviews, LSE researchers found people interviewed this way wrote 142 per cent more words than people answering in open text boxes, and expert graders rated the interviews at 2.95 where 3 meant an average human interviewer. The sample was recruited online in the United States, on topics outside work, but the lesson carries over to documenting tribal knowledge at work: a colleague or an interviewing agent drafts each entry, and the expert corrects it. Correcting is quicker, and it eases the worry that writing everything down will make them replaceable.

Test It on Someone Who Has Never Done the Task

The only reliable check is watching someone use the entry. Give it to a person who has never done the task, let them work from the page while the expert watches without helping, and note every point where they stop or ask. Each stop is a gap the expert could not see, just as the surgeons could not see theirs. Fix it and test again with someone else. Anything touching money, a customer or a legal duty is signed off by the expert before it goes live.

Keeping the Record True Once It Exists

Records decay faster than they are written. In a survey of 146 software practitioners, mostly at one multinational, 65 per cent rated lack of time to write documentation as an important problem and 69 per cent said the same of missing documentation for new features. Software is not every team, but the pattern holds wherever work changes faster than its pages.

  • Name an owner role for each entry, not a person, so the record would survive a resignation.
  • Change it when the work changes: a new system, client type or rule, not a yearly date.
  • Treat every question still asked as a fault report: the entry is missing, wrong or in the wrong place.
  • Move what repeats into something that runs. A step with the same answer every time becomes a rule, one that needs reading becomes an agent’s instructions, and a whole workflow is split step by step.

Documenting tribal knowledge at work is never finished; a record nobody owns goes stale the day it is filed.

Five Pieces of Tribal Knowledge in One Accountancy Practice

Take a regional accountancy practice of around 220 staff across three offices, where onboarding new clients ran on a checklist and two senior managers’ memory. When it began documenting tribal knowledge at work, each piece was drawn out in conversation, written up by someone else and tested on a trainee.

Piece of knowledgeHeld byWhat the first account left outWhat the newcomer test foundWhere it lives now
Identity checks when documents do not matchThe compliance managerWhich mismatches are routine and which go to a partnerThe trainee stopped at a trust client: nobody was named to sign offAn entry in the onboarding checklist, owned by the compliance role
Getting records from the previous accountantA senior managerWhich firms answer a letter and which need a phone callThe trainee did not know a call was normalAn agent drafts every chase; a person decides when to call
Engagement letters for farming and landlord clientsA partnerWhich clauses change for these clients, and whyThe trainee could not tell which template appliedTwo templates, each with its reason written in
First deadlines for clients with unusual year-endsThe client services leadThe system defaults to the most common year-endThe trainee accepted the defaultA practice-system rule that flags the default
Who at the client approves the accountsThe client managerSome clients have one contact who signs and another who gets copiesThe entry named one contact where the client had twoA field on the client record, confirmed at the first meeting

Two pieces stayed as written entries. The year-end check became a system rule, the approving contact became a field, and the chase for old records became an agent with a savings record. The agent drafts every chase and a person decides when to phone, because the senior manager’s habit of calling was the part nobody thought to mention. The same entries now serve every office.

Where to Start Documenting Tribal Knowledge at Work

Six habits make the first month work:

  • Start small. Pick a single team and the moments in its week that only one person can handle.
  • Explain first. Set out the purpose before anyone is interviewed: a record, not a judgement of anyone’s work.
  • Talk first. Capture each conversation by voice or chat, not with a blank template.
  • One moment per entry. Use the same five parts every time.
  • Test before filing. Every entry goes to a newcomer before it is stored.
  • Look in private places. Ask what sits in black books and personal AI chats, and move what matters somewhere the business owns.

Where GrowthNation Fits

GrowthNation interviews each team by voice or text, in confidence, so experts talk rather than write, about the work they actually do. The repeatable parts become agents that GrowthNation serves centrally, so the knowledge each one carries stays with the organisation rather than in one person’s account. It then tracks the hours each agent saves and rolls them into an organisation-wide figure, so the effort shows up as time returned, not pages written.

Test One Expert’s Know-How on Someone New

Documenting tribal knowledge at work starts with one person the team cannot do without. Ask what they handle that nobody else can, then give the answer to someone new and watch where they stop. Every stop is something only one head holds.

Book a walkthrough and GrowthNation will hand you three things:

  • The moments in one team’s work that only one person can handle
  • Each one written as an entry and tested on someone new
  • A working agent on the entry that repeats most often

Every agent built from those entries is measured against what the work took before, month by month.

Book a walkthrough: one expert heard, every entry tested, one working agent.

Join the GrowthNation waitlist. Organisations join in batches, so a place now means your first team’s know-how is written down in the next round.

Frequently Asked Questions

What is tribal knowledge?

Tribal knowledge is the know-how a team depends on that sits with one or two people and has never been written down: the workarounds, exceptions, reasons behind steps and contacts who get things fixed. It passes on by asking or watching, so it disappears when those people move on.

How do you start documenting tribal knowledge at work?

Start documenting tribal knowledge at work with one team. Find the moments only one person can handle, draw each out in conversation, and have someone other than the expert write it as a short entry: when, what to do, why, the exception and who to ask. Test each entry on a newcomer before filing it.

What is the difference between tribal knowledge and institutional knowledge?

Institutional knowledge is everything an organisation knows, written or not. Tribal knowledge is the unwritten part held by a few people. Tacit knowledge overlaps both: know-how that is hard to put into words at all, which usually takes conversation and observation to surface.

Is “tribal knowledge” still an acceptable term?

Some organisations and style guides now prefer “institutional knowledge”, “team knowledge” or “undocumented knowledge” because of the word’s cultural connotations. The older phrase is still widely used and searched. Use whichever term your staff are comfortable with; the method is the same.

Who should write tribal knowledge down?

Someone other than the person who holds it. Experts skip steps they no longer notice, and writing takes time they rarely have. A colleague or an interviewing agent drafts each entry from a conversation, the expert corrects it, and a newcomer tests it.

How do you keep tribal knowledge documentation up to date?

Give every entry an owner role, change it whenever the work changes rather than on a fixed date, and treat each question still asked as a sign the entry is missing, wrong or misplaced. Remove what no longer applies, and move steps that never vary into rules or agents.