- owners (who carry the financial risk)
- leaders (who make operational decisions)
family (history, identity, expectations). When those worlds overlap without rules, succession becomes predictable chaos: authority without role, role without authority, and conflicts that feel “personal” because there’s no operating frame.
Professionalization begins when I stop asking “who’s in charge?” and start asking:
what decisions exist, who makes them, with what data, and what happens if they’re wrong?
## Early symptoms that tell me succession will hurt
### 1) There is no single source of truth
If a project’s status requires three conversations, you don’t have a system—you have distributed memory. Succession breaks memory unless knowledge transfer is designed, not hoped for.
### 2) The founder’s calendar is the nervous system
When coordination runs through calls, exceptions, and instant approvals, the company feels fast… until it realizes it’s dependent. Typical sign: no one can explain why a date, a discount, or a promise was approved.
### 3) The company “works” because there are heroes
If execution depends on people who “just know,” leadership change turns small errors into structural failures. Succession doesn’t create the risk. It reveals it.
### 4) Rules change depending on who’s in the room
When standards live in a person, the team adapts to moods, not methods. Under transition, that becomes politics.
### 5) Conflict is avoided, not managed
Many families confuse peace with health. Peace without rules is a countdown. If money, roles, performance, or authority can’t be discussed without tension, protocol isn’t optional—it’s protection.
## A protocol is not bureaucracy—it’s an anti-ambiguity system
When I say “protocol,” I don’t mean a pretty document. I mean mechanisms that reduce ambiguity, because ambiguity feeds:
- interpretation (“I thought you meant…”)
- expectations without contract
and informal power taking over operations.
A useful protocol clarifies at least five layers:
what ownership means (rights, limits, responsibilities)
what leadership means (role, authority, metrics, consequences)
how decisions happen (rhythm, forums, minimum information)
how conflicts get resolved (method before crisis)
how continuity is protected (risk control, cash discipline)
It doesn’t remove emotion. It prevents emotion from governing operations.
## The uncomfortable starting question I always ask
Which decisions cannot be made without one specific person?
If the list includes pricing exceptions, promised dates, scope changes, complex claims, production/installation priorities, or critical suppliers, then the core problem is decision design—not “finding a successor.” My goal isn’t to “replace” someone. It’s to make key decisions exist as a system, not as instinct.
## Real risks succession can trigger (even in profitable companies)
### Risk 1: margin erosion without noticing
During transition, insecurity often gets compensated with concessions: more discount, more urgency, more exceptions. Without promise governance and change discipline, margin dissolves quietly.
### Risk 2: cash becomes unpredictable
Any friction in execution (rework, delays, claims) becomes cash tension when leadership is shifting.
Danger signal: “sales look fine, but we can’t breathe.”
### Risk 3: the team switches into interpretation mode
When rules are unclear, the team guesses who has authority, what is tolerated, and what is prioritized. Performance drops, attrition rises.
### Risk 4: customer experience fragments
Customers don’t experience “before” and “after.” They experience their project. Poorly governed succession shows up as inconsistency, weak communication, reactive after-sales, and visible disorder.
## My 12-question diagnostic (without implementation)
Is there a real org chart with roles and decisions (not aspirational)?
Is project status visible through a single truth source?
Do you measure promise vs reality (time, margin, incidents)?
Is there a way to say “no” early without breaking sales?
What % of projects change scope—and how is it governed?
How much rework is “normal,” and who sees it?
What breaks if two key people are absent?
What management rituals exist, and what decisions come out of them?
How do you train new leadership without the business “punishing” them?
How is quality defined and audited?
Where does coordination break: sales, technical, factory, installation?
Which family conflict could hijack an operational decision?
If answers are based on feelings instead of facts, I assume systemic succession risk.
## Healthy succession synchronizes two clocks
I always separate:
- the family clock (recognition, identity, perceived fairness)
the business clock (authority, metrics, continuity, decisions). The common mistake is solving the family clock with business roles (“here’s your title”) or solving business needs with family gestures (“they’ll learn”). A healthy transition isn’t the fastest. It’s the most legible.
## Signs you’re ready (even if it doesn’t feel comfortable)
- key decisions have owners and a method
- project truth is visible and reliable
- commercial promises have validation
- after-sales creates learning instead of exhaustion
- the team can execute without constant permission
cash is understood by milestones, not faith. I’m not giving a full implementation playbook here—only the detection criteria I use.
## The three most expensive mistakes
-
- naming a successor without redesigning the system
-
- “verbal” transitions where authority changes informally
-
- professionalizing outward (brand) while leaving governance inward weak
If you want, I’ll translate this into your case with a short diagnosis: dependencies, failure points, and what must exist before you touch roles, family dynamics, and ownership.
