What are the two times to execute systems?

What are the two times to execute systems? Yesterday, we covered the fundamentals of systems, the four components that the system itself the processes of that system, the templates that are in a system, and of course, most importantly, the results.

And one thing that was not possible to cover in that way, when do you use these systems, and I want to share the two times with you, you see, this is important because some systems will be on a regular schedule, they'll be on a daily execution or a weekly execution, perhaps a monthly quarterly or even a yearly execution.

And the trap that you'll run into with these is not hitting the schedule.

How do you do it? Well, the easiest way is to set a recurring calendar entry and link to wherever you execute your systems.

If that's in your project management system, that's great.

If that's in a Google Sheet, that's great as well just linked directly to that system.

The reminder comes and off you go.

Ideally, you actually block out that time in your calendar, so that you have the time available to execute it.

This would require you to know how long roughly it's going to take, is it going to take half an hour or is it going to take an hour is it going to take two hours and for you to be on point and not have something taking that time already be very careful about scheduling the systems as free time.

Because if you do not do them and they're regularly scheduled, then you will have to find time, later on, to catch up.

This is not so good.

So that's the first time scheduled systems.

The second well, what's the second, the second is on demand.

So this is not due to a timeframe, but rather something happens a trigger happens.

And then that system will get executed.

This can be set up where you have a system that sets off a number of other systems.

So there's a Master System that perhaps triggers three more, you can set up all sorts of stuff triggers might include a new client comes on board, that might include a requirement for a new project to be completed, there can be many, many different types of triggers that lead you having to execute that system.

So these are not ones that happen on a regularly scheduled basis but happen on demand.

The trap that you'll find with this one is remembering that you have these systems already created, I had an opportunity to use a system that I last used at least six to seven months ago.

And the reason that I know that is that it was a system that I use with music.

This is not a business system.

This is outside this is extracurricular.

But the reason I know that it was six to seven months ago is the last time I had a lesson was six to seven months ago.

And it hasn't been used since then.

And suddenly there was the requirement what this system does not check out that Gecko Hey, there's a gecko on the window.

Right on.

So lucky sign, what that system does is it takes a verbal song that is provided and turns it into music.

And there are about four steps in this, this is not an overly complex system.

But the fact that I had that system meant that I executed and took through from the song to the completed music in less than an hour, what would have happened usually is that I would not have been able to do this at all, I may have got lucky and been able to remember some steps and then the problem, shoot problems, shot problems shot the rest of them and got there but having more documented outside, I remember this remember these two systems executed.

So in review, two times that systems will be executed number one on demand.

This is your more challenging one.

This is where you want to have at least somewhere of all of your systems, and preferably have them defined as scheduled or On Demand.

And then you can scroll through and say oh yeah, that's an on-demand, one that I can use.

Now if you don't see the system, then you need to create a new one.

That's a whole different skill set.

But let's say that you do have it then you just execute that system.

Same with scheduled, put them in your calendar, block out the time and then execute.

Alright, hope you found that useful.

This could be transformational for the right business.

If you are struggling with systems that you know are meant to be done on a schedule but keep Getting missed.

And therefore you have to deal with the fires and the problems and the stress and the long hours and the stressed-out employees and employees coming to you to ask how to recover from the situations that should have been done.

Or you're finding yourself dealing with the consequences, which are messy.

You like, Man, why? How do we miss this? What I want you to do is to think about putting in those calendar entries on the recurring schedule.

Think about who's going to do the work, and how will it be tracked.

All of those things can be approached from a systems perspective in a very reasonable manner.

If you need some help that head over systemio.dev.

Thanks so much for tuning in to today's episode.

I hope you got a lot of value out of it.

I look forward to seeing you on tomorrow's episode.

As we continue this journey into power systems great results.

See you then.