The Loneliest Part of Being a Founder

The Loneliest Part of Being a Founder

December 1, 2025

Founder Leadership Team Decisions People & Systems GTM Infrastructure
TL;DR — Key Takeaways
  • Founders delay hard people decisions not because they don't know what to do — but because they're carrying the weight alone and feel responsible for the outcome.
  • Keeping someone in a role where they can't succeed isn't compassionate. It's enabling failure while penalizing everyone else on the team.
  • Before making a people decision, ask whether the problem is the person — or the system they're operating in. Often it's the system.
  • There are three paths: fix the system around them, find them the right seat, or help them exit with dignity. All three require clarity first.
  • The loneliest part of being a founder isn't making hard decisions. It's the belief that you have to make them alone. You don't.

Your spouse sees you stressed but doesn't understand why you can't "just fire them." Your friends think you're the boss, so it should be easy. Your investors just want to see the numbers improve. None of them gets it.

None of them sees how this person has kids. How they just bought a house. How they try so hard but just can't seem to get there. How letting someone go feels like playing Scrooge in your own story. Maybe they were your first hire, or someone you brought over from your last company. Someone you believed in.

After 20 years of sitting across from founders during these moments, here's what's actually true: the weight isn't about them. It's about you. It's about feeling like you somehow failed them — like maybe with different training, different systems, or different leadership, they could have succeeded. And it's about wondering if you're becoming the kind of boss you swore you'd never be.

Why Founders Get Stuck on These Decisions

The delay isn't weakness. It's the natural result of carrying a decision that no one else in the organization can help you make — and not having a framework to separate what's actually happening from what you're afraid is happening.

01

Guilt Disguised as Hope

You tell yourself things might click after the holidays, after the next product update, after one more quarter. But deep down, you've known for weeks — maybe months. The delay is rarely about them. It's about you not wanting to face what you already know.

02

Confusing Loyalty With Clarity

You remember who showed up when it was hard. That loyalty is real and it matters. But holding someone in a role where they can't succeed isn't protecting them — it's enabling failure while everyone else watches and adjusts their expectations of you.

03

Not Knowing If It's Them or the System

Maybe your sales rep can't close because your messaging is unclear. Maybe your marketing lead seems ineffective because there's no real GTM strategy. The hardest part isn't making the call — it's not knowing whether you're diagnosing correctly.

What Compassion Actually Looks Like

"I kept someone six months too long because I didn't want to be heartless. Then I realized I was being cruel to them, to my team, and to myself."

They know they're struggling. They feel it every day. Your team knows too, and they're watching to see what you'll do. Keeping someone in a role where they can't succeed isn't kindness — it's a slow erosion of their dignity, your team's confidence, and your own credibility as a leader.

Sometimes the kindest thing is honesty delivered clearly and early. Sometimes it's helping them find where they can actually thrive. Both options require you to stop waiting for the situation to resolve itself.

People Problem vs. System Problem: The Distinction That Changes Everything

Before you make any decision, you have to answer one question honestly: is this a people problem or a systems problem? Because the path forward depends entirely on which one it actually is.

Failed salespeople sometimes become excellent customer success managers. Wrong role doesn't mean wrong person. But a good person in a broken system will underperform every time — and firing them without fixing the system means the next person fails for the same reason.

Three Paths — Before vs. After Clarity

Without a Diagnostic Framework

✕ Operating Without Clarity Founder delays for months, hoping things improve. Team morale erodes as high performers lose confidence in leadership. The underperformer is stressed and uncertain. Eventually a decision is forced under worse conditions.
✓ Acting With Clarity Founder identifies whether it's the person or the system within 2 weeks. Takes one of three clear paths: fix the system, move the person to a better-fit role, or help them exit with dignity. Team respects the decisiveness.

The Compassion Reframe

✕ Misguided Compassion Keeping someone in a role they can't succeed in because it feels cruel to act. Result: they're stressed and uncertain, the team resents the double standard, and the founder feels trapped.
✓ Real Compassion Moving quickly with honesty, generous severance, and real support for their next step. They land somewhere they can actually succeed. The team's trust in leadership increases.

Three Paths Forward — This Week

Before you make any people decision, work through these three options in order.

1
Fix the system around them. Ask honestly: do they have transparent processes, training, and support? If you haven't given them a real system to operate in, the failure isn't theirs. Build the infrastructure before you make the call.
2
Find their correct seat. Is this a wrong-role problem rather than a wrong-person problem? Before letting someone go, look for where their actual strengths could create value. The answer sometimes surprises founders.
3
Help them transition with dignity. If it genuinely isn't working, move quickly and generously. Solid severance, honest references for what they did well, and support in their next step. This is what real leadership looks like — and your team will remember it.
GTM Truth Worth Sitting With The loneliest part of being a founder isn't making hard decisions. It's the belief that you have to make them alone. The problem might not be the person. It might be the system they're operating in — and that's something you can actually fix.

Frequently Asked Questions

How do I know if it's a people problem or a systems problem? +
Ask whether a different person — with the same skills — would succeed in the same role given your current infrastructure. If the answer is no, it's a systems problem. Look at what's surrounding the person: Is messaging clear enough for a rep to sell from? Is there a documented process or are they improvising? Is the ICP defined well enough to prioritize the right prospects? If those inputs are missing, the underperformance is almost always systemic. Fix the system, then evaluate performance against a fair baseline.
How do I have the conversation when I've decided it's time to let someone go? +
Be direct and human — both at the same time. Don't soften the message with so much context that the decision becomes unclear. State the decision, the effective date, and what you're providing to support their transition. Be specific about what they did well and honest about the fit issue. Keep it short. Most founders make the mistake of over-explaining as a way of managing their own discomfort. The person in front of you needs clarity, not a lengthy rationale. Treat them the way you'd want to be treated if the situation were reversed.
What does "building the GTM infrastructure that allows good people to succeed" actually mean in practice? +
It means giving your team the four things they need to operate: clear messaging they can sell from, a defined ICP so they know who to target, a documented sales process they can follow, and a tech stack configured to support that process. When those four things are in place, you can actually evaluate individual performance fairly. Without them, you're asking people to build the plane while flying it — and then blaming the pilot when it goes down. Most founders who keep making the same hiring mistake haven't yet recognized that the system needs to come before the hire.

Ready to Separate People Problems From System Problems?

You don't have to make the hardest founder decisions alone. Let's look at what's actually breaking in your GTM infrastructure — and build the clarity you need to lead with confidence.

Book a Free GTM Assessment →
Mark D. Gordon

Mark D. Gordon

Mark D. Gordon is a growth strategist with over 20 years of experience building and scaling companies through GTM systems. He works with founders and revenue leaders to align sales, brand, technology, and demand into one growth engine.