Process = Programming For The Machines

David Jenyns argues AI works best when you first document your actual business processes, then use AI to handle the repeatable parts. The systemologist's job is to capture what works, codify it, and turn it into prompts that machines can execute.
Chapters
With regards to AI, a lot of what a systemologist does, as I talked about, is capturing what currently is working in a business and it's about making it repeatable. So I see AI as not so much a replacement for team members or great staff, it's more of an accelerant. It helps people do things quicker, cheaper and to a higher quality standard. So when you work with a business owner as a systemologist and we're trying to capture current best practice, what we think about is how can we, once we capture those tasks and get them documented, how do we delegate them down so that lower cost team members can then execute on some of those tasks? There's still the element of figuring out what are the essential repeatable tasks. There's still the extraction of those systems and processes, which again can be accelerated with AI, but it's not necessarily a replacement of the systemologist. And I actually feel like systemologists will become more and more valuable as the rise of AI starts to kind of really take hold. Because when you think about it, a system or a process is ultimately going to be almost like programming for the AI. Like you think about prompt engineering and what it actually is about, you know, thinking about, well, what is it that you're asking the AI to do that is just like a recipe or a system or a process. So the systems and the processes that systemologists help to develop potentially could be the prompting for the machines that might end up executing on some of this. So I think you're kind of heading in the right direction and this idea of skating to where the puck is going to be, because systemologists will have a real solid understanding and potentially could be prompt engineers of the future because you're thinking about what is essential and what, what is repeatable and what's getting done and you're breaking it down into actionable steps that could then be executed. So I think more and more I want to start talking about that message at head office because it's, there's a lot of talk around it in business communities and people like, oh, how do I make AI useful in my business? And I want to start, you know, getting chatgpt working with me. And they're just finding busy time tasks or they're finding tasks. They might read an interesting thread on Twitter about, oh, I could get ChatGPT to do this. But they're kind of missing the point that you want to get AI executing things that you're already doing. Like, don't let AI be a distraction. Let AI help you complete what it is that you're already completing and do it faster to a better quality at a lower cost. So a systemologist is really great about kind of thinking about what those essential tasks are, the critical client flow, achieving minimum viable systems, identifying those critical systems, codifying them, and then thinking about how AI might help to execute on that. So definitely something we think about here at head Office and we'll explore a little bit more.
More from David

Remember me? Subscribe To My Channel For More Free Business Systems Content 📈









