The Exit Interview Nobody Runs: Capture the Knowledge, Not the Feelings

Exit interview knowledge capture is the meeting nobody books: a recorded session where the person leaving does the job on screen while you capture it. Your bookkeeper gives notice on a Tuesday, and by Friday somebody has scheduled the other exit interview, the one that asks how she felt about her manager. Run the knowledge version in the first 48 hours after notice, not the last week. The HR exit interview protects you from a lawsuit; this one protects Monday morning.

Key takeaway: Book the knowledge exit inside 48 hours of the resignation, rank what that person holds by what it costs when it goes missing, record them doing the work, then let the replacement run it once.

Exit interview knowledge capture: the standard version asks the wrong questions

The standard exit interview asks why you are leaving and whether you would recommend the company. Reasonable questions for HR. None of them tell you how the commission run works. The meeting already exists, with an owner and a calendar hold, aimed at feelings instead of at the work walking out the door.

One owner covered payables himself for a few weeks after a key person left and found 500 to 800 dollars leaking every week from skipped audits, missed deductions, and overpayments. His math: up to 10,000 dollars a month, not theft, just a process nobody followed.

An exit interview that produces a form is not knowledge capture, it is a compliance record.

Little of what walks out is secret. Most of it is work nobody ever wrote down, because the person doing it never called it a process.

Run the knowledge exit before the HR exit

These are two meetings and they should not share an hour. Book the knowledge exit inside 48 hours of notice; leave the HR exit on the last day. Goodwill decays fast, and the last week is farewell lunches and a person already half gone.

They also pull against each other. One is a faintly adversarial review of the company; the other is a session where the departing person is the expert. When an expert refuses to document, the request usually landed like an audit.

Side by side, barely the same meeting.

Respect is technique. One bookkeeper walked us through payroll at 1am in her own time zone, and what opened her up was hearing that we were impressed.

Which knowledge should you chase inside a two-week notice?

Chase what costs the most when it is missing on the first Monday they are gone. Never the whole role.

Two weeks is emergency extraction, not a documentation project. The 14-day rescue version ranks by damage rather than by title, so sort what the person holds through four filters.

1. Money and deadlines first. Payroll, commissions, invoicing, renewals, filings: anything with a date and a penalty behind it.
2. Then what only they can reach. Logins, vendor contacts, the account whose password reset goes to their phone.
3. Then the weekly rhythm. Whatever they do every Monday that nobody else has watched.
4. Skip what two other people already do. It will feel wrong. Skip it anyway.

The fourth filter pays for the first three. At 2 to 4 hours per process, two weeks buys a handful of processes, so a session on work somebody else can run is stolen from work about to break.

The cheap version is a knowledge transfer plan written while nobody is leaving.

The questions that surface undocumented work

The questions are not the deliverable. Their job is to tell you which sessions to record, so keep them short and pointed at the work.

Seven earn their place.

• What do you do every week that nobody has watched? The multi-day job hides here.
• If you were gone Monday, what breaks first? A ranking question and a risk question in one.
• What is the workaround you invented? Nobody volunteers these.
• Where do you have to make a judgment call? The forks documents miss.
• What frustrates you about how this works? Frustration is data.
• Who do you call when it goes wrong? Relationships transfer worse than steps.
• What would a new person get wrong in month one? That is the training outline.

Every one is a doorway, not an answer. When somebody says "I pull the report and then I fix it," book 90 minutes and watch them do it.

Tell the expert you want to be interrupted: no, it does not look like that, I am actually doing this. Any subject matter expert interview runs on those rules, but here there is no second pass.

Record the work, do not ask for a write-up

Never ask someone to write down how they do their job. Record them doing it. A person with nine working days left will not write a manual, and the attempt gives you the tidy version.

One exiting bookkeeper needed 85 minutes on a screen share just to describe the weekly commission process: two reports merged with VLOOKUP because the export strips the job IDs, screenshots of group chats to find the helper, receipts chased through a login she did not have. Watching his own process for the first time in years, the owner said this was a three-day job every week.

Nobody writes down the workaround they invented, because to them it was never a workaround.

Capture three things per session: the purpose, the decision points (where a judgment call happens and what the right call looks like), and the step by step. Purpose and decision points separate a usable SOP from a list of clicks.

Two people on the call, one asking and one taking notes, 60 to 90 minutes, screen shared, on a day the work happens. Record a real run, never a demo.

Put the replacement in the room

If a replacement exists, they attend every session. Not as a courtesy. As the test.

Most companies get this half right. One exiting bookkeeper was already training her own replacement over screen shares, on her own initiative, because none of the payroll process had ever been written down. The instinct was right; the execution moved knowledge into one other head and left the single point of failure wearing a new name.

Then flip the chair. In the final session the receiver drives. Nothing counts as transferred until the receiver has run the process alone, start to finish, with the person leaving watching in silence. Sitting beside someone proves little: one owner trained a man side by side for two full days, and he still missed a meeting because he had not checked his calendar.

---

What do you do when they have already left?

You reconstruct from artifacts and from the people on either side of them, and the rebuilt version will have holes. It is a worse process, not a lost cause.

Start with what they left behind. Recurring calendar entries give the rhythm of the job, the sent folder gives who they dealt with, and the ugly spreadsheets nobody else opens are usually the real system.

Then interview both ends of the handoff. The people who pass work into that role and the people who receive it each hold a fragment of the middle. Teams in one department have learned mid-session that they each ran the same process differently.

Have whoever covers the job record their first four weeks as they hit each unknown; it is how one owner found 500 to 800 dollars a week leaking out of payables. And search before you rebuild: one staffing company spent months believing it had no training content, until somebody found it sitting in their platform.

Turn the last week into three assets

A pile of recordings is not a deliverable. By the last day those sessions should have become three things.

1. The raw recordings, indexed. Named by process, stored where the team already looks. You go back to them when the SOP turns out wrong.
2. A written SOP per process. Purpose, decision points and steps, with screenshots pulled from the footage. The recording is cheap; the edit is the product.
3. A one-page access and contact sheet. Logins, vendors, the bank contact, the customer who only ever called that person.

Where they land matters as much as whether they exist. Content in an unlabeled drive folder does not get used, which is why a five-figure documentation project sat untouched for two years while the owner who paid for it called it his worst nightmare. Cards, equipment and access removal belong on an offboarding checklist.

At The Systems Effect we run this as recorded working sessions with the person leaving, then turn the recordings into SOPs and training the replacement can follow.

A letter on your desk starts a 48-hour clock. Book the first session before the farewell lunch gets scheduled.

Frequently Asked Questions

What questions should you ask in a knowledge transfer exit interview?

Ask about the work, not the feelings: what do you do every week that nobody has watched, what breaks first if you are gone Monday, what workaround did you invent, and what would a new person get wrong in month one. Run all four in one call and treat each answer as a session to book.

How do you capture knowledge from an employee who is leaving?

Record them doing the job instead of asking them to write it down. Book 60 to 90 minute screen-share sessions on days the work happens, and capture the purpose, the decision points and the steps. Budget 2 to 4 hours of their time per process.

How long does a knowledge exit interview take?

Plan 60 to 90 minutes per session and 2 to 4 hours per process, spread across the notice period rather than crammed into the last week. One weekly finance process took 85 minutes just to describe once. First sessions overrun, so book the next before ending the current one.

What if the employee has already left?

Reconstruct from artifacts first: recurring calendar entries, the sent folder, and the spreadsheets nobody else opens usually hold the real process. Then interview the people who hand work into that role and those who receive it, since each holds a fragment of the middle.

Should the replacement sit in on the exit interview?

Yes on the knowledge sessions, no on the HR exit interview. The replacement in the room is the test that the transfer landed: they watch the recorded sessions, then run the process alone while the departing person watches in silence.