Every stable business already has an operations manual — it is just stored in the owner's head and a few senior employees' habits, which means it walks out the door at every resignation and never scales past one location. Writing it down is how a business becomes an asset instead of a job. This is a practical method for producing a manual your staff will actually use, without stopping the business to write a book.
What goes in — and what doesn't
An operations manual answers one question repeatedly: 'how do we do this here?' Structure it by the business's real flow. A restaurant's chapters: opening procedures, prep and recipes, service standards, billing and cash, closing, cleaning schedules, purchase and receiving, complaint handling. A trading firm's: enquiry handling, quotation rules, order processing, dispatch, collections, returns. Leave out philosophy and history; include exactly the decisions a competent new employee would otherwise interrupt you to ask.
Capture reality, don't author fiction
- Follow your best performer through each process and write what they actually do — the manual should encode your A-player, not an ideal nobody follows
- Use phone video liberally: record the process once, transcribe the steps, keep the video as training material
- Write in numbered steps, present tense, one action per line: 'Weigh the dough ball — 110g ±5g' beats a paragraph
- Photograph the standard: the correctly set table, the properly stacked shelf, the completed form — pictures enforce what prose cannot
- Note the 'why' in one line where it prevents corner-cutting ('gloves because bare-hand contact fails FSSAI audit')
Checklists for routines, procedures for exceptions
The workhorse format is the checklist — opening, closing, cleaning, weekly maintenance, month-end — printed, laminated, signed daily. Procedures (step-by-step documents) suit tasks done occasionally or by new people: making a specific product, processing a return, responding to an inspection. Decision rules cover judgment: refund limits staff may approve, discount authority, when to escalate to the owner. Most manuals fail by writing procedures for everything; a great manual is 60% checklists, 30% procedures, 10% decision rules.
Don't plan a six-month manual project. Week one: write the opening checklist, the closing checklist and the three processes that generate the most mistakes or questions. Use them for a month, fix them, then add the next three. A living 20-page manual beats a planned 200-page one.
Make it usable at the point of work
A manual in the owner's drawer is decoration. Put each piece where the work happens: the cleaning schedule on the store-room door, recipe cards at the prep station, the billing-error procedure at the counter, everything also in a shared digital folder (or a simple app) searchable by phone. Version-control lightly — a footer with date and version — and ruthlessly remove outdated pages; one wrong instruction discovered by staff discredits the entire manual.
Drive adoption like a manager, not a librarian
Documents don't change behaviour; management routines do. Train against the manual (new staff learn from it, not from shadowing whoever is free); audit against it (weekly spot-checks of two checklists, findings discussed openly); update through it (when something fails, the fix is written into the page, so the manual absorbs every lesson); and appraise with it (following standard is part of reviews). Within a few months the sentence you are working toward appears naturally: 'check the manual first' — said by staff to each other, not by you.
How Aidwish helps
Aidwish writes operations manuals as part of its SOP stage — process capture on site, checklist and procedure drafting, digital deployment and the audit rhythm — so the founder's standards survive absences, expansion and attrition.