The short answer is “no” – founders don’t need to know everything (and trying to will break your business)!
If you’re a first-time founder, you’ve probably felt it: the weird pressure to be the person with all the answers. The one who’s meant to know finance and marketing and sales and tech and hiring and legal and compliance… all while keeping the lights on and customers happy.
In a conversation between Jon and Andrew, they both land on the same point from two very different angles: a founder should never expect (or be expected) to “know everything about everything”. And when they try, it usually ends in one of two ways: the business suffers, or the founder does.
Let’s unpack the stories and the practical lessons for anyone building a business for the first time.
Two founders, same trap, two different crashes
1) The “fountain of knowledge” founder (and the slow-motion collapse)
Andrew started with a flashback to a start-up where the CEO was young, confident, and completely convinced he was the smartest person in every room. He had hired capable people around him: operations, IT, marketing, finance, sales, but then spent his time telling them how to do their jobs, as if he personally knew each discipline inside out.
Andrew described him as believing he was the “fountain of knowledge” in the organisation.
That sort of founder often looks “strong” from a distance. They speak well, pitch confidently, and can even raise money early on, especially from friends and family. But Jon makes a sharp point: a business only improves if it’s absorbing learning and feedback. If a founder blocks that, the company becomes constrained. It can’t mature into a well-run operation because it refuses to evolve.
What happened in Andrew’s story is brutal: despite having a good idea, the founder burned through two friends-and-family rounds, including family members cashing in pension pots, and the company collapsed before earning any real revenue.
It’s tempting to think this is an “attitude problem”, but it’s also a systems problem. When a founder acts like they know everything:
- Experts stop contributing (because what’s the point?)
- Good people leave (quietly at first, then suddenly)
- Mistakes compound (finance, compliance, delivery, hiring: something eventually bites)
- Accountability becomes blame (“everyone else messed up”)
Jon’s view is that you can get “some distance” before things go wrong, but at some point they catch up, especially as complexity increases with growth.
2) The founder who knew he didn’t know (and still broke)
Then Andrew shared a second founder story that sounds totally different: until you realise it’s the same trap wearing a nicer outfit.
This founder didn’t think he knew everything. He knew there were gaps. But he believed his team expected him to have all the answers. So whenever someone brought him a problem: legal, marketing, tech, sales, he’d take it on himself, go off and research, find solutions, and carry the whole thing.
Over time, it turned into 24/7 work, huge stress, and eventually a full mental breakdown and family strain.
This is the version that catches a lot of good, conscientious founders. The ones who care. The ones who don’t want to let anyone down.
And it’s a misunderstanding: leading a business is not sitting an exam. You don’t get graded on whether you already know everything. You get results by building the ability to learn fast, decide well, and use other people’s expertise.
What founders are actually responsible for
Here’s the mindset shift that sits underneath the whole conversation:
Your job isn’t to know everything. Your job is to make sure everything important gets known, by the right people, at the right time.
That might sound like wordplay, but it changes how you behave day-to-day.
A founder is responsible for:
- Direction: what are we building, for whom, and why?
- Priorities: what matters now vs later?
- Standards: what “good” looks like (quality, ethics, customer care)
- Resourcing: who do we need (hire/contract/adviser) and what can we afford?
- Decisions: making calls when there’s uncertainty
- Culture: whether people feel safe to speak up, challenge ideas, and do their best work
Notice what’s not on that list: “personally solve every specialist problem”.
The “monkey on your back” rule for delegation
Jon brough in one of the most practical images you can use as a founder: the “monkey” metaphor from The One Minute Manager.
When someone walks into your office and hands you a problem, it’s like they’re trying to move a monkey off their back and onto yours. If you accept it, now you have to feed it, clean up after it, train it, worry about it constantly.
Take on enough of those monkeys and you collapse under the weight.
So what do you do instead?
You don’t dismiss the problem. You don’t pretend it isn’t real. You do this:
- Acknowledge it
“You’re right, that is a problem.” - Assign ownership (not blame)
“You need to own solving this.” - Support without swallowing it
“I’ll give input, we’ll bring in an expert if needed, but you coordinate it and bring options.”
This protects the founder’s time and sanity and gives your team real responsibility. Jon points out that he tries to ensure he’s not on the critical path for key delivery work: he’s involved, but the business doesn’t grind to a halt if he’s unavailable.
That’s not “hands-off leadership”. It’s building a company that can actually scale.
“Don’t buy a dog and bark yourself”
Andrew dropped a blunt line that every first-time founder should write on a sticky note: “You don’t buy a dog and bark yourself.”
In plain English: if you’ve hired smart people, let them do the thing you hired them for.
If you’re overriding them constantly, you’re paying twice:
- paying their salary/fee, and
- paying for the delays, mistakes, and frustration caused by micromanagement.
And you’ll lose them anyway!
Why “I don’t know” is a leadership skill
For many founders, saying “I don’t know” feels risky. It can sound like weakness. But the conversation makes the opposite case: “I don’t know” is often the start of good leadership.
Try these founder-safe versions:
- “I don’t know yet, let’s find out.”
- “Good question, who’s best placed to answer that?”
- “I’m not the expert here. What are our options?”
- “Let’s get proper advice before we decide.”
This does two things:
- it keeps you honest (no confident guessing in areas like compliance or finance), and
- it builds a culture where people bring facts and options, not just panic.
Your secret weapon: advisers, non-execs, and founder communities
Andrew also touched on something a lot of early-stage founders underuse: support structures outside the company.
Non-execs and advisers
If you have investors or a board, don’t treat them like decoration. The point isn’t just governance on paper. It’s guidance, pattern recognition, and judgement that you don’t yet have.
A good adviser/non-exec can:
- spot “this will bite you later” issues early
- pressure-test your assumptions
- help you hire better, faster
- bring calm when you’re emotionally attached to the plan
Founder communities
Andrew’s advice is simple: look locally or online for other founders. Most of them have already hit the exact wall you’re heading towards. And they’ll often share what they learned, because they remember what it felt like to do it the first time.
It’s not a weakness to ask for help. It’s competence.
A quick self-check for founders: are you acting like you must know everything?
If any of these sound familiar, you’re drifting into the danger zone:
- You’re the bottleneck for every decision.
- People bring you problems without suggestions.
- You redo your team’s work “to make it right”.
- You feel guilty if you don’t have an answer immediately.
- You’re working longer hours but getting less done.
- You’re quietly scared the business falls apart without you.
Pick one fix to start with this week:
- Rule: “Bring me the problem and your recommended options.”
- Habit: Before you accept a task, ask: “Is this my monkey?”
- System: Weekly check-in where each team lead owns their top risks and next actions.
- Support: Book one call with an accountant/lawyer/specialist for the issue you keep avoiding.
- Community: Join one founder group and ask one honest question.
Small moves. Big relief.
The bottom line
A founder who pretends to know everything will eventually damage the business (and often the people around them). A founder who believes they must know everything will eventually damage themselves.
The healthier, more effective path is the same in both cases:
Be confident enough to lead, humble enough to learn, and structured enough to share ownership.
You’re not the fountain of knowledge.
You’re the person building the system that makes knowledge, decisions, and progress possible.
(If watching or listening is more your thing, this article is a summary of the full discussion available on YouTube below).
