Right Person, Right Seat Starts When You Admit What You’re Protecting

I watched a founder stare at his org chart like it was a crime scene photo.

Not because the lines were messy. The boxes were neat. Titles were clean. Everyone had a lane.

The problem was quieter: he already knew one seat was wrong, and he was negotiating with himself about whether to say it out loud.

I’ve done that same negotiation more times than I want to admit. I’ve called it loyalty. I’ve called it patience. I’ve called it “giving it one more quarter.” Underneath, it was fear—fear of the conversation, fear of being misunderstood, fear of the fallout.

EOS gives you language for this: right person, right seat. But the real work isn’t the phrase. The real work is the moment you stop protecting the story you’ve been telling yourself.

The seat problem is rarely a performance problem

When a seat is wrong, founders tend to chase symptoms.

We rewrite job descriptions. We add weekly check-ins. We install new dashboards. We tighten the scorecard. We “coach harder.”

Those things matter, but they can also become camouflage.

A wrong seat often looks like one of these patterns:

• Decisions stall because everything routes back to you.
• A leader owns outcomes in conversation but not in behavior.
• The team feels the drag but can’t name it, so they start whispering.
• Customers feel inconsistency because internal standards are inconsistent.

Here’s the uncomfortable truth: if you’re honest, you can usually name the wrong seat in under ten seconds.

The question is why you won’t act on what you already know.

Founders flinch because the wrong seat exposes something personal. It’s not just “they’re not good at the role.” It’s “I put them there.” It’s “I didn’t see it soon enough.” It’s “If I move them, what does that say about me?”

Right person, right seat is an operational decision. The flinch is emotional.

Your flinch is protecting three things

When I slow founders down and ask what they’re afraid of, the answers come out in polished language.

“I don’t want to hurt them.”

“I don’t want to cause chaos.”

“I don’t want to lose culture.”

Let’s translate.

You’re protecting your identity as a good guy

A lot of founders have an internal script that says, “I’m the leader who takes care of people.”

That’s a strength—until it becomes a shield.

If you equate leadership with avoiding discomfort, you’ll keep people in seats they can’t win in. You’ll call it kindness. They’ll experience it as confusion.

The most respectful thing you can do is tell the truth early. Not brutal truth—useful truth. The kind that gives someone a real chance to respond.

One of the simplest ways to measure whether your “care” is actually care: are you willing to say the sentence that could cost you their approval?

Because approval is cheap. Clarity is expensive.

You’re protecting the story that your first hires were ‘special’

Early teams are built in chaos. People wear five hats. Loyalty gets earned in late nights and thin margins.

That loyalty is real.

But the company you’re building next requires different competencies than the company you built to survive.

When founders flinch, it’s often because admitting “this seat is wrong” feels like rewriting history. It feels like saying the early wins didn’t matter.

They mattered. They got you here.

Now you have to build what gets you there.

A founder once told me, “If I move him, it feels like I’m betraying the version of me who needed him.”

I get that.

You’re not betraying that version of you. You’re honoring him by refusing to let sentiment sink the mission.

You’re protecting yourself from the second-order consequences

A seat change triggers ripple effects:

• Who else will question their role?
• What if they leave and take institutional knowledge with them?
• What if the team thinks we’re unstable?

Those are legitimate risks.

But there’s a bigger risk: letting the wrong seat quietly teach your organization what you tolerate.

Culture isn’t what you preach. Culture is what you permit—especially at the leadership level.

Here’s a phrase I use with founders: “You’re paying for this either way.”

If you move now, you pay in discomfort.

If you wait, you pay in drift, resentment, and the quiet loss of standards.

Right person, right seat is a truth-telling system

EOS gets reduced to charts and meetings by people who haven’t used it under pressure.

The value isn’t the tools. The value is the honesty the tools demand.

A few practical frames I use with founders:

Separate ‘person’ from ‘seat’ out loud

When you keep it vague, everyone fills in the blanks with fear.

Say the actual sentence:

• “I believe you’re a right person, but this seat is wrong.”
• “I believe this seat is right, but you’re not a fit for it.”

That clarity is not cold. It’s merciful.

It stops the slow bleed of mixed expectations.

One caution: don’t weaponize “right person, wrong seat” as a way to avoid accountability. If the seat is wrong because you never defined it, that’s on you.

Define the seat in outcomes, not activities

A lot of role confusion comes from activity-based job descriptions.

“Manage marketing.” “Oversee ops.” “Run sales.”

Those are verbs. They don’t define success.

A seat should be defined by outcomes that the rest of the leadership team can recognize without debate.

If your team can’t articulate what winning looks like for a role, you’ll keep hiring (and retaining) people based on personality and effort.

Effort is not the metric. Outcomes are.

If you want a simple way to do this, ask one question: “If this seat is winning 90 days from now, what is true that isn’t true today?”

Make the answer measurable.

Stop rewarding proximity to you

Founders accidentally train an organization to depend on their attention.

The person who gets the most face time gets the most influence. The person who can talk you into “one more chance” stays.

That’s not culture. That’s codependency.

When you install a real operating system, it has to operate without your moods.

If your team can’t win without you hovering, that’s a seat definition problem—or a leadership discipline problem.

And if you’re honest, this is where the flinch shows up too. Keeping someone close to you can feel safer than letting them own a real number.

Ownership creates exposure. Exposure creates accountability.

The conversation you’re avoiding is the bottleneck

I’ve seen companies lose years because of one avoided conversation.

The team knows.

You know.

And the longer you wait, the more the narrative forms without you. People start creating their own explanations:

• “He won’t do anything.”
• “She’s untouchable.”
• “Results don’t matter here.”

When you finally act, it feels sudden to you, but it doesn’t feel sudden to the team. It feels overdue.

If you want to lead with strength, you don’t wait for certainty. You move when you have enough clarity to act responsibly.

Here’s a litmus test: if you had to rebuild this exact seat from scratch today, would you hire the same person into it again?

If the answer is no, you already have your decision.

Another litmus test that’s harder: if the person in the seat wasn’t loyal, wasn’t likable, and didn’t have history with you—if they were just a candidate—would their results earn them the role?

If not, your culture has a fairness problem.

Re-seating people can be an act of leadership, not failure

A wrong seat doesn’t always mean someone needs to be gone.

Sometimes it means:

• moving a high-character operator out of management and back into production
• reducing scope so they can actually win
• changing the reporting structure so authority matches responsibility

But none of those moves happen while you’re tiptoeing.

The founder who refuses to flinch is not the founder who’s harsh.

It’s the founder who’s honest.

And honesty creates stability faster than avoidance ever will.

Here’s what I want you to hear if you’re staring at the org chart right now: you’re not firing a person. You’re protecting the standard.

You can be compassionate and decisive at the same time.

Compassion without decisiveness becomes cruelty over time.

Decisiveness without compassion becomes ego.

The goal is leadership.

If you need a clean framework to evaluate seats, expectations, scorecards, and the weekly cadence that keeps this from becoming an annual crisis, EOS is a good place to start. I work with operators inside EOS Implementation when the goal is to install a system that can scale without constant heroics: https://www.kairoscoaching.com/programs/eos

Action Items From Today

1. Write down the one seat you’ve been negotiating with yourself about, and name the specific outcome you’re not getting.
2. Define the role in 3–5 measurable outcomes (not tasks) that the rest of your leadership team would agree on.
3. Schedule the conversation you’ve been avoiding and write the opening two sentences so you don’t improvise your way into vagueness.
4. Remove one dependency on you this week by pushing a decision fully into the seat that should own it—and letting them feel the weight of it.
5. Set a 30-day window with clear scorecard metrics so you’re not stuck in endless “we’ll see.”

Five Bridges Challenges

Internal: Where are you avoiding the truth because you don’t want to feel like the villain?

Relationships: Who deserves clarity from you this week—because your silence is forcing them to guess?

Legacy: If this company is part of what you leave behind, what standard are you teaching your leaders by what you tolerate?

Optional: Bridge Builder Mastermind is where this work gets done in a small room of operators: https://www.kairoscoaching.com/programs/bridge-builder

Inspire & Impact,

Josh