A-1 Business System

Hey, it's David Jennings, founder of Systemology and As you start to build systems in your business and mapping out different processes, you'll find quite often there might be different variables and scenarios that might cause different results. Maybe when you're selling something, there's option A, B or C and depending on what the client ends up taking, some of the steps end up being a little bit different. So we need to think about, look, if we're designing a system for the first time, do we capture all of those variations? And if we have a look on the iPad here, I've got a little graphic that kind of illustrates this quite well. If this is the start and this is the finish, you can see with this graphic there might be multiple different paths that can happen to deliver maybe that product or service or that particular widget or whatever it is that you're working on. So these multiple paths, then the question becomes, well, if I'm creating a system, am I going to capture every variable? Now this is quite a simple example and it might be easy to break away, but oftentimes there might be loads of different decisions that need to be made throughout the delivery of whatever the system is that you're trying to capture is. And the question is, will we going to capture all of those variables? It can be quite overwhelming at the start to think about the immenseness of what might need to be captured to capture every possible scenario. So what I'm going to suggest is when you first build a system, capture what we call the most probable, what is the most Think about who is your ideal client and what is the system that you're working on and what is most Now most You're going to have team members that are newer to the team and then you're going to have team members that are more experienced. Now in situations where the path doesn't follow the most probable and it goes off the beaten track, that's where, well maybe these exceptions because you might not have it doc So all of the most probable path, which is obviously the green one, maybe that goes to the less experienced team members. Now when you think about it, you're designing a system and a process to capture the most probable then you're getting less experienced team members to learn and follow that process and learn it inside and out. You've created systems, processes, extra video, supporting notes to all support that most probable path, which then makes it easier for the less experienced team member to understand what to do as they move someone through that process. And then when it heads off the beaten track, then they can flag it for a more experienced team member to take over and then handle that exception. Now over time your systems, because they're an organic doc Now we look to do this. But that comes down the line. Systems are organic doc But in the early days, when you're just getting started, just capture the most probable. You will actually find that has tremendous wins for your business and also gets you focused on optimizing for the most probable experience and scenario, which is particularly important if you've selected a primary target audience or a client that you're looking to serve. And then you're optimizing towards them. That means that dream client is going to get the best experience because you've done the most thought and it will be that most probable path. So there are some ideas to explore. If you want to find out more and you haven't got a copy of the systemology book, definitely check that out. I think that's going to be really helpful for you and I'll