SOPs feel like an administrative overhead to many team leaders and it drives them nuts keeping them up to date. It would drive us nuts too if we had to follow the all these steps advocated by some. They generally consist of a set of detailed instructions showing how to perform a complex operation in a piece of software. People find them especially useful if they perform the task infrequently.
Today, we did a demo where we recorded a process for a set of SOPs for a team. After recording the process we did some very basic editing and produced a manual, a quick reference guide and a powerpoint presentation along with the e-learning. This was all perfectly on brand and nicely presented. From start to finish it took about 30 minutes and it would have been quicker if it wasn’t for the fact that we were teaching how to do a recording at the same time as we did the recording, and the team leader did most of the work herself.
An average SOP has got to be about 2-3hrs to build using MS Word / Snagit or Snipping tool. This took about 30 mins, so saved about 2.5 hrs per SOP.
Multiply that up to 20 or 30 SOP’s and you are easily in the 1 to 2 weeks worth of work saved, plus the boredom of writing SOPs helps make people want to leave companies.
No wonder the team leader in question looked happy.
Let us know if you’d like a demo as well..!
Addendum: Since writing this article an audit has been performed and on top of the massive saving in time and effort the auditor was very impressed with the quality.