Expertise allows creativity.

Alright, thanks for joining me in this session.

Today, I'm having an interesting experience with various different forms of online storage.

So you're probably familiar with this if you're in business, but there are providers like Dropbox, and there's Google Drive, and there's a box.

And there's a bunch of these services, one drive.

And I have a client, and he's using Dropbox.

And I'm like, oh, sweet, okay, that's totally fine.

I usually deploy in Drive.

And I have deployed inbox as well.

And they all have their idiosyncrasies.

They have some interesting features.

For instance, box, we'll put one and then 10, and then 11.

And then 2345 versus Google Drive, we'll put 1-234-567-8910 1112.

And so to get around this activity, zero in front of 010203, and then the ordering became the same.

One of the challenges about Dropbox was that it actually said, Hey, you can use Word or you can use Google Docs box was totally cool.

It was like, hey, you know, we only get word.

And drive obviously doesn't have Microsoft built-in.

It's only got Google Docs, but Dropbox, in the interesting choice of said, Hey, we're cool.

If you use Microsoft Word, we're cool.

If you use Google Docs, which would you like to use?

And as I started to play with this, I found out that one of the issues is that can't use both of them.

If you open a file in Microsoft Word, that's fine.

But then if you close down opening Google Docs, and then try and go back to Word where it's like, I know it's already open.

We can't do it, because it'll get conflicted files.

It's like, Alright, sweet.

So I reached out to my phone, like, hey, what do you want to do? Do you want to use Google Docs? Or do you want to use Microsoft Word? Now? They didn't come back to me and come back to me with their decision.

I'm like, okay, great.

Is there anything that I can do? Can I begin the process of deployment? Now, the installation system for the system IO, is, as you'd expect a series of processes like do this, do this, do this.

And early in the process, it starts talking about installing folders and linking documents, but none of that's possible.

Because there's no decision on whether to use Word or Google Docs.

Not quite.

Let me rephrase that.

It is possible, obviously, to install the folders and go, Okay, great.

Here's the Folder Setup.

Here's the folder structure.

So put that in.

But the linking is very dependent on which one is chosen because the link that goes to Microsoft Word in Dropbox is different from the link that goes to Google Docs.

So I need to know that, but I was like, Okay, what am I going to do? Is there anything that I can do? And I was like, alright, well, maybe there's some separation, some ability to deploy some of these processes, but not all of them.

Because I'm waiting on that decision.

I was like, Okay, great.

So I go ahead and do what I can.

And it actually allowed me to do a bunch that I was like, Okay, great.

That's on the point that's taken care of here are the gaps that remain that aren't possible until I get that decision.

Now, what I want to share with you is that this is not possible with someone who's doing it for the first time, they will not have the capacity to see the interrelatedness or not between different processes.

So some processes can be done without this decision, but some can't.

And they might just go through and as soon as that first block comes, that says, link this document to this thing, they're like, well, we can't do it, because I don't know whether we're using Google Docs or word.

And the benefit of expertise or mastery is to like, Alright, great, I can see that we can survive without that decision.

And I can proceed with steps three, and steps five, and go ahead and get those done.

And then when that decision is made, I'm already further ahead than if I chose not to.

Now, look, I could have stopped and gone.

You know what, I'm not going to deploy this right now at all, I'm not going to install the system at all, I'm going to wait for that decision, and that contingency to be done.

But for whatever reason, I was like, Look, I want to be ahead of the game, there was a call that we had, and the timeframe for that was therefore compressed, it's like, well, this will make a difference for me if this is done.

So I went ahead.

The lesson out of all of this is that mastery allows creativity, I could proceed with the steps that could still be done.

Because I knew the whole system.

I know the whole installation.

I'm like okay, yep, we can do this.

We can do this.

We can't do this.

That doesn't happen if it's my first time through.

It actually takes experience to go through and improve and learn.

And then the creativity can come.

This is a significant benefit for when you're an entrepreneur, and you want your team to be able to both handle the first implementation of a system, and that they can go through in detail and, you know, go to this thing, and then do that, and then click this and click that.

But as they get better, and they get reps on the system, they're not going to need to look at all that fine detail.

We're extraordinarily good at learning how to do things, particularly over repetitions, and it's like, okay, great, I might just need to look at the major headings and go this, this, this, this, this, okay, great.

And if I get really good, or I'm doing a system a lot, I'm just like, Okay, I just need to know that's done.

And that's done.

And that's done and all the fine detail is taken care of.

And so a good system has to be able to handle not only a first time through but also an experienced person who's like, great, I don't need to find detail, I know how to do this.

But they still need to be able to show you as the entrepreneur where they're up to, what is the step that they're working through, even if they're not even going to that fine detail.

So this is, this is an important thing to consider when you're thinking about, hey, it's time to systematize.

What do you want what you want levels of mastery you want someone first time through can achieve it.

But you also want somebody who's done it 14 times or 28 times to be able to not have to go to that fine level of detail.

So different levels of readership, different levels of competency need to be able to be built into your systems and how you do those.

All right, if you want some help on this, if you're like, you know what, Tom, you seem like you have dialed this in.

I am at that stage, I'm doing a million-plus in revenue, or I've got 567 team members.

We're succeeding and we're starting to run into the problems of not having systems on point.

Then I invite you to head over to the www.systemio.dev and pop in your email, put any name there go watch the training that was put together.

Thanks so much for tuning in.

Look forward to seeing you on tomorrow's episode as we continue this exploration around systems and processes and the power that they have to scale your business.

See you then.