She left for Google but what else did she take with her?

All right, how are you doing there? My name is Tom Rolley of System IO.

And I was on a business call this morning with a couple of my brothers out of Wake Up Warrior.

And this issue came up, He was a very interesting issue, most of them in heavy entrepreneurs, running businesses, and I'm really big into systems and processes.

And some of them are just like, Man, how can you be so excited about this stuff? Like, where's the benefit, this is not entrepreneurial.

This is not the creative experience like this is the boring grind part of the business.

But a situation occurred where it was like, Hey, this is why systems and processes in your business actually make a massive difference.

And that is that one of the men had a team member, poached by Google, not poached, but they were recruited by Google, they got hired by Google.

And they're like, look, love the company.

But hey, I'm out of here.

I'm making a move for it, I'm going to make a move for Google.

And he's like, cool, okay, I get it.

I get but He was like, You know what, I'm not really into these systems and processes.

And so when she left, guess what happened? Like everything that she had learned and improved and discovered, all of those things also went with her straight out the door.

And I suppose like, He could call her up and say, hey, you know, what was one or two of the big breakthroughs that you had.

And she might remember those, perhaps, but any small breakthroughs, any small improvements, and most likely, the big ones to all go out the door with her, like, literally just leave her to leave with her.

Like, as she leaves, nothing gets left in that business like it, essentially, He was purely paying for her to do the work.

And what I want to let you know is that there was a way there would have been away if He was more into systems and processes.

And she actually updated or improved or tweaked the processes for her role that when she left, there was actually a legacy of investment.

And a small portion of that hourly money that went into her day into her payment into her wage actually ended up as an asset in the business.

And it might have been only 1% or 2%, maybe 5% of this money of the hour, let's say that she was getting paid 20 bucks now, just for ease of numbers, and it's 5%.

So that's going to be what about $1 $1 an hour, actually made it into the business as a long-term investment into an asset, called the systems and processes.

And this is actually pretty critical.

This has some serious effects on the long term business, not so much in the day to day might not notice it very much.

But in the long term, particularly if there's a culture where this is the default behavior where everybody knows that their life gets better by using systems and processes.

But also, the business gets better as a whole, it becomes more valuable, because people are actually doing this on a consistent basis.

And so she leaves.

And he's now stuck in this interesting position, which is, hey, I'm not into systems and processes.

So the next hire for that person coming on to replace this girl that left for Google, guesses what the onboarding experience is less effective, He has to manually teach her like in terms of doing guide her and say, Hey, this is how the job is it has to be done by voice by teaching, which is okay.

It's great.

But it's slow, and it doesn't scale.

And also, it means that the handover is slow.

It's like, Oh, where are these people up to? Where was this work? When, when that employee left when that team member left, the handover to the new team members is poorer, because there's going to be less documentation? It's like, well when she keeps her files, I don't really know we didn't have a place for those.

And just like the laundry example, from yesterday, it's like, Oh, why was she keeping the laundry in the kitchen? And those files might even be on her computer.

And it's like, man, you got our files for the business on your personal computer.

I mean, I haven't backed up because not in the cloud.

Like, this is not this may or may not be happening.

Hopefully, they're in the cloud, so that the files are available, but it could be that there was stuff left on her desktop that you didn't routinely have uploaded to the cloud.

And so, Therefore, that stuff also went out the window.

So not only the learnings and the discoveries and the improvements not getting translated into process documentation for the next team member, but also there could well have been actual work that went out.

And now perhaps he's got to chase up.

It's like, oh, by the way, I know you haven't worked here for three weeks.

But we're missing the client file.

Do you happen to have it? I mean, it's an awkward conversation to have, it's no big deal, it can easily be done.

But nonetheless, it represents, once again, the issue of a business that is not taking systems and processes to see their true potential, their true value, like why would someone be excited about it, because it means that business can grow that business can actually have more people come on, and it thrives.

And if it's competing against a competitor that is disorganized and does not value systems and processes, then it will have a strategic advantage.

And that $1 per hour out of the payment for their wage actually goes into building a business that can grow faster and stronger, because this is the culture.

And so that really is the lesson that your team is not just doing the work that you pay them for each day, but they are in a small way contributing to building the asset of the business that is the systems and processes.

So look, if this is something that you know, is an important issue for you, and you're like, you know what, I get that this is important, I get that I should have systems and processes, but either you've read the books, and they haven't led you to like, oh my goodness, how do I actually do this? Or you're just like, I have no time I have so many fires going on that if I pull my attention away from dealing with the day-to-day fires, then there will be no good there will be no business like we're running on the edge.

And we need to get this on point.

If you've got something for me.

This is you then you need to head over to System IO dot def pop in your name, pop in your email address, and it will take you through to training that will help you look at this systems issue.

See how critical it is not just in the short term for putting out the fires but also the long term benefits to your business for you to scale beyond one to 3 million in revenue way up to however how you want to go.

Alright, that's all I got for you today.

I hope you have an awesome day.

I'll catch you soon.

Bye.