Worked example: cross-training a backup for a dispatch lead

Subject

Mari Vega

Dispatch Lead

Engagement

Cross-training

Proactive

Goal

2-week vacation

Coverage · day 0

0/100

The situation

A single point of failure who never gets to leave

Cascade Freight, a regional carrier. Mari has run dispatch for twelve years. No one is leaving - but she is the only person who can run the board on a bad day, and she has not taken a real vacation in four years. The goal is simple: make it safe for her to go.

What they own

The boardThe daily route board - which driver and carrier for which lane, balanced against service promises.
ExceptionsHot loads, breakdowns, and weather reroutes - the judgment when the plan falls apart.
CarriersThe backup-carrier relationships and who actually answers after hours.
CustomersWhich accounts to call proactively, and which loads truly have slack.

What the manager is afraid of

“If Mari’s out sick for two days, we feel it. She holds the whole board in her head - which carrier to call for a hot load, which lanes run tight, which customers to call before they call us. We can’t ask her to never take a vacation.”

Backup: Theo Ramirez, a dispatcher of two years. Sharp on the system, but he has never run the board solo.

Phase 01 · Set up

Before a single question, the system maps the risk

It reads the role and the manager’s intake and predicts where the tacit knowledge concentrates, so the first interview walks in aimed, not cold.

Predicted high-risk tacit areas

CriticalHot-load and exception triage - the judgment when the plan breaks.
HighBackup-carrier relationships - who to call off-book for capacity.
HighTight-lane knowledge - the buffers that aren’t in the system.
MediumCustomer slack ranking - which loads can wait, which never can.

A probe it generated for session 1

“Walk me through a normal day on the board. When it goes sideways, what is it usually, and what do you do that the TMS wouldn’t tell someone?”

Phase 02 · Capture

3 interviews, 3 layers

Each session has a different job. After every one, the transcript is analyzed and coverage is re-scored, so the number climbs as the tacit knowledge comes out.

UnexploredExploredSuccessor-ready

1The boardGeneral capture~47 min · AI interview

Transcript · excerpt

Facilitator

When the day goes sideways, what is it usually?

Mari

Capacity. A carrier no-shows on a tight lane and now a load’s at risk. The TMS shows it green until it’s already late. I know which lanes run tight and need a thirty-minute buffer that isn’t in the system, so I’m already working a backup before the board turns red.

Facilitator

Is any of that written down?

Mari

No. It’s twelve years of knowing the lanes. Theo can read the board, but he doesn’t know which green is actually amber.

Knowledge captured

Daily route boardProcess
Tight-lane buffersDecision
Carrier rosterContact
Driver-lane assignmentsProcess

Tacit knowledge surfaced

Knows which "green" lanes actually run tight and pre-works a backup before the TMS flags a delay.

HighTight-lane buffers exist only in Mari’s memory.

HighNo backup-carrier reference for the board.

Coverage44▲ +44

2When the plan breaksCritical decisions~49 min · AI interview

Transcript · excerpt

Facilitator

Tell me about the last really bad day.

Mari

The pass closed - I-90 over the mountains. Everyone reroutes the obvious way and now that road jams too. I send the reefers the long way south and call the two carriers who run chains and actually pick up their cell after hours. And I triage: Account A’s loads never wait, they’ll escalate to the VP. Account B talks tough but their loads have a day of slack. So B waits, A moves.

Mari

None of that is in the TMS. The SLA says both are the same priority. They’re not, and knowing the difference is the whole job on a bad day.

Knowledge captured

Choke-point reroutesDecision
After-hours carrier listContact
Customer slack rankingDecision

Tacit knowledge surfaced

Reroutes around known choke points before the system flags a delay, and knows which carriers run chains and answer after hours.

Ranks customers by real slack, not SLA tier, to decide which loads move first in a crunch.

AutoAutomation candidate: the tight-lane buffers could be encoded in the TMS.

HighCustomer slack ranking is undocumented judgment.

Coverage66▲ +22

3Building the backupCross-training checklist~43 min · AI interview

Transcript · excerpt

Facilitator

What does Theo need to run the board for two weeks?

Mari

A tight-lane cheat sheet and a backup-carrier card per lane - who to call, in what order, and who answers after hours. The escalation contacts for the top accounts. And the month-end surge pattern, because if my vacation lands near close, the board doubles. I want him to run a full week with me watching before I’m gone.

Facilitator

Could he run a normal week today?

Mari

A normal week, with the cheat sheets, yes. A bad-weather day alone - after one supervised week, close. That’s what the trial run is for.

Knowledge captured

Backup-carrier cheat sheetReference
Account escalation contactsContact
Month-end surge patternProcess

Tacit knowledge surfaced

The month-end surge pattern that doubles the board - and how to pre-stage capacity for it.

ClosedTight-lane buffers and backup carriers now on a cheat sheet.

MedPeak-season (Q4) surge - deeper than a two-week window; flagged for a follow-up.

Coverage81▲ +15 · gate cleared

Phase 03 · Analyze

What the conversations became

Knowledge nodes

Tacit items saved

Automation candidates

Quality score

The knowledge map

The conversations become a structured, connected graph - one node per area of knowledge, linked by relationship and coloured by how transfer-ready it is. This is the same view you get inside the product; drag a node, or zoom in.

Loading graph…

Coverage by area

coverage (% captured) avg depthout-of-scope excluded

Successor-readyExploredUnexplored

Coverage reached 81/100 with no open critical gaps. The board is no longer a single point of failure: the tight-lane buffers, backup carriers, and slack ranking that lived in Mari’s head are now a cheat sheet Theo can run from. One deeper pattern - the Q4 peak surge - is flagged for a follow-up capture, not blocking the vacation.

Phase 04 · Deliverables

The artifacts, generated from the capture

Every document is built from the same structured findings, so they agree with each other. Numbers are code-computed; the writing is grounded in what was actually said. Here is the flagship in full.

Flagship deliverable · shown in full

Continuity Report

Knowledge transfer - Dispatch Lead

Subject · Mari VegaBackup · Theo RamirezSessions · 3Coverage · 81/100Open critical gaps · 0

Executive summary

Mari Vega is the single point of failure on the dispatch board, and has not taken a real vacation in four years. This proactive capture built a backup so she can take two weeks off without service degradation. Three sessions raised coverage from 0 to 81/100 and cut single points of failure from 5 to 1. The judgment that ran the board on a bad day - tight-lane buffers, backup carriers, and real customer slack - is now a reference Theo can hold. With one supervised week, he can run a normal fortnight; only the Q4 peak surge remains for a follow-up.

01 · Critical capabilities & current coverage

Hot-load / exception triage - was Mari only; now a documented decision guide with Theo shadowing.
Backup-carrier network - captured as a per-lane cheat sheet with after-hours contacts.
Tight-lane buffers - documented; flagged to encode in the TMS.
Daily board operation - transferable; Theo runs it with the cheat sheets.

02 · Tacit knowledge captured

Which green is really amber: the tight lanes that need a buffer the TMS doesn’t show.
Reroutes: the choke points to route around before the system flags a delay.
Real slack: ranking customers by actual flexibility, not SLA tier, to triage a crunch.
After-hours carriers: who runs chains and who answers their cell when a pass closes.

03 · Risks & mitigations

High - tight-lane buffers were undocumented. Cheat sheet now; TMS encoding proposed. Owner: Ops, wk 1.
High - backup carriers lived only with Mari. Per-lane card built. Owner: Mari, wk 1.
Med - Theo has not run the board solo. One supervised week before the vacation. Owner: Theo, wk 2.
Med - Q4 peak surge is deeper than this window. Follow-up capture scheduled. Owner: Ops, post-vacation.

04 · Backup readiness - Theo Ramirez

Theo already operates the TMS and the routine board. With the tight-lane cheat sheet, the backup-carrier cards, and one supervised week, he can run a normal fortnight - which is exactly the goal. A severe-weather day alone is close but not certified; the supervised trial run is designed to close it. Peak-season (Q4) is intentionally out of scope for this window and scheduled as a follow-up.

The pack this produces

Role Briefing

Theo’s guide to running the board: the triage judgment, the reroutes, and who to call when.

Cross-Training Plan

The supervised-week plan with tasks, owners, and a verifiable "can run a normal fortnight" criterion.

Risk Heatmap

Every dispatch capability on one chart, so the cross-training hours go where the exposure is.

Gap Report

What is cheat-sheet-ready, what is shallow, and what (Q4 surge) needs a follow-up.

Knowledge Risk Assessment

The key-person case: five single points of failure before capture, one after.

Quick Reference

The board on one sheet: tight lanes, backup carriers, escalation contacts, real slack.

Want the finished documents to hold? Download real sample deliverables from a full engagement.

Phase 05 · Readiness

The difference: a vacation nobody has to fear

Day 0

Four years without a real vacation.
The whole board "in her head."
5 single points of failure on dispatch.
Coverage 0/100.

Handover ready

81/100 coverage, no open critical gaps.
A cross-training plan and a board cheat sheet.
Bus-factor down to 1; Q4 surge scheduled as a follow-up.
Theo ran a supervised week - Mari takes her two weeks.

Run one on your own critical role.

Start free: the role analysis, the interview scripts, and a full Knowledge Risk Assessment on your own expert cost nothing.

Start free See the other examples

Nobody’s leaving. She still can’t take a vacation.

A single point of failure who never gets to leave

Before a single question, the system maps the risk

3 interviews, 3 layers

What the conversations became

Coverage by area

The artifacts, generated from the capture

The difference: a vacation nobody has to fear