Fail faster.

So let's talk about failing faster.

Because this is a bit awkward, it's a bit awkward to talk about failure and things that didn't work.

And having the courage to take a step into a likely failure.

This has come up for me a couple of times now.

I went ahead, and I'm like, You know what, I know how to do systems.

I'm so excited for this.

Now, many people are excited about systems, what they are excited about is about the results that come from systems, but systems themselves.

Most people like, Yeah, whatever, whatever.

But my experience was that to run good systems really take software, software, you can show you can do it with Excel boards, and word documents and cotton copy and pasting and all that sort of stuff.

But really, to have systems run smoothly, you need software.

I've never done software before.

I'm like, okay, great.

Let's go and what I thought I thought, you know, what, I'm going to be really clever, I'm going to invest in great blueprints, because these tools are available for doing this figma.

The tool is called figma.

Adobe has one as well.

And my great, let's make some great blueprints.

And I put, I think, I don't know, like 17,000 bucks into blueprints.

And then we started coding.

And I like six grand in and we've done like, three pages.

And I'm like, oh, oh, hang on.

This is like, this is suddenly turning into an $80,000 app.

My budget was 25.

And I'm like, Oh, hang on, maybe maybe I've messed this up just a little bit, perhaps, should have spent a little less on blueprints on the on the actual design.

But you know what I actually needed to do that.

I needed to have that level of design.

And the problem, just That's how much software costs.

So I quit.

I failed, didn't go anywhere.

$17,000 into designs that went nowhere.

And so I gave up I gave up for a while.

And then I had a strange thing happened in one week, I had three separate people tell me about this idea of no code software.

Might was no code.

I spoke to a buddy of mine in Sophos i Hey, Tom, you want to save $100,000? I'm like, Yeah, for sure.

It's like, check this stuff out.

And when there's no code, and I found that even with another 18,000, I think of spent on no code student get there.

I'm like, What is this, but I saw the potential in no code.

But my no code was a failure.

There was too many rules too many, too many idiosyncrasies of using no code, like no code is like the Wild West will like maybe seven years in to no code, which sounds like an incredibly long time.

But really, the number of people using is relatively small.

It's challenging.

It's curious.

It's like a, an enigma.

It's a bit like, I suppose like Bitcoin or Ethereum, maybe 10 years ago.

It's like, what's going on? And you may say, Well, Tom, why would you even give that analogy, look at where bitcoin is, look where Aetherium is, they went to boom, but no code, I think is different.

And I'm happy that I failed.

Because my next attempt is exciting.

My next attempt is, okay, what happened? Where did I end up? And I had to pay another four and a half $1,000, just to find out where the errors were.

And they're like, here it is, this is what your last team didn't understand.

And I'm like, what? And they're like, yeah, yeah, you need to work at this database level, not where they were working.

I'm like, okay, shit.

Okay, great.

This is exciting.

This is exciting to actually have that.

Turn the lights back on, car turns off the lights and a bit.

So two failures down.

So here's the question, Where would I be? If I didn't choose to fail? Wherever I choose, where would I be in? You would say, Well, Tom, you would have 39 and a half $1,000 in your pocket? And like, Yeah, that's true.

That's true.

But it also would still be exactly where I was back then.

I wouldn't know about the ability to mess up with blueprints.

I wouldn't potentially even know about no code.

But now for the grand price of $39,500.

I have learns very painful lessons about what not to do, but I am true failures closer to success.

So perhaps you're on the edge.

Perhaps you're thinking about it.

Perhaps you're like should I do something.

And if it's a calculated risk, then you should Go for it even if it's a failure because it takes you closer to success that's all I got for you thanks for tuning in today look forward to seeing you another episode as we continue this journey into the power of systems create results See you then