Does SYSTEMology Work With Small Teams?

Does systemology work for small teams? And I think there's a little bit of confusion for this. It's kind of like the same question is almost like, does Systemology like the actual seven stage process work for a consultant, let's say. And I think some of this confusion comes from, you know, in the book, I think it's within the first chapter. I talk about when is the right time to systemize. And I say you've got a small team, you know, maybe you've got five or more staff, you've been in business for a while, you've already got traction and that's the ideal scenario. So now people go, oh, okay, does that mean that systemology doesn't work for consultants or people with smaller businesses? And it was more so me identifying who is my perfect fit target audience and what this message was initially written for. That doesn't mean that a lot of the principles don't apply. You just need to know where the tweaks are. So for example, if you're just a consultant and it's just you or you've got a virtual assistant or something like that, there's no need to over document. You don't need to write lengthy how to processes for every facet of your business. Try and start more high level using checklists, making sure that you record videos of you doing certain tasks. But don't get caught up in the detailed, time consuming process of actually documenting the process. But I actually feel like it's important that you as a consultant demonstrate, you know, that you, that you follow your own advice. Like oftentimes a consultant and a coach. And I see this with business coaches all the time, they will preach the benefits of and virtues of systems and they'll say you need business systems in your business. And you know that. Preach it, preach it, preach it. But then you look under the hood of their own business and they've got extremely poor or non existing systems. And I think you want to be the best example of what it is that you teach. So just as long as you simplify what it is that you're capturing, but you still want to bake systems thinking into your business. It's part of the culture, it's a cultural thing. So then when you hire a va, they kind of already know, oh, you know, Joe already has a way of doing this, Ray, or as in they already have a way of doing things. Like my suggestion would be go, you know, when you go through Systemology, create your own critical client flow, then start to record videos for those and then at Some point, as you get busier, you might hire a virtual assistant, get them to read system ology, run through the steps, and then start to watch the videos that you've recorded and have them do the documentation. I've got a great little story of that. There's a guy, Dan Lenny, is a videographer. He's actually just gone through the Systemology certification program as well. But what he does is he helps videographers like he's a videographer coach, basically. And he started off by systemizing himself. That's how he came across Systemology. He applied it to his own business, got an amazing result, and then has now gone on to get certified. But he first wanted to do it himself, and that's what he did. He. He recorded everything. He used loom videos and literally recorded all parts of his business. How he's handling an inquiry, what is the email template that he sends to a client, how he gets them to fill out a questionnaire, how he's onboarding them, what is first covered in those first couple of meetings. And he just recorded loads of videos, put it into a system hub or just like a central location. And then he hired a VA and then had the VA read Systemology, go through some of the training, and then basically did all of the documentation. And I feel like that's a big hack for a lot of consultants that I think would be worthy and enables you to then lead by example.