Every small team has tasks that only one person can do. Most of the year that's invisible. The person is there, the task gets done, and nobody thinks about it. Then the holidays arrive, that person takes a well-earned week off, and the task either waits, gets done wrong, or gets done by the person on vacation from a phone at a family dinner.

Cross-training is the fix, and most teams know it. What stops them is that “cross-training” sounds like a program — a curriculum, a schedule, weeks of shadowing nobody has time for. It doesn't have to be. Done well, it's a short list of critical tasks, a backup named for each one, and a few deliberate practice sessions before the calendar forces the issue.

Find the tasks only one person can do

Start with a simple list. For each person on the team, write down the tasks they do that would cause a real problem if nobody else could do them for a week or two. Not everything they do — just the tasks where an absence means a missed payment, an unhappy customer, a broken process, or a compliance problem. Ask each person to add to their own list; they'll know about tasks nobody else has noticed.

Then look across the lists and note, for each task, who can currently do it. The tasks with a single name next to them are your cross-training plan. If a task has one name and that person is taking time off in December, it goes to the top.

Pick the backup deliberately

The natural choice is whoever sits nearest or seems least busy. A better choice is someone who'll actually be available when the primary person isn't — not someone taking the same week off — and whose own work leaves room to cover. Check the holiday schedule before assigning backups. If the time-off calendar isn't settled yet, settle it first; cross-training someone who'll be away the same week helps nobody.

Spread the load. If one reliable person ends up as the backup for everything, you've moved the single point of failure rather than removed it. And tell the primary person why this is happening. Being asked to teach your job to someone else can feel like a signal that your job is at risk. Say plainly that the goal is the opposite: a week off where nobody has to call you.

Train the backup on the real task

A sequence that works: the backup watches the task done once, does it once with the expert watching, and then does it alone while the expert is still around to catch problems. Watching by itself teaches less than it seems to. People who have only watched a task tend to discover, the first time they try it alone, all the small decisions the expert made without saying so.

So the middle step matters. When the backup does the task with the expert watching, the expert's job is to stay quiet until something is about to go wrong, and then to explain why. Those explanations are the knowledge that wasn't written anywhere. Capture them as they come up — the SME interview questions work just as well in a ten-minute session beside a colleague as in a formal interview.

Leave a job aid behind

The backup may not do the task again for weeks, and training fades when it isn't used. So every cross-training session should end with a job aid the backup can follow on the day: the steps in order, the screens or forms involved, the decisions they'll face, and what to do if something looks wrong. Have the backup write it, or at least edit it, while the task is fresh. A job aid written by the learner is written in the learner's language, which is the language they'll need it in.

It's the same reason a job aid outlasts a slide deck in everyday training: the aid is there at the moment of need, and the memory of the session isn't.

Check it before the break

Don't wait for the holiday to find out whether the cross-training worked. Before the primary person leaves, have the backup do the task alone on a real instance, from the job aid, without help. Then look at the result together. If it went well, you have a backup. If it didn't, you still have time to fix it.

Record who can do what. A simple grid — people across the top, critical tasks down the side — is enough. It tells you where you're covered, where you're not, and who to call when someone is out unexpectedly, which isn't limited to the holidays.

Keep it alive after January

Cross-training decays like any other training. A backup who did a task once in December won't remember it in June. Rotate the task occasionally: let the backup do it for real once in a while during the year, even when the primary person is available. It costs a little time and keeps the skill current. When a process changes, update the job aid and tell the backup, not just the primary.

If you're bringing on seasonal hires at the same time, the grid does double duty: it shows which experienced people are free to train newcomers, and which are already stretched covering for colleagues.

The bottom line

The week someone is away is the wrong time to learn that only they knew how to do something. Before the holidays, list the tasks only one person can do, and name a backup for each who'll actually be available. Train on the real task: watch it once, do it with the expert watching, do it alone. Have the backup write the job aid. Check the skill with a real solo run before the break, record who can do what, and rotate the task during the year so the skill survives. It's a few hours of work now, and a week off that's actually off.

— Tom

A backup for every critical task

LearningByDesign turns your task list into short training, printable job aids, and a sign-off checklist per task — so every backup is checked before the holiday, not during it.

See how LearningByDesign works →

About the author

Tom Christian is the founder of LearningByDesign, an AI-native learning platform that builds real training — needs analysis to course to evaluation — without hiring a Director of L&D.

He has spent twenty years inside training, learning, and quality at scale — building and running programs at Guardian Life, ConnectiveRx, and Horizon Blue Cross Blue Shield. He writes about course design that changes behavior, the discipline of starting with outcomes, and running an L&D function without a department behind you.