Institutional Knowledge at Your MSP: Get It Out of One Head
Institutional knowledge, which many MSP owners call tribal knowledge, is what your MSP knows that nobody wrote down: client quirks and when a ticket goes up a tier. If one senior tech holds most of it, their resignation takes your training program with it, and every new hire pulls them off the queue. The fix: list what only they know, record real work, turn it into SOP lessons, put those in a role path and check who finished.
The steps below work with a phone, a screen recorder and the ticket reports your PSA already gives you.
The Short Version
- Institutional knowledge, often called tribal knowledge, is the know-how your MSP runs on that exists only in people's heads.
- When one senior tech holds most of it, the desk slows down whenever they are out, and every new hire's training lands on them.
- Capture it in five steps: pick workflows from your ticket data, record real work, turn recordings into SOP lessons, build a role path and check who finished.
- Keep shadowing for judgment on live tickets, and have the senior tech sign off once a new hire finishes the path.
What Is Institutional Knowledge at an MSP?
Institutional knowledge at an MSP is the know-how your service desk runs on that lives in people's heads. Your documentation may hold the steps of a process, but rarely the why and the when around them: why one client's tickets always go to the same tech, and when the quick fix is the wrong call.
Someone on your desk knows that a client's line-of-business app needs a workaround after every update, and which vendor support path gets a real answer instead of a case number. They know when a ticket is Tier 2 work and when it is a project, and how a client's owner wants to hear about an outage. Some of that sits in a doc nobody can find. The rest sits in one person's memory. "Tribal knowledge" is the same idea; the FAQ at the end sorts out the terms.
What Happens When One Senior Tech Holds the Know-How?
Your desk runs on one person's calendar: when they are out, the tickets that need them stall. Tickets that bounce between techs or keep escalating show you which work only a few people know.
People also leave. In January 2026, the median US wage and salary worker had been with their current employer for 4.1 years, and the median for workers ages 25 to 34 was 3.0 years, according to the Bureau of Labor Statistics. Even a loyal senior tech takes vacations and gets offers.
A 2018 survey of US workers at companies with 200 or more employees (not MSPs), run by the software company Panopto with YouGov, found that 42 percent of institutional knowledge is unique to the individual. When that person is out, coworkers cannot do that part of the job, the report says.
Training lands on the same person. Your best troubleshooter becomes your only teacher, and the queue pays for it. Each hire is taught from memory, so no two hires come out of it knowing the same desk.
| In One Head | When They're Out | Where It Should Live |
|---|---|---|
| Client quirks | Tickets stall or bounce | Client SOP lesson |
| When to escalate | Wrong tier works it | Escalation SOP and quiz |
| Vendor support paths | Someone hunts for them | Doc linked in a lesson |
| Workarounds | Solved again from scratch | Short video lesson |
| How the desk runs | Each hire learns it another way | Role path with due dates |
Why Doesn't Shadowing Alone Transfer Knowledge?
Shadowing passes on whatever comes up while the new hire is watching. Rare ticket types may never appear in those weeks. Nothing gets recorded either, so the next hire starts from zero and the senior tech teaches it all over again.
Shadowing is still the best way to teach judgment on a live ticket, such as when to call the client instead of sending another email. Keep it as the last step, the sign-off, once the basics are in lessons. For a side-by-side look at the tools, see our comparison of Empath and shadow training.
How to Capture Institutional Knowledge in 5 Steps
Take one workflow at a time, in short sessions, so the senior tech stays on the queue.
- Pick what to capture first from your ticket data: escalations that bounce between techs, reopens, SLA misses, routing errors and stale tickets. Add the ticket types your team already handles well, so their way becomes the standard.
- Record the senior tech doing the real task, with a phone or a screen recorder (camera on) and no script. Ask "why?" at each step; the answers are the part nobody wrote down. A recorded Teams call works too.
- Turn each recording into an SOP lesson: the video, the written steps with screenshots and a short multiple-choice knowledge check. The check shows whether the next person understood the steps.
- Put the lessons in a role path, in the order a new hire needs them, with due dates. Our guide on how to build MSP training pathways covers the design.
- Track who finished, then have the senior tech watch the new hire work live tickets and sign off. The first of our IT onboarding checklists for MSP hires lays out that supervised work.
The full method, with the ticket reports to start from, is in our help center: how to decide what to record first.
How Do You Keep Captured Knowledge Current?
Captured knowledge goes stale as clients and tools change. Give every SOP lesson one named owner, usually the tech who recorded it. The program as a whole needs an owner too: see who owns MSP training.
The same ticket signals tell you when a lesson is wrong: a reopen or an escalation on a workflow you already captured means its lesson needs a look. Put a regular review date on each role path as well.
First recordings are first versions, so skip the editing: when a lesson goes out of date, record it again. Recording this way often gets other techs offering to record one too.
Capturing Institutional Knowledge in Empath Learn
Empath Learn, the training platform an MSP uses for its own owners and staff, holds the recordings, SOP lessons, role paths and progress tracking in one place. The authoring tools and the Curated Collection, with its labs and roleplays, come with every Empath Learn seat.
To build your own courses, paste an SOP from your IT documentation, a PDF or a Word file into a text lesson with screenshots, then follow it with a multiple-choice knowledge check in the same course. You can also record with the built-in recorder (screen, camera or both) or import from YouTube.
Start the role path from a ready-made template, such as New Hire Onboarding or Tier 1 (T1). Our new-hire training for MSPs page shows the T1 template. Replace the placeholder lessons with your SOPs and videos, then assign it to each new hire with due dates. You can also edit the lessons of a Curated Collection course to match your desk.
For practice, the Collection has more than 40 hands-on labs by topic (CompTIA, Cisco networking, Azure and cybersecurity) and hundreds of AI roleplays. In a roleplay, a tech types or speaks replies, for example to an upset client user, and gets instant, personal feedback (what went well and what to change).
Managers see who finished a course or path and who is off track, so you know who still needs the senior tech's time. Browse the full library in the Empath course catalog. If you are comparing programs first, see our guide to the best MSP training programs.
Which workflow would stall first if your senior tech left tomorrow? Start there. In a demo, we'll map it to a role path template and open the progress view your managers would use. Book a Demo
Frequently Asked Questions
What is the difference between tribal knowledge and institutional knowledge?
In daily use, very little: both mean the know-how a team relies on that is not written down. "Tribal knowledge" is the casual term many MSP and IT teams use for what a few people carry in their heads. "Institutional knowledge" is the more formal business term, and some teams also use it for what the company has documented.
What's a better term for tribal knowledge?
Some teams prefer "institutional knowledge" or "organizational knowledge." Both mean the same thing: the know-how that lives in people's heads and not yet in your documentation. Pick the term your team already uses and keep it the same in SOP titles and job descriptions, so people searching your documentation find what they need.
Is tacit knowledge the same as tribal knowledge?
Not quite. Tacit knowledge is know-how that is hard to put into words, such as a senior tech's sense that a "simple" ticket is about to turn into a project. Tribal knowledge is wider and also covers plain facts nobody wrote down, like a client's after-hours contact. Recording real work while you ask why captures some of both.
What is a knowledge transfer plan?
A knowledge transfer plan lists what one person knows that others need, who will learn each part and by when. At an MSP it usually covers client procedures, escalation rules, vendor contacts and the workarounds only one person knows. Give each item an owner and a due date, then check that someone else can do the work alone.
How do you retain institutional knowledge when an employee leaves?
Start before anyone gives notice. Have the people who hold the most record their real work while someone asks why, turn each recording into an SOP lesson and assign it to the next person in that role. If notice has already come, spend the remaining time on the workflows only they handle, starting with the ones that cause escalations.
