Meera did everything the business gurus said.

She spent her entire Diwali week writing SOPs. Forty-three pages. Every process documented. Printed, spiral-bound, three copies. Handed out in the Monday meeting to applause.

Six months later, she found one of the copies.

It was propping up a wobbly monitor in the accounts room.

Nobody had opened it after week two. Not because her team is lazy. Because the manual was built for an audit, not for work.

SOPs fail because they're written to impress, not to use.

Here's the difference nobody explains. A manual answers "what should ideally happen." Work needs "what do I do right now, at this desk, with this order in front of me."

A 43-page document competes with human memory — and loses every time. When following the SOP takes longer than asking the founder, everyone asks the founder. The binder becomes decoration, and the business goes right back to running on memory and shouting.

And there's a structural reason it stays dead: no owner, no review date, no consequence. An SOP that nobody owns is an orphan. Orphans don't get updated. Outdated instructions get ignored. Ignored once, ignored forever.

How do you make SOPs your team actually follows?

Six rules, learned the expensive way:

  • One page per process. Not one manual per company. A checklist, not an essay. If it doesn't fit on one page, you've written two processes — split them.
  • Keep it at the point of work. Laminated at the machine. Pinned in the department's WhatsApp group. First tab of the sheet they already open daily. An SOP in a drawer is a rumour.
  • Give every SOP an owner and a review date. One name, one date, written on the page itself. Ownership is what separates a living system from a dead document.
  • Build it WITH the person doing the job. Let the doer dictate the steps; you clean up the language. People follow what they helped write. They quietly sabotage what was handed down.
  • Audit by rhythm, not by mood. Two SOPs a month: stand there, watch the actual work, compare it to the page. A gap always means one of two things — update the paper, or retrain the person.
  • When a mistake repeats, fix the checklist before blaming the person. A repeated error is the system's confession, not the employee's crime.

Do this and something shifts. New employees become productive in days, not months. Quality stops depending on who came to work today. And the founder's phone goes quiet — because the answers now live on the page, not in his head.

The real question

Take your newest employee. Hand them your best SOP. Can they complete the task without asking anyone a single question?

That is the only test an SOP ever needs to pass.

If you want to know which five processes in your business deserve a one-page system first — the ones currently living in only one head — that's exactly what we identify in a complimentary Strategic Advisory Session with our Director of Strategy.

Book a Strategic Advisory Session →

Related reading: Who Is Your Rajan? · The Factory That Runs on One Man's Memory

Founders also ask

What is an SOP in business?

A Standard Operating Procedure is a written, repeatable way to do one task so the outcome doesn't depend on who performs it. In practice, the useful format for an SME is a one-page checklist kept at the point of work — not a thick manual stored in a cupboard.

Why do employees not follow SOPs?

Usually because the SOP is longer than the task, lives far from the work, was written without the people who do the job, and has no owner or review. When asking the boss is faster than reading the document, the document dies. Fix the format and placement before blaming discipline.

How long should an SOP be?

One page. List the trigger (when this process starts), the steps in order, the quality check, and who to contact for exceptions. If a process genuinely needs more than a page, it is two processes — split it and give each its own checklist.

Which processes should an SME document first?

The ones that live in only one person's head — your Rajans — and the ones where mistakes repeat: order entry, quotation, dispatch checks, payment follow-up, machine changeovers. Documenting these five typically removes the majority of daily firefighting and founder interruptions.