Today, we're talking about standard operating procedures. So if you want your team to actually perform better, you need to learn how to create better SOPs. So in today's video, I'm going to walk you through seven steps to creating SOPs that your team will actually use and make them 10 times more effective. Now, after watching this video, I guarantee you will think differently about systems.
By the way, my name is Stacy Tushal and I've been a business owner now for over 22 years, and my businesses generate over $10 million in annual revenue, and I've written hundreds of SOPs for my businesses and many others. So step one is understanding the difference between SOPs versus trainings. So a lot of people lump these two together, but they're not the same thing. And SOP is how we do this task.
Think step by step instructions or a playbook of this is how we do things here. This could also be in written and or video format. It should be clear and replicable. So you want anybody to be able to read that document and be able to do it without you.
This is your process is documented so anybody can actually follow it. Now training is how you learn this job. Training is actually using the SOPs you've already built. And it adds contacts and coaching and practice and feedback.
So we drill them. This is your opportunity to teach how you execute, not just read the steps. So when you say make sure you're friendly when somebody opens the door. Okay, well what does friendly mean to somebody, right?
You actually want to show them how you get up out of your chair and you say hello, welcome to the studio, right? And you're smiling and you're using hand gestures. Show, don't just tell. We all have different ideas of what friendly means.
Now here's another rule. An SOP is the recipe. Training is the cooking class. Hopefully that helps.
Your team can't succeed if you only give them one without the other. You need both. Step number two is pick the right format. If the format isn't clear, the SOP won't actually get used period end of story.
So here are the most effective formats that we have seen for standard operating procedures that teams will actually reference. So one is just a simple Google Doc. I can't tell you how many times people will say, what fancy software do I need to buy? Or what should I be using this?
Should I be using that? You can, but you don't have to. It could be as simple as Google Docs, which you're probably already using. Now it also could be using a software like Trainio or Notion.
These are all great options for written procedures. Loom videos are great if you want something visual or it's tacked based or you're actually watching through how to go specific softwares. You can also screenshot with Markups. This is ideal for click heavy system.
So think CRM's scheduling tools with things with multiple steps. A checklist inside of your project management tool. You can make it actionable by embedding right inside of monday.com, click up or sauna. This is actually what we use most often and we actually just link it to Google Docs.
Bonus tip, use consistent naming. Start each file maybe with a verb. So how to onboard a client instead of just client processes. Something is really, really important.
Always go with the name that everybody uses for that system. Now if you're like, well we kind of use a lot of names. I would go back to the team and say, hey, we call this X and then sometimes we call this Y and then yesterday I heard somebody call it Z. What is the name?
We can start all collectively calling it so that when we need to go find that system, we're typing in the exact same phrase. So you can see how that can be really, really confusing. You're calling somebody something onboarding and then somebody else is calling it a client walkthrough and then somebody else is calling it new client. It's going to be really hard to find those systems moving forward.
So figure out what are we all going to call it and name it and start naming it consistently. So here's a really simple framework that every SOP should follow. Number one, what is the purpose? Why does this SOP even exist and what does it actually accomplish?
So an example would be this SOP outlines how to onboard a new dance student into our CRM to ensure accuracy and timely communication. Number two, what tools are needed? So what do I actually need to execute this? I think links, login, passwords that I'm going to need, et cetera.
So this is a big one. Your system might say log on to monday.com and the person reading your system's like, where do I find the user and password? So I don't suggest putting the user and password on the system, but you should absolutely say, if you don't know where to find the password, make sure you log into one password or last password, whatever it is. So they know, oh, it's in the software.
That's where I'm going to find it. Otherwise, what's going to happen? They're going to come knocking on your door like, hey, where do I get the password for this? And it's just a very simple redirect by putting it right in the system.
Then number three is step by step instructions. So use short numbered steps and add screenshots or a loom if needed. And then number four is the expected result. What does done or success look like?
This structure is going to give clarity and reduce questions. So you're going to be interrupted a whole lot less. Think of it like you're giving somebody a GPS and not just a map. Then step four is build it with your team.
Biggest reasons why most SOPs don't actually get used. You need buy-in when you're making this kind of change. So get them involved. Don't just write SOPs for your team.
Build them with your team. Have the person who owns the actual task. Screen record themselves doing it. Then write the draft SOP.
Then walk a team member through it to see if they can actually follow it without your help. Now make sure their manager or somebody else is double checking that the system's actually works without assistance. You don't want a bunch of systems written down that don't actually mean anything. We acquired a business in the last few years and we were so excited to see they had a ton of systems documented.
However, after looking a little closer and actually trying to use the system, it was missing a lot of instruction. We didn't know where to go or what to do next and we had to go back to that person to ask them many follow up questions. You don't want to get ready to go on vacation and think, oh my goodness, I built all these systems. My team's got this.
It's going to be amazing. And every day for 10 days they're like, hey, where do I find this? And where's the password for this? This was missing on the system.
So make sure you've got it all properly documented and somebody else has tested before you actually need somebody to go and use those systems. You're not just building documentation. You're building ownership. So a pro tip would be make an SOP creation part of the job.
If someone's doing a task regularly, it's their responsibility to maintain that SOP. Step five is roll these SOPs into onboarding day one. Here's where most business owners drop the ball. They create these and think that the team is going to magically find them and use them.
Not what happens at all. You need to train them on how to actually use the SOPs. So here is what to do. You actually want to create a training portal or a folder for every single role.
We do this right in their job description. You'll want to include a welcome video from you, what's nice. You do it once and you never have to do it ever again. Another great thing to add is the company mission, vision and values.
And then maybe the top five to 10 SOPs that they will use right away or in their first 30 days for this specific role. And then a checklist for the first week. Walk them through the portal on day one. When I say portal, this could be Google Docs.
This could be your project management software. This could be in maybe a trainable or a notion doesn't matter. Remember, you're not training them to memorize these things. You're training them to know that they exist and where to find the answers if they need it.
Step six is build a culture of SOP use. You need to make SOPs part of your culture and here is how you do it. So during training, before you ask a question, check the SOP. Go and search for it.
Did you find anything? If you couldn't find anything, let me know. If you're messaging back and forth with Slack instead of just answering with the real answer, put the link to where they could find it. You're not helping them by just giving them the answer all the time.
What you're doing is you're teaching them that when you have a question, just come to me. You want to teach them when you have a question, we've got all the answers in our SOPs. And if you're thinking, but CC, I've tried this, it doesn't work, they so come to me, just keep doing it longer. Consistency is key.
In your one on one, did they ask the question say, does this have a system yet? If not, assign it. At team meetings, highlight a system of the week and revisit it, maybe revise it together or just walk through it to make sure they understand there's a process on this. The more you model SOP culture, the more your team will follow.
And yes, in the beginning, it's going to feel slower, but this is the slow down to speed up phase. Once your team is using SOPs consistently, you will never go back. Trust me. I tell you, I have coached hundreds and hundreds of clients on actual systems.
And the biggest problem that we typically see is owner can sometimes be the biggest problem. So number one, they're not using the SOP. So they're not modeling things correctly. They're just doing something and everybody's watching like, wait, is that, is that what we're supposed to do?
Cause I thought it was this, but of course he or she's in charge. So I should probably do it. They're doing, so you've got to be careful. You have to truly lead and show them that this is how we do things here.
If you go, well, this is how you're supposed to do it, but I do it differently. It's a lot harder to keep that consistency. Step number seven is keep SOPs alive. An outdated SOP is just as dangerous as having no SOPs.
So build in regular check-ins. Maybe that's a quarterly audit, assign team members to review and update their own SOPs. So what this looks like is in my company, everybody has a job description and every year we update that job description or maybe more frequently if they've gotten a promotion, they've stepped into a different role. We always want to make sure that that job description is accurate.
Why? Because if they were to leave or we let them go, bringing on somebody to replace them is going to be a whole lot easier when you have an updated job description. Now think about this. You hired somebody five years ago.
You thought they were going to do xyz. So that's what their job description looks like. Now they've been here for five years. Think about what they actually do today.
I'm always on the original job description. It is probably night and day. They might have a different title. They might do something completely different.
They may be in a different department. So if you are updating these every year with what they actually do and everything is really organized and clicks over to the actual system, training is going to be super, super easy. When mistakes happen, ask, was it the person or was it the process? A lot of times we get angry at our team members that they're not doing this right or how do they mess this up?
Go back to the system and ask, where was I not clear? Where was and sometimes well, there wasn't a system. I told them one time it wasn't a recorded meeting. They took notes, didn't catch it all.
And then I didn't get the finished project. I actually wanted so slow down and make sure these are done right. SOPs should be evolving with your business. So the only bad system is the one that's frozen in time that no one is using anymore.
SOPs that actually get used are built with intention and are trained on from day one. Again, it's that culture that shows people we really do use these systems. Now if you want help building these into your business the right way, that's what we do inside of well-oiled operations. We help small business owners get out of the weeds by actually building systems that actually will help you scale and get your team to use.
So you can go to welloiledoperations.com to check out our free training on our entire three part framework and a lot of the systems that we use and how we get our business just running effectively.