Thomas Rolley 00:00
To create the template or just get it done was a problem that I was facing today.
And it's a tough call; it's literally a tough call; you might have faced this before; you might not even consider it the decision.
And if you don't consider this decision, or then you, by default, just go ahead and get it done.
The particular situation was for an application funnel.
So if you've been through DotcomSecrets, then you will recognize the application funnel; typically, it looks something like an opt-in and then some content.
And then there's an application when the application is come through; it's decided yes or no.
And then you schedule the call, or the person schedules a call with you to have a phone call about the item for sale, it's typically for high ticket items, something over 5000 up to 25,000 100,000, whatever the amount is, but this is a very powerful funnel.
And I had the choice I do; I'm aware that, hey, I've often got that choice between making the template and then having that template be able to be used over and over again and also shared with others.
So they don't have to go through the work.
Or I just get it done, which is quicker.
In the short term, it's quicker in the short term, just to get it done.
But its longer-term value is less now short; you could take that completed thing that's done in this, taste the copy for the application funnel, and then reverse engineer it and go and drop in all the blanks of the various bits that make up that application funnel.
But the downside of doing that is that you don't get the run-through; you don't get the actual testing.
You see, when I make a template first, or we make the template first, then there's the opportunity to test it and see whether it actually works.
You see, when you do the work first, then reverse engineer it, you may run into an interesting problem.
And that is that you think that it works, I think that it works.
But in actual fact, it doesn't.
And this might be perhaps the highest value for doing it as the template first.
First of all, I want you to take that you have a choice in virtually all of the work that you do.
There will be a template that you can use; we can use templates and get work done quickly.
If there is no template, then you'll have this choice.
Do I make the template? Or do I do the work? And when we choose to do the template, it's slower upfront.
But in the long term, it's far more powerful.
Not only every time that we do work again will it actually function quicker.
But also, it is shareable.
So I'd like to consider a change in mindset, that we begin to at least ask the question, should this be done as a template? And then you might have a little subsequent challenge.
And that is, well, hang on.
We've got these templates; how do we use them.
And what I want you to consider what I would do is that those templates go in processes that there's documented usage, and it says, Open this template, copy this template, and then stick the template into your project management system as the copy and then you will have your clean templates.
And you will have copied it so that it can be used.
This is a very powerful methodology, a powerful principle of systems in general, that you want to copy things to use them.
That's all I got for you today.
A little question mark, should we do templates or should we do the work? I hope you got a lot of value out of it if you need help around systems, processes and templates to get what you really want, which is results head over systemio.dev look forward to seeing you on tomorrow's episodes.
We continue this journey into the power of systems to create results and create what we want, which is results.
I look forward to seeing you then.
