When do hidden processes make sense for entrepreneurs and their teams?
Welcome to today's episode, my name is Tom, really excited to talk to you about that, because most of the time we have been discussing on this podcast on this series of live videos, that the problem that you face is that your processes are hidden, that your team is working from assuming knowledge, learned knowledge, they have been receiving instructions that are passed down, they solve problems on the fly as they arise.
But they're the same problems they solve last week and the week before and three weeks before that, but every time they come and solve them, and interestingly enough, in a slightly different way, giving you the dreaded inconsistent results.
So it's been the journey that we've been discussing in this systems creating results idea that the more that you can document and bring out of the hidden realms into the scene realms, the processes, when you've got this stuff written down, suddenly, your team's going to operate more consistently, more effectively with fewer errors.
And you can do way more with way less.
So the interesting concept, then come to when would you want to keep them hidden? Would this ever make sense?
And I want to bring to your attention that there is a particular case, if you know that a system creates the desired results every time and you have documented those processes, clearly, then you may choose to make them hidden.
Because you don't want your team to even be involved in the processes, you just want them to do the work.
And you can do this with software.
So software makes sense.
Software, you might just show them, hey, do this, do this, do this.
And when those three things are done, suddenly, in the background, all of the magic happens, you know, all the automations, you know, all the documents that have got to be produced, perhaps there's software that goes out and pulls ideas from the web, or it documents research.
And it just comes out and says Now search this, search this or rewrite this or choose between this.
So this is a very linear experience where there's an input, and there's an output.
And all of the underlying processes that are going on, are hidden, you don't need your team to know about them, you just need the software to handle it.
Now, this works when a system does not change very frequently.
Because every time the system changes, that means you've got to have a software developer or somebody go in a human going and tweak the back end and fix it.
If you have things that change a lot, then you want your team to be able to do that.
And so this is not an occasion that you want software involved.
You want them to be able to edit and improve and change the processes because it needs to be editable.
The second case, where this doesn't work is that if you are not sure what those system processes are, like, what are the actual steps to get to that result, if you're not at that extremely defined level, then you're not going to do this.
But if you are, then you can literally just tell them and flash up the screen, say, hey, fill this in, do this, do this and all of the software's happening in the background, to get them through the hidden processes and get them true to that consistent result.
without them even knowing this, this is going to be a value judgment, you're going to weigh the cost of the software versus the cost of just having a team do it step by step.
In some instances where there's a lot of repetitive work or a lot of work that can go out and be done by software or computers then this may make sense the rest of the time you're going to want your processes out of the hidden realms in the same realms.
But when you have that particular instance, where you're like, you know what we know exactly what we want, we know how to do it, then your next step is to consider a software option in order to bring through that particular result without your team even needing to know what they need to do.
Alright, that's all I got for you.
So hope you're having an awesome day and enjoyed this extra episode this little hidden one, where we look at when does the hidden make sense? I look forward to seeing you tomorrow on the next episode as we continue this powerful journey into how systems create results.
I'll see you then.
