← Back to SOPs & Operational Excellence
Why do SOP projects turn into bureaucracy?
In my experience the usual cause is ambition without priorities. A leader decides the business needs procedures, a template is circulated and every team is asked to document everything. Months later there is a large library, much of it describing low-risk tasks, and very little of it in use. I covered the common failure patterns in why SOPs fail.
Which procedures should you write first?
Use a simple risk-based filter. Score each candidate activity against three questions:
- Consequence — would getting this wrong harm a customer, a colleague, your reputation or your legal position?
- Dependency — does it rely on knowledge held by one or two people?
- Variation — do different people or sites do it differently, with visibly different results?
Activities that score high on two or three of these go first. Everything else waits, and some things never need a procedure at all — good judgement and a short guideline are enough.
Who should write them?
The people who do the work, with someone to provide structure. Frontline co-authoring produces procedures that match reality, and it changes how they are received: people follow what they helped create. My role is to facilitate, apply consistent structure and checklist discipline, and keep the language plain. Your business approves the result, following the roles in who should create, approve and manage SOPs.
How short should an SOP be?
Short enough to use at the point of need. Aviation checklists are deliberately brief because they are used under time pressure; the background lives in manuals. That is aviation practice, not a rule for your business, but the idea transfers well. A useful target is one or two pages of steps, with the critical points easy to see and background linked separately.
How should you roll them out?
- Pilot — introduce three to five priority procedures in one team or site.
- Listen — ask after a few weeks what was unclear, what was missing and what was ignored.
- Revise and approve — update, re-approve and record the version.
- Train — brief the people affected, focusing on why each procedure exists.
- Extend — move to the next team or the next set of priorities.
Once procedures are approved, your Company Operations Hub gives employees one place to find the current version, and I support six-monthly training, refreshers and updates.
How do you win over sceptical managers?
Sceptical managers usually have good reasons: they have seen procedure projects waste time before. Rather than arguing, I suggest three things. Start with a problem they already feel, such as repeated errors at a handover. Involve their most experienced people as authors, so expertise is respected rather than overruled. And agree up front which procedures will not be written. Showing restraint does more for credibility than any presentation.
How often should procedures be reviewed?
Every procedure needs a review date proportionate to its risk. I work on a six-monthly training and update cycle, while any material change to a critical procedure should be communicated immediately. Measuring whether procedures are actually helping is the subject of how to measure operational excellence.
Frequently asked questions
How many SOPs does a small business need?
- There is no correct number. Start with the handful of activities where inconsistency costs the most, and add more only when there is a clear reason.
Should we buy a template library?
- Templates can help with format, but borrowed content rarely fits. Procedures should reflect your own Business DNA and the way your people actually work.
What if staff resist?
- Involve them as authors, explain why each procedure exists and act on their feedback. Resistance often signals a procedure that does not match the work.
Who signs off each procedure?
- A named approver in your business. I facilitate documentation; approval remains yours.
Read about my methodology, or book a discovery call to plan a sensible starting point.
