Batched and fast moving systems?

Alright, welcome to today's episode, I thought I would cover advanced systems because you might be thinking, gee, this is great that you've got some way of doing systems and processes, and that it might give me optics on my business.

So I can see what my team is working on if they're remote, or even if they're at the office, and you've got a large team can actually see what everyone's doing.

But does it hold up for advanced systems.

So what could be an a, an example of an advanced this one could be that got a lot of moving parts really quickly.

So something like where you've got many, many orders coming in through through the day.

And in this case, the actual to do how to do the work doesn't change much.

This is analogous to a classic kind of Henry T, Ford, industrial, make the car pipeline.

And it just like, you know what the instructions don't move, change that much.

It's like, do the same thing, do the same damn thing, do the same thing.

But what's important is speed.

And the interesting thing is that you can set up a system like this, but instead of, say, completing the system, where all the works done, it's never going to be done.

And instead, you just have to have a couple of different categories, and move them down from beginning to work on to next step to next step two done.

And this, if you moved it, instead of vertically, tweaked it horizontally, you're probably going to recognize this as combat commands, awesome.

Campaigns are awesome.

As long as the work instructions don't change much.

So that's easy to set up.

What about batched systems? Like, you know, what, man, what about if we've got a bunch of work that needs to be done at a set time, and it's repeating work, but there's a lot of details in it.

And the two examples that I'll give you for this.

So one might be a client fulfillment experience, where you're fulfilling over eight weeks or 12 weeks or six weeks, and you want to have an overview of what's going on.

And then you're going to have a particular week that covers that as well.

So that could be an example of a batched system.

Hello, Philippa.

How are you tonight telling me to say hi?

Giveaway? Yeah.

Another one, which you might recognize is that if you did a live video with random events, like my daughter coming to visit, so good to have you on the video, buddy, how are you doing tonight? Okay, nothing much to say that's okay.

Another example might be doing a live video every day.

But then you want to multiply that material, you want to spread it out across different platforms.

So this idea is sometimes called Content multiplication, content amplification, that you do the one video, and then you syndicate it out, perhaps like me, you choose to do on Facebook Live, but then you send the video to YouTube, and you send it to LinkedIn.

And then you strip out the audio and you send that to Spotify for the podcast.

And then if you're good, you can take three quotes out of it.

And actually, go ahead and make some quote cards.

And do that every day.

Now, this sounds relatively simple, like what we discussed, just say like, yeah, that's easy.

The challenge is when you've got to do it every day, and you can't backlog.

And in that case, there are significant advantages to batching.

And batching basically means that at the end of the week, you're going to take the next week to pay perhaps produce the videos and then the week after that to schedule the videos.

And then the week after that, deploy the videos.

And so there is this batch experience whereby you're taking some time to complete the smaller boards.

So each daily video would have a board and you go through and do that work, but it's significantly easier to do seven days at once.

So this would be a second example of a batched system.

So we're going to first one, which is the fulfillment of a client, and they're getting fulfilled over six weeks, eight weeks, 12 weeks, and you've got an overview board and then each level each week's board and then on the other example, you're doing a daily video, and then the syndication of that content out to other channels get scheduled out a couple of weeks time they're both batch systems.

So this essentially is not that hard as long as you get the system structure right.

If you know how to structure a system Then these, these things are just variants on that same structure, instead of a simple system that's just got a bunch of processes and a bunch of results.

These batch processes have like a high-level board and then a bunch of small ones that you just do.

And the fast-moving board that I discussed before, you just have no the basically don't apply some of the strategies, you may lose some optics, but you benefit from just speed use, like gets done.

As I said, the disadvantage of that style board is you do not want work that changes frequently.

You don't want to lose the instrument, the instructions for that change all the time.

But these is a brief discussion on advanced systems.

These are very, very doable, very, very, relatively easy once you get the understanding of how to do a simple structure.

That's all I got for you tonight.

Thanks for tuning in.

I hope you got some insights about power systems and how they can be adapted for your particular needs in your business.

If you want some help with this head over to systemio.dev.

Otherwise, I'll look forward to seeing you tomorrow as we continue to journey into the power of systems to create results.

See you then.