Monday, October 22, 2012

Yes, SOPs Are Hard To Write…It’s Not Just You

Ask anyone who works in a regulated industry about the purpose of SOPs and you’ll be told it has to do with minimizing variation.  Consistency, they’ll say, promotes quality.  It follows, then, that SOPs must be straight-forward and unambiguous.  If procedures are too complex or can be interpreted in a number of ways, they will not produce consistent results, and quality of the end product, whatever it is, will be at risk.  Simple.  Obvious.  SOPs 101.
It’s too bad for us that tasks are not always simple or obvious.  Often, a worker can achieve a quality result only by correctly responding to a number of variables that could arise.  An SOP that outlines such procedures has to describe each situation the worker might encounter and then provide the appropriate corresponding response.  In complicated procedures, these situations can become nested.  (Is it A, B, or C?  If it’s C, is it X, Y, or Z?)  An otherwise simple, linear set of instructions can quickly become a complex decision tree.  Also, the distinction between situations that require different responses may not be clear cut, and may only be a matter of degree.  Unless decision criteria are thoroughly explained, each worker will devise his or her own, and consistency will be lost.  Naturally, the more complicated the instructions, the more subject to misinterpretation they are.  SOP writers are challenged to capture all this complexity in a clear, concise set of procedures.
We expect a lot from our SOPs.  In many companies, SOPs don’t just supplement training, they are training.  Once upon a time, new employees were mentored by seasoned workers who would teach them the rationales behind the procedures and share undocumented nuances that they’d learned over the years.  Now, with mentorship programs becoming an extravagance most companies can no longer afford, we increasingly rely on SOPs to communicate that accumulated wisdom.  We also use SOPs to demonstrate regulatory compliance.  Sometimes, we even expect to use our SOPs as a means of legal defense, should our conduct be called into question.  Is it any surprise that the more we try to cram into our SOPs, and the more masters we have them serve, the harder it is for us to write them in a concise, easy-to-follow manner?
Smaller companies, with minimal or non-existent training staff, may rely more heavily on SOPs than their larger counterparts do, yet maintaining SOPs requires a significant resource commitment of its own.  Subject matter experts are needed to research the latest regulations, determine their impact on existing procedures, and author updates.  It’s difficult for experts in small companies to move steadily through this process because SOP maintenance is necessarily put on the back burner when profit-generating work demands. 
So, if all along you’ve been wondering why writing and revising your set of SOPs seems so hard or takes so long, maybe you can take some comfort from the fact that it’s not just you!
By Laurie Meehan

If you think you might like some help writing or maintaining your SOPs, contact us at info@polarisconsultants.com and we’ll set up some time to talk.

2 comments:

  1. i believe that SOPs have come to do with more of "WHAT" & "HOW" & "WHEN/WHERE - WHO" .... added up where "transfer of undocumented naunces...mentorship" are becoming rare + compliance attitude of personnel monitoring/governing it...!!!

    SO, one way to get around is to add the "WHY"/Rationale"and "ever evolving DECISION TREES" to the SOPs and start maintaining the same.
    that way, Quality function can add the value and keep the SOPs concurrent and sync with current process realities...& alive!!!

    one technology alternative could be to evolve the SOPs with wikis;

    ReplyDelete
    Replies
    1. I think your Wiki idea is a very good one. Off the top of my head, I'm thinking that contributions could be divided into "Tips for Use", "Suggested Correction/Improvement", etc. Have you ever tried this approach to keeping SOPs current? Have you had any success? Thanks!

      Delete