The reasoning behind the course
Our Principles
Five ideas guide how this course is built. None of them are complicated. All of them are easy to skip when you're busy, which is exactly why they're written down here.
A backup system doesn't fail because the idea was wrong. It usually fails because a step existed only in someone's memory, or because a workflow was never actually tested before it mattered. The principles below exist to close those specific gaps, in the order they tend to appear.
Write it down once, in plain language.
A task that lives only in your head cannot be delegated, automated, or reviewed. The first job of any operations manual is not to be impressive. It's to be readable by someone who has never done the task before, using ordinary words instead of internal shorthand.
Automate the response, not the relationship.
Automated replies can confirm receipt, set expectations, and route a request to the right place. They shouldn't pretend to be you. Clients tend to forgive an honest autoresponder. They notice, and mind, a fake one.
Train for the common cases, not every edge case.
A part-time backup person doesn't need to know everything you know. They need clear instructions for the situations that come up often, and a simple rule for what to do when something falls outside that list.
Tell clients the truth about your availability.
A communication plan works best when it's honest about response times during an absence, rather than implying nothing has changed. Clear expectations, set in advance, tend to prevent the anxious follow-up email.
Test small before you commit big.
A long weekend is a low-stakes rehearsal. Two weeks is not the moment to discover that your backup person doesn't know where the invoicing template lives, or that an automated reply has a typo in it.
On video walkthroughs
Show the task once, on screen, at normal speed.
Written instructions are useful for reference. A short screen recording is often more useful for training, because it shows the actual clicks, the actual order of steps, and the small decisions a written manual might skip over. Module three covers how to record these without needing production equipment or editing skills.
A five to eight minute video, filmed once and labeled clearly, tends to outlast a much longer document that nobody rereads.
A note on expectations
This course describes a process. It does not promise an outcome.
Every business has different clients, different tools and different tolerance for risk. The five modules walk through a method for documenting, automating, training and testing. How much of it applies, and how quickly, depends on the specifics of your work. The course is built to be adapted, not followed word for word.