Two approaches to onboarding new team

All right, welcome to today's episode, I want to look at two very different approaches to onboarding.

So let's say that you have successfully hired a new team member, they've been through some kind of process, whether it was a group interview or single interviews, whether there were challenges, or however you got to the hire.

And now they are beginning their first couple of days with your business.

Now, there are two extremes of how to do this.

One is that the new hire perhaps learns by osmosis that they watch an existing team member do the work and go through the training that way.

And then as they watch them, they begin to become skilled enough to do what the other person was doing.

And slowly over time, they learn all of the skills.

The other alternative, which I significantly prefer, is that they're deployed on systems, they're basically plugged into a system and they run that system.

Now, with any luck, or perhaps excellent structure, you will have set up your systems the same way.

And so once they've learned that first system, then they can go and deploy any system in your business.

And so these two models are very different, very different.

In the first one in the copy what other people are doing well, you need someone who's already doing that work, first of all, and that could be difficult if you're a very small business, and it's only you and they're copying you.

And they've got questions, and they come and ask you and they forget stuff.

And that's going to happen whenever you are onboarding, new as the business owner can never really be sure what has been passed on whether they're competent.

And most likely, you will only find out that their skill sets are limited.

When problems arise.

Let's go over to the other method, you go the system new hopefully have run that many times, and it is in good condition.

This enables you to know that if the result that the system is designed to get was achieved by your new hire, then they have at least once successfully deployed that system.

And they can continue to do this over and over.

And you will know that they can follow the instructions.

Now as they get better with systems, they could actually start to improve them and build them up for you.

And suddenly you actually have a team member that is building a critical asset in your business, because realize that all of the systems that run your business are a very powerful asset in your business.

So that's the choice that you've got.

The disadvantage of the second one is that well, you have to have some systems, you have to have some documentation.

And what I discovered is that it is extremely effective at exposing systems that are not up to scratch.

My new hire came back to me said Tom, hey, 6-412 Not so good.

Not so good.

Seems outdated.

What had happened was twofold.

Number one, it was designed for me.

So when I'm using my own computer, I had some issues where I was like, oh, I'm going to solve it this way.

But my new VA doesn't have that same system.

And so that system broke.

When it went to him.

He's like, hey, this doesn't work.

And I was like, Oh my goodness.

Okay, let's, let's fix it.

The second thing that happened was that I had been neglectful in updating my own system.

And so some of the parts of it had fallen away.

This was rectifiable it was like, Okay, I have I've done so much system building now that I went in and basically ran the system to improve systems.

It's called Success 603 system to modify or improve systems.

And it was wonderful, I taped it and so He could see how I was thinking and all the intricacies and oh, that's how that fits in.

It's kind of like solving Rubik's Cube once you know how to do it.

It's relatively easy to solve a Rubik's Cube.

There are only eight processes It doesn't matter what the beginning one is because it always begins with making a daisy.

From there, you just proceed through the white cross solve the first layer, solve the second layer, yellow cross, and then there are three more processes at the end to finish off and you will end up with a solved cube every time.

This is it.

helpful, yes, you will most likely need some instruction at the beginning.

It's a bit like learning to surf or learning to play tennis or learning to play golf, or really learning pretty much anything.

There is a learning curve to learning how to build systems and run systems.

But once you've got it, you're good to go.

In fact, I call the system to build systems, the holy grail of business.

And the reason for that is that it allows you to build whatever systems that you need in your business, it also allows you to improve them and change them and modify them.

In case you find yourself in the situation that I did that I had let a system learn the decay as they will do if they are not updated.

And yet the requirement for me to go in and fix it, it took about 40 minutes for me to get it up to a pretty nice standard.

I was pretty, I was really happy with this system like oh, that's dialed that is significantly better than it was before.

And my suspicion is that it's close to 95 96% to optimize.

There might be a few little tweaks here and there.

But from now on, I could take that system to a brand new hire an additional team member and say, Hey, run this.

And I know that if they produce the five results that the system produces, and they match up to what I expect them to be, then we're good to go.

Alright, that is all I got for you tonight.

I hope you found that interesting.

If you have a choice between the two then the significant advantages lie in training with systems.

It is a very powerful methodology and overcomes many of the difficulties of the traditional learn by osmosis method.

If you want some help setting up your systems head over to systemio.dev.

Thanks for tuning in today as we continue to explore the power of systems to create results.

I'll see you again very soon.