Skip to content
Efidis
Efidis

OperationsUpdated 10 min read

Write your process manual in an afternoon: template + AI

3D illustration of an open ring binder, a lilac microphone and stair-like blocks as steps.
In this article

The person who does invoicing goes on vacation for two weeks. On the first Monday, nobody knows what order the orders get checked in, which customer has special pricing or why the carrier has to be called before 11. All of it lived in one person's head, and that head is at the beach.

It happens at a lot of companies. In a survey of 1,001 employees at U.S. companies, Panopto found that 42% of the knowledge each person uses in their role is theirs alone: if they're out, coworkers can't do that part of the job. The same respondents said they lose 5.3 hours a week waiting for information from a coworker or redoing something someone already knew how to do (Panopto, 2018). The study covers large companies; at a small business, where each role is held by one person, the risk is usually higher.

The new-hire test

Most manuals fail for the same reason: they're written by someone who already knows the job, for someone who also knows it. They skip exactly the steps the expert does without thinking.

That's why this method has a single rule for deciding whether a procedure is finished, the new-hire test: someone who has never done the process runs it start to finish, sheet in hand, without asking anyone anything. If they have to ask, the sheet isn't ready. Every question is a missing line.

The test changes the goal: every process that matters has to survive the absence of the person who runs it, even if not everything gets documented. That fits in an afternoon if you start with a few processes and use your voice instead of the keyboard.

The template: one procedure, one page

Every process gets a page with the same fields. If a field doesn't apply, write "N/A"; a blank field doesn't tell you whether someone forgot it or it isn't needed.

FieldWhat goes inExample (shipping an order)
NameVerb and object, the way people say it in the officeShip a confirmed order
TriggerWhat starts the processThe customer confirms the order by text or email
OutcomeHow you know it ended wellOrder handed to the carrier and tracking number sent to the customer
OwnerA role, not a name, plus who covers for itShipping clerk; backup: warehouse clerk
Steps5 to 12, each starting with a verb1. Check stock. 2. Pick the items. 3. …
ToolsWhere each step happens: file, system, group chatInventory spreadsheet, invoicing system, carrier portal
Data recordedWhat gets written down and whereOrder number, units, tracking number
What can go wrongThe two or three mistakes that have already happenedShipping without stock; sending to an old address
When to escalateWhen to stop and who to tellIf items are missing or the customer has a past-due balance: tell the manager
Time and frequencyHow long it takes and how often it happens15 minutes per order, about 40 a day
Last reviewedDate and who did itEvery six months or whenever a tool changes

The most valuable fields are the ones almost nobody fills in: "what can go wrong" and "when to escalate." They turn a list of steps into judgment you can hand to someone else.

One page per process, not per department

"Sales" isn't a process; "send a quote," "take an order" and "approve a discount" are. If a page runs past 12 steps, it's almost always two processes stuck together. Split it.

The method: from voice memo to procedure

Writing is tiring, and whoever runs the process rarely has time. Talking is faster: in a Stanford study, dictating on a phone was about three times faster than typing on its keyboard, with fewer errors made while entering text (Ruan et al., 2016). The idea is for the person to explain the process the way they would to a new coworker and let AI do the work of organizing it into the template.

  1. Pick five processes (30 minutes)Choose the ones that meet one or more of these: they stop when one person is out; they touch money or customers; they happen every day; they produce mistakes you already know about. Five is enough for the first afternoon.
  2. Record one voice memo per process (one hour)The person who runs the process records 5 to 10 minutes while doing it or right after. Have them start with what triggers it and end with how they know it went well. Ask them to describe the mistakes they've seen and what they do when something doesn't add up. No customer names or personal data.
  3. Turn each memo into text and into the template (one hour)Use your phone's transcription or the AI tool you already have, and paste the text in with the prompt below. Check that it doesn't invent steps: anything the memo doesn't say should come back as a question.
  4. Review with the person who runs the process (one hour)Read the page out loud with them. Answer the open questions, fix the order and fill in "what can go wrong." This step improves the page more than any other.
  5. Run the new-hire test (30 minutes to plan it)Over the next few days, someone who doesn't usually do the process runs it from the page while the person who knows it only watches. Every time the newcomer asks something, write the answer into the page.

The times are a guide for five simple processes, not a measurement. A process with lots of exceptions may need a second memo.

The prompt to turn a memo into a procedure

Copy and adapt: "Here is a transcript of someone explaining how they handle a process at our company. Turn it into a one-page procedure with these fields: name, trigger, outcome, owner, steps (5 to 12, each starting with a verb), tools, data recorded, what can go wrong, when to escalate, time and frequency. Use only what the transcript says. If a field is missing information, don't make it up: write the question we should ask the person. At the end, list any steps that seem to depend on something that isn't explained."

That last instruction is the one that matters. AI tools tend to fill gaps with something that sounds reasonable. Asking for questions instead of answers turns that flaw into a list of things to confirm.

Be careful with what you record

A memo about how you collect payments or approve discounts can include customer names, amounts and passwords mentioned in passing. Ask people to use generic examples, and check the tool's terms before uploading audio: whether it stores what you give it, for how long and whether it uses it to train its models. If your company already has an AI use policy, apply it here. If you don't have one yet, here's an AI use policy template.

The map: how your processes hand off work

Once you have the first pages, line them up. A process almost always ends where another one begins, and mistakes live in those handoffs. Here's an illustrative example of the quote-to-cash chain at a company that sells to other businesses:

ProcessTriggered byOwnerWhat it hands to the next one
QuoteA customer asks for pricingSales repApproved quote with prices and terms
Take the orderThe customer accepts the quoteSales rep or sales assistantOrder with products, quantities and address
ShipConfirmed orderShipping clerkGoods delivered and tracking number
InvoiceShipment confirmedAccounting clerkInvoice issued with a due date
CollectDue date is near or pastCollections or managerPayment received and applied to the invoice

Look at the last column. If "what it hands to the next one" gets passed along by copying it from one file to another or forwarding a message, that's the weak spot. Write it into "what can go wrong" on both pages it touches.

From manual to improvement

Writing processes down has a side effect you weren't looking for: it shows you what's being done badly. Asana surveyed more than 9,600 workers in six countries, and they estimated that better processes would save them 4.9 hours a week (Asana, 2023). That's the workers' own estimate, not a measurement, but it matches what shows up when you put a process on paper: repeated steps, approvals nobody checks, data typed in twice.

With the pages in hand, use this checklist to see which processes are ready to automate.

  • It passed the new-hire test: someone ran it start to finish from the page without asking.
  • It's done the same way every time; the exceptions are written down and there are few of them.
  • It happens more than once a week.
  • The data it uses already exists in a file or system, not just in someone's memory.
  • It has at least one step that's copying data from one place to another.
  • You know how long it takes today, so you can compare later.
  • The owner agrees with the page and wants it to change.
  • It hasn't changed in the last three months and isn't expected to change soon.

A process that checks nearly every box is a good candidate to move into a system. One that fails the new-hire test isn't ready yet: automating something nobody can explain just makes the mess move faster. To put a number on it first, use the formula in what manual data entry costs.

When it isn't worth it

Documenting takes time too, and not every process deserves it. Skip the page or put it off if:

  • The process happens twice a year and the owner does it. A five-line note is enough.
  • The process is changing this week. Wait for it to settle; documenting a moving target means rewriting it.
  • The company is two or three people who sit together and cover for each other without trouble. The risk is real, but smaller.
  • Your industry requires procedures in a format and with sign-offs set by regulation (food handling, healthcare, workplace safety). The one-page sheet works as a draft, but it doesn't replace the official document or the review of whoever signs it.
  • What you actually want is to fix the process, not describe it. If everyone knows it's broken, writing down the broken version in detail won't help; decide first how it should work.

A manual nobody opens goes stale in months. Keep it where the work happens (the shared folder people already use, pinned in the team's group chat) and put a review date on every page. When a tool or an owner changes, the page gets reviewed that same day.

What comes after the first afternoon

Five pages aren't a complete manual, but they cover what carries the most risk. Repeat the method one afternoon a month with the next five processes on the list. In a quarter you'll have the 15 processes that run your operation, each one tested by someone who didn't know it.

At some point the manual will describe steps a system could do on its own: check stock before confirming, flag a customer with a past-due balance, send the order to invoicing without retyping it. That's when the manual stops being just a document and becomes the spec for how your software should work, whether it's off-the-shelf or custom. That's where a custom software project starts.

Sources

  1. Panopto, "Workplace Knowledge and Productivity Report," 2018 (YouGov survey of 1,001 U.S. workers), as covered by HR Dive (opens in a new tab)
  2. Ruan, S., Wobbrock, J. O., Liou, K., Ng, A. and Landay, J., "Speech Is 3x Faster than Typing for English and Mandarin Text Entry on Mobile Devices," arXiv, 2016 (opens in a new tab)
  3. Asana, "Anatomy of Work Global Index 2023," 2023 (opens in a new tab)

Frequently asked questions

Keep your operation from depending on one person

Efidis turns your procedures into an app that guides each step and records who did it. On the call we'll go over your process sheets and which one to move into the system first.