Skip to main content
Change Management•8 min read

Succession Planning When One Person Knows Everything

October 20, 2026•By Ajan Kanagalingam

Succession planning gets discussed as an ownership question: who buys the shares, what the business is worth, how the transition is financed. Those matter and they are rarely the thing that breaks. What breaks is that one person knows how the pricing actually works, which suppliers will bend on a deadline, and why the machine in the back is never run above a certain setting.

Start with the month-long absence

The useful exercise takes an afternoon. For each key person, list what would simply stop if they were unavailable for a month with no handover. Not reduced. Stopped.

Write it per person rather than per process, because the concentration is the finding. Most owners come out of this with two or three items they genuinely cannot delegate and a considerably longer list of things they have simply never written down, and the second list is where the cheap wins are.

Do it for yourself first if you are the owner. The answer is usually longer and more uncomfortable than it is for anyone else on the payroll, which is itself the result worth having.

Four kinds of knowledge, and what transfers

KnowledgeExampleHow it transfers
FactualSupplier codes, pricing bands, passwordsWrite it down, today
ProceduralHow month-end actually gets doneRecord a walkthrough, transcribe, correct
JudgmentWhen to make an exception for a clientWorked examples, slowly
RelationalWho at the supplier answers the phoneIntroductions, mostly

The first two categories are where capture technology has genuinely changed the economics, and together they are more of the total than people expect. The second two have not changed at all, and treating a document as a substitute for an introduction is how a handover looks complete and fails in month two.

Record, do not write

Asking a long-serving employee to document their job produces a two-page summary of what they think you want to hear, delivered three weeks late. Asking them to narrate a task while doing it produces forty minutes of detail they would never have thought to write.

Transcribe that, have it structured into a procedure, and hand it back for correction. Correcting a draft takes a fraction of the time of producing one, and the corrections are where the real content arrives, because people are far better at noticing a wrong step than at recalling a complete one.

Accuracy on names, part numbers and settings needs a check, since transcription fails on exactly that vocabulary, which is covered in where automatic transcription falls short. The format to aim for is in standard operating procedures with AI.

The archive already holds a lot of it

Before running capture sessions, look at what is already recorded. Years of email, job notes, quotes and support threads contain a great deal of how this business works, and the obstacle has always been that it was unsearchable rather than unwritten.

Making that archive answerable is now a modest project rather than a large one, and it reaches the exceptions that nobody would think to document. The practical mechanics are in building a company brain, and where the material is on paper it starts with scanning.

One caution. An archive that answers questions confidently from outdated records is worse than no archive, so date the sources and prefer recent material where they conflict. Contradictory records are a cleaning problem before they are a retrieval problem, as in data cleansing.

Judgment transfers by example

The hardest category is the decisions made by someone who has seen the situation forty times. A procedure can say what to do; it rarely captures when not to follow the procedure.

The method that works is unglamorous. Collect worked examples of real decisions with the reasoning attached, especially the ones that went against the obvious answer, and review them with whoever is learning. A dozen of those teaches more than any document, and recording the conversation means the twelve examples exist for the next person too.

This is also where handing judgment to an assistant goes wrong, because it will produce a confident answer for a situation it has no basis to judge. Keeping the person in the decision while the tool handles retrieval is the arrangement that holds, and the risk of letting it erode is in keeping your team sharp.

Frame it correctly or it will not happen

Asking someone to document everything they know lands as a request to make themselves replaceable, and the cooperation you get will reflect that. The honest framing is that the business should not depend on any single person being reachable, which is true, applies to the owner most of all, and is usually accepted when the owner goes first.

Capture as a continuous habit beats capture as an exit process. Thirty minutes a month on one task produces a complete picture within a year, and it avoids the version where a resignation letter starts the clock. The wider framing of working alongside these tools is in training your workforce to collaborate with AI.

Frequently Asked Questions

What is key person risk in a small business?

The exposure created when one individual holds knowledge, relationships or access that the business cannot operate without. It is distinct from ownership succession, which is about who holds the shares. A business can have a clean ownership plan and still stop functioning for six weeks because the only person who knows how the pricing works is unavailable, and that second risk is the one most owners have not costed.

Can AI capture what a long-serving employee knows?

It can capture a meaningful portion cheaply, which is a genuine change. Recorded walkthroughs turned into written procedures, years of email and job notes made searchable, and a question-answering layer over the result together cover the factual and procedural knowledge well. What it does not capture is judgment about unusual situations, and relationships, which transfer by introduction rather than by documentation.

Where should succession planning start?

With a list of what would stop if each key person were unavailable for a month. Write it per person rather than per process, because the overlaps are what reveal the concentration. Most owners discover two or three items they genuinely cannot delegate and a much longer list they simply never have, and the second list is where the quick wins are.

How do you capture knowledge without it becoming a documentation project?

Record rather than write. Ask the person to narrate a task while doing it, transcribe the recording, and have the transcript structured into a procedure that they then correct. Correcting a draft takes a fraction of the time of producing one from nothing, and it is the difference between a capture programme that runs and one that is abandoned after two weeks.

Does this reduce the value of experienced staff?

It changes what they are valued for rather than reducing it. Documenting a procedure removes the dependency on one person being available, and it does not remove the judgment that decides when the procedure does not apply. Framing capture as reducing single points of failure for the business, rather than as making anyone replaceable, is both more accurate and the only version that gets cooperation.

Stop depending on one person being reachable

We map where your knowledge is concentrated, capture it in sessions that take minutes rather than weeks, and make the archive you already have answerable.

Related Articles

Change Management

AI Proof of Concept: Designing One That Decides

October 13, 2026Read more →
Change Management

Performance Reviews When AI Wrote the Work

September 29, 2026Read more →
Change Management

Delegation Is the Skill AI Actually Needs

September 30, 2026Read more →
AK
Ajan Kanagalingam
Founder & ChatGPT Consultant, ChatGPT.ca

Ajan leads the ChatGPT.ca team: 200+ custom GPT builds and automation projects for 50+ businesses across 20+ industries. Based in Markham, Ontario. PIPEDA-compliant solutions.

Stay ahead of AI in Canada

Weekly case studies, new tools, and ROI playbooks for Canadian SMEs. One email, zero spam.