David Jenyns walks through documenting business processes: start simple with an overview, steps, and attached videos, then refine based on how people actually use them. Skip flowcharts until processes stabilize. Layer in training so new users watch videos, then consult notes, while experts just scan headlines. Fold questions and edge cases back into the docs as you go.
Keep it really simple first, that's the main thing. And then if you want, over time you can get more detailed. Like your systems might evolve over time and you might start to hone them and improve them based on feedback. When you teach someone how to do something, they might have a question and then that folds back into the system and. And then you improve the system for next time. And really the way that I think about it is the first time someone is doing a task, they probably watch the video and then they look at the notes once, they've watched the video once, then next time they might, if it's the second or third time, they might just review the notes and then when they get really good at that particular task, they might just review the headlines. And then over time, sometimes it's hard to enforce even, particularly for existing team members, the exact following of a system. And that's why when you need to marry it together with a project management system where you kind of put the key milestones in the delivery of whatever that system is looking to do and then that way you assign the responsibility of those steps. But we'll talk a little bit more about that. I just kind of wanted to give you this idea that these systems will evolve over time and to keep them easy up front. The anatomy. I mean, if you just model the system for creating a system, that's fine. You'll have an overview and objective up the top. You may or may not use flowcharts. I'm not a huge fan of flowcharts because very quickly they get out of date. Usually one or two team members know how to update them and no one else. So we do use them sometimes because it gives a good snapshot and overview of what needs to be done. But I wouldn't start with flowcharts. For me, flowcharts come later. Just get the guts of it down. And then once you polish it and improve it and optimize it, then you might start to add in the flowchart. So that's when you might add in lucidcharts or whatever. You'd have the steps. Sometimes underneath those steps you'd have more detail where required. And then you would attach any videos, supporting documents, email templates and things like that all gets housed underneath that system. I'll show you inside our business to give you a little bit of an idea of the way that that that looks. But you've got the system for creating systems, so you're kind of already on the way. Another gentleman who'll be joining us.
Remember me? Subscribe To My Channel For More Free Business Systems Content 📈
