You Wouldn’t Fly a Plane… Would You?
We’ve never had more access to information.
Podcasts, YouTube channels, social media, websites, forums, well-meaning friends - all contributing to a growing sense of “I think I understand how this works.” You can learn the terminology, follow the sequence, and get a feel for what’s involved. And that’s a good thing. An informed client is a stronger client. Better questions get asked. Better decisions get made.
But it’s only part of the picture. Because knowledge is not skill.
You can read about flying a plane. You can understand lift, thrust, drag and control surfaces. You might even become quite fluent in the language of aviation. But no one - no one - wants to be on board when you attempt your first landing off the back of that reading.
Thankfully, managing a Self-Build isn’t quite as life-or-death as aviation.
But the principle still holds. There’s a meaningful difference between understanding a process and having the skill to execute it under pressure, in real time, with competing interests, and money on the line.
That gap is where experience lives.
The 10,000 Hour Idea
Malcolm Gladwell popularised the idea that mastery in complex fields requires around 10,000 hours of practice. It’s a neat concept. Memorable and reassuringly measurable.
It’s a helpful way of illustrating a point, but it’s not a magic number, and it’s often misunderstood.
Ten thousand hours of doing something badly doesn’t create expertise. It just ingrains bad habits. And crucially, not all hours are equal. An hour making decisions on a live construction project carries a very different weight to an hour reading about one.
In Self-Build terms, you don’t get your “hours” cheaply. They are accumulated through time spent making real decisions, learning what works and what doesn’t, and developing critical thinking and judgement based on feedback and outcomes.
In other words, experience built through doing, not just understanding.
Experience is Pattern Recognition Under Pressure
What an experienced Project Manager develops over those thousands of hours is something harder to define:
They see problems before they fully form.
They recognise patterns:
Spotting something that doesn’t quite add up.
Understanding the knock-on effect of a small decision.
Knowing when to push, when to pause, and when to rethink.
Recognising a design detail that looks fine on paper but won’t work on site.
Seeing a programme that is quietly slipping out of control.
Questioning a cost plan that is optimistic in all the wrong places.
It’s less about reacting to problems, and more about keeping things on track in the first place.
This is why experience is not a “nice to have”. It is a form of risk management.
So Where Does That Leave the Self-Builder?
None of this is to suggest that a Self-Builder shouldn’t be involved - quite the opposite. Your project should reflect your priorities, your decisions, your brief.
But there’s a difference between being in control and being expected to carry the full weight of delivery. When experience sits alongside you; guiding, structuring, and quietly managing risk, the project moves forward with purpose, rather than uncertainty.
You don’t need 10,000 hours to build your own home. But someone on your team probably should have them.
Bringing It Together
Self-Build is not about having all the answers from day one. It’s about embracing the process and engaging with it – supported by experienced guidance that helps you move forward with clarity and confidence.
When it comes to delivering the outcome in a way that works in practice, knowledge will help you understand what’s happening…
Skill is what ensures it goes to plan.
