top of page

On Learning As You Go and Failing Forward

  • Stuart
  • Mar 24
  • 3 min read

I’ve been thinking a lot about what it actually means to “know what you’re doing.”


Because right now… I don’t.


Not fully.


Not in the way I thought I would by this stage.


When I first started, I had this idea that clarity would come early.


That I’d research enough, plan enough, prepare enough-

and eventually reach a point where things just clicked.


Where I’d feel ready.


Where I’d feel like I understood the process.


That hasn’t happened.


Instead, what’s actually happened is this:


I’ve been learning in motion.


Figuring things out while doing them.

Understanding things after I’ve already started.

Making decisions without having the full picture.


And if I’m honest, that’s been uncomfortable.


Because there’s a certain security in knowing.


In having a plan that feels complete.


In feeling like you’re moving correctly.


But building something from scratch doesn’t really work like that.


There is no complete picture at the start.


Just pieces.


And you only start to see how they fit together once you’re already moving.


That’s where the idea of “failing forward” has started to make sense to me.


Not as a cliché.


But as a reality.


Because I’ve made mistakes already.


Small ones.

Some avoidable.

Some I couldn’t have predicted.


Moments where I realised I misunderstood something.

Or approached something the wrong way.

Or simply didn’t know enough yet.


And every time it happens, there’s that initial reaction:


I should’ve known this.


But the truth is- I couldn’t have.


Not without going through it.


That’s the part no one really emphasises enough.


You don’t learn everything before you begin.


You learn because you begin.


And that doesn’t mean research isn’t important.


It is.


Actually, it’s been one of the most valuable parts of this process.


Listening to people who have done this before.

Reading about what worked- and more importantly, what didn’t.

Understanding patterns.

Seeing where others struggled.


That kind of learning gives you a blueprint.


Not a guarantee.


But a direction.


It helps you avoid certain mistakes.


Or at least recognise them faster when they start to appear.


But even with that blueprint…


you still have to walk your own version of it.


Because no amount of research fully prepares you for execution.


For the moment where it’s no longer theoretical.


Where it’s your decision.

Your timing.

Your responsibility.


That’s where real learning happens.


And I’m starting to see that failure- or what feels like failure-

isn’t something to avoid completely.


It’s something to move through.


Not recklessly.


But without expecting perfection.


Because every mistake has carried something useful.


Clarity.

Adjustment.

Awareness.


Things I wouldn’t have gained if everything had gone smoothly.


There’s also something grounding about realising:


Everyone who looks like they know what they’re doing…


learned like this too.


Not all at once.


Not perfectly.


But step by step.


Mistake by mistake.


We just don’t always see that part.


So now, I’m trying to shift how I see this phase.


Not as a lack of knowledge.


But as an active process of building it.


Learning as I go.


Failing forward.


Refining as I move.


It’s slower than I expected.


Less polished than I imagined.


But it feels real.


And maybe that’s more important.


Because I’m not just learning what to do.


I’m learning how to think.


How to adapt.

How to recover.

How to keep moving even when things don’t go as planned.


That’s the part that stays.


Heavy Days reminder:


You don’t need to know everything to start.


You just need to be willing to learn along the way.


Research gives you direction.


Mistakes give you understanding.


And both are necessary.


So if you feel like you’re figuring it out as you go…


you are.


And that doesn’t mean you’re behind.


It means you’re building.


“This is heavy. But I’m still here.”


And right now, that’s enough.

Comments


bottom of page