1 00:00:00,540 --> 00:00:03,060 Scott Ritzheimer: Hello, hello, and welcome, welcome once again 2 00:00:03,150 --> 00:00:05,910 to the Start Scale and Succeed podcast, the only podcast that 3 00:00:05,940 --> 00:00:09,210 grows with you through all seven levels of your journey as a 4 00:00:09,270 --> 00:00:13,290 founder. We are now in part three of our "You're Not in 5 00:00:13,350 --> 00:00:17,850 Whitewater dot dot dot yet" series, where we're not talking 6 00:00:17,910 --> 00:00:20,430 about the levels of the founder's evolution, but instead 7 00:00:20,520 --> 00:00:23,900 we're talking about the stages that organizations go through 8 00:00:24,680 --> 00:00:28,580 together, and one of those really important stages-one that 9 00:00:28,610 --> 00:00:31,040 I spend a lot of time working with my clients in-is the 10 00:00:31,190 --> 00:00:36,410 whitewater stage. And a big part of the reason why you might have 11 00:00:36,470 --> 00:00:38,930 heard about me or started following this probably had to 12 00:00:38,990 --> 00:00:41,830 do with whitewater. You heard me talking about it somewhere. You 13 00:00:42,460 --> 00:00:44,440 heard one of our scale architects talk about it 14 00:00:44,440 --> 00:00:47,740 somewhere, or you heard Les talk about it. The guy who created 15 00:00:47,740 --> 00:00:51,190 the model, the predictable success model. And what we're 16 00:00:51,310 --> 00:00:57,880 exploring here in this series is the growing phenomena. I guess 17 00:00:57,940 --> 00:01:01,920 you could call it pattern, maybe more appropriate, where I'm 18 00:01:02,100 --> 00:01:06,210 seeing more and more and more organizations end up in 19 00:01:06,270 --> 00:01:12,630 whitewater prematurely by their own doing, not for the right 20 00:01:12,810 --> 00:01:16,890 reasons than ever before, and I think it's a trend that's going 21 00:01:16,950 --> 00:01:19,290 to continue. I think it's actually going to accelerate 22 00:01:20,580 --> 00:01:23,840 because when you look at it, there's actually three times as 23 00:01:23,960 --> 00:01:27,980 many ways, or at least you know three times as many groups of 24 00:01:28,100 --> 00:01:30,350 ways. There's an infinite number of ways, but there are three 25 00:01:30,440 --> 00:01:34,940 times as many ways to end up in whitewater for the wrong reason 26 00:01:35,210 --> 00:01:38,390 as there is to end up in whitewater for the right reason. 27 00:01:39,080 --> 00:01:42,250 So in episode one, if you haven't seen that in this little 28 00:01:42,310 --> 00:01:45,100 mini series, I'd encourage you to go back to it because I lay 29 00:01:45,250 --> 00:01:47,890 some of the foundation. We talk about what the different stages 30 00:01:48,010 --> 00:01:51,070 are, just in case you're new to the the predictable success life 31 00:01:51,160 --> 00:01:54,430 cycle. We talk about the different leadership styles, 32 00:01:54,460 --> 00:01:56,890 which is a really really important part of how 33 00:01:57,130 --> 00:02:01,020 organizations end up in whitewater by mistake. We talk 34 00:02:01,080 --> 00:02:04,230 about why it matters, like what's the problem with getting 35 00:02:04,320 --> 00:02:06,750 into whitewater too early, and we actually built on that a 36 00:02:06,810 --> 00:02:09,630 little more in episode two. So, if you want to know more about 37 00:02:09,660 --> 00:02:12,780 why getting into whitewater early is a bad thing, check out 38 00:02:12,960 --> 00:02:17,940 the second episode in this little series. In this third 39 00:02:18,570 --> 00:02:22,070 series, we're going to talk about the second reason why 40 00:02:23,450 --> 00:02:26,660 organizations end up in whitewater prematurely. Now, 41 00:02:26,720 --> 00:02:30,140 again, the first reason, which we talked about in the previous 42 00:02:30,290 --> 00:02:34,250 episode, is that they are overvisioned, and the only right 43 00:02:34,490 --> 00:02:39,950 reason is that they are overoperated. So the goal then 44 00:02:39,950 --> 00:02:43,030 is to make sure that your organization only ever gets to 45 00:02:43,060 --> 00:02:47,110 Whitewater by having too much operator to sustain that 46 00:02:47,200 --> 00:02:50,980 success. If you're overvision, or if you're wondering what 47 00:02:51,040 --> 00:02:53,500 overvision is, or you think you might be overvisioned, check out 48 00:02:53,530 --> 00:02:55,960 the previous episode. In this one, we're going to talk about 49 00:02:56,080 --> 00:02:59,830 one of you know maybe the most confusing reasons, and that is 50 00:02:59,950 --> 00:03:03,960 that you can end up in whitewater because you are 51 00:03:04,290 --> 00:03:09,660 overprocessed. Now, again, if you've been following along in a 52 00:03:09,720 --> 00:03:12,030 couple of these episodes, you might think that's insane 53 00:03:12,390 --> 00:03:16,710 because, again, if you're familiar with the model at all, 54 00:03:16,830 --> 00:03:19,440 you know that what do you have to do when you're in whitewater? 55 00:03:19,560 --> 00:03:22,610 You have to add systems and processes. The reason why you're 56 00:03:22,640 --> 00:03:24,860 in whitewater is because you don't have enough system and 57 00:03:24,890 --> 00:03:27,440 process, and there's too much complexity, and you need system 58 00:03:27,470 --> 00:03:31,850 and process to overcome that complexity. Then why in the 59 00:03:32,390 --> 00:03:36,920 world would adding system and process put you into whitewater? 60 00:03:37,100 --> 00:03:40,040 And if you're in whitewater because you have too much system 61 00:03:40,100 --> 00:03:44,170 and complexity, you have too much system and process. Then, 62 00:03:45,160 --> 00:03:48,730 how in the world do you get out? Because the only way out, Scott, 63 00:03:49,330 --> 00:03:52,000 is to to add system and process. If we have too much, how can we 64 00:03:52,180 --> 00:03:54,760 add more and think that it's going to change anything? It 65 00:03:55,000 --> 00:04:00,810 won't. It won't. And that's the point. That's the that's the 66 00:04:01,110 --> 00:04:03,750 whole problem with ending up here. Now, how does this happen? 67 00:04:04,080 --> 00:04:06,450 Let's unwind this a little bit because it's really important to 68 00:04:06,450 --> 00:04:09,210 understand how we get here. Because this is again, I think 69 00:04:09,270 --> 00:04:13,920 the it could very well become the the most common reason why 70 00:04:14,100 --> 00:04:16,710 organizations struggle with whitewater when they shouldn't. 71 00:04:17,100 --> 00:04:19,800 I think it's going to pass being overvisioned if it hasn't 72 00:04:19,860 --> 00:04:25,790 already. And here's what the problem is, and it's twofold. 73 00:04:27,500 --> 00:04:32,330 One, people who've been through whitewater, or people who help 74 00:04:32,420 --> 00:04:35,330 people through whitewater, folks who understand the whitewater 75 00:04:35,450 --> 00:04:39,560 stage, and have learned the lessons of needing more system 76 00:04:39,620 --> 00:04:43,330 and process, when they are asked, "Hey, what do I do to 77 00:04:43,390 --> 00:04:46,660 grow? How do I scale? They, because Whitewater is so 78 00:04:46,810 --> 00:04:49,240 painful, one of the very first things they're going to say is, 79 00:04:49,810 --> 00:04:54,040 "You need to have systems and processes to scale, and that is 80 00:04:54,040 --> 00:04:58,030 accurate for somebody who's legitimately in Whitewater who 81 00:04:58,180 --> 00:05:03,750 has over-operated. And can no longer sustain fun. The path 82 00:05:03,990 --> 00:05:08,850 forward for them is absolutely to add system and process. Now 83 00:05:09,000 --> 00:05:12,060 it's a very specific set of systems and processes. It's not 84 00:05:12,120 --> 00:05:17,400 just system and process galore, and it's and it's to use those 85 00:05:17,460 --> 00:05:21,260 systems and processes in a very specific way, not just to throw 86 00:05:21,320 --> 00:05:24,500 them haphazardly at everything, or ask ChatGPT to make you a 87 00:05:24,590 --> 00:05:30,350 handbook. That's not going to do anything. Instead, you have to 88 00:05:30,380 --> 00:05:32,690 have the right systems. You have to embrace those systems, and 89 00:05:32,720 --> 00:05:35,690 you have to you have to build them into the way that you lead. 90 00:05:35,840 --> 00:05:45,070 It has to change the way that you lead. Now, how do we end up 91 00:05:45,160 --> 00:05:47,830 here prematurely? Well, those folks who recognize, hey, I've 92 00:05:47,920 --> 00:05:50,140 been through whitewater. I know what that's like. I know how we 93 00:05:50,260 --> 00:05:52,720 got out. It was by adding systems and processes. They tell 94 00:05:52,900 --> 00:05:56,470 other people you need systems and processes, but everyone 95 00:05:56,560 --> 00:06:00,540 fails to recognize that there's a timing to this, that there's a 96 00:06:00,660 --> 00:06:04,110 sequence to it. That when you're a young organization in early 97 00:06:04,170 --> 00:06:06,990 struggle, systems and processes aren't going to do anything if 98 00:06:07,110 --> 00:06:10,170 you don't even know what you're having to systematize or process 99 00:06:10,260 --> 00:06:13,350 in the first place. If you're creating a new product and you 100 00:06:13,410 --> 00:06:16,560 don't even know what it is yet, you can't build a system for 101 00:06:16,650 --> 00:06:19,770 delivering it. Right now, that's a little extreme, but it's kind 102 00:06:19,800 --> 00:06:23,270 of the same thing all across the board in early struggle, and so 103 00:06:23,300 --> 00:06:25,940 what I'm getting is there's a right time and place for system 104 00:06:25,970 --> 00:06:30,350 and process, and the right time for for system wide, enterprise 105 00:06:30,500 --> 00:06:34,520 wide system and process for a systematic way of leading the 106 00:06:34,640 --> 00:06:37,460 organization. The time for that is when you get into whitewater 107 00:06:37,820 --> 00:06:42,460 again because you've overoperated, but that also 108 00:06:42,550 --> 00:06:46,480 means that that time is not before that, because here's the 109 00:06:46,570 --> 00:06:50,290 problem: operators, the folks that you want to drive you 110 00:06:50,410 --> 00:06:54,580 toward Whitewater, if we could say it that way. Let me say it a 111 00:06:54,610 --> 00:06:57,700 better way: operators, the ones who are going to make the most 112 00:06:57,880 --> 00:07:00,870 fun in fun, the ones who are going to let you get the biggest 113 00:07:00,960 --> 00:07:04,680 in fun. The ones who will need the least management from you in 114 00:07:04,860 --> 00:07:10,470 fun. The ones who can create the most success in fun. Those 115 00:07:10,590 --> 00:07:15,120 folks, they don't like systems and processes. Not overly 116 00:07:15,240 --> 00:07:19,020 cumbersome ones. They will deal with as little system and 117 00:07:19,050 --> 00:07:22,610 process is as needed, and probably not a whole lot more, 118 00:07:23,540 --> 00:07:25,880 because one of the things you need to know about operators is 119 00:07:25,970 --> 00:07:28,310 that the motto of a great operator is "Tell me what to do 120 00:07:28,400 --> 00:07:33,110 and don't watch. You can tell me what to do, but I don't want you 121 00:07:33,200 --> 00:07:36,650 hovering over my shoulder telling me how to do it. That's 122 00:07:36,680 --> 00:07:40,480 the way that operators work. Well, what happens when we hear, 123 00:07:40,780 --> 00:07:43,870 oh, you need systems and processes to scale. And instead 124 00:07:43,900 --> 00:07:46,510 of letting our operators have room to breathe and do their 125 00:07:46,630 --> 00:07:50,020 thing and grow the organization their way, we go in and we start 126 00:07:50,110 --> 00:07:53,620 imposing systems and processes on them. What do you think a 127 00:07:53,710 --> 00:07:57,940 great operator is going to do in that circumstance? They're gone, 128 00:07:58,570 --> 00:08:01,200 right? They're gonna. They're either going to ignore the 129 00:08:01,290 --> 00:08:04,530 system and process, and if you're wise enough, you'll 130 00:08:04,650 --> 00:08:09,120 actually let them because you're the one who's wrong, or they 131 00:08:09,420 --> 00:08:12,390 will leave and find somewhere else where they can work without 132 00:08:12,540 --> 00:08:15,750 having someone over their shoulder 24/7. Because operators 133 00:08:15,870 --> 00:08:18,750 hate being micromanaged, and the amount of system and process you 134 00:08:18,780 --> 00:08:21,710 need to get out of Whitewater will leave a lot of operators, 135 00:08:21,740 --> 00:08:24,200 not all of them, but a lot of them, feeling micromanaged. 136 00:08:26,179 --> 00:08:31,579 So operators are this like critical gift for the fun stage, 137 00:08:32,389 --> 00:08:36,019 and we want to set up our system in the fun stage for operators 138 00:08:36,109 --> 00:08:38,359 so that we can get as big as possible, as simple as possible. 139 00:08:39,529 --> 00:08:42,489 And when we add system and process. We actually 140 00:08:42,789 --> 00:08:46,659 artificially add complexity because it's actually more 141 00:08:46,869 --> 00:08:51,099 complicated to do the thing and write it down and follow the 142 00:08:51,219 --> 00:08:55,719 checklist and report to five different people than it is to 143 00:08:55,809 --> 00:09:00,779 do the thing, right? Like that. That's that's indisputable. And 144 00:09:00,869 --> 00:09:03,149 so when we add system and process, here's what's here's 145 00:09:03,179 --> 00:09:07,799 what happens. The the best way I can describe what being over 146 00:09:07,979 --> 00:09:11,939 processed is and why it pushes you to whitewater prematurely is 147 00:09:12,029 --> 00:09:15,029 it's kind of like if you took I I drive a little pickup truck 148 00:09:15,359 --> 00:09:18,359 and if you take even that little pickup truck and you take its 149 00:09:18,479 --> 00:09:21,349 brakes right you take its brakes off that's the dangerous 150 00:09:21,439 --> 00:09:23,989 vehicle. That that's not a pleasant thing to drive because 151 00:09:24,019 --> 00:09:26,239 the moment you've got to stop at an intersection, you're in an 152 00:09:26,329 --> 00:09:29,479 accident. So those brakes are a good thing. Agreed, right? It's 153 00:09:29,539 --> 00:09:32,449 pretty straightforward. Well, what happens when I put those 154 00:09:32,839 --> 00:09:38,419 brakes on my mountain bike? I mean, that that's a good like if 155 00:09:38,479 --> 00:09:41,709 it can stop my truck, it can stop my bike, right? I mean, 156 00:09:41,799 --> 00:09:44,829 like they're gonna be plenty strong enough. If I'm gonna, you 157 00:09:44,859 --> 00:09:47,469 know, pedal faster and go faster, eventually I'm gonna 158 00:09:47,559 --> 00:09:52,779 need that, right? I know it's ridiculous, but but this is 159 00:09:52,839 --> 00:09:55,089 that's the point. This is ridiculous. What happens if you 160 00:09:55,299 --> 00:09:59,049 put the the braking system from my truck onto my mountain bike? 161 00:10:00,209 --> 00:10:02,549 First thing that's going to happen is when I'm trying to 162 00:10:02,609 --> 00:10:04,169 pedal, they're going to get in the way and they're going to 163 00:10:04,199 --> 00:10:06,659 slow me down. That's what systems and processes do to your 164 00:10:06,839 --> 00:10:09,419 operators. They just get in their way and slow them down. 165 00:10:10,109 --> 00:10:13,589 And then what happens? Heaven forbid, where I ever touch the 166 00:10:13,739 --> 00:10:18,059 brake lever and activate that braking system, it's way too 167 00:10:18,269 --> 00:10:21,139 much for the bike. And so the moment I do, boom, straight over 168 00:10:21,139 --> 00:10:24,379 the handlebars, right? Not even a glimmer of hope of avoiding 169 00:10:24,649 --> 00:10:29,359 it. That would be insane. No one would do that. At least I hope 170 00:10:29,449 --> 00:10:32,959 no one would do that. But that's exactly what we do. We think I 171 00:10:33,139 --> 00:10:35,749 got to pedal faster, so I need to get the brakes from something 172 00:10:35,809 --> 00:10:39,559 that's faster, and I need to put them on my vehicle. Another 173 00:10:39,679 --> 00:10:44,109 braking analogy, and this one might help as well. Fun is a 174 00:10:44,259 --> 00:10:48,549 little bit like NASCAR on an oval circuit. The goal is to go 175 00:10:48,969 --> 00:10:53,709 and to go fast. If you're using your brakes on an oval circuit, 176 00:10:53,829 --> 00:10:55,959 you're either coming into the pit lane or avoiding an 177 00:10:56,079 --> 00:10:58,779 accident. Like those are the only two reasons, because the 178 00:10:58,929 --> 00:11:01,949 rest of the time you should be pedal to the metal or close, 179 00:11:03,239 --> 00:11:05,849 because how in the you know how are you gonna like you just 180 00:11:05,969 --> 00:11:10,169 you're you're just going you're just going, and so when you look 181 00:11:10,229 --> 00:11:13,679 at the braking system on a NASCAR vehicle, right? I think 182 00:11:13,709 --> 00:11:15,989 they have 1000 horsepower, something like that. These are 183 00:11:16,259 --> 00:11:20,929 monster engines, super powerful machines with these teeny little 184 00:11:20,989 --> 00:11:23,929 itty bitty brakes, because the brakes would just slow them 185 00:11:24,049 --> 00:11:27,529 down. Well, what happens whenever they go to a street 186 00:11:27,589 --> 00:11:30,499 circuit, or what happens when you go to a Formula One style or 187 00:11:31,459 --> 00:11:34,759 you know indie style street circuit? You need much bigger 188 00:11:34,879 --> 00:11:37,969 brakes. The brakes on a Formula One car, even though it's much 189 00:11:38,179 --> 00:11:43,839 lighter and less powerful, are significantly more powerful the 190 00:11:43,929 --> 00:11:47,889 brakes are than those on a NASCAR vehicle set up for an 191 00:11:48,039 --> 00:11:51,429 oval track. Why? Because you're using brakes a lot. You have to 192 00:11:51,549 --> 00:11:56,379 slow down to speed up. In fact, the fastest way around the track 193 00:11:56,379 --> 00:12:02,549 is to slow down the most at the right points. You actually can 194 00:12:02,789 --> 00:12:06,869 exit a corner faster by slowing down better. Otherwise, you just 195 00:12:06,929 --> 00:12:10,139 end up in the wall. And so, both of these, I want to show you. 196 00:12:10,229 --> 00:12:12,929 Systems and processes are like breaks for your organization. 197 00:12:13,289 --> 00:12:17,399 And when the time comes that you need them, you need them. And 198 00:12:17,549 --> 00:12:22,159 so, when you move to a street circuit, something that has 199 00:12:22,219 --> 00:12:25,579 something other than just left turns, you will very quickly 200 00:12:25,699 --> 00:12:28,159 recognize the need for them. And if you don't, it's pretty 201 00:12:28,369 --> 00:12:29,029 catastrophic. 202 00:12:29,330 --> 00:12:33,740 Which is why people who've been through that experience are so 203 00:12:34,400 --> 00:12:38,690 right to say you have to have systems and processes. But if 204 00:12:38,780 --> 00:12:41,920 you add all that breaking to your team that's just trying to 205 00:12:41,950 --> 00:12:45,460 go in a straight line as fast as they can. The only thing it's 206 00:12:45,550 --> 00:12:49,210 going to do is slow you down, and then throw you into 207 00:12:49,240 --> 00:13:01,660 whitewater prematurely. What's going on here is that folks 208 00:13:02,410 --> 00:13:04,320 who've either been through Whitewater and want to help 209 00:13:04,470 --> 00:13:08,820 others, or folks who see that Whitewater exists-right? You've 210 00:13:08,940 --> 00:13:11,430 read the Predictable Success book. You know that Whitewater's 211 00:13:11,580 --> 00:13:14,700 out there. We have the temptation to try and skip 212 00:13:14,970 --> 00:13:18,270 Whitewater. We think, well, if I can add those systems and 213 00:13:18,330 --> 00:13:22,850 processes now, then I'll never feel the pain of whitewater, and 214 00:13:22,850 --> 00:13:25,490 if you've got anything from this episode, I hope you recognize 215 00:13:25,640 --> 00:13:29,720 that it's that doesn't work. It actually makes whitewater twice 216 00:13:29,810 --> 00:13:34,850 as long, twice as expensive, and twice as hard, because you hit 217 00:13:34,940 --> 00:13:38,750 whitewater with less velocity. And I know I'm throwing a bunch 218 00:13:38,780 --> 00:13:41,470 of metaphors at you, but I really want to land the point, 219 00:13:42,190 --> 00:13:44,530 and I actually had someone who who had a bunch of whitewater 220 00:13:44,560 --> 00:13:48,400 experience who said to me, the safest way to hit whitewater 221 00:13:48,520 --> 00:13:52,060 rapids is to hit them as fast as you can. When you have a big 222 00:13:52,180 --> 00:13:55,450 rapid, you want to get as much momentum going into it as you 223 00:13:55,540 --> 00:13:58,930 possibly can, so that you have the greatest opportunity to 224 00:13:59,050 --> 00:14:02,400 steer and navigate through it. That's what's going on for 225 00:14:02,430 --> 00:14:05,070 organizations. When organizations are overprocessed, 226 00:14:05,100 --> 00:14:09,600 they hit whitewater without the requisite momentum. Why is that 227 00:14:09,810 --> 00:14:13,200 a problem? Well, it's a really big problem because, like we've 228 00:14:13,260 --> 00:14:17,040 mentioned earlier, you have to, if you're going to get through 229 00:14:17,070 --> 00:14:19,740 whitewater that you created on your own by having too much 230 00:14:19,800 --> 00:14:23,690 system and process, you have to simultaneously reduce system and 231 00:14:23,750 --> 00:14:27,560 process, increase operator, usually increase some vision as 232 00:14:27,680 --> 00:14:32,750 well to get through it, and add systems and processes all at the 233 00:14:32,930 --> 00:14:38,360 same time. Like that screws with your mind, and it's really 234 00:14:38,480 --> 00:14:43,420 really hard to do. What happens is more often than not, and I've 235 00:14:43,570 --> 00:14:46,000 helped folks through this before I recognize what was going on. 236 00:14:46,060 --> 00:14:50,530 I've helped folks do this exact thing. I've helped folks to add 237 00:14:50,710 --> 00:14:53,530 more system and process that they need than they needed, 238 00:14:53,650 --> 00:14:57,370 thinking it would help them. And here's what happens every single 239 00:14:57,490 --> 00:15:01,440 time, and and it's. It's unfortunate because most of the 240 00:15:01,530 --> 00:15:04,350 time folks can't even see that they've done this until the end. 241 00:15:04,830 --> 00:15:07,530 Here's how you know, and unfortunately it's at the very 242 00:15:07,650 --> 00:15:09,930 end. But here's how you know if you were overprocessed when you 243 00:15:09,990 --> 00:15:13,710 started dealing with whitewater, it's that when you do the things 244 00:15:13,830 --> 00:15:16,140 that you need to to get out of whitewater, and again they're 245 00:15:16,200 --> 00:15:18,360 very specific. Read the Predictable Success book. We're 246 00:15:18,420 --> 00:15:20,990 not really going to talk about what those are too much in this 247 00:15:21,110 --> 00:15:24,050 series, but there's a ton of great information on it. This 248 00:15:24,080 --> 00:15:27,050 this one right here looks like this: Predictable Success by Les 249 00:15:27,140 --> 00:15:33,920 McEwen. When you do all of those things, you can check all the 250 00:15:34,040 --> 00:15:38,150 boxes. You can have a great org chart, perfect job descriptions, 251 00:15:38,540 --> 00:15:40,450 crystal clear strategy on how you're going to get to 252 00:15:40,510 --> 00:15:44,500 predictable success, and you'll add all of that system and 253 00:15:44,530 --> 00:15:48,610 structure, and it will amount to absolutely nothing. Your 254 00:15:48,670 --> 00:15:54,010 organization won't grow any faster on the other side of it. 255 00:15:54,100 --> 00:15:58,750 It's crazy. When and and that's not because those things don't 256 00:15:58,840 --> 00:16:00,630 work. Because if I take an organization that's 257 00:16:00,750 --> 00:16:03,870 overoperated, and even some that are overvisioned, and I put them 258 00:16:03,990 --> 00:16:08,820 through the that same course, that same set of practices, and 259 00:16:09,150 --> 00:16:13,200 and same set of processes, and same set of structures. Most of 260 00:16:13,260 --> 00:16:16,350 them will something like triple their bottom line. Some of them 261 00:16:16,380 --> 00:16:20,820 will double their revenue in the first year after doing that. The 262 00:16:20,910 --> 00:16:25,760 transformation is unbelievable when you do the right things at 263 00:16:25,850 --> 00:16:29,900 the right time, but if you try and do all of those things early 264 00:16:30,020 --> 00:16:32,660 because you arbitrarily push yourself into whitewater by 265 00:16:32,810 --> 00:16:36,290 putting too much system and process on your operators, it's 266 00:16:36,380 --> 00:16:36,980 not going to work. 267 00:16:39,710 --> 00:16:43,330 So the second big reason why folks end up in whitewater 268 00:16:43,450 --> 00:16:46,330 prematurely, and I think it's going to be the first big reason 269 00:16:46,390 --> 00:16:50,230 very soon, is that they they take all of the talk in our 270 00:16:50,380 --> 00:16:53,080 world now about systems and processes, systems and 271 00:16:53,110 --> 00:16:56,740 processes, systems and processes, and they take those 272 00:16:56,950 --> 00:16:59,710 big heavy braking systems and they stick them on their little 273 00:16:59,800 --> 00:17:02,010 mountain bike and they're pedaling harder than ever and 274 00:17:02,070 --> 00:17:05,910 not getting anywhere. And so, if you're sitting there thinking, 275 00:17:06,000 --> 00:17:08,610 here's probably the best way that you can diagnose this ahead 276 00:17:08,640 --> 00:17:12,030 of time. If you're sitting there thinking, "Hey, we've really 277 00:17:12,090 --> 00:17:16,290 invested in systems and processes, and honestly, I think 278 00:17:16,320 --> 00:17:18,660 they're good systems and processes, but I can't tell a 279 00:17:18,720 --> 00:17:21,680 difference. We're not any more profitable. We're not any. We're 280 00:17:21,740 --> 00:17:25,130 not. Our revenue is not growing like crazy. We're still not able 281 00:17:25,220 --> 00:17:28,550 to scale. If you added all of those, there's a chance that you 282 00:17:28,730 --> 00:17:33,200 added the wrong ones. But there's also a good chance that 283 00:17:33,260 --> 00:17:36,380 you added the right ones at the wrong time. You added them too 284 00:17:36,890 --> 00:17:39,410 soon. Here's another thing, and we talked about this in the 285 00:17:39,410 --> 00:17:43,390 previous episode, but it applies here as well. If you end up 286 00:17:43,600 --> 00:17:46,780 overprocessed and in whitewater, one of the ways to tell that you 287 00:17:46,870 --> 00:17:50,650 did it too soon is to look at how many people you have on your 288 00:17:50,740 --> 00:17:55,870 team, because while it's not perfect, the head count should 289 00:17:56,140 --> 00:18:02,520 give us a decent way of approximating complexity, and if 290 00:18:02,610 --> 00:18:05,550 you're sitting there and you've got great systems and processes, 291 00:18:05,640 --> 00:18:08,850 and there's 15 or 20 of you on the team, and that's bigger than 292 00:18:08,910 --> 00:18:11,790 it's ever been before, but you are drowning in whitewater. 293 00:18:12,090 --> 00:18:15,120 There's you're dropping the ball over the stuff. Stuff's going 294 00:18:15,180 --> 00:18:18,690 wrong. Your systems and processes aren't working. You 295 00:18:18,750 --> 00:18:21,140 probably have too much system and process. You've probably 296 00:18:21,230 --> 00:18:25,520 tried to overcompensate for a lack of competent process. I'm 297 00:18:25,550 --> 00:18:29,360 sorry, operators. A lack of competent or quality operators. 298 00:18:30,050 --> 00:18:32,960 You've tried to compensate for that by adding a bunch of system 299 00:18:32,990 --> 00:18:36,440 and process to something. You've overcooked it, and you still 300 00:18:36,500 --> 00:18:40,280 don't have enough operator to grow. Well, if that's you, what 301 00:18:40,280 --> 00:18:44,560 do you do? And just like if you're overvisioned, what you 302 00:18:44,650 --> 00:18:47,020 have to do is you actually have to go back before you go 303 00:18:47,320 --> 00:18:50,980 forward. It's kind of like you were driving down the road next 304 00:18:51,040 --> 00:18:53,920 to a river, and there was a bunch of rapids over here, and 305 00:18:53,920 --> 00:18:55,930 they're not the ones that you want to be in, but they look 306 00:18:56,020 --> 00:18:59,140 kind of fun. And instead of driving down the road at 60 307 00:18:59,230 --> 00:19:02,280 miles an hour, you all jumped out and got into the rapids, and 308 00:19:02,280 --> 00:19:06,360 you're just bouncing around for no reason at all. Let's get back 309 00:19:06,450 --> 00:19:09,360 on the road. You're going to move a lot faster on the road. 310 00:19:09,930 --> 00:19:15,000 How do we do that? We actually do that by not necessarily just 311 00:19:15,240 --> 00:19:17,610 lessening system and process, because that's kind of an 312 00:19:17,700 --> 00:19:20,700 arbitrary thing. We just like let's just abolish processes. 313 00:19:21,150 --> 00:19:24,170 Instead, what I want you to do is not think so much about 314 00:19:24,290 --> 00:19:27,950 lessening system and process, but about increasing the 315 00:19:28,880 --> 00:19:32,090 operatorness of your organization, and that's going 316 00:19:32,090 --> 00:19:34,490 to happen in two different ways. First, you're going to have to 317 00:19:34,550 --> 00:19:37,640 make sure you have good operators on the team, or go get 318 00:19:37,820 --> 00:19:42,730 some. Then, what you want to do is take your decision making, 319 00:19:43,030 --> 00:19:46,390 your systems, your processes, your products, everything that 320 00:19:46,480 --> 00:19:50,350 you do, and I want you to run it through this filter. What can we 321 00:19:50,500 --> 00:19:55,990 do to this to help our operators succeed even more? How can we 322 00:19:56,260 --> 00:20:00,510 simplify what we're doing so that our operators can? Succeed 323 00:20:00,630 --> 00:20:06,120 even more, and when you use quality operators as the lens, 324 00:20:06,120 --> 00:20:09,780 as the litmus test for whether you need a system or not, 325 00:20:09,840 --> 00:20:12,240 whether you need a process or not, whether you need another 326 00:20:12,360 --> 00:20:16,950 idea or not, when you really focus in on just equipping those 327 00:20:17,280 --> 00:20:21,680 really great operators to go get stuff done, not to be super 328 00:20:21,770 --> 00:20:26,960 strategic, not to be the most innovative, but to go and sell 329 00:20:27,350 --> 00:20:30,590 and deliver and sell and deliver and sell and deliver and sell 330 00:20:30,650 --> 00:20:33,560 and deliver until you have a gigantic organization that's 331 00:20:33,620 --> 00:20:35,990 wonderful in every way. I'm being a little facetious, but 332 00:20:36,050 --> 00:20:43,570 you get the point. Go find the operators and then refine all of 333 00:20:43,690 --> 00:20:46,900 what you do, from how you make decisions to what checklists you 334 00:20:47,020 --> 00:20:47,290 have. 335 00:20:48,460 --> 00:20:52,600 Refine all of that using the lens. How can we make this serve 336 00:20:52,840 --> 00:20:57,400 our operators better? And then listen. They will tell you what 337 00:20:57,580 --> 00:21:01,080 sucks, and they're probably right. At least, if they're a 338 00:21:01,200 --> 00:21:04,020 quality operator and they're complaining about something, 339 00:21:04,650 --> 00:21:06,750 well, sometimes quality operators complain, so we have 340 00:21:06,780 --> 00:21:10,290 to be a little careful with this. But even so, if they're 341 00:21:10,380 --> 00:21:13,290 complaining about something and they're saying, "Hey, that's not 342 00:21:13,350 --> 00:21:16,470 necessary. That's too much. Why are we doing that? It's too 343 00:21:16,620 --> 00:21:22,160 complicated, then at least listen. At least listen, because 344 00:21:22,250 --> 00:21:26,180 they very well may be onto something, and so that's what 345 00:21:26,180 --> 00:21:28,190 happens when we're overprocessed. We end up in 346 00:21:28,190 --> 00:21:30,890 whitewater prematurely. We set ourselves on a path for doing 347 00:21:31,010 --> 00:21:33,560 all the right things and getting none of the right results, and 348 00:21:33,560 --> 00:21:36,830 that's miserable. You don't want to be there. Instead, what we 349 00:21:36,920 --> 00:21:41,650 can do is get out of whitewater, get back on the highway, and get 350 00:21:41,740 --> 00:21:45,850 a lot bigger, a lot more successful, and have a ton of 351 00:21:45,970 --> 00:21:49,990 fun doing it. This I'm realizing that this is coming across a 352 00:21:50,020 --> 00:21:52,540 little negative, but it really shouldn't. I actually get 353 00:21:52,840 --> 00:21:56,650 really, really excited when I come across an organization that 354 00:21:56,860 --> 00:21:59,620 is prematurely in whitewater because I can recognize pretty 355 00:21:59,710 --> 00:22:03,570 quickly they don't actually need to go through whitewater. They 356 00:22:03,630 --> 00:22:08,010 don't need to do the the open heart surgery that is the the 357 00:22:08,010 --> 00:22:10,410 stuff of getting through whitewater to predictable 358 00:22:10,470 --> 00:22:13,710 success. They don't have to do that right now. I can look at an 359 00:22:13,770 --> 00:22:17,370 organization and recognize, hey, they've got another five or 10 360 00:22:17,730 --> 00:22:22,670 years of fun ahead of them. Let's go back there and crush 361 00:22:23,090 --> 00:22:26,330 it. And again, you'll see organizations that can get four 362 00:22:26,510 --> 00:22:29,450 times as large without tipping back into whitewater. 363 00:22:30,140 --> 00:22:34,070 Legitimately, literally seen that, and that could be the same 364 00:22:34,310 --> 00:22:37,670 for you. So, if you're overprocessed, it's important to 365 00:22:37,700 --> 00:22:40,870 recognize that you probably are a big part of putting you there, 366 00:22:41,140 --> 00:22:44,860 you might like process a little bit more than you should, and if 367 00:22:44,950 --> 00:22:47,950 that's the case, then we just need to tap the brakes on the 368 00:22:48,100 --> 00:22:51,520 brakes. We need to we need to chill out on the system and 369 00:22:51,550 --> 00:22:54,970 structure, and we just need to find some good people, and we 370 00:22:55,060 --> 00:22:58,600 need to help manage them well, and that's what's going to help 371 00:22:58,690 --> 00:23:01,020 those of you who are overprocessed and end up ended 372 00:23:01,050 --> 00:23:03,810 up in whitewater because of it to get back to fun and 373 00:23:04,080 --> 00:23:08,550 thoroughly enjoy both being in fun and growing in fun. It can 374 00:23:08,550 --> 00:23:14,730 be very cool. With that, that sets us up for the third most 375 00:23:14,820 --> 00:23:20,220 likely reason or the third wrong way to get into whitewater, and 376 00:23:20,310 --> 00:23:24,140 this is the one that nonprofits struggle with almost all the 377 00:23:24,380 --> 00:23:28,220 time. So, if you're a nonprofit leader in particular, or if 378 00:23:28,370 --> 00:23:31,640 you're a very people-oriented leader, even if you're in the 379 00:23:31,670 --> 00:23:34,940 for-profit world, then you are not going to want to miss the 380 00:23:35,030 --> 00:23:38,660 next episode in this series because this is what happens to 381 00:23:38,870 --> 00:23:42,790 people leaders that causes them to accidentally get into 382 00:23:42,820 --> 00:23:46,240 whitewater way too soon. I'll show you what it is, why it 383 00:23:46,270 --> 00:23:48,670 happens, and what you can do about it. All that in the next 384 00:23:48,700 --> 00:23:55,030 episode. I'll see you there. Hey everyone, Scott Ritzheimer here. 385 00:23:55,180 --> 00:23:58,300 Thank you so much for listening to the Start Scale and Succeed 386 00:23:58,360 --> 00:24:01,860 podcast. I hope this episode gave you exactly what you need 387 00:24:01,920 --> 00:24:05,460 for the level you're in right now. If you want to discover 388 00:24:05,730 --> 00:24:08,880 what level you're in, take our 10-question Founders Evolution 389 00:24:08,940 --> 00:24:12,510 Quiz for free at foundersquiz.com. That's 390 00:24:12,660 --> 00:24:17,040 foundersquiz.com. It'll pinpoint exactly where you are and give 391 00:24:17,070 --> 00:24:20,460 you tailored tips to move forward and reach that next 392 00:24:20,520 --> 00:24:23,930 level in your journey as a founder. If you got something 393 00:24:23,990 --> 00:24:26,720 out of today's episode, don't forget to subscribe, rate, or 394 00:24:26,810 --> 00:24:30,410 review. It helps us reach more founders like you, and let's be 395 00:24:30,470 --> 00:24:34,220 honest, it means a ton to me, my team, and all our incredible 396 00:24:34,280 --> 00:24:38,150 guests. So keep starting, scaling, and succeeding, and 397 00:24:38,180 --> 00:24:40,070 I'll see you in the next episode.