Processes

How to document a process people actually follow

delpra™ team6 min read

Almost every company has tried to document its processes. Someone spent weeks writing a manual, the file went into a shared folder and was never opened again. The problem is rarely a lack of discipline on the team. It is that the document was made to exist, not to be used.

Why the manual nobody reads keeps getting written

Documentation usually begins in a moment of alarm: someone important left, a mistake cost a lot, an audit is coming. At that point, the goal becomes "having everything documented". The result is long texts, written by people who already know how to do the work, for people who do not, with nobody testing whether the task can be done from the text alone.

Michael Hammer, in "The Process Audit" (Harvard Business Review, 2007), lists what a process needs to work: a clear design, people who know how to execute it, an owner, supporting infrastructure and metrics. Documentation is only the record of the first item. Without an owner and without daily use, it goes stale within weeks.

Three signs the document will not be used:

  • It describes the ideal process, not what really happens.
  • It is far from the work. To look something up, the person has to leave the system, find the folder and open a twenty-page file.
  • Nobody is responsible for updating it. At the first change, the text becomes wrong, and a wrong document teaches the team not to trust any of them.

What is worth documenting

Documenting everything is the fastest way to end up maintaining nothing. Start with what hurts:

  • processes that only one or two people know how to do;
  • processes that cause the most errors, rework or complaints;
  • processes that repeat every week and cross more than one area;
  • processes you plan to automate next.

The last item matters more than it seems. As we show in Map the process before you automate it, automation inherits the quality of the process. Documenting well is the first step of the project, not a separate bureaucratic task.

A format that fits on one page

The best format is the shortest one that lets a newcomer carry out the task without asking questions. In practice, one page per process, with six blocks:

  1. What it is for. One sentence stating the expected result. Example: "the new customer receives access, a contract and a first meeting scheduled within two business days".
  2. When it starts. The trigger: an approved order, a submitted form, the first business day of the month.
  3. Steps. Five to nine steps, each starting with a verb. If it goes past nine, it is probably two processes.
  4. Who does each step. The role, not the person's name.
  5. How to know it is done. The completion criterion for each step. It is the item most often missing and the one that prevents the most rework.
  6. What to do when it goes wrong. The two or three most common exceptions and who to take them to.
If a person needs more than three minutes to find the answer in the document, they will ask a coworker. And the process goes back to living in someone's head.

Screen details, such as "click the blue button", work better in a short video or in screenshots tied to the step. They change every time the system changes and should not clutter the main page.

How to write it with the people who do the work

The document has to be written together with the people who do the work, not by an outsider who interviews them and disappears. A routine that works:

  1. Watch a real execution. Ask the person to do the task while narrating what they do. You will discover steps they do not even remember exist.
  2. Write the draft in an hour. A rough draft today is worth more than a perfect manual a month from now.
  3. Test it with someone else. Hand the page to someone who has never done the task and ask them to carry it out. Every question they ask is a hole in the document.
  4. Fix it and publish it where it is used. Inside the tool where the task happens: on the CRM card, in the recurring task, in the area's channel.

Imagine a clinic documenting how follow-up appointments are scheduled. During the observation, it finds out that the receptionist checks the patient's health insurance on an external website before confirming. That step was written nowhere, and it was exactly the one that got stuck when she was out.

How to keep the document alive

Documentation dies of neglect. Three simple practices keep it going:

  • An owner with a name and a date. Each process has someone responsible for the document and a visible date of the last review.
  • Review by event, not by calendar. Did the system change, did the rule change or did a mistake happen? The document is updated the same day. A quarterly review serves only as a safety net.
  • Use in training. Every new person learns from the page. If they cannot, the flaw is in the document.

When the process starts to run inside a system, with steps, owners and deadlines configured, a good part of the documentation stops being text and becomes the flow itself. The system shows the next step, and the document is left with only the why and the exceptions. It is the best destination for a well-documented process.

Common mistakes

  • Starting with the easy processes. It feels like progress and reduces no risk at all.
  • Writing in policy language. "The employee shall proceed to the verification" pushes the reader away. Write the way people talk: "check that the payment came in".
  • Storing it in several places. One version on the drive, another in email, another printed. There should be a single address.
  • Documenting to punish. If the document only shows up when someone makes a mistake, the team learns to avoid it.

Where to start this week

Pick one process, the one that generates the most repeated questions. Watch one execution, write the six-block page and test it with someone from outside the area. In a few days you will have a template to repeat on the next ones.

After three or four processes documented this way, it becomes visible where the repeated manual steps are, and the conversation about what to automate first stops being guesswork. Process mapping and structuring is the first of delpra™'s services for exactly this reason: it is the foundation for everything else.

Written by the delpra™ teamProcesses, automation and AI so operations scale efficiently.

How mature are your operations?

The Operational Maturity Assessment takes 4 minutes and shows where to start.

Take the free assessment

Read next