Latest
What You Have to Decide Before Anybody WritesWriting It Before You Need ItCross Training Covered Everything Except the Role That Mattered MostBehind the Book: You Don’t Own Anything AnymoreBehind the Book: The Woke VirusBehind the Book: Galactic InvasionWhat’s New at The Writing King: Week of November 8, 2026Alexander Zhidkov: Decision MakingJessi Szurek: Expand Your RangeYou Don’t Own Anything AnymoreThe Budget Decided How My Department Was ShapedWhy Your Competitor’s Book Is Working and Yours Would NotWhy Are These Guys Smiling? A Business Book That Became a Wrestling MemoirPangram Wants to Decide Who Gets PublishedWhat You Have Enough Material For Right NowWhen a Book Is the Wrong ToolThe Woke VirusGalactic InvasionChatGPT Turns Four: From a Free Research Preview to GPT-6What’s New at The Writing King: Week of November 1, 2026Diwali: The Festival of Lights and the Story Behind the LampsHow Much Water and Power Does Heavy AI Use Take? I Ran My Own NumbersBad Boys: Ride or Die (2024)Vesuvius Day: The Teenager Who Wrote Down Pompeii’s Last DayAnti-Communism Week: Remembering the Writers Communism SilencedVoyager 1 One Light-Day: Fifty Years to Travel One Day of LightVellum Added an Optional AI Feature. A Pile-On Killed It in a Day.Are AI Subscriptions Losing Money? The Gym Membership Math Says NoAI Terms Every Writer Should Know, and Why Each One MattersWorking While Sick: What 24/7 On Call Cost MeHe Banned AI From His Writing Group. His Own Cover Got Called AI Slop.Who Writes the Fake Fan Mail Authors Get? Inside the Scam CompoundsSMS Appointment RemindersJoe Rockey: Ghostwriting His BookDarrell Stern: Stop Being Invisible, Become UnmissableFree BooksHow to Turn Your Expertise Into a Book People Want to Read | The Expert MethodWhat’s New at The Writing King: Week of October 25, 2026Challenger Remembrance Day: The Engineer Who Wouldn’t SignJoel Salomon: The Truth About MoneyReddit Is Putting Up a Login Wall. Wikipedia Won’t Be Far Behind.Victoria Chemko: The Body Is the First TechnologySir Patrick Stewart: A TributeA Year in the Bank: ADHD, Face Blindness and the Freedom to Walk Out | The Impossible Puzzles Show, Episode 326A Yale Economist Says We Won’t Be Missed. He Forgot the Bread Line.Walter Koenig: A TributeAI Has Paid Off Outside Tech. Apollo Is Reading the Wrong Scoreboard.I Don’t Post Bad ARC Reviews. I Send the Author a Note.The Little Red Book of Stuff That Works!Your Kids Are Your Own Fault
The Writing King Your Ethical Ghostwriter. Your Story, Done Right.

Cross Training Covered Everything Except the Role That Mattered Most

TL;DR: Cross training costs hours this week and pays off on a day nobody can name, which is why almost nobody does it. I put it in across my team and it was important to our survival. It also failed to cover the one role that touched everything, and the money I spent covering that gap bought something worse than a trained colleague.

Pick the role whose absence would hurt most and make sure a second person can do the job.

Why does cross training never happen?

The cost is immediate and specific. The benefit is deferred and hypothetical.

Training hours come out of this week, from a person who has work that is already late. Somebody has to cover, or the work slips, and both are visible immediately.

The payoff arrives on a day nobody can name. Somebody is sick, somebody quits, somebody is on a plane when a system fails. Nobody can point at that day in advance, so nobody can price it.

Every argument for cross training loses to every argument against it, right up until the day it does not.

What did cross training look like on a small team?

I put it in so that no role was a single point of failure.

My team did not like it at first. They did not know why it was happening, they did not understand the reasoning, and they did not think they had time for it.

That reaction was reasonable. From their side it looked like being pulled off their own work to learn somebody else’s job for no stated reason.

Then they could all do the job, and they were happy with it. Cross training was very important for our survival, and I would not run a small team without it again.

What changes when everyone can cover?

People can be away.

On a team where each person owns their systems completely, one person being unavailable means an entire area is unattended. Not degraded, unattended. Vacations become negotiations and illness becomes a problem for the company rather than for the person.

Cross training converts that. Somebody can be away and the area still has an owner, which means the rotation works, holidays work, and a resignation is a hiring problem rather than a crisis.

The second effect is quieter. When two people know a system, they discuss it. The person who has owned something alone for years has assumptions nobody has ever questioned, and a second set of eyes finds those.

How do you find hours for training that nobody has?

Take work away first, because willingness does not create time.

The failure I have watched most often is a manager announcing cross training, scheduling it, and then leaving everyone’s existing workload untouched. The training slips every week, and after two months it is quietly abandoned and everyone learns that the initiative was not serious.

Something has to give. Defer a project, accept slower response on something for a month, or bring in outside help to cover the gap while the training happens.

If nothing can give, the honest conclusion is that cross training is not going to happen, and the company should plan around the single points of failure it has rather than pretending they are being addressed.

Which role should be cross trained first?

The one that touches everything, and that is where I got it wrong.

My database administrator overlapped every system and every person. Every application depended on that layer, and every problem eventually became a question for that role.

That role was not cross trained.

The reasons were practical. Database administration is deep, specialized work that takes years rather than weeks, and nobody else on the team had the background or the hours to acquire it. It was the hardest role to cover and therefore the one that did not fit the plan.

So the single point of failure I had designed the entire scheme to eliminate survived in the one place where it mattered most.

Can you buy your way out of a single point of failure?

Partly, and less than I expected.

I hired a database consulting company as a backstop. The theory was that somebody could always step in.

It did not always work out that way.

A purchased backstop is a different thing from a trained colleague and the difference shows up exactly when you need it. The consultants knew databases. They did not know that database, that schema, those decisions, or why any of it had been built the way it was.

Cross training transfers context. A contract transfers capacity. Those get treated as interchangeable on an organization chart and they are not.

What is the honest version of covering your gaps?

The plan covers most of the risk, the hardest piece does not fit, and it gets solved with money that buys something weaker.

That was my situation and I suspect it is most people’s. The scheme worked. Cross training was one of the better decisions I made. And the role I most needed to cover was the one I could not, so I paid for a substitute and the substitute was not equivalent.

Nobody writes it that way. Every account of resilience planning describes a complete solution, because a partial one sounds like failure.

A partial one is what most companies have. The useful step is knowing which gap you did not close, so that when it matters, nobody is surprised by what the backstop cannot do.

Frequently Asked Questions

How long does cross training take?
Weeks for operational coverage of a system somebody else owns, and considerably longer for deep specialist roles. The realistic goal is a second person who can keep things running and knows when to escalate, not a full replacement.
How do you cross train a specialist role like database administration?
Usually you cannot, in any full sense. What works is training somebody to handle routine operations and recognize when the specialist is needed, combined with documentation of the decisions rather than the procedures.
Do people resist cross training?
At the start, frequently, because it takes time from work they are measured on and the reason is rarely explained well. Resistance drops once people experience being able to take a week off without their area going unattended.
What should be documented for a single point of failure role?
The decisions rather than the procedures. Why the system is configured this way, what was tried and rejected, and what will break if somebody changes a particular thing. Procedures can be rediscovered. Reasoning cannot.
Is a consulting retainer a substitute for internal knowledge?
It covers capacity and does not cover context. A firm can supply skilled people quickly and they will not know your specific system, which is what matters during an incident. Treat a retainer as a supplement rather than a solution.
How do you decide which single points of failure to accept?
Rank them by what happens if that person is unavailable for two weeks with no notice. Some produce inconvenience and some stop the business. Close the second kind and document the first, and be explicit that you have chosen to live with them.

Categories and tags
CategoriesTechnology
About the Author
Richard Lowe, professional ghostwriter

Richard Lowe is a professional ghostwriter and author with 113+ books authored and 54+ ghostwritten. Before writing full time he spent 33 years in enterprise technology, including 20 years as Director of Computer Operations and Technical Services at Trader Joe's. He writes nonfiction, fiction and memoir, and works with executives and experts on books that build authority.

More about Richard Lowe →

Disclaimer

The views and opinions expressed in this blog post are solely those of Richard Lowe and are based on personal experience and research. This content is for informational purposes only and should not be construed as professional legal, financial, accounting, or business advice. Always consult with qualified professionals before making important business or legal decisions. Richard Lowe is not a lawyer, accountant, or licensed professional advisor, and this content does not establish any professional relationship.

0 comments

No comments yet. Yours can be the first.

Was this useful?

Leave a comment