HDI: So You Want To Write An SOP

**A standard operating procedure (SOP) is a procedure specific to your company or organization that describes the activities necessary to complete a particular task. **

-The article's author feels that writing SOPs is both science and art. While I'd agree, the proof is always in the pudding. Rule #1 is an SOP MUST BE EFFECTIVE. Otherwise, it is trash. Here are some other observational truths about SOPs:

• They are not completely standalone. SOPs must be informed by policy (from above its level), and contribute to Work Instructions (to below its level).

  • Policy answers the "Why", and Work Instructions more specifically get to the "How." SOP is the in-between "some-why"/"What"/"When"/and "some-how"

• SOPs encourage consistency in execution, which is important in a team environment.

• SOPs must be kept current. SOPs that aren't current, aren't effective (See Rule #1).

Things to consider

-SOPs must be:

• Readable - legible font sizes, numbered pages, titles, numbered paragraph headings, and effective use of whitespace

• Consumable - Using a template or predefined format so its easier to read.

• Understandable - Focused and to the point. simple terms

• Actionable - Clearly describe what is to be done.

• Measurable - All described activities should be specific and measurable.

Make A Plan For Writing Your SOP

Write an Outline, Or Make a Flowchart.

Define your terms, and Write out the processes step-by-step.

Add a paragraph at the beginning to intro the topic

Add a section at the for possible troubleshooting and desired endstates, or what to do next if unsuccessful.

You're done!

Five Guiding Principles

1. Keep It Simple

2. SOPs Should be Portable

3. Flowcharts and Diagrams tell a story

4. Consistency counts

5. Remember Your Audience

Things I want to know more about