How NOT to Write Standard Operating Procedures (SOPs) 

Thank you so much for this helpful video. I have been having some difficulty in creating an effective SOP because of your point number 4 I think that an SOP should be as long as it needs to be to convey the correct way to perform a task if you walked off the street and sat down. No tribal knowledge, no assumptions. I look at it this way, imagine if you had a flat tire and couldnt figure out how to release the spare tire in your trunk (this happens all the time). You open the manual and they "skimmed" because they felt it was "too long" . This would not be an effective instruction manual. I would also, respectfully argue, that it is not the businesses problem that the worker has a short attention span and doesn't "feel like" reading the SOP. Now I am all for short, concise and grouping section together to avoid redundancy, in an SOP but there is a clash of culture and procedure going on out there that will ultimately affect performing tasks in a negative way.

How would you write an SOP for say Cargo Acceptance for Air Cargo, where there are different ways to accept for example, a live animal, dangerous goods, human remains etc.

Want to work with me to get your SOPs updated (or created for the first time)? Join me for a live workshop on September 21, 2023. 🔗 Here's where you can learn more: processdriven.co/services/sop?YT&YTOrganic&

Want to work with me to get your SOPs updated (or created for the first time)? 1 - Join my next live SOP workshop: processdriven.co/services/sop 2 - Unlock 109 SOP examples: processdriven.co/sop

One of the biggest issues I come across is being told, That wasn't included in the training, or I wasn't taught that by the trainer. How do we eliminate documenting the anomalies and still hold people to broad language? Example, keep shoes tied when getting on and off equipment. This statement would never be included in our training but is an anomaly soon as someone trips