All issues
Answering my inbox · Issue No. 4
Ready, But Not Ready
Manhattan Grit, Manila Grace.
The Question
A CEO wrote in
“My daughter is twenty-eight and says she's ready to take over. The company isn't ready for her. How do I tell her ‘not yet’ without it sounding like ‘never’?”
The Manhattan Read
This is the first distinction I make in every one of these conversations, because it is the one that changes how they go. Separate two things that are getting collapsed into one: her readiness, and the company's readiness to be led by her. They are different questions with different owners, and treating them as one is what makes this feel like an impossible conversation instead of a structured one.
Her readiness is a development question: capability, experience, judgment under pressure. It has a timeline you can actually design. Specific roles, specific decisions she owns end to end, specific metrics she is accountable for, reviewed on a schedule. That is coachable, and naming it as a plan rather than a verdict changes the entire conversation.
The company's readiness is a governance question, and it faces two directions.
Inward. Is there a defined transition process at all? A documented set of criteria for what "ready to lead" means here, not vibes, not birth order, but an actual role-readiness framework? A board or advisory structure, with at least one voice from outside the family, that can evaluate that objectively?
Outward. Will the people the business depends on follow her? The senior team who did not grow up at the dinner table, the bank, the key clients whose loyalty runs to you personally. That is not something she can earn alone. It is something the company has to transfer deliberately, relationship by relationship.
Most family-governed companies have built neither side. So "not ready" ends up sounding like a judgment about her, when it is often an admission that the company never built the structure to judge her fairly, or the bridges to hand her the relationships it runs on.
The Manila Read
I have never had this conversation at a family table, but I have had it from both sides of a desk, delivering "not yet" and receiving it. This is where most succession conversations actually go wrong: not in the substance, but in the delivery. Said badly, "not yet" sounds like "not enough," and that wound does not heal on the same timeline as the business plan. In a family enterprise, the relationship is not a variable you can trade off against the outcome. It is the outcome, alongside the business. Sacrifice it to get the transition timeline right and you have not succeeded at all.
The version of malasakit this calls for is not protecting her from heartbreak by avoiding the conversation. It is investing in her long enough, and structurally enough, that she can receive "not yet" with trust. Clearly about the runway, never about her. That means the plan has to be real, with milestones, mentorship, and a genuine path. Not a stalling tactic dressed up as development. She will know the difference, and so will everyone up and down the company watching how this is handled.
The Move
Do not answer "is she ready" as a yes or no. Bring her a written transition plan instead: the specific roles and decisions she will own over the next 18 to 36 months, who evaluates her progress and how, and what "ready" concretely means when you get there. Put the framework in front of her before you put a timeline in front of her. It turns a verdict into a shared project, which is a conversation you can both survive.
I have never once seen a transition plan undo the damage of a badly delivered "not yet." I have seen it prevent one.
Where This Shows Up
This is where eCSI earns its keep: building the governance backbone a transition stands on. That means the board or advisory structure, the readiness criteria formally adopted and on record, and the decision trail that makes "not yet" a plan instead of a wound. The other half is the conversation itself, and that is where I come in personally, drawing on years of designing and facilitating alignment across generations of a family-governed enterprise and across the C-suites of global companies. Built before the conversation happens, not patched together after it goes badly.