Habits vs Systems

I hope you're having a great day.

It is a Good Friday here in Australia.

And we're always blessed by being ahead of the curve.

It's always the first place, not first place New Zealand's ahead of us.

There are a few islands ahead of us.

But it's pretty cool.

I thought I wanted to cover systems and habits today and just cover similarities differences.

What is a habit, I have been a big fan of the habit-based lifestyle introduced to me by Garrett J.

Whiteout of Wake Up Warrior began with them in November 2017.

And they or Garrett is essentially very heavy on one thing, which is habits.

And so there's a bunch of habits that Wake Up Warrior instill in people or recommend it's not a requirement.

It's not like Garrett comes around and stands next to my bed and says, Hey, Tom, did you do any of the habits today.

But over time, they just became ingrained in me that basically a couple of things, one using this software tool called the stack, which was which is basically go through and clean my brain and get insight, then doing core four, which sets up the day.

And this all was extremely helpful these habits that were established in my life.

But when I look at them from a systems point of view, what is interesting is essential, these habits are systems that have been done so many times that the requirement for the instructions, has fallen away, that's essentially when I show up in the morning and bring up the attack with a stack app, I have been through all of them.

Quite a lot of times, at least on the power front, that I've been through mega stacks, something like 223 times I've been through angry stacks, 300 plus times gratitude stacks, 400 times, happy stacks, I'm working towards 200.

I think I'm about 115.

At the moment, I've been through these systems so many times that it's relatively smooth, and I don't need the instruction manual.

So I'll go open and start.

And this is essentially the way that I start every day.

And I have you can track like that software will give you a streak.

I think I'm at like 587, something like that.

It's a lot.

I've been doing this every day for the last year and a half or so that system has transitioned to habit.

And this is extremely useful in a lot of ways.

Like I don't need to look at the instruction and go, Oh, gee, what's next? And there's actually a lot of benefits from being so ingrained in these habits is like, okay, my brain knows what's coming.

Next, there's less of a or what is this question that I'm being asked versus, okay, just the downloading of the information that needs to come out and the insights that I need to get from that tool.

So, at its core, though, these habits are systems that have just been done so many times, I don't need to think about them.

So there are probably a bunch of things in your life that are habitual their systems that you don't need to think about, we talked in one of the other Facebook Lives about the dishwasher not being emptied.

And it's like, okay, this system is empty the dishwasher when it's done so that when we start loading it, we know that they're all dirty, there's not a documented system for this in my family, there probably could be and probably would be beneficial to review and say, Hey, this is how we unload the dishwasher.

It's a very simple example.

But there are three occasions that I wanted to discuss where systems that are documented are extremely helpful.

The first off is when there's irregular usage of a system.

Like if you're only coming to a system once every 10 days, once every three months, once every whenever it is, it's like, well, what am I doing? Again, this is not a habit system where you can just run without the instructions, you can, but the likelihood of error is the likelihood of taking a lot more time to find the instructions to go Oh, where is it again? Oh, there were some changes that need to be made.

I can't really remember that.

I hope that this is okay.

And so errors and time are both a problem when systems are not documented and they are used irregularly.

The second time is when they're complex.

So I was on a Kajabi hero forum and someone asked how to set up a deadline funnel using Kajabi.

And I like ran them through it and when I ran through it, I realized that this to Zapier is there are two forms, there's tag two tags, one to start and one to end the email sequence, this type form and then there's the deadline funnel setup itself, like even though that He only needed to be done once in order to set it up.

There's quite a lot of steps in there, where the company Flexity if you don't get it right, if the tag isn't set up correctly, or the forms not set up correctly, or the Zapier is not set up correctly, then there are errors.

And all of those areas take time to fix.

But if it's written down, and you just can pull out the standard operating procedure for this and go to Okay, great, I need to forms here, I need tags here, I need deadline funnel here.

Any emails here, I need links here, I need to insert the time is here.

If you can get all of those things done that what might take maybe two days can be reduced down to three hours.

If you've got the instructions, as I give you the analogy, it's a lot like trying to build Lego when you have the instructions.

And when you don't, that the Lego building experience without the instructions is pretty difficult.

The Lego building experience with the instructions is generally pretty reasonable.

Like they've actually mastered instructions, like if there's one company that has mastered the deployment of instructions to ensure that if you follow step after step after step, you will end up with that Lego model.

And I said three.

So the third one is where there are other people involved.

So if you're in a business, and you've got a team and you're working with other team members, if you guys don't know what each one is working on, or who's assigned what, or, Hey, I thought you had this, but you don't or what's going on, then this is obviously very difficult as well.

So even though it might be a relatively simple task, if there are other people and people involved in it, then this is where you need some way of knowing that those instructions are being worked on to create something or deploy something in the business.

And if that's missing, or someone in the team doesn't know that they've been in signed work, and they're like, oh, no, I didn't know it.

So that all have consequences in the way that they plan their day, how they assign what's important, what's not.

So there are three situations where habits that are not really appropriate habits are systems that have been done so many times over and over and over.

You don't need to have the instructions, but where do you need systems, you need systems on those three occasions.

One, it's complex.

Number two, you're coming to a system at an irregular timeframe.

Number three, where there are other people involved.

If this is a helpful conversation for you, you're like, oh my goodness, I know that I need to get my systems and processes on point.

Then head over to System IO dot Dev.

Then you can put in your name put in your email address and run through some ideas about how you can approach getting systems on point for your business so that you can actually benefit from making more money in your business and also hopefully having more time for yourself and for your family.

Alright, so head over to System IO dot Dev and go get that training.

Thanks for tuning in today.

Look forward to seeing you on another Facebook live pretty soon.