Copy to use... Keep your originals clean!

Hello, and welcome to today's episode, my name is Tom Rolley of System IO, we have been on a journey and we're continuing that today, we began looking at the problem that you face as a successful business owner, looking to scale beyond where you are right now that you've had some success.

But in that success, a series of problems have opened up, that has meant that your journey from one to 3 million in revenue, five to seven people in your team up to where perhaps you want to be 10 million 20 million bigger teams that you have hit a plateau, you have hit a time where you are spending all your time managing your people and things are not going well.

On the other hand, we opened up the possibility that you have designed your business to work with you without you that you can sell it that you can scale it that you can take a holiday and still take the profits.

Yesterday, we looked at the first of four steps in bridging the gap between these two realities.

And that one was called get organized, if you haven't watched that invite you to go and watch or listen to yesterday's episode, and take out the insights from that idea of getting organized.

But today, we're going to leave that and move into the idea of copy, to use copy to use what the heck am I talking about? Well, before we go there, let's layout a little bit of structure for you so that you have in your mind, the anatomy, so to speak of a system.

When I think about systems, I think about four things.

One, there is the system itself.

Secondly, there are one or more processes that make up that system versus like so a system could be considered as a game of soccer.

It's got rules, it's got timing, it's got outcomes, it's got how to win.

But the actual processes that make that up are more like climbing up a ladder.

It's like step, step, step, step step, it takes you from A to B.

So we've got systems, we've got processes, some processes may use a template.

So this could be a Google Doc, this could be a typical form or a jot form.

This could be anything where you're entering in data, and it's going to produce something out of it.

And that thing that it produces is an asset.

Now for clarification, not all processes will have templates.

But whatever they do at the end of the system that is in my word idea, an asset, it's an asset for the system, it's an asset for the business, sorry, this means that the system has been run, and it's done something, it's produced something now that could be a tangible product that could be that the banking got done, that could be that a new client was onboarded, that could be a new team member was hired, there is a purpose for the system.

And that purpose is classified as an asset.

So they're the four things that we've got one the system to the processes, three, the templates, and for the assets.

So let's come back having laid out that structure to this idea of copy, to use, what am I talking about here? Well, I want you to imagine that you're going to deploy a system.

And instead of going along and using that system and filling it up with the data, that you actually copy it so that you've got the original preserve, the original system stays as a clean system.

This means a couple of things.

One, you've always got a clean system, you're like ready, we want to do two or three systems great, we can duplicate it and have multiple copies of that same system being executed at the same time.

And you will have, there's no doubt that all businesses will have multiple copies of the same system running depending on which aspect of the business we're looking at, whether that's in fulfillment, whether that's in sales, at least those two areas are highly likely to have multiple copies of the same system running.

The second thing that it opens up is that you can tweak a system a little bit.

So let's say that you've got a clean system that's working well.

But you recognize that for this particular time, you actually want to change up a few things in it so you can copy that system.

Make the tweaks and it doesn't matter.

mess up your original.

So next time you go and use it, hey, it's back and preserved.

The final thing about this is when you make improvements to your system, these will now carry on through all future iterations of that system.

recognize the value of this, as you go ahead and make a change to that system.

Let's say that you improve it.

From now on, every time you go and use that system that improvement will carry through.

This is powerful, this is potent, this is extremely useful in terms of increasing the efficiency and effectiveness of how your business works, this means you can go in, and maybe it takes you one to three hours even to make an improvement in a big system.

But ongoing, you will see a half-hour improvement every single time that system gets run.

Alright, let's leave systems let's move to processes, processes.

You're not going to duplicate the processes, the processes are the instructions, they might be improved, but you're not going to use those to duplicate them, the instructions sit separately.

So let's go to our third piece, the templates.

Now, these are exactly the same, not exactly the same.

But these are the same idea as the systems that when you need to use that template, you copy it, this should not be of major breakthrough like it's a template, you've done this before.

What you may not have done before or understood before is that you can have your system set up as templates.

And that when you duplicate them, you get all the benefits that I have just described.

Finally, assets are going to be produced every time the system is executed.

So they are not a copy to use, but the two things that should be copied to use them.

Number one, the system number two, the templates, if that is a system that uses templates.

Alright, I hope you got a lot of value here.

Just learn setting out that structure systems process templates, assets, and then look at the idea of both copying the systems and the templates in order to keep your originals clean.

And particularly the idea that when you improve either of those things, the systems or the templates, every single time you use it forward is going to be of benefit to you.

If you need some help with this head over to systemio.dev.

I look forward to continuing this conversation we've got two more important steps to cover in bridging that gap from where you find yourself stressed out and struggling with exceeding business that has led to absolute chaos through to that dream result of being able to sell at a high multiple or to be able to be free of the business and continue to collect profits.

I look forward to seeing you tomorrow.

I hope you're enjoying this conversation about the power of systems and processes in business.

I will see you then.