Plant Money Trees By Making SYSTEMS

[NeoDialectic]

Was there a particular tipping point for both of you to start being hands off?

I would have to really think about it, but I'm not sure there was a dramatic tipping point. I think it was just knowing that there is only one way to get more hours in the day and slowly dipping our toes in. It started from paying people we know to do easy tasks. Using people you know alleviates the trust portion and starting with easy tasks makes it, well, easy.

Then we grew our confidence and skill set from there.

I love researching things and finding the supposed best and fastest way of doing things. I do this obsessively with my hobbies. But I've long learned that there is a huge rift between logically knowing something and being in the right state of mind to act on it. That's why I strongly believe that the best advice can only come from a place of meeting people where they are at (mentally). Even if it means my recommendation is doing something in a way that is far from some kind of theoretical ideal. Good advice is advice that the person would actually be able to follow and even more importantly be willing to follow.

I apply the same idea when dealing with my own action plans. I try not to dwell on what I'm not willing to do, but rather what it is that I am willing to do to get me closer to the end goal. Even if it is just a small step at first.

 

Dislike ads? Remove them and support the forum: Subscribe to Fastlane Insiders.

[kommen]

Part 4:​

You need to spend 1:1 time with your employee going over things. If this is an in person employee then you sit down with them. If this is online, it will depend on the task, but you should figure out a way to talk with them live and maybe share screens or something of the sort. Lets say it is with an in person employee and the task is on the computer. I will sit down with them with the instructions directly in front of us. First I would explain what they are going to be doing in a very general way. I will show them the variable sheet and have them read it. For example if it is a questions/answer sheet, have a discussion with them on whether they understand the questions and whether the answers make sense.

Just a question, would you think it's better to first let your employee come up with his own solutions, processes and instructions? In my opinion, there's a small chance his own processes are just better. Haven't finished reading though.

 

[fastlane_dad]

Was there a particular tipping point for both of you to start being hands off?

I would have to really think about it, but I'm not sure there was a dramatic tipping point.

Let me chime in a bit here also - the reason there was no dramatic tipping point is because how heavily our mindset was rooted in bootstrapping.

We were mostly at all times, looking to spend as little as possible on outside help, and do as many tasks ourselves as we could take on. Our purse opened up quite a bit as time went on as well (especially towards expanding business further and experimentation), as we could be a bit frivolous in some spending without fully feeling any repercussions.

The stumbling block most of the time was when 150 widgets needed to be packaged a day, and between both of us we can only package 50.

This is not even necessarily the correct mindset for everyone, or at any and all times.

There was always an internal struggle in us figuring out what our time was worth, especially when we were just getting started and not bringing in a lot of revenue / profit.

If someone is trying to build a TESLA, GOOGLE or a UBER -- that tipping point must almost come at day one. Speed is of the essence, and you recruit thousands of investors and raise funds to make it happen as soon as possible with hundreds or more employees.

We are both still big believers that the bootstrapping / do it yourself attitude is extremely important for almost 99% of people going into entrepreneurship and taking on that risk. We have always started off making $3 before $5, and as both of us come from immigrant families, every dollar from day 1 had to be personally earned to be invested into a business.

 

[Guest-5ty5s4]

If your business is in the south, you need a standard procedure with steps to take for freezing / low temp. weather. All standard procedures need revision dates as well as reminders too.

 

Dislike ads? Remove them and support the forum: Subscribe to Fastlane Insiders.

[NeoDialectic]

Just a question, would you think it's better to first let your employee come up with his own solutions, processes and instructions? In my opinion, there's a small chance his own processes are just better. Haven't finished reading though.

If you are Elon Musk and you are hiring experts in the field to improve your current battery design by 1%... Obviously yes.

If you are reading this post for advice, the answer is a resounding NO.

Keep in mind that part of being a good leader is building trust in your team to be able to voice concerns and suggestions. Once they learn your process and are competent, they should feel comfortable asking questions and giving suggestions on how the process can be improved. But your first order of business before improving the process is at minimum getting it off your shoulders with as little negative consequences as possible.

 

[kommen]

If you are Elon Musk and you are hiring experts in the field to improve your current battery design by 1%... Obviously yes.

If you are reading this post for advice, the answer is a resounding NO.

Keep in mind that part of being a good leader is building trust in your team to be able to voice concerns and suggestions. Once they learn your process and are competent, they should feel comfortable asking questions and giving suggestions on how the process can be improved. But your first order of business before improving the process is at minimum getting it off your shoulders with as little negative consequences as possible.

Thank you for your post and your reply. Your post was so good I even printed it out!

 

[parabolic]

Always appreciate your posts and threads. This is another great one. Thank you.

 

Dislike ads? Remove them and support the forum: Subscribe to Fastlane Insiders.

[Consolation]

DAMN! Did MJ installed advanced AI on this forum? Because this is what I'm looking for since last week.

My client currently has asked me to setup a booking system for a homestay on Wordpress. Due to limited budget constraint, plus I'm not very fluent in HTML, CSS, JavaScript, and PHP; the backend workflow for her employees would be a bit complicated.

So, I got stucked on writing user guide.

Thank you. Thank you. Thank you. Thank you so much @NeoDialectic I'm going to use this systems right away.

 

[kima]

I've seen "making systems" and delegating mentioned throughout the forum a few times now (@Antifragile , @Kak , @mikecarlooch , @BizyDad, @MTF , and more) but I haven't stumbled on any recent easy approachable guides to it. It seems like some people are really hesitant because it looks harder than it could be. But it must be done. At one point in every business life cycle, there will come a time that the owner can no longer do everything and must start delegating more things than just simple tasks or labors.

There are probably unlimited ways of doing this. My goal is to show you just how easy this part could be as long as you follow my own system on it! Remember, the quality of your system has more to do with the result than the quality of your employee. I have had very low skill, technologically illiterate, employees do relatively complicated things on computers pretty much flawlessly. Tune in till the end to see other applications outside of just employees and contractors!

I will include examples from experiences that @fastlane_dad and I dealt with on a follow up post as this one has got pretty long.

Prelude:​

When thinking about which systems to automate first, I think about 3 factors.

1. Which of my processes are super simple and only take a few steps to do?
2. Which of my processes take me the most amount of time?
3. Which of my processes are least consequential to the core of the business if there are small mistakes?

I would then sort my priorities based on these answers. Everything can be automated, but this is just the thought process I would use to figure out the order to go in

1. If something is super simple and only takes a few steps, then it may be a good idea to get this off your plate first. It will get you thinking in the right direction and expose you to just how freeing delegating can feel. An example of this is if you have been sending out postcards in the mail, you can now get someone else to do this. All they have to do is open the boxes, put the stamp on, put it in a new box for the mail man. You don't need a guide to teach you how to delegate this. But maybe it's the kick in the butt you needed to actually do it.
2. The more time a process takes the more value (free time) you will get by taking it off your hands. Time intensive processes are prioritized
3. You should start with the parts of the business that matter the least if something was messed up. If your $5 widget gets sent to the wrong address every once in a while, its not preferable but it's not a big deal either. You just send a new one out. But if a mistake or oversight could mean that you are now out of stock from your product for the next 2 months and are losing $1000s a day in sales... I would delegate that last.

Part 1:​

Make sure you have done the task yourself and have become comfortable with it. Notice what part of the processes stay the same and which part of the processes are variable.

Part 2:​

Do the task yourself and write down every single step. I really mean every single one. When you hit a part that is variable, address it by saying "consult X sheet for examples". At the end of this part you should have a sheet that is so exact that a programmed machine will get all the steps right other than the variable parts that you reference.

Part 3:​

Now you have to create the references for the variable portion. If you have done a task over and over, you will start noticing a pattern. You want to be able to give an example sheet for 80%+ of all possibilities. This could mean questions/answers. It could mean common scenarios and what to do in those scenarios.

Part 4:​

You need to spend 1:1 time with your employee going over things. If this is an in person employee then you sit down with them. If this is online, it will depend on the task, but you should figure out a way to talk with them live and maybe share screens or something of the sort. Lets say it is with an in person employee and the task is on the computer. I will sit down with them with the instructions directly in front of us. First I would explain what they are going to be doing in a very general way. I will show them the variable sheet and have them read it. For example if it is a questions/answer sheet, have a discussion with them on whether they understand the questions and whether the answers make sense.

I will now proceed to do the task, but completely base off the instructions and not memory. That means I will point to the step on the sheet before doing the step in real life. Depending on how complicated the procedure is I may do it a few times.

Then I will have the employee do it in front of me. The next part is one of the most important parts and the part that I think gets skipped the most out of laziness. You need to watch the employee do it over and over again. The first times, give them room to breathe and allow them to explore. Don't just step in when they are having trouble. Them doing their own trouble shooting will solidify their learning. Also keep in mind that it is nerve racking to have your boss breathing over your shoulder while you are doing something new. So relax. The only time you should leave is after you have seen that they are getting the processes without stumbling over the easy parts and can do the whole thing SEVERAL TIMES without your input. Don't shortcut this step. Wasting your precious time here today, will pay off in dividends over the next days.

This is also a learning opportunity for yourself. See where they keep stumbling and think about what you could have added to prevent the stumbling. Did you forget to say that Button x is on the other side of the screen of Button y? It may sound dumb to be so thorough when you are there and could just show them, but it's not. You'll see! They will pick up the task today and then come in after a long weekend and it's as if their brain did a hard reset. Luckily, they can just consult the sheet and don't have to bother you! Or they may be in the middle of the task and their brain throw up a blue screen of death? No problems, consult the sheet! Be patient and understand that your business may be the number one thing on YOUR mind, but they are just an employee that is likely thinking about their "actual" life back home. Thats OK as we have accounted for that.

Part 5:​

Don't leave just yet! Make sure they know that you are there if they need anything. If they aren't sure about something, no matter how little or dumb, to come to you. Depending on the processes (like customer service), there will always be variables that you did not list on your example sheet. Tell them to come to you with it and you will help them. Depending on your scenario and the task itself, they should either come to you whenever it comes up or they should leave all the unknowns till a specific time of the day and come to you with all of them.

When they do come to you, it is very important to be welcoming and to not just answer the question but also explain your reasoning behind it. If 80% of variables can be covered in an example sheet, the remaining 19.9% can eventually be learned by the employee just by seeing the example and understanding the guiding principles of your decision in the answer. We have all read how they program ai computers by throwing more and more examples at them. That's exactly your expectation here.

Pro tip: You should start noticing patterns in the way you answered these variables. You should start distilling these patterns to principles. Eventually you should have a set of guiding principles that can be attached to the training sheet that will shortcut future learning and possibly even other systems.

Part 6:​

Thats it! A few things to keep in mind

• Make sure to update the sheet as you run across stumbling blocks by your employee.
• Don't be afraid to ask them if they understand why you decided to deal with Variable X a certain way. Don't just tell them. Remember, they are thinking about whether they did the laundry at home. Make sure they can articulate your reasoning back to you. P
• Eventually you will outsource everything. Including this process itself! We gave instructions on creating systems to our businesses manager and had him do it to some of his tasks to hand it off to employees underneath him.
• As you grow, don't limit this process to only delegating duties. Occasionally have your employees create step by step processes for every single thing they do. So when Becky gets sick, David can fill in on a rudimentary level and the business keeps chugging along with minimal input from you. Or what about when David quits? You now have a training manual that will get your new employee up to speed immediately.
• The less you have to rely on the employee that you can automate on your end, the better. For example, we had an employee that had to randomly choose a prize for a contest we ran. Leaving it to the employee ended up bogging the processes down and would also result in far from random results. I built an html page in 10 minutes that randomly selected a number and showed which prize to give. So much better. Non-programming solutions are easy too. Just google random number generator and have them click that , with a reference sheet that pins numbers to product. Again....Your employees are thinking about whether they left their stove on at home or if Sandy will want to hang out that night. The least amount of decisions they have to make the better.

Postscript:​

You may have noticed I italicized a few words here and there. They were all breadcrumbs for the ultimate form of a successful system. All these steps can be applied to creating computer automated systems. I only know basic levels of programming but between my knowledge, google fu, and macro's and have automated things that others thought you definitely needed humans to do. You can automate an ASTOUNDING amount of things and you should think about hiring someone to create a program/macro/script.

It's really this simple. Once you create the instructions sheet, the most important part is following your employee through the steps and watching them do it on their own. So don't be scared to dive right in. Modify the process as needed to account for different needs. Just don't shortcut dwelling on the details.

Notes on hiring:

Many online tasks can be delegated over the internet, which puts lets stress on you taking the plunge and getting your first employee. However, it may be time to hire your first employee if you have many real life tasks that need to be done or if you have a lot to delegate. I'm sure there are great threads and how-to's already on this from more qualified people. I'll only briefly touch on it since it is pertinent to my guide. Don't be nervous about hiring someone just to let them down or finding out it wasn't the right time for you and having to let them go. I know this is a big stumbling block for many people. If you are nervous about it, just be completely up front with them. Tell them the plan is to hire them for years to come, but that you are a startup so it is always possible that situations can change. I recommend paying relatively well compared to others in your market, but that is a personal business choice. Plenty of people are happy to jump aboard as long as you are up front with your requirements and you treat them right. Keep in mind that when allocating time, I would expect my low skill employees to do things at no more than 1/4 the speed that I do things. (Atleast at first)

What do you guys think? Are you ready to delegate some of your tedious tasks now? What about the complicated ones? I would love to hear stories of complicated tasks that were delegated and any creative solutions you had.

very detailed thread. Fantastic read with lots of knowledge

 

[Andy Black]

explain via video, not text.

I think there's too much emphasis on explaining by video. I want to redo some of my videos as text with screenshots. They're easier to follow and easier to keep up to date.

 

Dislike ads? Remove them and support the forum: Subscribe to Fastlane Insiders.

[Andy Black]

Just a question, would you think it's better to first let your employee come up with his own solutions, processes and instructions? In my opinion, there's a small chance his own processes are just better. Haven't finished reading though.

There's the option of hiring rockstars who create the automations and SOPs as they go along. Less senior people can then use the tools and SOPs.

 

[mikecarlooch]

almost 2 years later, this thread is coming in handy big time.

After coming back here I'm sitting down my whole saturday today writing out every single detail of tasks that can be turned into a system.

Can it be automated with code? can it be automated with VA's? or do we need an employee..

Very clarifying process.