Three steps to cross-train your team before the next emergency

Executive overview

Businesses that rely on one person to own a critical process are one sick day away from chaos. Cross-training solves this by spreading procedural knowledge across the team before an emergency forces the issue. The framework has three steps: document the process, train a backup using a progressive practice model, and build a recurring schedule so the backup stays sharp. Most teams skip the practice schedule and wonder why their cross-training never sticks.

The single reason cross-training fails is not poor documentation — it is the absence of a recurring practice schedule after training ends.

Defining your recipes (step 1)

• A "recipe" is any process that lives only inside one person's head; the goal is to get it into a written, shareable format.
• Standard operating procedures (SOPs) are the vehicle — a consistent template with steps, context, and expected outputs.
• The knowledge holder should write the SOP themselves; their tacit know-how is the raw material.
• If that person has already left, the incoming trainee takes on the job of capturing the process while someone else demonstrates it.
• Recipes stored in human memory introduce fragility; recipes stored in a system introduce resilience.

Personalising the recipe with the backup (step 2)

• Hand the SOP to the backup person and make them a co-author, not just a reader.
• Training follows three phases: I do (demonstrate while they watch), we do (work through it together), you do (they execute with decreasing oversight).
• The number of repetitions at each phase scales with process complexity and stakes — a coaching methodology may need 50 repetitions; a copy-paste data task may need just one.
• During "we do," gradually shift control: first the trainer narrates while the trainee watches; then the trainee acts while the trainer prompts; finally the trainee leads while the trainer observes.
• At every phase the trainee updates the SOP with gaps, corrections, and reminders they discover — the document improves through use.
• If the trainee struggles during "you do," step back to "we do" before moving forward again.
• The benchmark for completion is that the backup can produce a result as good as or better than the original owner.

Building a practice schedule (step 3)

• Cross-training without a practice schedule is temporary; the knowledge will erode before it is ever needed.
• Assign the backup ownership of the task on a fixed recurrence — for example, the first Friday of every month or the first Monday of every quarter.
• Two recurring tasks in a task management system make this automatic: one for the primary owner and one for the backup on their practice day.
• The practice cadence should reflect how perishable the skill is and how quickly the person learns; there is no universal right answer.
• Even a quarterly repetition keeps the backup functional; the goal is never zero.
• When the primary owner is genuinely absent, the backup steps in — this doubles as real-world practice without extra scheduling overhead.

Identifying where cross-training is needed most

• Almost every business has at least one "Susie" — the sole holder of a critical process, often the founder or a long-tenured employee.
• Single points of human failure are risk vectors; auditing for them is a straightforward way to surface business vulnerabilities.
• Start with one process that is currently bottlenecked on one person, commit to it, and build the habit before expanding.
• The three-step framework scales from a solo operator with one assistant up to a growing team with layered responsibilities.
• The payoff is a calmer, more resilient operation where no departure, illness, or vacation triggers a crisis.