Watch three employees issue the same type of invoice and you'll often see three different procedures — different templates, different sequences, different ideas of what "done" means. None of them is being careless. Each learned the task from a different person, on a different day, under different pressure. The company doesn't have a process; it has an oral tradition. And oral traditions don't scale, don't survive resignations, and don't pass audits.
The standard prescription is "write SOPs" — standard operating procedures. The standard result is a thick binder, produced over a painful month, admired once, and never opened again. The failure isn't the idea; it's the format. Here's the version that works.
Why the binder fails
Long SOPs fail for predictable reasons. They're written by someone who doesn't do the task, so the steps describe policy, not reality — and the team quietly ignores documents that are wrong about their own work. They live far from the work — a shared drive nobody browses at the moment of doing. They try to cover every eventuality, which makes them long, which makes them unread. And they're never updated, so six months later the one person who did consult the SOP did the task the old way. A procedure that isn't read at the moment of work isn't a procedure; it's a liability with page numbers.
The one-page method
Four rules produce SOPs that survive contact with reality.
One page per task. Hard limit. If it doesn't fit, you're documenting two tasks — split them. The discipline of one page forces the only question that matters: what does the doer actually need at the moment of doing? Steps, the two decisions with rules ("discount above X → owner approves"), the one screenshot that matters, and what "done" looks like. Everything else is commentary.
Written with the person who does the task, not about them. Sit together for twenty minutes. They narrate, you write, both of you discover the workaround step nobody knew about. The document that results is theirs — and people follow their own documents with a loyalty no policy memo ever earns.
Stored where the work happens. Not a binder, not a distant drive — attached to the task itself. If invoicing happens in your system, the invoicing SOP belongs in the system, one click from the invoice screen. The moment of doubt and the answer must be in the same place.
Reviewed on trigger, not on schedule. Annual reviews die quietly. Instead: the SOP gets updated the day the process changes, by the same twenty-minute method, and the change is announced in one line. A living page beats a maintained library.
Which tasks to document first
Not all of them — that way lies the binder. Start where the money flows and the risk lives: how a quote becomes an invoice, how a payment gets recorded and reconciled, how goods leave the warehouse, how a new supplier gets approved, what month-end requires from each person. Five to eight one-pagers, chosen this way, typically cover the paths where inconsistency actually costs money — and where an auditor, a bank, or the FTA might one day ask "show me how this happens."
The multilingual detail that decides everything
A UAE-specific truth: your storekeeper, your accountant and your sales lead may not share a first language. An SOP written in polished English for a team that thinks in Arabic or Persian is compliance theatre — technically present, practically absent. Write each SOP in the language of the person who does the task. It's a small discipline with an outsized effect on whether the page gets read at 5pm on a Thursday under pressure — which is the only moment that counts.
From pages to system
One-page SOPs stand on their own — you can start this week with a notebook and twenty minutes per task. But their full value arrives when the SOP and the system agree: the documented approval limit is the system's approval rule, the documented sequence is the default workflow, and deviation requires effort instead of memory. At that point the procedure stops depending on anyone's discipline, including yours. That pairing — the page for humans, the configuration for enforcement — is how a company stops being an oral tradition and starts being an organisation.
FAQ
How do I write an SOP employees will actually follow?
One page maximum, written together with the person who does the task, stored where the work happens, updated the day the process changes. Format matters more than thoroughness.
Which SOPs should a small business write first?
The money paths: quote-to-invoice, payment recording, goods out, supplier approval, month-end duties. Five to eight one-pagers cover most of the real risk.
What language should SOPs be in?
The first language of the person doing the task. In UAE teams that often means the same procedure exists in English, Arabic or Persian — matched to the doer, not to the head office.
What's the difference between an SOP and a process map?
The map shows how a whole flow moves across people; the SOP tells one person exactly how to do one task inside it. Map first, then write SOPs for the steps that need consistency.