operations · 4 min read

Write a process people will actually use

Turn a recurring task into a short, clear guide that survives a busy working day.

A useful process document helps someone complete the work. Start with a real example and the person who currently does the task. Watch the sequence, including the small decisions that experienced people often skip when explaining it.

Define the start and finish

Write one sentence for the trigger and one for the finished result. “When an approved enquiry arrives, create a complete handover record for the delivery team” is easier to follow than a broad instruction to “manage enquiries”. Name the owner and the expected handover.

Capture decisions, not just clicks

List the necessary steps in order. At each decision, explain what information is needed and what happens if it is missing. Include one example of a good output. Keep passwords, personal information and sensitive records out of the document.

Test it with someone else

Ask a colleague who does not usually do the task to use the draft. Observe where they pause or ask a question. Improve those points before adding more explanation everywhere else. A short checklist alongside a worked example is often easier to use than a long narrative.

Give the document an owner

Record who maintains it and when it was last checked. Link to the current version from the place where people actually work. Review it after a meaningful change to the process, and remove steps that no longer serve the outcome.