All issues
Answering my inbox · Issue No. 9
Two Sons, No Crown
Manhattan Grit, Manila Grace.
The Question
A client asked
“My two sons both work in the business. Neither one is ‘the’ successor yet, and I refuse to decide in a way that looks like I'm choosing. Is it possible to build succession without picking a winner?”
“We haven't picked yet” and “we've picked not to pick” are two different things. Right now you're doing one of them while telling yourself it's the other.
Yes. But only if you replace the word “winner” with something more precise, and do it deliberately, rather than letting the silence do it for you.
The Manhattan Read
One crown, one head. That binary isn't actually the only structure available to you, even though everyone defaults to this zero-sum imagining. Proven co-leadership models exist.
- Defined operational domains, where each son owns a distinct, real area of the business end to end.
- A family council that handles ownership and family matters, kept separate from an operating board that handles the business.
- Explicit, documented decision rights specifying exactly what each of them decides alone, what they decide jointly, and who breaks a tie when they don't agree.
What you can't avoid, though, is building an explicit structure. Indefinite ambiguity isn't neutral. It's a decision, made silently, that just happens to avoid the discomfort of naming it. The ambiguity eventually resolves itself anyway, through attrition, resentment, or a crisis that forces the question, and usually on worse terms than if you'd structured it on purpose.
The actual governance question isn't “who's the successor.” It is this: what decisions does each son own today, on what schedule is that reviewed, with what transparency, and what specific, named trigger forces the leadership question to be revisited formally, with criteria both of them agreed to in advance? That trigger can be a birthday, a tenure milestone, a performance benchmark, or your own retirement date.
The Manila Read
I completely understand that this is not indecision. It's protection. You're protecting the relationship between two brothers, as you should, because it is load-bearing. The fear underneath “I refuse to decide” is usually love at its most hard-working: you don't want either son to hear “not you” as “not enough,” and you don't want the succession pathway you're laying today to harden, over time, into a wall between them that trust can no longer cross.
But here's the part that's easy to miss from inside that fear. Avoidance does nothing to actually protect the relationship. It simply defers the damage to later, burdening the very two people you're trying to protect with the arduous job of interpreting your silence with objectivity. Without a visible process, each son is quietly building his own version of the story about who was “really” being groomed: who was given which projects, who was in which meetings, the compliment you paid the other one two years ago.
Ambiguity doesn't prevent a verdict from forming. It just lets two different verdicts form in two different heads, unspoken, and that is a far more dangerous seed for resentment than a documented process either of them can point back to.
Real malasakit here isn't refusing to choose. It's building a process careful enough that both sons are able to focus on what is happening to the company instead of on what is happening to them, whatever gets decided. That includes, possibly, genuine co-leadership with no single “winner” at all.
The Move
This week, before naming any successor at all: write down what each son currently owns, end to end, and get both of them to confirm it's accurate.
Then name, in writing, the specific trigger that forces a formal leadership conversation. Not “when it feels right.” An actual date or milestone. Name the criteria that conversation will use, agreed by both sons and reviewed by one outside advisor neither of them reports to.
You're not avoiding the choice. You're making sure the choice, whenever it comes, has a paper trail both sons helped write.
Where This Shows Up
This is the kind of governance architecture eCSI builds and keeps running for family-owned enterprises: a documented decision-rights framework for each son's domain, the family council and board calendar with proper minutes and resolutions, and a compliance calendar that tracks the review trigger you named, so the leadership conversation happens on schedule rather than by default.
Two siblings can share real authority without either one privately wondering, indefinitely, where he actually stands.