Variable results are a consistent outcome!

Alright, so I had an interesting situation this morning, we have an Airbnb, on our property.

It's a two-bedroom, one bathroom, cottage, and it's on our property where it got two acres here in the broken head.

It's been on Airbnb maybe for two or three years.

And it has been a wonderful benefit.

But the downside is that Airbnbs take work.

They take effort to maintain, they take effort to make sure that the sheets changed that the house is cleaned all of these things that go into maintaining and running Airbnb.

And that's just the physical side of it.

Obviously, there's all of the messaging and the booking and all of that kind of stuff as well.

So there's quite a bit of work that goes into this, Airbnb.

And this can be outsourced this could be got rid of, but for whatever reason, right now we are doing it.

Well, my wife, Leslie is doing it.

And so we had a small situation this morning, she goes down there, and there is a problem, the outside of the house has not been dealt with.

She didn't know about this.

And so she kind of was a bit frustrated.

In fact, she was frustrated by this.

She's like, how did this happen? Why did this happen? And she went to a place which was like, well, it's their fault.

It's the cleaner’s fault.

And the advantage of this is that she gets to say, hey, it's somebody else's problem.

It's somebody else that is responsible for this outcome.

And to a degree, yeah, sure.

The outside was missed.

But the higher calling is that if she was able to take responsibility for it herself and say, you know, what, this should have been handled, and the person that is responsible for that, ultimately, is me.

And if she'd been able to do that, then it opens up for a question.

It's like, why did that result happen in the first place? Because I guarantee that while it was this time, it was the outside that wasn't handled, like there'll be little pieces that get missed each time, like whether the fan got forgotten to test or whether the remote controls didn't go back to their spot, or a wineglass got broken, and it didn't get picked up.

And the reason for this is that all of these behaviors, this cleaning behavior is managed, in someone's head, it's done as an initial training experience.

Here, this is how we do this work.

And then it's kind of like, okay, well, you know how to do it, the CCleaner knows how to do it, you go ahead and do it.

But there's no checklist to check off and say, Hey, have all these things been dealt with.

And so what happens is that there's a situation that arises where the work was not done correctly.

And so the outcome of all of this is variable results like I cannot go down there and be sure that everything's been dealt with.

This is a variable outcome, like a variable outcome, a variable result is a consistent outcome.

A variable result is a consistent outcome, a variable result, like it's not done to spec every time is the consistent outcome.

And what has to change in that is that the background system, like realize that they use a system of some sort being run here.

It's largely in my wife's head, and our cleaner’s head, and they kind of go through, but there's no documentation, there's no checklist, there's no process to ensure that everything's handled.

And so the easiest system, it's just a virtual system, or it's a system in people's heads, instead of being written down.

And so the transition, first of all, is to recognize that these variable results have a consistent outcome.

And then to take ownership and say, you know, what, I don't want variable results, I want a consistent result.

And therefore, something has to change.

Someone's got to change, because if nothing changes, guess what, it's going to continue to be that variable result.

So let's say then there's a responsibility piece that comes in, alright.

I'm responsible for getting this system to do what? What's got to change in the system? Well, I want to suggest to you that one of the first steps could be to bring that system out of the background, out of people's heads and into some kind of documentation, some kind of checklist and this could be extremely simple at the beginning.

That even it was just like, hey, the outsides done the insides done.

Like that is an extremely simple checklist, you might say, Well, why would you even bother with that? Because from that, if the system gets used, it can be improved.

And it's like the next time they go through, they can go through and go, Okay, barbecue clean outside.

What does that mean? Well, that means the barbecue is cleaned, the tables cleaned, the chairs are clean, the tables that go with the little CT bits, they're in the right place, the dog bowls in the right place, check, check, check, check, check.

And suddenly, because they started with this one that said, outsides done insides done, if they're able to improve it because they used it, then that thing starts to take on an interesting characteristic, which is that it improves with time.

Now, this is not what typically happens with most standard operating procedures at all.

Even if they get done in the first place.

They decay, they entropy down and fall away.

And it's like, oh, that's not actually what we do because they're not getting used every time the work gets done.

So that is something that I want you to consider.

Consider the possibility of what happens if, in your business, the systems get used every time? What would that be worth to you? What's it costing you right now to not have your systems used, because know that you have the same situation that my wife does, there is a system being used, the fact that it's in the background, or in people's heads doesn't mean that there's no system, it just means that system is in the background has got to be brought out to the foreground in order for the outcome that's generating at the moment, which is variable results to transition to consistent results.

Alright, if you want some more help around this, if you're like, you know what, Tom, I know that this is my situation, that it's costing me big time to not have this on point then your next step is to head over to System IO dot dev that's SYSTEM io dot Dev, and pop in your name, pop in your email address to find out how you can start to address the systems issues in your business to look at what the problems you're getting, because you haven't handled this and what the possibility could be, particularly financially in terms of a profitable outcome for you to get this dealt with.

Alright, head over there now.

Thank you so much for tuning in.

Look forward to seeing you on the next Facebook Live as we continue to explore this very interesting discussion for systems and processes in business.

See you then.