The owner is away for a day, and a routine customer request sits unanswered because only one person knows which form to use, who approves an exception, or where the current file lives. That is not a motivation problem. It is a process that exists in someone’s memory instead of somewhere the team can use it.
Choose the right process
Do not begin by trying to document everything. Pick a task that happens often, has a clear beginning and end, and regularly creates questions for someone else. In a repair shop, that might be how a new job moves from intake to an estimate; in a small online store, it could be handling a damaged shipment.
Write for the next person
Capture the steps in the order they happen, including where to find the necessary information and which decisions require approval. Add a sample of a completed form or message when it clarifies what “done” looks like. A short working guide is more useful than a polished manual that skips the awkward exceptions people actually encounter.
Test it during real work
Ask a colleague who does not own the process to follow the guide on the next suitable job. Watch for the moment they have to stop and ask what comes next; that is where the documentation needs more detail. Update the guide when the process changes, and assign someone to notice when its instructions no longer match the work.