Operations · PRACTICAL FIELD NOTE
If your best employee quit tomorrow, would your process leave with them?
A candid, practical field note for small-business owners about if your best employee quit tomorrow, would your process leave with them, with a clear next step.
If your most capable employee called in sick tomorrow, could someone else complete the work they quietly keep moving? In a small business, the answer may depend on one person remembering the right steps, spotting the usual exception, or knowing which customer needs a call first. That dependence can feel efficient. You avoid writing procedures nobody has time to read, and experienced people can solve problems without waiting for permission. But when a key person is away, busy, or ready to leave, what looked like flexibility can become a bottleneck for the whole team. You do not need a manual for every task. Start by identifying one repeatable job where a missed step would cost time, money, or customer trust. This field note will help you choose that task, capture the know-how in a usable format, and test whether another person can follow it before a real handoff is on the line.
What to know
Consider a fictional two-person repair shop. One employee places parts orders and knows which substitutes are acceptable, which jobs are urgent, and when a customer must approve a change. When that employee is away, a colleague delays an order because the checklist says what to do, but not how to handle exceptions. The owner’s useful first step is not to document every task. It is to record one recent order: what triggered it, what information was checked, which decisions were made, what required approval, and when to escalate. Then ask a colleague to use the draft on a routine order and note where they hesitate. The practical lesson: capture decision points and boundaries, not just steps. A checklist cannot replace expertise, but it can show when that expertise is needed.
Put it into practice
Choose a task that matters
Do not start with the easiest task to describe or the person who seems most indispensable. Choose repeatable work where a missed step could cause a costly delay, rework, or a damaged customer relationship. Consider how often it happens, how much judgment it needs, and what happens if it stalls. Frequency is a useful clue, not a rule: a rare task with serious consequences may deserve attention first.
Try this: list three tasks that would become difficult if their usual owner were away for a week. For each, write down what could go wrong and who would notice. Choose one with a clear consequence and a scope you can observe. Instead of documenting “customer service,” for example, define “process a refund request when the original payment is unclear.” If several people or tools are involved, begin with the handoff most likely to lose information.
Record the decisions
Write down what triggers the task, what information is needed, and what counts as a successful finish. Then capture the decisions between those points. For each, note what to check, which options are acceptable, and when to stop and ask for help. “Confirm the order number before changing an address” is more useful than “check the details.” Make approval limits explicit so a colleague can distinguish a routine choice from one outside their authority.
For example, in a fictional online shop, instructions for replacing a damaged item might cover verifying the order and recording the replacement, while directing a colleague to seek approval for a second replacement or a request for cash instead of store credit. The point is not to transfer every judgment; it is to show where routine work ends and escalation begins.
Make it usable, then test it
Choose the simplest format that fits: a one-page checklist, a short decision tree, or a screen recording with brief notes. Include where to find relevant files, what to save, and who can approve a change. Keep passwords out of ordinary procedures; point to the approved access process instead. Put the instructions where the work happens, with the next action and escalation route easy to find.
Ask someone who did not write the instructions to use them on a routine case. Stay available, but note where they pause, guess, or need information the procedure leaves out. Then try one safe exception. If the instructions cover a standard refund, for instance, check what they direct the person to do when the payment record is missing. Success does not mean every case is handled independently; it means the person can recognize a boundary and reach the right decision-maker before making an unsafe promise.
Assign someone to review the procedure when tools, policies, or approval limits change. Try the first version on a few instances and revise the specific gaps the trial reveals. For rare or highly variable work, a named contact and clear escalation path may be more useful than a detailed manual. The aim is a safer handoff, not a claim that written steps can replace expertise.