When to run systems?

Hi, and welcome to today's episode, my name is Tom Rolley of System IO, we have been having a conversation about the possibility of you having a business that is designed to work, whether you're there or to work without you.

And the significant benefits from this, that you can be present, and be involved in the business growing the business take on that entrepreneurial role.

But also you have the option to be able to step away for four weeks and go on holidays and eventually sell your business with its systems and processes in place.

Yesterday, we looked at the benefits of systems and processes giving you what work needs to be done in your business, like actually defining the work that needs to be done.

But today, I want to look at it as a problem of knowing who's going to do that work.

And the initial conversation is that if you have documented systems, and you have documented processes, then it is possible that you can assign your team to do that work.

So this could look like either that if there's work that every time they need to do that task, it's already got their name there.

And when you go to copy that system and use it, then they're ready to go, it automatically assigns them.

And they can see that they've got to do that work.

If on the other hand, it's something that could be done by anyone, then on copying the system, then you can assign who's that work is, and they can go through and as they start each process, they take off staff and then they finish that process.

And that's going to give you one critical thing that it's unlikely that you have right now.

And that is optics on who's doing the work in your business.

At the end of the week, you can actually look and say, Hey, what work did that team member do? And you can see that's the work they got done.

This is extremely helpful in terms of a couple of things.

One, if there's a question mark, about what got done, because, like Qi, I'm paying them a lot of money, what actually got done, and you can look and you can see the data, it's there, it's like, okay, I can see that they ran this system, this system, this system, this system, these all got done their meeting expectations, it suddenly takes it out of an unknown feeling about whether they are or not underperforming to actual data, you know, okay, there it is, it's clear, it also gives you a couple of other advantages.

One is that you can redeploy your team, let's say that you've got a deadline that's coming up.

And you can see that the work that is required to get done for that deadline isn't going to get done with the available manpower that you've got.

And so you can take your team and bring them off things that might be due in the future and say, Hey, let's get this deadline met.

We need more resources here.

And if you have documented processes, then people who don't normally do that work can pick up, they might be a little slower.

But the instructions are there.

And suddenly the deadlines were met.

It also enables you to have more complicated systems in your business where you might have multiple team members working on that one project.

And that by having the capacity to say, hey, this team members on this process and these team members on this process, it gives everybody the ability to see what that what's getting worked on.

It gives everybody the ability to see that what are the dependencies on further work down this down the chain and say, hey, well, we need that done.

And that done.

They're currently getting deployed, what's the estimated time, and this actually now enables you to work as a team.

Now a lot of the work might just be one system, one team member.

But as you get into bigger teams, you've got to have more cross-collateralization of work where multiple teamwork members are working on a single project.

And so this capacity, this ability to actually see the work that's getting done in real time is extremely powerful.

And this requires you, to have your systems and processes documented so that you can then assign who's going to do that work.

If that's something that you're interested in, head over to system I O dot Dev, go through the training around this topic you will cover not only copied us but also a bunch more helpful information at the end of that.

There's an opportunity for us to meet together, see if we're a match and how I can help in your specific situation.

Thanks so much for tuning in today.

Tomorrow we're going to cover an interesting topic about when doing these systems get used now we know what systems theory is and who's going to do it and next question is when are these going to be deployed join me then thanks so much for your attention and look forward to seeing our next one tomorrow.