How systems decrease errors...

How do systems decrease error? Like this is one of the significant benefits of a system or in a business multiple systems that they significantly decrease error rates.

Because when you have errors, then this cost you money, this cost you time this cost you headaches, it's cost you profit this is all very not good things to have.

And so, you might wonder, well, how is it that systems do actually decrease errors? Well, let's, let's have a look at what a system is, essentially, a system is a series of defined actions or defined processes that get done.

And out of that work comes a set of results.

And you bind that whole thing up.

And that is a system a system is made up of the actions, and it's made up of the results of those actions, you can think of it like a recipe, a recipe is a very clear example of a system, basically, you get a bunch of ingredients, you do a bunch of things to them, and outcomes a completed meal.

This is much the same as business systems, except you got a few more challenges.

Often in business, you'll have multiple people working on a system.

And people will also be working on multiple systems themselves.

The imagine this kitchen that instead of having one meal, or one, one recipe that was being followed that there was was 12 recipes, and everyone's involved in all of them, this is a significantly more difficult situation to handle.

Now imagine that you took away all the recipes and just kind of said vaguely about what kind of outcomes you would want.

Now you've got a recipe for one thing, and that is errors.

So how, with that analogy, how would you limit the number of errors? Well, first of all, we really good if everyone knew what the instructions were, they could look and say, hey, I can see these instructions, I can see these actions that have to be done.

And they knew what results were coming out of them.

Next up, if they could know which steps they're responsible for, and they could see which other team members are doing other steps, then that's going to significantly help them as well, they're going to be able to know what's to come later, or what's already be done.

They can see what works happening by their colleagues.

And they can make adjustments, they can say, hey, you're falling behind with this recipe over here, I'm going to come across and help you there.

But this requires them to have the instructions to know what they're actually producing and use the right recipes.

I want to bring this awareness to you that your error rate with systems will not go down if you have documented systems.

So you've written out the action steps and you've got the results.

But no one can find them, no one can use them.

This is a significant problem.

It's almost the same as if you didn't have them at all, or that you had documented them and then not kept them up to date.

All three of these situations, no documentation out of date, document documentation, and documentation that people don't use lead to the same thing, which is a massive increase in errors.

So your real challenge is, first of all, knowing what a system is and how to build them.

And then your second challenge is getting your team to consistently use them.

My advice on this, is you have to make it easier for them to use the systems than to not to that they have to be able to easily and quickly go yep, that's the system that we need.

That's the results that we're after deploying that system and then just executing it.

And that has to be done in a way that is easier than them trying to work out or remember how to get those results just by problem-solving or just from memory.

You got to make it easier for your teams to use your systems than not to and when you do that, suddenly your error rate is going to significantly decline.

That's all I got for you today.

Hope you got a lot of value out of it.

I hope you're getting your business system as dialed in the advantages are significant.

It means that your error rate is down that your productivity is up you need fewer people to do more work.

And at the end of the day, you are more profitable.

Alright, thanks so much for tuning in.

I look forward to seeing the next episode's continuous journey into power systems create results.

See you then.