---
id: "claim-chair-role-mismatch"
type: "claim"
source_timestamps: ["§ Choose the Right Model"]
tags: ["role-design", "governance"]
related: ["framework-founder-role-archetypes", "concept-role-scorecards", "entity-bill-gates"]
confidence: "medium"
testable: true
speakers: ["Samantha Hellauer", "Sanja Kos", "Julie Vermoote", "Sapna Sadarangani Werner", "BJ Wright"]
sources: ["tail2"]
sourceVaultSlug: "hbr-seg-tail2"
originDay: 2
articleStem: "hbr-tail-122-leading-after-founder"
sourceUrl: "https://hbr.org/2026/01/leading-after-the-founder"
sourceTitle: "Leading After the Founder"
---
# The Chairperson role rarely aligns with founder strengths

Moving a founder to a Chairperson role is a common archetype offering prestige and continuity, but it rarely aligns with a founder's core strengths, which typically involve building, innovating, or executing. Without strict boundaries and a well-defined scorecard, this role often devolves into a symbolic title that either disempowers the founder or lets them undermine the new CEO. This is why the first pathway in [[framework-founder-role-archetypes]] must be paired with [[concept-role-scorecards]].

**Confidence: medium.** **Enrichment / evidence:** Directionally consistent with governance literature warning that poorly specified founder–chair roles blur authority and create dual power centers, especially when the founder retains significant shareholding and reputation. But "rarely" is an experience-based generalization, not quantitatively validated — there are notable counterexamples, most obviously [[entity-bill-gates]] (chair and "chief software architect" for years). The sharper counter-perspective is that the problem is *poor role design and unclear boundaries*, not the chair role itself. Treat this as a patterned risk, not a universal rule.