Ask a growing business whether it has SOPs and the answer is often yes. Ask to see one being used on the shop floor or in the accounts department, and the answer changes. The file exists. The practice does not.
This is not a discipline problem. In our experience, SOPs fail for a handful of predictable reasons, and each has a practical fix.
They describe the ideal, not the work
SOPs are frequently drafted by a manager, a consultant or an auditor working from memory and good intentions. The result describes how work should happen in theory. The people doing the work recognise this immediately and carry on as before.
The fix is to write the SOP by watching the work, with the person who does it. Where the current practice is wrong, change it deliberately and say why. Where it is right, record it as it is.
They are too long
A twelve-page procedure for raising a purchase order will not be read. A one-page checklist with a flowchart, linked to the actual screen in Tally or the ERP, will.
Good SOPs are written for the person at the desk, in the language they work in. For stores, dispatch and production staff that is often Gujarati or Hindi, not English.
Nobody owns them
An SOP without an owner has no one to update it when the process changes, and no one to decide what happens in an exception. In owner-led businesses, the default owner of every exception is the promoter, which is exactly the dependency the SOP was meant to remove.
Each SOP needs a named owner, a deputy, and a review date.
Exceptions are not designed
Real processes are mostly exceptions: the urgent order, the customer over their credit limit, the material that arrived short. If the SOP covers only the normal case, every exception becomes a phone call to the owner.
The useful question is which exceptions happen every week, who can approve them, and up to what limit. That is where SOPs connect to a delegation of authority matrix.
They are not checked
Procedures that are never tested drift. A light monthly check of a handful of transactions against each critical SOP, done by someone other than the process owner, keeps them honest without becoming an audit.
A practical starting point
Do not start by documenting everything. List the ten processes where mistakes cost the most money or depend on a single person, write those first, and run them for a month before moving on. A small set of procedures that are actually followed is worth more than a complete manual on a shelf.