You've probably heard lots of business bloggers talk about how important written procedures are. I know I have. And honestly, as good an idea as it sounds, it also sounds like a lot of work!
But I realised it doesn't have to be. Here's the method I use to develop written procedures for my biz.
First, I write down each step that I can remember in a text document. Yes, I'm a bit forgetful at times - isn't everyone? As I go through the list of steps, other steps that I've left out will come back to me, and I'll stick them in where they belong.
I'll re-read the list, and check that I've put in everything. If I've missed something, I'll add it in.
Then, the next time I'm doing that particular task, I'll keep that file open on my desktop while I'm doing it. This allows me to a) remember what order to do things in, and b) add in any notes that I couldn't when I was writing the procedure in the first place.
I can also add in any 'if this happens, then do that' comments for certain steps. For instance, if my client's web hosting doesn't use cPanel, I'll have a different procedure for installing WordPress than if cPanel was available.
Every time I do the task from that point on, I refer to the list I made at the beginning. Each time, I not only follow the list of steps, but I also add any changes or comments to the file for next time.
Sure, setting up written procedures takes a bit of effort at the start. But the time you spend on doing it will save you time in the long run.
But why?
What if you need to take on an employee? Or you're going on maternity leave, and someone needs to take over for you for a few weeks? Wouldn't it be easier to direct them to your written procedures than having to explain everything yourself?
I thought so.
But I realised it doesn't have to be. Here's the method I use to develop written procedures for my biz.
First, I write down each step that I can remember in a text document. Yes, I'm a bit forgetful at times - isn't everyone? As I go through the list of steps, other steps that I've left out will come back to me, and I'll stick them in where they belong.
I'll re-read the list, and check that I've put in everything. If I've missed something, I'll add it in.
Then, the next time I'm doing that particular task, I'll keep that file open on my desktop while I'm doing it. This allows me to a) remember what order to do things in, and b) add in any notes that I couldn't when I was writing the procedure in the first place.
I can also add in any 'if this happens, then do that' comments for certain steps. For instance, if my client's web hosting doesn't use cPanel, I'll have a different procedure for installing WordPress than if cPanel was available.
Every time I do the task from that point on, I refer to the list I made at the beginning. Each time, I not only follow the list of steps, but I also add any changes or comments to the file for next time.
Sure, setting up written procedures takes a bit of effort at the start. But the time you spend on doing it will save you time in the long run.
But why?
What if you need to take on an employee? Or you're going on maternity leave, and someone needs to take over for you for a few weeks? Wouldn't it be easier to direct them to your written procedures than having to explain everything yourself?
I thought so.
No comments