On Monday the one person who knows how to issue invoices is ill. On Tuesday a customer asks for a document that only that person can find. By Wednesday the owner is learning the invoicing system under pressure.
In a team of five, almost every job has exactly one person who can do it. That works until someone is away, leaves or is simply overloaded. Cross-training is the habit of making sure at least two people can do each important task. It does not mean everyone learns everything. It means no single absence stops the work.
Start with tasks, not people
Write down the tasks that must happen on a regular basis. Think of the things customers or colleagues notice within a few days if they are missed: invoicing, answering the shared inbox, ordering supplies, payroll, preparing deliveries, updating the website, backups.
For each task, note two things: how often it happens and what goes wrong if it is late by a week. Aim for 10 to 20 tasks. If you have more, group them. This list is also the natural starting point for the notes described in covering holidays and absence, which tell a stand-in where to find things.
Build a skills grid
A skills grid is a table with tasks in rows and team members in columns. In each cell, write one of four levels:
| Level | Meaning |
|---|---|
| 0 | Has never done it |
| 1 | Has seen it done, needs the instructions open |
| 2 | Can do it alone at normal quality |
| 3 | Can do it, fix it and teach it |
Fill it in together, in one short meeting, so the numbers reflect what people actually think rather than what the owner assumes. A spreadsheet is enough.
Now look at each row. Where only one person scores 2 or 3, that task is a single point of failure. Mark those rows. In most small teams, there are more of them than anyone expected, and that is the point of the exercise.
Choose what to cover first
You cannot train everyone on everything, so rank the marked rows by the damage of a one-week gap. Payroll and customer deadlines come before internal reports. Tasks that are rare but painful, such as renewing a domain or filing an annual return, deserve a place too, because nobody will remember how to do them when the date arrives.
Start with the top three. Finishing three tasks is better than starting twelve.
Decide who covers whom
For each marked task, name a backup. Choose carefully:
- Pick someone with a related job. The person who prepares quotes can probably cover invoices more easily than the person who drives the van.
- Do not pair people who are often away together. Two people who take holidays at the same time are not a backup for each other.
- Do not overload one backup. If one colleague is the backup for six tasks, you have moved the single point of failure rather than removed it.
- Add a second backup for critical tasks. If the task cannot wait a week, one backup is not enough.
Write the pairs into the grid, as a column called "Backup". Ask the person you are naming; do not just announce it. People accept the extra responsibility more readily when they have a say in it.
Train in small sessions
A full day of training is rarely repeated, and its content is mostly forgotten within a month. A better plan is a short session every week or two, built on three steps:
- Watch. The expert does the task while the backup watches, and explains each step aloud.
- Do. The backup performs the task while the expert watches and keeps quiet unless something goes wrong.
- Write. The backup writes or corrects the instructions in their own words. They are the best judge of whether a missing step would have stopped them.
This is the same idea as in a thirty-minute session for a new tool: small, practical and ending with a cheat sheet. Aim for 30 to 45 minutes per task.
Keep the skill alive
A skill that is not used fades. Once a task has a backup, build in practice:
- Let the backup run the task once a quarter, while the expert is available but not involved.
- Swap tasks during a quiet week, or during planned absences, so that cover is real rather than theoretical.
- After any real cover, ask the backup two questions: what was unclear, and what would have helped? Add the answers to the instructions.
Real absences are the best test. If you are planning for a known gap, such as a long leave, use it. A short note in your one-page decision log about who covers what and why keeps the reasoning available later.
Mind the workload and the limits
Cross-training takes time, and the time has to come from somewhere. Look at your weekly capacity check before you add sessions, and agree what is paused to make room. If cover is added without reducing anything else, people will treat it as an extra burden and it will be dropped.
Some limits are legitimate. A task may need a licence, a qualification or legal authority that you cannot share. In that case, record it in the grid and plan for an outside substitute, such as an accountant or a freelancer, with access and instructions prepared in advance.
Review regularly
Look at the grid every quarter, and whenever someone joins, leaves or changes role. Check three things: has a single point of failure appeared, has a backup moved on, and has a task changed enough that the instructions are out of date? A fifteen-minute review is enough.
A short start
This week, list your regular tasks and mark those that only one person can do. Pick the top three and name a backup for each, after asking them. Book the first 30-minute watch-do-write session for each pair within the next two weeks, and put the quarterly review in the calendar. When the next absence comes, you will see the difference.