There's one person on every founder's team who's different from the rest. They were there before there was much of a "team" to speak of. They answered the phone when the company was just you and a folding table. They stayed late without being asked, covered for you when you were sick, believed in the thing before there was much evidence to believe in.
And now, years later, the role has grown past them. Everyone can see it. Nobody wants to say it. Least of all you.
The Obligation That's Hard to Name
This isn't a performance problem in the usual sense. Performance problems are relatively easy - you can coach them, document them, manage them out if it comes to that. This is harder, because it's tangled up with something performance reviews were never built to measure: what you owe someone who helped build the thing you now run.
You owe them something. That's not sentiment, it's just true. They took a risk on you when taking that risk cost them something real - a more stable job, a bigger paycheck elsewhere, years they could have spent building expertise somewhere with more to teach them. Loyalty like that isn't nothing, and pretending it doesn't factor into the decision is its own kind of dishonesty.
But the company owes something too - to the customers this person now serves imperfectly, to the newer employees quietly picking up their slack, to the version of the business that has to exist in order for anyone's job, including this person's, to still be here in five years.
Both of those obligations are real. That's what makes this hard. It's not a case of loyalty versus the bottom line, where the answer is obvious once you strip away the sentiment. It's two legitimate obligations pulling in different directions, and founders who pretend otherwise usually end up serving neither one well.
How the Avoidance Usually Looks
Most founders don't consciously choose to avoid this. It just happens, one small deferral at a time.
You quietly route the hardest accounts to someone else, telling yourself you're just balancing the workload. You start double-checking their work before it goes out, telling yourself it's a busy season. You hire someone new, nominally "to help them out," and everyone in the building understands what that hire is actually for except, maybe, the person it's meant to help. Months pass. Sometimes years. The role has been hollowed out from underneath them, quietly, without anyone ever having the conversation that would let them understand what's happening and do something about it.
This feels kind in the moment. It rarely is. What it actually does is deny someone the chance to rise to a real conversation, and it slowly erodes trust with everyone else who's watching you manage around a problem instead of through it.
What Dignity Actually Looks Like Here
Real respect for someone's history with the company isn't protecting them from the truth. It's trusting them enough to tell it to them straight, and giving them a genuine chance to meet it. That, more than the eventual outcome, is where dignity actually lives - not in what happens, but in how someone is treated on the way there.
Separate the person from the role. The role may have outgrown them. That's not the same as saying they've stopped being valuable, or that everything they built no longer matters. Founders who conflate the two - treating a role mismatch as a referendum on someone's worth - tend to either avoid the conversation entirely or handle it with more brutality than it calls for. Neither serves anyone.
Have the conversation earlier than feels comfortable. The version of this conversation that happens two years too late, after the workarounds and the second-guessing and the new hire nobody named, is worse for everyone than the version that happens honestly and early. Early conversations leave room for growth, for a different role, for a graceful transition. Late conversations tend to leave only cleanup.
Be specific about the gap - and careful with the person. "You're struggling" isn't useful information for someone who's been good at their job for a decade, and it collapses a person into a deficiency. What's specific about how the role has changed - new complexity, new scale, new skills it now demands - that wasn't part of the original deal? "This part of the role has outgrown what either of us expected when you started" names a gap between a role and a moment in time. It's a truer statement, and one a person can hear without it becoming an attack on who they are. Naming the gap accurately is also what makes it possible to close, or to have an honest conversation about whether it can be.
Offer a real path, not a face-saving one. Sometimes the path is training or support to grow into what the role has become. Sometimes it's a different role - one that draws on what this person is genuinely still excellent at, even if it isn't the role they've held for years. Sometimes, honestly, it's a well-handled exit. What matters is that the path is real, not a soft landing designed mainly to make the founder feel less guilty.
Dignity Is the Part Obligation Doesn't Cover
Obligation and responsibility get most of the attention in this conversation, but there's a third thing underneath both of them, and it's often the one that determines whether the whole thing goes well or badly: dignity.
Obligation is about what you owe someone because of history. Dignity is about how you treat them in the moment itself, independent of history, independent even of outcome. You can honor someone's loyalty badly - a vague explanation, a severance check, a conversation that never quite happens - or you can honor it well, in a way that leaves their sense of self intact even when the news is hard. The difference isn't in what you choose. It's in how the person experiences getting there.
A few places this shows up in practice:
They're told the truth, not managed around. The quiet workaround - routing accounts elsewhere, a shadow hire nobody names, work double-checked without explanation - might feel protective. It actually costs more dignity than a direct conversation would, because it treats someone as a problem to be handled rather than an adult capable of hearing reality and responding to it.
They keep their history intact. Dignity doesn't require erasing the past to make an honest case about the present. Both things can be true in the same sentence: you built this with me, and the role has changed in ways neither of us fully planned for.
They have real agency in what happens next. Whether someone gets to actively choose their next chapter - growing into a changed role, moving into a different one, or choosing how and when to exit - matters as much as what that chapter turns out to be. The same outcome feels entirely different depending on whether someone had a hand in reaching it or simply found out last.
The uncomfortable truth underneath all of this: avoiding the conversation to spare someone's feelings usually costs them more dignity in the long run than having it would. Watching a role get quietly hollowed out around you, without ever being told why, is a deeper blow than an honest, well-timed conversation - even one with a hard outcome.
The Question Underneath the Question
Founders often frame this as: what do I owe this person? It's usually more useful to ask a second question alongside it: what does the company need to become, and does this person's role, as it exists today, still serve that?
Those two questions don't have to conflict as often as they seem to. A company that has outgrown someone's current role hasn't necessarily outgrown that person. But finding out requires an honest conversation, not a slow, silent management-around that spares you the discomfort while it costs them the dignity of knowing where they stand.
What This Really Tests
This moment tests something bigger than one employee relationship. It tests whether you can hold two true things at once - genuine loyalty and genuine responsibility - without collapsing into either one. Collapse toward loyalty alone, and you protect one person at the expense of the team and the mission you're all supposedly building together. Collapse toward responsibility alone, and you become the kind of founder whose early believers learn, the hard way, that loyalty only ran in one direction.
The harder, better path runs between those two. It means telling the truth soon enough that it can still be useful. It means offering a real chance before making a final decision. And it means understanding that dignity was never a soft add-on to this process - it's the measure of whether you got it right, regardless of what you ultimately choose. The most respectful thing you can do for someone who helped build this with you is treat them as someone strong enough to hear where things actually stand.
If this is a conversation you've been avoiding, you're not the first founder to avoid it — and you don't have to figure out how to have it alone.
At MacklinConnection, we work with business owners through exactly these moments: the ones that are as much about identity and loyalty as they are about org charts and role descriptions. Coaching gives you a confidential space to think it through clearly, before the conversation happens, not after it's gone badly.
Explore Coaching with MacklinConnection
.png){kind=small}