Why Your Team Ignores The SOPs You Wrote
Writing your SOPs is hard. Getting your team to follow them takes a rollout: a walkthrough, a quiz they sign off on and a weekly scorecard.
Most teams ignore written SOPs because nobody walked them through each process and nothing checks whether they follow it. Writing them is hard. Getting your team to follow them is the other half, and that half is the rollout.
Why do written SOPs sit unused?
Picture a three ring binder on a shelf. Nobody reads it. A folder of Google Docs goes the same way, because there's nothing in it to use. There's no checklist to fill out and nothing to submit.
When the Ten Commandments came down the mountain, the people down below were building golden calves. Hand your team a finished set of SOPs they had no say in, and you'll get about the same result.
How do you roll out an SOP so your team follows it?
The rollout I teach has five steps. Write it, save it, walk your team through it, give them the quiz, then put it on a weekly scorecard.
Write the process the way your company actually runs it. If someone is already doing the job, build it with him. Show it to your superintendent and ask what he'd change. He knows the work, and once he's had his say, it's his process too.
Then put it on a page in the SOPs area of your Structur account, under the department it belongs to. Everyone in that department finds their processes in one place.
How do you walk your team through it?
Book an hour with the people who'll run the process. Read it front to back, every bullet point, and spend the back half of the hour answering their questions.
Explain why each step is there. People follow processes they understand.
What's the quiz for?
The quiz is a sign-off. Say one field management question asks how often a superintendent does a daily log. The choices are monthly, quarterly, yearly and daily. He reads it, picks daily and clicks submit, and his name is on that answer.
Answering it also makes him think the process through, so it sticks. A Structur SOP page can hold a quiz element right under the written process. He reads it and answers it in the same place.
If he scores below 80%, go back over the parts he missed. The quiz comes back later too. Say a superintendent stops doing daily logs every day. Send him back to take the whole quiz for his role, then go over it with him.
What's the weekly scorecard for?
The scorecard holds each person to the numbers for his role. Set a weekly goal, like five daily logs. If he puts in four, it turns red. Five or more turns it green.
Add a scorecard element to the same SOP page in Structur and look at it every week. It's like Christmas: you look for the red and the green, and you know how that department is doing.
Start tracking it in week one. Without the scorecard, you're guessing whether the process works.
What if someone keeps skipping it?
A team member who keeps skipping the process after all that has a performance problem. You've got a quiz with his name on it to start that conversation.
When someone calls you with a question the SOP already answers, tell him to go read the SOP. Do it every time, and the page becomes the first place your team looks.
This week, pick the department giving you the most trouble. Take one of its processes and book the hour to walk that team through it.
More From The Blog
How To Code A Supplier Statement For Job Costing
Split every supplier statement line by line to the job and the cost code. One materials line can't show you what any part of the job cost.
Read the post 2 min readStandard operating proceduresHow To Run A Construction Knowledge Quiz In An Interview
Run the construction knowledge quiz live, one question at a time, as a conversation. A candidate who hasn't done the work can't keep it going for long.
Read the post 2 min readSubcontractsShould A GC Subcontract Every Trade?
In-house crews come with vehicles, gas and insurance. Subbing out most trades turns your company into a management company that can grow past ten million.
Read the post 2 min read