How to think about systems in your business...

Well, hello and welcome to today's episode.

My name is Tom Rolley of System IO, we are talking systems frameworks.

I want to bring this up because I was asked a question, they'll tell me really into this system stuff, how do I know that you're legit.

And I'm going to give you two things.

One is, you can look at the front-end marketing of a systems business and businesses saying, Hey, we know how to do systems.

And you can look and see, because if there is a consistency that is present with their marketing, then that suggests that they have some kind of systematic approach to getting things done.

So you can go to the Cisco dot dev Facebook page, and you'll see one live video a day that I do five to 10 minutes, plus three quote cuts.

If you head over to Instagram, you'll see three quote cards.

If you go to YouTube, you'll see the edited video, if you go to Spotify, the podcast is there.

All of these things coming off this one video.

Now a day in day out, the video gets done, but it takes a system to produce the marketing assets consistently.

I have a VA that does the editing and the distribution.

And I have a copywriting team that writes the copy that takes the transcript from this video and turns it into the quote cards and the descriptions and all that kind of stuff.

So they're the two additional things.

Notice that my requirement is 10 minutes a day, I make the video, and then from that the system and the people that work those systems distribute and create the assets.

So you can look, you can go and check out somebody who's like, yeah, we know how to do systems.

It'll be obvious.

If there are gaps in their production, if it falls away, says, yeah, what's going on, you guys are saying that you know systems, but it's not really evident on your front-end marketing.

But let's go to a second one.

And let's talk systems frameworks.

When I think about systems, I've got four things that I think of, and I want you to write these down one the system to the process three, the templates, and for the assets, systems, process, templates, assets, system, process, templates, assets, you got them.

Alright, let's talk a little bit about the system.

So the system is what creates the assets, it uses processes to do that.

And some of those processes may or may not use templates, the asset can be anything, it can literally be a document, it can be the fact that the cash got moved to everyone in the team's bank accounts, it could be that the credit card got paid, it could be that the Rubik's Cube got solved, it could be that the Facebook Live got done, the quote pads got done, whatever the outcome of that system is the asset.

So that's the purpose of the system.

Let's talk about triggering systems.

So when you want to think about, hey, when is this system going to get used.

And there are three that I want you to think about one is on-demand, something happens in your business, and that requires a system to be deployed, a new client comes on or scheduled.

Scheduled means something has to happen regular daily, weekly, fortnightly, monthly, quarterly, yearly, when does this need to be done? We've covered this before.

But the idea is to put those scheduled systems into your calendar, and particularly if you know how long they take them to block out that time.

Alright, so we've got on-demand, we've got scheduled.

And then there's one more type that I want to talk to you about.

And that is a system that creates more systems.

This is an advanced concept.

And it's not somewhere that you should start.

But we were talking about the advertising and marketing creation from this video, I want to let you know that what happens on a Monday is a system runs that extracts the videos out of Facebook and creates seven smaller systems.

And those daily systems of what actually produce the video.

So you got to have this one system and its purpose is to create seven more systems.

So that is the third and final case for system deployments.

So we've got on-demand scheduled and then a like a high and a low-level board creation system.

So let's use systems.

Let's go to processes.

Processes will always be part of a system.

You don't want to have orphan processes.

You can't just if there's no There's a process without a system, it's like, well, how's that going to actually get triggered? Like, how's that going to get used? So every process must be in a system.

And a system can have one process or it can have many processes.

And that's a deeper conversation about how do you split up the work of that system into how many processes.

But nonetheless, we've got processes that sit in the system and they get executed, they get run, think of the processes like a ladder A to B, they take us from A to B, A to B, A to B commonly will be deployed sequentially 1234, it is possible that you can run processes concurrently, depending on what's going on.

All right, let's talk about templates.

Do all processes have to have a template? No.

processes can use templates, some processes will.

And when you use a template, you want to copy it and then have a fresh copy to use.

Otherwise, your template will get filled up with data.

But some processes will use templates to create the assets.

Do all processes have to have templates? No.

Do all templates need to be part of a process? Yes, just like processes need to be part of a system templates need to be part of a process.

Otherwise, you won't know where those processes where those templates get used.

So there are cascading levels here, one system, one or many processes that may or may not use one or multiple templates to create the assets.

So this is a systems framework, this is the way that you should be thinking about systems.

What's the system going to do? Why do we even have it if you have created systems for systems purpose, like for their sake, that's no good wasting your team's energy-wasting your energy, it's got to have a purpose, the system has to have a purpose, what is that purpose, it's to create something.

And that something is the asset, it doesn't have to be a tangible item doesn't have to be a doodad night, it could be just that the task got completed.

But there is an outcome that systems got.

And the way that we do that is using processes and some processes can have templates in order to create those assets.

I hope you got some idea here that this system staff is helpful in that it is systematic, that it is a way of thinking.

If you have read Sam Carpenter's book work the system you will know the system's mindset.

It's like requiring the ability to look under the hood of the car and go right the engines working the transmissions working but the air conditioners are not let’s fix the air conditioner.

And the cool thing about businesses once you get them working, you can upgrade the systems you can add on more you can bring on a second vehicle.

But it all requires you to have an understanding of systems and how to deploy them successfully in your business.

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

Number one, you can understand whether a business about systems knows what they're doing by looking at their front-end marketing.

And number two, you now have the four elements that go into all systems one system to process three templates for assets.

If you want some help for this head over to systemio.dev, as we continue this journey into the power of systems and processes to scale your business to sell at high multiples or even just go on holiday for a week or two without your business imploding.

Alright, thanks so much for joining me.

I look forward to seeing you on tomorrow's episode as we continue this journey into the understanding and power of systems.

See you then.