WEBVTT
00:00:00.040 --> 00:00:15.210
I think one of the things that we need to look out for as somebody that's looking for this concept of scaling and understanding what that means, I think a lot of people struggle with what does scaling mean.
00:00:15.210 --> 00:00:21.440
I think a lot of times they believe that scaling means to grow through a group of people.
00:00:21.449 --> 00:00:27.489
Now, the more people I have, the more revenue I generate and so on and so forth, but truthfully, that's not scaling at all.
00:00:28.079 --> 00:00:40.609
Scaling is putting in the foundational structures, processes, systems, training, that kind of stuff so that when you do go out and hire folks, you have a system to plug them into.
00:00:40.829 --> 00:00:51.310
It doesn't matter how many people you hire because you have a system and a process that you can put them into and repeat over and over and over again because you know exactly what it's supposed to spit out.
00:00:51.700 --> 00:00:55.030
It's the biggest mistake that I see most contractors make.
00:00:55.179 --> 00:01:10.805
It's their thought process is to see their ability to scale is to go hire a bunch of people that probably do what they do, or they think they can do what they do, and all it does is create more of the problems you're already dealing with by the things that you currently do.
00:01:11.254 --> 00:01:13.325
You weren't able to get all the work done.
00:01:13.325 --> 00:01:15.594
You weren't able to get to all of the customers.
00:01:15.594 --> 00:01:20.575
You were starting to have a bit of fall through and not meeting your timelines and commitments.
00:01:20.704 --> 00:01:24.515
And now you've got to go out there and hire a bunch more people to do the same thing, because there is no process.
00:01:24.545 --> 00:01:25.465
There is no system.
00:01:25.625 --> 00:01:28.254
There is no exact way of doing things.
00:01:28.334 --> 00:01:31.444
And you can't train them very fast either because there's no process for that.
00:01:31.444 --> 00:01:31.905
So they got to.
00:01:32.254 --> 00:01:41.025
Hand, hold, verbally, train the whole time, which what that ultimately does is diffuses your scaling and actually shoots your scaling down, shoots growth down.
00:01:41.064 --> 00:01:48.295
Scaling is one thing, growth is a different thing, and I think most people would believe those are the same thing, and they are not.
00:01:48.724 --> 00:01:57.944
Growth is what happens after you scale, after you have your systems, your processes, your structure, your training, hiring processes, everything in place and ready to go.
00:01:58.424 --> 00:02:00.055
You can generate leads and you can sell them.
00:02:00.135 --> 00:02:01.614
You got all that figured out.
00:02:02.305 --> 00:02:03.375
All right, awesome.
00:02:03.784 --> 00:02:07.394
Now we can grow inside of our scale.
00:02:07.965 --> 00:02:08.754
Does it make sense?
00:02:08.814 --> 00:02:14.875
You hear a lot of the whole 10x your business grow and scale your, but they say grow and scale, right?
00:02:14.875 --> 00:02:18.384
The reality is in order to grow a business, you've got to scale it.
00:02:18.384 --> 00:02:29.284
And to scale it means that you have documented the processes and systems in every aspect of your business, both foundationally and operationally so that now whoever you hire.
00:02:29.775 --> 00:02:38.164
You can set them behind a screen, a desk, in a job, and it is fully functional and they can literally just read what needs to be done and do it.
00:02:38.175 --> 00:02:40.365
That's truly being able to scale.
00:02:40.564 --> 00:02:47.944
But the idea of being able to put somebody in position and say, here's the stuff you need to know and expecting them to execute that.
00:02:48.974 --> 00:02:52.854
If you're not there, that means that you are partially.
00:02:53.289 --> 00:02:54.770
Ready to scale, maybe.
00:02:54.919 --> 00:02:56.840
Depends on how far you are along in the process.
00:02:57.379 --> 00:03:02.620
Very first year in, in the roofing business, home service contracting, exteriors, that type of thing.
00:03:03.150 --> 00:03:04.770
I did really well as a salesperson.
00:03:04.949 --> 00:03:07.419
I sold 108 jobs in the first three months.
00:03:07.905 --> 00:03:11.694
I kind of developed some systems and processes for myself to execute.
00:03:11.764 --> 00:03:13.814
And they asked me to be the sales manager.
00:03:13.914 --> 00:03:14.955
I'm like, that sounds great.
00:03:14.995 --> 00:03:16.044
I'd love to.
00:03:16.055 --> 00:03:17.175
What's the job description?
00:03:17.664 --> 00:03:19.504
They're like just make people do what you do.
00:03:20.164 --> 00:03:22.064
And I went, that's not really a job description.
00:03:22.094 --> 00:03:26.064
Let me put together some things and let's see if we can actually make this work.
00:03:26.814 --> 00:03:36.514
So I took a couple of months, actually started to develop process and system and started really thinking about, okay, one person, me, Versus a bunch of people doing it.
00:03:36.655 --> 00:03:38.474
What kind of problems does that create?
00:03:39.375 --> 00:03:41.814
Because now it's a volume and can you actually get it done?
00:03:42.245 --> 00:03:44.094
Those type of questions pop up.
00:03:45.074 --> 00:03:52.425
And so I did a pretty decent job of putting together what I thought the process and system was, and I missed some things.
00:03:53.264 --> 00:03:54.814
I mean, this is how I know I missed some things.
00:03:54.814 --> 00:03:57.735
I hired 107 people.
00:03:58.169 --> 00:04:00.620
Inside of three months is just salespeople.
00:04:00.629 --> 00:04:04.449
That's not all the support staff and everybody else to come in and sell.
00:04:04.460 --> 00:04:13.310
Thinking mathematically, if I can get each one of those people to just average 500, 000, that would be a 50 million company.
00:04:13.310 --> 00:04:22.029
So let's go and brought them all in, did a pretty decent job of training three to five day training program and then ongoing education and training.
00:04:22.470 --> 00:04:27.870
And all the systems and all the processes were only documented as like what the task was.
00:04:28.500 --> 00:04:30.800
It was like, create an estimate, turn in an order.
00:04:31.269 --> 00:04:34.410
There wasn't the depth of it, exactly how to do it, right?
00:04:34.430 --> 00:04:41.069
Like the next step, how long it should take, what tool to use, all these other things that we help with, uh, building processes around here.
00:04:41.110 --> 00:04:46.959
And so what I ended up doing is I created a sales team that was high functioning.
00:04:47.009 --> 00:04:49.920
We did 41 million, which created.
00:04:50.589 --> 00:04:56.139
Literally a ticking bomb of explosion when it came to customer service.
00:04:56.329 --> 00:04:57.790
We weren't executing quickly enough.
00:04:57.790 --> 00:04:59.819
We weren't follow doing much follow through.
00:04:59.819 --> 00:05:02.779
We weren't even concerned really too much about the production side of things.
00:05:02.779 --> 00:05:06.009
So we didn't have quality control, final inspections, any of that kind of stuff.
00:05:06.209 --> 00:05:13.759
And I just, Did not get deep enough into what it was that I needed to cover to create a great client experience.
00:05:13.829 --> 00:05:24.910
I've learned my lesson since then quite well, and not necessarily about how fast can I hire a bunch of people, but how great can I make the system and what number of people can it handle at a time.
00:05:24.970 --> 00:05:30.930
So yeah, that's my stories that like the climax 29 years old.
00:05:31.115 --> 00:05:40.574
Trying to do it all trying to keep customers happy and hold the thing together Not a lot of fun to go through that not exactly the way you want to learn something But I promise you this it's send it home.
00:05:40.915 --> 00:05:41.524
I learned it.
00:05:41.774 --> 00:05:55.824
All right I got to do this a little bit better takeaway is be persistent about your processes I mean like get it nailed and then run it and practice it with the number of people that you currently have and see if It breaks if it breaks you're not ready.
00:05:56.365 --> 00:05:57.584
We actually did an exercise.
00:05:57.745 --> 00:06:03.779
This is a great exercise for this We do this with several of our clients We will build what we call the ideal process.
00:06:03.810 --> 00:06:06.709
That it's way that a job is supposed to go from start to finish.
00:06:07.250 --> 00:06:12.319
And then we'll get all the key players into a boardroom and we'll start where it starts.
00:06:12.399 --> 00:06:13.360
Hey, this is Jim.
00:06:13.420 --> 00:06:14.939
I'd like to get an estimate for my roof.
00:06:15.459 --> 00:06:30.329
And Janie, the person taking in the phone calls, does her script and enters her lead and does exactly what she's supposed to do and then hands it to the sales rep and the sales rep does his part and he's got to walk it through every little step of the way.
00:06:30.329 --> 00:06:30.389
Okay.
00:06:30.800 --> 00:06:33.639
And then it gets handed off to production and breaks, right?
00:06:33.680 --> 00:06:35.699
Like there wasn't the right thing, he couldn't do his job.
00:06:36.149 --> 00:06:44.910
And that's how you break a process before actually implementing a process to ensure that you have a process that's going to stand up to the test of time.
00:06:45.250 --> 00:06:46.279
That'll go two ways.
00:06:46.279 --> 00:06:49.509
One is they, they built out the process the best they could think of.
00:06:50.029 --> 00:06:51.769
And then it just doesn't work.
00:06:52.009 --> 00:06:57.060
That's because they didn't test it and didn't consider some of the outside factors that come into play.
00:06:57.060 --> 00:06:57.100
Okay.
00:06:57.725 --> 00:06:59.685
Uh, the other is they over process it.
00:07:00.055 --> 00:07:04.774
They say, Hey, um, this thing happened one time, but it was a big thing.
00:07:04.774 --> 00:07:05.725
Like it was a problem.
00:07:06.014 --> 00:07:07.235
I'll give a great example.
00:07:07.274 --> 00:07:11.324
We had a client that, uh, reneged on a contract.
00:07:11.654 --> 00:07:14.464
I also knew that my contract wasn't like an airtight contract.
00:07:14.564 --> 00:07:16.564
Like it was a simple design contract.
00:07:16.944 --> 00:07:21.704
And so we, when we got involved, the homeowner had like 6, 000.
00:07:21.754 --> 00:07:24.535
We went to the back to the insurance company, got everything covered for him.
00:07:24.535 --> 00:07:28.204
It was like 62, 000 windows and doors and all these other things.
00:07:28.899 --> 00:07:30.560
And they reneged on the contract.
00:07:31.990 --> 00:07:32.649
Pissed me off.
00:07:32.649 --> 00:07:34.410
I was beyond irritated with it.
00:07:35.170 --> 00:07:37.680
I felt like we just lost sixty some odd thousand dollars.
00:07:37.680 --> 00:07:39.149
That's never going to happen again.
00:07:39.899 --> 00:07:41.079
I'm going to get an attorney.
00:07:41.079 --> 00:07:42.980
We're going to write a loctite contract.
00:07:43.160 --> 00:07:44.009
And sure enough, we did.
00:07:44.620 --> 00:07:47.889
And we implemented it, trained on it, practiced it, and the whole bit.
00:07:48.009 --> 00:07:51.350
Cut our sales in half overnight.
00:07:51.769 --> 00:07:53.850
because we over process something.
00:07:54.310 --> 00:07:57.199
We said, Hey, we don't ever want to let this happen again.
00:07:57.430 --> 00:08:01.170
So we're going to do this next step, which then created a whole nother problem.
00:08:01.170 --> 00:08:05.670
Cause what happens is you go, okay, I'm going to make this move and you make the move.
00:08:05.670 --> 00:08:06.930
It creates a new problem.
00:08:06.949 --> 00:08:10.410
So now you have to do a new thing to your process to solve that problem.
00:08:10.860 --> 00:08:18.470
And there's this downhill flow that comes out of it and you end up becoming way over processed, way too restrictive.
00:08:18.740 --> 00:08:19.800
You're not agile.
00:08:19.800 --> 00:08:20.860
You're not flexible.
00:08:21.290 --> 00:08:23.240
And the whole thing comes crashing down around you.
00:08:23.240 --> 00:08:24.660
And people are just irritated by it.
00:08:24.879 --> 00:08:31.370
There was actually a piece of software that came out in 2009 that was competition to the software I was working for at the time.
00:08:32.009 --> 00:08:33.830
And I got a little sneak preview of it.
00:08:33.870 --> 00:08:35.840
I went, that thing's never going to last.
00:08:36.414 --> 00:08:40.475
Because every step somebody had to answer a question, yes or no, yes or no.
00:08:40.735 --> 00:08:44.764
And most of the questions were no, no, no, no, no, I don't need to do that thing.
00:08:44.764 --> 00:08:45.764
Don't need to do that thing.
00:08:46.315 --> 00:08:51.485
And so they over processed something which made it hard to use the user interface.
00:08:51.565 --> 00:08:52.985
A side of it became garbage.
00:08:53.125 --> 00:08:54.154
Nobody wanted to do it.
00:08:54.774 --> 00:08:57.404
So you've got to find this balance and my best advice for that.
00:08:57.585 --> 00:09:03.615
So my best advice for building a process for a contractor, think of 80 percent of the things that you need to cover.
00:09:03.879 --> 00:09:16.629
What happens 80 percent of the time, 80 percent of the time it goes like this, and this is the ideal way for it to go get that nailed first, concentrate on focusing on 80 percent of the time.
00:09:16.629 --> 00:09:18.039
This is the way it's supposed to go.
00:09:18.080 --> 00:09:19.820
We call that the ideal process.
00:09:20.059 --> 00:09:24.269
And then every if then thing becomes a new process.
00:09:24.399 --> 00:09:27.909
If this happens, go do this and follow that process.
00:09:28.230 --> 00:09:29.460
If this happens, go do this.
00:09:29.460 --> 00:09:30.559
And that's this process.
00:09:30.975 --> 00:09:32.825
But get the ideal one down first.
00:09:32.845 --> 00:09:36.514
If everything went perfectly, what does that look like?
00:09:36.705 --> 00:09:37.965
Okay, I've got that nailed.
00:09:38.014 --> 00:09:42.544
We're following it most of the time and now 20 percent of the time something's popping up.
00:09:42.764 --> 00:09:46.705
Now we build a process for those little things and it's not nearly as hard.
00:09:46.804 --> 00:09:50.825
Most people overbuild processes from the beginning and it's just a nightmare for them to get out.
00:09:50.865 --> 00:09:51.164
But
00:00:00.040 --> 00:00:15.210
I think one of the things that we need to look out for as somebody that's looking for this concept of scaling and understanding what that means, I think a lot of people struggle with what does scaling mean.
00:00:15.210 --> 00:00:21.440
I think a lot of times they believe that scaling means to grow through a group of people.
00:00:21.449 --> 00:00:27.489
Now, the more people I have, the more revenue I generate and so on and so forth, but truthfully, that's not scaling at all.
00:00:28.079 --> 00:00:40.609
Scaling is putting in the foundational structures, processes, systems, training, that kind of stuff so that when you do go out and hire folks, you have a system to plug them into.
00:00:40.829 --> 00:00:51.310
It doesn't matter how many people you hire because you have a system and a process that you can put them into and repeat over and over and over again because you know exactly what it's supposed to spit out.
00:00:51.700 --> 00:00:55.030
It's the biggest mistake that I see most contractors make.
00:00:55.179 --> 00:01:10.805
It's their thought process is to see their ability to scale is to go hire a bunch of people that probably do what they do, or they think they can do what they do, and all it does is create more of the problems you're already dealing with by the things that you currently do.
00:01:11.254 --> 00:01:13.325
You weren't able to get all the work done.
00:01:13.325 --> 00:01:15.594
You weren't able to get to all of the customers.
00:01:15.594 --> 00:01:20.575
You were starting to have a bit of fall through and not meeting your timelines and commitments.
00:01:20.704 --> 00:01:24.515
And now you've got to go out there and hire a bunch more people to do the same thing, because there is no process.
00:01:24.545 --> 00:01:25.465
There is no system.
00:01:25.625 --> 00:01:28.254
There is no exact way of doing things.
00:01:28.334 --> 00:01:31.444
And you can't train them very fast either because there's no process for that.
00:01:31.444 --> 00:01:31.905
So they got to.
00:01:32.254 --> 00:01:41.025
Hand, hold, verbally, train the whole time, which what that ultimately does is diffuses your scaling and actually shoots your scaling down, shoots growth down.
00:01:41.064 --> 00:01:48.295
Scaling is one thing, growth is a different thing, and I think most people would believe those are the same thing, and they are not.
00:01:48.724 --> 00:01:57.944
Growth is what happens after you scale, after you have your systems, your processes, your structure, your training, hiring processes, everything in place and ready to go.
00:01:58.424 --> 00:02:00.055
You can generate leads and you can sell them.
00:02:00.135 --> 00:02:01.614
You got all that figured out.
00:02:02.305 --> 00:02:03.375
All right, awesome.
00:02:03.784 --> 00:02:07.394
Now we can grow inside of our scale.
00:02:07.965 --> 00:02:08.754
Does it make sense?
00:02:08.814 --> 00:02:14.875
You hear a lot of the whole 10x your business grow and scale your, but they say grow and scale, right?
00:02:14.875 --> 00:02:18.384
The reality is in order to grow a business, you've got to scale it.
00:02:18.384 --> 00:02:29.284
And to scale it means that you have documented the processes and systems in every aspect of your business, both foundationally and operationally so that now whoever you hire.
00:02:29.775 --> 00:02:38.164
You can set them behind a screen, a desk, in a job, and it is fully functional and they can literally just read what needs to be done and do it.
00:02:38.175 --> 00:02:40.365
That's truly being able to scale.
00:02:40.564 --> 00:02:47.944
But the idea of being able to put somebody in position and say, here's the stuff you need to know and expecting them to execute that.
00:02:48.974 --> 00:02:52.854
If you're not there, that means that you are partially.
00:02:53.289 --> 00:02:54.770
Ready to scale, maybe.
00:02:54.919 --> 00:02:56.840
Depends on how far you are along in the process.
00:02:57.379 --> 00:03:02.620
Very first year in, in the roofing business, home service contracting, exteriors, that type of thing.
00:03:03.150 --> 00:03:04.770
I did really well as a salesperson.
00:03:04.949 --> 00:03:07.419
I sold 108 jobs in the first three months.
00:03:07.905 --> 00:03:11.694
I kind of developed some systems and processes for myself to execute.
00:03:11.764 --> 00:03:13.814
And they asked me to be the sales manager.
00:03:13.914 --> 00:03:14.955
I'm like, that sounds great.
00:03:14.995 --> 00:03:16.044
I'd love to.
00:03:16.055 --> 00:03:17.175
What's the job description?
00:03:17.664 --> 00:03:19.504
They're like just make people do what you do.
00:03:20.164 --> 00:03:22.064
And I went, that's not really a job description.
00:03:22.094 --> 00:03:26.064
Let me put together some things and let's see if we can actually make this work.
00:03:26.814 --> 00:03:36.514
So I took a couple of months, actually started to develop process and system and started really thinking about, okay, one person, me, Versus a bunch of people doing it.
00:03:36.655 --> 00:03:38.474
What kind of problems does that create?
00:03:39.375 --> 00:03:41.814
Because now it's a volume and can you actually get it done?
00:03:42.245 --> 00:03:44.094
Those type of questions pop up.
00:03:45.074 --> 00:03:52.425
And so I did a pretty decent job of putting together what I thought the process and system was, and I missed some things.
00:03:53.264 --> 00:03:54.814
I mean, this is how I know I missed some things.
00:03:54.814 --> 00:03:57.735
I hired 107 people.
00:03:58.169 --> 00:04:00.620
Inside of three months is just salespeople.
00:04:00.629 --> 00:04:04.449
That's not all the support staff and everybody else to come in and sell.
00:04:04.460 --> 00:04:13.310
Thinking mathematically, if I can get each one of those people to just average 500, 000, that would be a 50 million company.
00:04:13.310 --> 00:04:22.029
So let's go and brought them all in, did a pretty decent job of training three to five day training program and then ongoing education and training.
00:04:22.470 --> 00:04:27.870
And all the systems and all the processes were only documented as like what the task was.
00:04:28.500 --> 00:04:30.800
It was like, create an estimate, turn in an order.
00:04:31.269 --> 00:04:34.410
There wasn't the depth of it, exactly how to do it, right?
00:04:34.430 --> 00:04:41.069
Like the next step, how long it should take, what tool to use, all these other things that we help with, uh, building processes around here.
00:04:41.110 --> 00:04:46.959
And so what I ended up doing is I created a sales team that was high functioning.
00:04:47.009 --> 00:04:49.920
We did 41 million, which created.
00:04:50.589 --> 00:04:56.139
Literally a ticking bomb of explosion when it came to customer service.
00:04:56.329 --> 00:04:57.790
We weren't executing quickly enough.
00:04:57.790 --> 00:04:59.819
We weren't follow doing much follow through.
00:04:59.819 --> 00:05:02.779
We weren't even concerned really too much about the production side of things.
00:05:02.779 --> 00:05:06.009
So we didn't have quality control, final inspections, any of that kind of stuff.
00:05:06.209 --> 00:05:13.759
And I just, Did not get deep enough into what it was that I needed to cover to create a great client experience.
00:05:13.829 --> 00:05:24.910
I've learned my lesson since then quite well, and not necessarily about how fast can I hire a bunch of people, but how great can I make the system and what number of people can it handle at a time.
00:05:24.970 --> 00:05:30.930
So yeah, that's my stories that like the climax 29 years old.
00:05:31.115 --> 00:05:40.574
Trying to do it all trying to keep customers happy and hold the thing together Not a lot of fun to go through that not exactly the way you want to learn something But I promise you this it's send it home.
00:05:40.915 --> 00:05:41.524
I learned it.
00:05:41.774 --> 00:05:55.824
All right I got to do this a little bit better takeaway is be persistent about your processes I mean like get it nailed and then run it and practice it with the number of people that you currently have and see if It breaks if it breaks you're not ready.
00:05:56.365 --> 00:05:57.584
We actually did an exercise.
00:05:57.745 --> 00:06:03.779
This is a great exercise for this We do this with several of our clients We will build what we call the ideal process.
00:06:03.810 --> 00:06:06.709
That it's way that a job is supposed to go from start to finish.
00:06:07.250 --> 00:06:12.319
And then we'll get all the key players into a boardroom and we'll start where it starts.
00:06:12.399 --> 00:06:13.360
Hey, this is Jim.
00:06:13.420 --> 00:06:14.939
I'd like to get an estimate for my roof.
00:06:15.459 --> 00:06:30.329
And Janie, the person taking in the phone calls, does her script and enters her lead and does exactly what she's supposed to do and then hands it to the sales rep and the sales rep does his part and he's got to walk it through every little step of the way.
00:06:30.329 --> 00:06:30.389
Okay.
00:06:30.800 --> 00:06:33.639
And then it gets handed off to production and breaks, right?
00:06:33.680 --> 00:06:35.699
Like there wasn't the right thing, he couldn't do his job.
00:06:36.149 --> 00:06:44.910
And that's how you break a process before actually implementing a process to ensure that you have a process that's going to stand up to the test of time.
00:06:45.250 --> 00:06:46.279
That'll go two ways.
00:06:46.279 --> 00:06:49.509
One is they, they built out the process the best they could think of.
00:06:50.029 --> 00:06:51.769
And then it just doesn't work.
00:06:52.009 --> 00:06:57.060
That's because they didn't test it and didn't consider some of the outside factors that come into play.
00:06:57.060 --> 00:06:57.100
Okay.
00:06:57.725 --> 00:06:59.685
Uh, the other is they over process it.
00:07:00.055 --> 00:07:04.774
They say, Hey, um, this thing happened one time, but it was a big thing.
00:07:04.774 --> 00:07:05.725
Like it was a problem.
00:07:06.014 --> 00:07:07.235
I'll give a great example.
00:07:07.274 --> 00:07:11.324
We had a client that, uh, reneged on a contract.
00:07:11.654 --> 00:07:14.464
I also knew that my contract wasn't like an airtight contract.
00:07:14.564 --> 00:07:16.564
Like it was a simple design contract.
00:07:16.944 --> 00:07:21.704
And so we, when we got involved, the homeowner had like 6, 000.
00:07:21.754 --> 00:07:24.535
We went to the back to the insurance company, got everything covered for him.
00:07:24.535 --> 00:07:28.204
It was like 62, 000 windows and doors and all these other things.
00:07:28.899 --> 00:07:30.560
And they reneged on the contract.
00:07:31.990 --> 00:07:32.649
Pissed me off.
00:07:32.649 --> 00:07:34.410
I was beyond irritated with it.
00:07:35.170 --> 00:07:37.680
I felt like we just lost sixty some odd thousand dollars.
00:07:37.680 --> 00:07:39.149
That's never going to happen again.
00:07:39.899 --> 00:07:41.079
I'm going to get an attorney.
00:07:41.079 --> 00:07:42.980
We're going to write a loctite contract.
00:07:43.160 --> 00:07:44.009
And sure enough, we did.
00:07:44.620 --> 00:07:47.889
And we implemented it, trained on it, practiced it, and the whole bit.
00:07:48.009 --> 00:07:51.350
Cut our sales in half overnight.
00:07:51.769 --> 00:07:53.850
because we over process something.
00:07:54.310 --> 00:07:57.199
We said, Hey, we don't ever want to let this happen again.
00:07:57.430 --> 00:08:01.170
So we're going to do this next step, which then created a whole nother problem.
00:08:01.170 --> 00:08:05.670
Cause what happens is you go, okay, I'm going to make this move and you make the move.
00:08:05.670 --> 00:08:06.930
It creates a new problem.
00:08:06.949 --> 00:08:10.410
So now you have to do a new thing to your process to solve that problem.
00:08:10.860 --> 00:08:18.470
And there's this downhill flow that comes out of it and you end up becoming way over processed, way too restrictive.
00:08:18.740 --> 00:08:19.800
You're not agile.
00:08:19.800 --> 00:08:20.860
You're not flexible.
00:08:21.290 --> 00:08:23.240
And the whole thing comes crashing down around you.
00:08:23.240 --> 00:08:24.660
And people are just irritated by it.
00:08:24.879 --> 00:08:31.370
There was actually a piece of software that came out in 2009 that was competition to the software I was working for at the time.
00:08:32.009 --> 00:08:33.830
And I got a little sneak preview of it.
00:08:33.870 --> 00:08:35.840
I went, that thing's never going to last.
00:08:36.414 --> 00:08:40.475
Because every step somebody had to answer a question, yes or no, yes or no.
00:08:40.735 --> 00:08:44.764
And most of the questions were no, no, no, no, no, I don't need to do that thing.
00:08:44.764 --> 00:08:45.764
Don't need to do that thing.
00:08:46.315 --> 00:08:51.485
And so they over processed something which made it hard to use the user interface.
00:08:51.565 --> 00:08:52.985
A side of it became garbage.
00:08:53.125 --> 00:08:54.154
Nobody wanted to do it.
00:08:54.774 --> 00:08:57.404
So you've got to find this balance and my best advice for that.
00:08:57.585 --> 00:09:03.615
So my best advice for building a process for a contractor, think of 80 percent of the things that you need to cover.
00:09:03.879 --> 00:09:16.629
What happens 80 percent of the time, 80 percent of the time it goes like this, and this is the ideal way for it to go get that nailed first, concentrate on focusing on 80 percent of the time.
00:09:16.629 --> 00:09:18.039
This is the way it's supposed to go.
00:09:18.080 --> 00:09:19.820
We call that the ideal process.
00:09:20.059 --> 00:09:24.269
And then every if then thing becomes a new process.
00:09:24.399 --> 00:09:27.909
If this happens, go do this and follow that process.
00:09:28.230 --> 00:09:29.460
If this happens, go do this.
00:09:29.460 --> 00:09:30.559
And that's this process.
00:09:30.975 --> 00:09:32.825
But get the ideal one down first.
00:09:32.845 --> 00:09:36.514
If everything went perfectly, what does that look like?
00:09:36.705 --> 00:09:37.965
Okay, I've got that nailed.
00:09:38.014 --> 00:09:42.544
We're following it most of the time and now 20 percent of the time something's popping up.
00:09:42.764 --> 00:09:46.705
Now we build a process for those little things and it's not nearly as hard.
00:09:46.804 --> 00:09:50.825
Most people overbuild processes from the beginning and it's just a nightmare for them to get out.
00:09:50.865 --> 00:09:51.164
But
