# When Your Key Executive Quits: Build a Company That Keeps Running

**Speaker:** Patrick Bet-David, with audience case respondents  
**When:** 2026-09-01 · 11:52 PM–12:22 AM ET (8:52 PM Las Vegas)  
**Theme:** Continuity & family business  
**Sources:** WxJ71lw00yLq36jk6Rlz  
**Notes page:** https://vault.chels.ai/sessions/d1-final-case-study/

> **Losing the one person who holds your company's knowledge is going to happen to everyone, so respond in a set order (step in for customers, name an interim, mine the data, put the anxious leaders to work) and then build the 'insurance policies' (a knowledge vault, a number two behind every seat, a manual, transparency) so it never hurts the same way twice.**

The last exercise of Day One, running past midnight Toronto time, was a fictional case: Hartwell Industrial Services, a $23 million mechanical contractor, loses its 19-year VP of Operations without warning. He held every client, vendor and process in his head; there was no key-man insurance, no accurate operations manual and no second-in-command. Groups had ten minutes to produce three to five moves, then several attendees, including a CEO with $15 million EBITDA who had lived exactly this scenario, presented at the mic. Patrick Bet-David then turned the question from recovery to prevention: what insurance policies do you build so a key departure cannot hold you hostage a second time? For the year ahead, this is your continuity playbook and your test of whether anyone in your company is currently irreplaceable.

**Best for:** Owner-led companies with one indispensable operator; CEOs who have never written down what their number two actually does; Founders planning succession or preparing for a sudden resignation, illness or death; Leaders who have just lost a key person and need a first-two-weeks plan; Managers who want to document institutional knowledge before it walks out; Anyone who wants to stop being held hostage by an ultimatum

## Claude skills from this session

- `key-person-continuity-plan` — Build or run a continuity plan for the loss of a key person - the CEO's personal continuity guarantee to customers and vendors in the first 48 hours, naming an interim, a number two behind every critical seat plus a second backup, a knowledge vault of SOPs and CRM records, a data-recovery drill over invoices and email, and the four-workstream response team. Use whenever the user mentions a key employee, VP, operator, or co-founder quitting, threatening to quit, falling ill, or being unreachable, "institutional knowledge", key-man insurance, succession, bus factor, being held hostage by an ultimatum, or one person who "knows everything" - even before anyone has actually left, and even if they only ask "what happens if X leaves?".  
  https://vault.chels.ai/skills/key-person-continuity-plan/SKILL.md

## Skills to build

- **Stepping into the gap as CEO on day one** — When a key leader leaves, the CEO personally fills the void with customers and vendors so nobody outside feels the pain, before any structural fix. _How to practise:_ Rehearse the call now: 'Everything is going to be okay. We have someone in place. The systems and processes are there so the quality you receive continues.' The CEO who did this for real lost zero customers. Keep a current list of your top clients and critical vendors so you can start calling within hours, not days.
- **Building bench depth: a number two behind every key seat** — Ensuring every critical role has a qualified person who can step up, and a backup behind them, so no single resignation can stall the business or become leverage. _How to practise:_ List every role whose loss would hurt for more than a week. For each, name the person who steps up today and the person behind them. Where there is no name, that is your hiring or development priority this quarter. One attendee with about 100 staff keeps a first and a second backup for everyone and says the sooner someone leaves, the better.
- **Turning one person's head into a company knowledge vault** — Capturing the clients, vendors, processes and judgment calls that live in individuals into shared, accessible documentation and systems (SOPs, CRM records, process maps). _How to practise:_ Pick the person whose departure would hurt most. Each week for a month, have them document one process or relationship in a shared system. Then test it: can someone else run that process from the document alone? Repeat for the next person. The goal, in one attendee's words, is a vault of knowledge the whole team can access.
- **Rapid data recovery with AI and existing systems** — Using your invoicing, CRM and (authorized) company email to rebuild a picture of customers, prospects and open conversations fast when the person who knew them is gone. _How to practise:_ Before you need it, confirm you can export two years of invoices and pull a ranked customer list in an hour. Know your policy for reviewing a departed employee's company email for prospects and open threads before the account is wiped. Practise with an AI tool on a sample export so the process is ready. Then hand the ranked list to the remaining team to divide and conquer.
- **Reading departures as culture signals** — Treating a surprise resignation from a long-tenured leader as evidence about your own leadership and culture, not only a staffing problem. _How to practise:_ Every month, have a real conversation with each of your senior leaders about how they are doing and what would make them leave. When someone does leave, interview the remaining leaders: they knew parts of the story. Ask what the person's strengths and downfalls were so the replacement is better. If a departure surprises you, pick up the mirror first.
- **Running a continuity response as a team** — Converting the anxious senior leaders ('who's next?') into workstream owners with clear roles, short huddles and a measured transition. _How to practise:_ Within 48 hours of a departure, name the interim, then hold twenty-minute huddles to list everything the departed person did and who takes each item. Assign owners for: the manual and systems, client relations, internal affairs, and developing future people. Set a recurring resilience check-in until the all-hands. Prepare a clear update for every department.

## What matters

- **The people who leave early are showing you the story of their life:** Bet-David opened by pointing at attendees walking out before the final exercise, right after speakers on preparation and discipline. His point: stamina is the whole game, and the people who cannot make the '25th hour' are the ones who wanted the drinks and comfort. Finishing the last exercise when tired is the same muscle as finishing a hard quarter. _(Evidence: 23:52:56-23:53:36, 23:58:13 / WxJ71lw00yLq36jk6Rlz)_
- **Institutional knowledge in one head is an uninsured liability:** The case's VP knew every client, vendor and process because the knowledge lived only in his head, and there was no key-man insurance, no accurate manual and no second-in-command. Each of those gaps is a choice the company made by default. Audit yours before someone hands in a resignation on a Tuesday morning. _(Evidence: 23:56:39-23:57:00 / WxJ71lw00yLq36jk6Rlz)_
- **The external damage comes second; the internal politics come faster:** Two weeks after the departure, clients asked for the VP by name and a vendor refused to negotiate. But inside, four senior leaders assumed they were next, alliances formed and meetings turned political. Your first communications must address the people still in the building. _(Evidence: 23:57:07-23:57:54 / WxJ71lw00yLq36jk6Rlz)_
- **Customers accept a new face if the CEO personally guarantees continuity:** The attendee who lived this ($15 million EBITDA) stepped in as CEO, called customers, said everything would be okay and that systems were in place, and lost none. A second respondent said he would tell every customer he is personally responsible for continuity. Hearing it from the top is what holds accounts. _(Evidence: 00:07:02-00:07:42, 00:17:22 / WxJ71lw00yLq36jk6Rlz)_
- **A visible interim stops the 'who's next?' spiral:** The second move in the real-life account was to make sure the whole organization knew a qualified person now held the role. Naming someone quickly removes the vacuum in which alliances and politics grow. _(Evidence: 00:07:42 / WxJ71lw00yLq36jk6Rlz)_
- **A number two behind the interim removes future leverage:** The same CEO immediately put a number two behind the newly promoted supervisor, so the problem could not repeat and so the new leader knew there was a replacement if they 'thought about screwing around'. Depth is both continuity and negotiating position. _(Evidence: 00:07:42 / WxJ71lw00yLq36jk6Rlz)_
- **The company goal is that no one is irreplaceable:** After the fire was out, that CEO built SOPs, processes, systems and organizational functions so there are always enough supervisors and managers to step up. Irreplaceability is a design flaw you engineer out, not a compliment you pay someone. _(Evidence: 00:08:12 / WxJ71lw00yLq36jk6Rlz)_
- **Your invoices and inbox already contain the customer list:** One respondent would use an AI tool over two years of invoicing to rank every transacting customer by spend, then review the departed VP's company email for prospects and live conversations before the account is wiped, and hand both to the team to divide and conquer. The knowledge is not really gone; it is unorganised. _(Evidence: 00:10:21-00:12:03 / WxJ71lw00yLq36jk6Rlz)_
- **Go to the person who left hat in hand, not to win them back but to transfer knowledge:** One pair proposed visiting the departed VP at his home with food, asking what happened, and inviting him to train the replacement. You may not get him back, so have a second plan, but a respectful approach can buy weeks of handover you would otherwise lose. _(Evidence: 00:12:09-00:13:56 / WxJ71lw00yLq36jk6Rlz)_
- **Put the four anxious leaders to work on four workstreams:** Instead of letting the senior leaders speculate about who is next, give each one a job: the operations manual and systems; client relations; internal office affairs; and developing future people. Ownership converts anxiety into continuity. _(Evidence: 00:13:56-00:14:35 / WxJ71lw00yLq36jk6Rlz)_
- **A surprise resignation after 18 years means the CEO was asleep at the wheel:** One respondent argued the case is cultural, not transactional: the VP mentally quit six to eighteen months earlier and someone in the building knew. Shore up the boats, then interview the remaining leaders about the discontent they saw, and look in the mirror. _(Evidence: 00:14:42-00:15:48 / WxJ71lw00yLq36jk6Rlz)_
- **Addition by subtraction: do not panic-hire:** The same respondent said a 20-year-old company has a CRM and the data; this is not panic mode. Losing a leader who had checked out can be an upgrade if you use the moment to raise the standard rather than rush a replacement. _(Evidence: 00:15:24-00:15:34 / WxJ71lw00yLq36jk6Rlz)_
- **Recovery is the first answer; the insurance policy is the real one:** Bet-David asked how many had lived this and how many immediately built a strategy so it could not recur. If it happens a second, third or fourth time, you are not building the right systems. The lesson of a key departure is the protection you build afterwards. _(Evidence: 00:17:58-00:18:33 / WxJ71lw00yLq36jk6Rlz)_
- **Refusing ultimatums is what drives real redundancy:** The attendee with about 100 staff built first and second backups for every role because he does not accept ultimatums, direct or indirect. Once you have been put in that position you must assume it will happen again, 100%, and either prepare or fail. _(Evidence: 00:19:07-00:19:35 / WxJ71lw00yLq36jk6Rlz)_
- **Tell the team they are replaceable, and that replacing them is not the plan:** He is transparent with his people: everyone is replaceable, but that is not the plan, and as long as you bring value you are good. Said plainly and consistently, this removes the hostage dynamic without creating fear. _(Evidence: 00:19:36-00:20:04 / WxJ71lw00yLq36jk6Rlz)_
- **Certainty in your answers is a leadership signal:** Bet-David told the room to notice how the redundancy-minded CEO answered: short, certain, no hedging. He joked the man had been listening to Floyd Mayweather. Practise answering hard questions about your company with that kind of clarity. _(Evidence: 00:20:05-00:20:12 / WxJ71lw00yLq36jk6Rlz)_
- **Do the personal identity audit tonight, not the bar:** Closing Day One, Bet-David gave one challenge: skip the drinks, go finish the personal identity audit from the workbook, because there are levels to the game, and the difference is what you do with the energy of the day. An attendee who has done it every year for four years credited it with a massive change in his business. _(Evidence: 00:21:15-00:22:16 / WxJ71lw00yLq36jk6Rlz)_

## Frameworks, lists & numbers

- **The Hartwell case facts** — Hartwell Industrial Services, a $23 million mechanical contracting firm. VP of Operations, 19 years in, quits on a Tuesday morning without warning. He knew every client, vendor and process; most lived only in his head. No key-man insurance, no accurate operations manual, no second-in-command. Two weeks later: three client accounts ask for him by name; a critical vendor will not negotiate until the right person is at the table; four senior leaders think they are next; alliances form; meetings turn political. All-hands in two weeks. Question: your next three to five moves.
- **The lived four-step response (CEO with $15 million EBITDA)** — 1) Step up as CEO and fill the void personally; call customers and tell them the systems and processes are in place (lost zero customers). 2) Put a qualified person in the role and make sure the whole organization knows. 3) Put a number two behind that person so the problem cannot repeat and the new leader knows there is a replacement. 4) Build SOPs, processes, systems and organizational functions so no one is irreplaceable.
- **Four-workstream response team** — Give each of the four anxious senior leaders one job: (1) the operations manual and systems, (2) client relations, (3) internal office affairs, (4) developing future people. Meanwhile the owner personally handles the three clients threatening to walk.
- **Four-point continuity plan (respondent)** — 1) Name the interim VP and huddle with management in twenty-minute sessions to build the dependency list of everything the departed person did and who takes it. 2) Lock down customers, vendors and critical people: call each customer, meet each vendor personally, one-on-one interviews with the executive team, implement a retention plan. 3) All-hands to plan continuity and launch the rebuild, with the CEO personally responsible for continuity. 4) An operational resilience plan with regular meetings to measure the transition and catch anything missed.
- **AI-assisted data recovery** — Run an AI tool over one to two years of invoicing to rank all transacting customers by spend. Before wiping the departed person's company email, have it surface prospects and open conversations. Hand both lists to the remaining team to divide and conquer, and use the moment to recruit an even better replacement by asking the team about the departed person's strengths and downfalls.
- **The prevention rule** — This will happen to everybody. After the first time, immediately create the strategy (the 'insurance policy') so it cannot happen the same way again. If it happens a second, third, fourth or fifth time, you are not creating the right systems.
- **Vault of knowledge with double backup** — Knowledge cannot sit in one person; the whole team must be able to access it. Every role has a first backup and a second backup. Result: an ultimatum has no leverage, and 'the sooner they leave, the better'.
- **The transparency line** — Tell the team all the time: everyone is replaceable, but that is not the plan; as long as you bring value, you are good.
- **Levels to the game (Day One close)** — Those who left early; those who stayed to the end; and those who go home and finish the personal identity audit rather than going out. Do the audit tonight and every year.

## Exercises & frameworks to run

- **The Hartwell case (run it with your leadership team)** _(10 minutes in groups, 20 minutes of read-outs and debrief)_ _[speaker]_
  1. Read the facts: you are CEO of Hartwell Industrial Services, a $23 million mechanical contracting firm. On a Tuesday morning your VP of Operations, 19 years in, quits without warning. He knew every client, vendor and process; most of it lived only in his head. No key-man insurance, no accurate operations manual, no second-in-command. Two weeks later three client accounts ask for him by name and a critical vendor refuses to negotiate. Inside, four senior leaders think they are next, alliances form and meetings turn political. The all-hands is two weeks away.
  2. In groups, take ten minutes to write your next three to five moves.
  3. Sort your moves into: first 48 hours, first two weeks, and before the all-hands.
  4. Check that your plan covers all four audiences: customers, vendors, the four senior leaders, and every department at the all-hands.
  5. Present and grade each plan (par, birdie, eagle), rewarding moves nobody else said.
  6. Finish by swapping the fictional VP for your own most critical person and re-running the plan.
  - **Finish with:** A time-boxed continuity plan you have already rehearsed against your own key-person risk.
- **Key-person dependency list** _(90 minutes)_ _[editorial (speaker idea, steps written by us)]_
  1. List every person whose sudden departure would hurt the company for more than a week.
  2. For each, list what only they know or do: clients, vendors, processes, passwords, relationships, judgment calls.
  3. Mark each item green (documented and someone else can do it), yellow (partly), or red (only in their head).
  4. Name the interim and the number two for each role. Leave blanks where none exists.
  5. Turn every red item and every blank into a dated task with an owner.
  - **Finish with:** A one-page map of where your company is held hostage and a task list to fix it.
- **The first-48-hours call script** _(60 minutes)_ _[editorial (speaker idea, steps written by us)]_
  1. Write the list of customers and vendors you would call personally, ranked by revenue and criticality.
  2. Draft the call in three sentences: what happened, who is in place, and that you personally guarantee continuity of quality and service.
  3. Draft the internal message to senior leaders that names the interim and their own role in the response.
  4. Draft the all-hands update: fast, clear, one paragraph per department.
  5. Store all three drafts where you can find them in a crisis.
  - **Finish with:** Ready-to-use scripts for customers, vendors, leaders and the all-hands.
- **Knowledge-vault sprint** _(4 hours over a month, per person)_ _[editorial (speaker idea, steps written by us)]_
  1. Choose the one person whose knowledge is most concentrated.
  2. Book them for one hour a week for four weeks.
  3. Week 1: document the top 20 client relationships (contact, history, quirks, open issues) in the CRM. Week 2: vendors and negotiation history. Week 3: the five most critical processes as step-by-step SOPs. Week 4: the judgment calls they make that nobody else knows about.
  4. Have their number two run one process from the documents alone and note every gap.
  5. Repeat with the next most concentrated person.
  - **Finish with:** A shared, tested body of documentation for your most critical role, and a repeatable method for the rest.
- **Data-recovery drill** _(Half a day)_ _[editorial (speaker idea, steps written by us)]_
  1. Export the last two years of invoices and, using a spreadsheet or an AI tool, produce a ranked list of transacting customers by spend.
  2. Confirm in writing (with legal or HR) your policy for reviewing a departed employee's company email for prospects and open conversations before the account is closed.
  3. Confirm you can pull every open opportunity from the CRM without a specific person's login.
  4. Time how long the whole drill takes. Anything over a day is a gap to close.
  5. Assign the drill to someone other than the person who owns the data.
  - **Finish with:** Proof that the customer and prospect picture can be rebuilt in hours, and a list of access gaps.
- **Four-workstream response team** _(2 hours to set up, then 20-minute huddles)_ _[speaker]_
  1. Name the interim leader for the vacated role.
  2. Assign four senior leaders one workstream each: (1) the operations manual and systems, (2) client relations, (3) internal office affairs and morale, (4) developing future people.
  3. Hold twenty-minute huddles to list everything the departed person did and assign each item to a workstream.
  4. Set a recurring operational-resilience check-in (weekly until the all-hands, then monthly) to measure the transition and catch dropped balls.
  5. Report progress at the all-hands with a clear update for every department.
  - **Finish with:** An organised response with owners, a dependency list and a cadence for checking nothing is missed.
- **Culture post-mortem after a departure** _(One week of conversations)_ _[editorial (speaker idea, steps written by us)]_
  1. Ask yourself honestly: was this a surprise? If yes, why did nobody tell you?
  2. Meet each remaining senior leader one on one and ask what discontent or turmoil they saw and when.
  3. Ask what the departed person's strengths and downfalls were, so the replacement is an upgrade.
  4. Write down the cultural issue the departure exposed and one change you will make.
  5. Decide whether this is a case of addition by subtraction before you rush to hire.
  - **Finish with:** A clear diagnosis of why the person really left and a better brief for the replacement.

## What to do — and how often

- [ ] **Write your key-person dependency list: every role whose loss would hurt for more than a week, what lives only in that person's head, and who steps up.** — Once, this month _[once; editorial recommendation]_
- [ ] **Name a number two behind every critical seat, and a second backup behind them; where there is no name, make it a hiring or development priority.** — Once, this quarter; review every quarter _[quarterly; editorial recommendation]_
- [ ] **Get a quote for key-man insurance on your most critical people and decide whether to buy it.** — Once, this quarter _[once; editorial recommendation]_
- [ ] **Start (or update) the operations manual: one hour a week with your most knowledge-concentrated person documenting clients, vendors and processes into a shared system.** — Weekly for the next quarter _[weekly; editorial recommendation]_
- [ ] **Run a data-recovery drill: rank customers from two years of invoices and pull all open prospects without relying on any one person's login.** — Once, this quarter; repeat annually _[once; editorial recommendation]_
- [ ] **Write and store the three crisis scripts: the customer/vendor continuity call, the senior-leader message naming the interim, and the all-hands update.** — Once, this month _[once; editorial recommendation]_
- [ ] **Hold a one-on-one with each senior leader to ask how they are doing and what would make them leave, so a resignation is never a surprise.** — Monthly _[monthly; editorial recommendation]_
- [ ] **Tell your team plainly that everyone is replaceable, that replacing them is not the plan, and that bringing value keeps them good.** — All the time (the speaker's wording); at minimum at every all-hands _[quarterly; speaker-stated]_
- [ ] **After any key departure, write the new strategy or system that stops it hurting the same way next time, before you move on.** — Immediately after each departure _[once; speaker-stated]_
- [ ] **Complete the personal identity audit (see the Move One session) and repeat it every year** — Once now, then annually _[annually; speaker-stated]_

## Questions to ask yourself

- If my most critical person quit on Tuesday morning, what would I not know how to do by Wednesday?
- Who in my company is 'institutional knowledge wearing a name badge', and what is written down?
- Do I have key-man insurance, an accurate operations manual and a ready second-in-command? Which of the three am I missing?
- Could I personally call my top customers within 24 hours and credibly guarantee continuity?
- Which of my senior leaders would assume they were next, and what would I have them own instead?
- If a long-tenured leader resigned tomorrow, would it be a surprise? If yes, why has nobody told me?
- Have I ever been given an ultimatum, direct or indirect, and what did I build afterwards so it cannot happen again?
- Does my team know they are replaceable, and that replacing them is not the plan?
- Am I the kind of person who leaves before the last exercise, or who goes home and does the work?

## Quotes

> “Look around real quick. This is the story of your life. The guys can't make it to the 25th hour because they wanted to be comfortable” — Patrick Bet-David (23:53:19 · WxJ71lw00yLq36jk6Rlz)
>
> Pointing at attendees leaving before the final exercise.

> “No keyman insurance, no accurate operations manual, no second-in-command ready to step in.” — Case study video narrator (23:56:56 · WxJ71lw00yLq36jk6Rlz)
>
> The three missing safeguards in the Hartwell case.

> “Greg wasn't just an employee, he was institutional knowledge wearing a name badge.” — Case study video narrator (23:57:00 · WxJ71lw00yLq36jk6Rlz)
>
> Why the VP's departure was a company-wide risk.

> “The culture Greg built starts cracking under one question nobody prepared to answer: Who's next?” — Case study video narrator (23:57:32 · WxJ71lw00yLq36jk6Rlz)
>
> The internal politics that followed the departure.

> “The systems and processes are in place to make sure that the quality of service that you're receiving is going to continue.” — Audience case respondent (CEO who lived the scenario) (00:07:21 · WxJ71lw00yLq36jk6Rlz)
>
> What he told customers on the calls that lost none of them.

> “To make sure that we always have a system that no one is irreplaceable.” — Audience case respondent (CEO who lived the scenario) (00:08:12 · WxJ71lw00yLq36jk6Rlz)
>
> The design goal of the SOPs and systems he built afterwards.

> “Don't call him into the office, don't go somewhere, go there hat in hand and go tell us what's going on.” — Audience case respondent (00:13:22 · WxJ71lw00yLq36jk6Rlz)
>
> How to approach the executive who quit, to learn what happened and secure a handover.

> “If someone worked there for eighteen years, it's no surprise that they quit if you're the CEO.” — Audience case respondent (00:14:47 · WxJ71lw00yLq36jk6Rlz)
>
> Arguing the case is a cultural failure, not a staffing event.

> “So in my mind, this guy quit mentally six, twelve, eighteen months ago.” — Audience case respondent (00:14:55 · WxJ71lw00yLq36jk6Rlz)
>
> Resignations are decided long before they are announced.

> “If you're running the ship and you lose your best guy and it's a surprise to you, then it's really time to pick up the mirror and look at yourself.” — Audience case respondent (00:15:39 · WxJ71lw00yLq36jk6Rlz)
>
> The leadership lesson in a surprise departure.

> “But I'm gonna call the customers, and I'm gonna let them know that I'm gonna be personally responsible for continuity.” — Audience case respondent (00:17:22 · WxJ71lw00yLq36jk6Rlz)
>
> The CEO's personal guarantee as the customer-retention move.

> “The question is what insurance policies you create for it not to happen the second time.” — Patrick Bet-David (00:18:24 · WxJ71lw00yLq36jk6Rlz)
>
> Turning the case from recovery to prevention.

> “If it happens second, third, fourth, fifth time, you're just not creating the right systems.” — Patrick Bet-David (00:18:30 · WxJ71lw00yLq36jk6Rlz)
>
> Repeated key-person losses are a systems failure.

> “I think you gotta create a vault, vault of knowledge.” — Audience case respondent (CEO with about 100 staff) (00:18:35 · WxJ71lw00yLq36jk6Rlz)
>
> The prevention system: knowledge the whole team can access, with two backups per role.

> “I don't like being given ultimatums in business, whether it's direct or indirect.” — Audience case respondent (CEO with about 100 staff) (00:19:13 · WxJ71lw00yLq36jk6Rlz)
>
> Why he built first and second backups for every role.

> “They need to know that they're replaceable, but that's not the plan.” — Audience case respondent (CEO with about 100 staff) (00:19:52 · WxJ71lw00yLq36jk6Rlz)
>
> How he sets expectations transparently with his team.

> “Whatever you do tonight, make that time for yourself.” — Patrick Bet-David (00:21:15 · WxJ71lw00yLq36jk6Rlz)
>
> The Day One closing challenge: finish the personal identity audit instead of going out.

## Watch-outs

- Letting one person hold every client, vendor and process in their head with nothing documented.
- Skipping key-man insurance and a second-in-command because the key person has 'always been there'.
- Treating a resignation as purely transactional and never asking what culture problem it exposed.
- Being surprised by the departure of an 18-year veteran; the surprise itself is the leadership failure.
- Focusing on clients and vendors while the four senior leaders inside form alliances and politicise meetings.
- Panic-hiring a replacement instead of using the data you already have and the leaders you already employ.
- Wiping a departed employee's accounts before recovering prospects and open conversations.
- Surviving the first key-person loss and building nothing so it happens a second, third and fourth time.
- Leaving the final session early, or going out instead of finishing the identity audit, and wasting the day's energy.

---

Cole's Notes Vault 2026 — https://vault.chels.ai — built by chels.ai (https://chels.ai). Only stage content is published; quotes are verbatim from automatic transcripts with light punctuation. Speaker-stated cadence and editorial recommendations are labelled separately. Times are Eastern; Las Vegas was three hours earlier.