What to do with a coaching program inherited after an acquisition.
Decide whether to continue, expand, or rationalize a coaching program the company inherited through acquisition, so the parent does not orphan or blindly clone the acquired stack.
The deal closed. About thirty people arrived with a coaching program already running. The parent is a few hundred people. Founders on the acquired side have stepped back. There is a new chairman, a new CEO a few months in, and the org chart is still moving. Nobody has said whether the inherited room continues, grows, or gets folded.
Stay on that decision. This is not a post-merger integration cadre. This is not years of overlapping catalog rooms. We will not invent an unused-seat percentage and we will not run a vendor bakeoff. The job is continue, expand, or rationalize so the parent does not orphan the stack or clone it by accident.
Inheritance is not a strategy. Leaving it running because the acquired shop liked it is how you get two stacks and no owner.
Thirty people arrived with a live program.
Operator pattern, not a cited sample. A parent in the mid-hundreds acquires a small shop and inherits their coaching. The acquired program was optional and encouraged. It never became how everyone in that shop grew. Those are design facts. They are not a utilization rate we will publish, and not a reason to declare the room a failure.
Optional that collapsed inside a larger program is a later policy fight (coaching as expectation, not an add-on). Who is invited versus waitlisted is access policy (nomination vs open enrollment). Benefit versus system is the trust split (is coaching a benefit or a talent system). Pick those after you decide the inherited room still exists on purpose.
New CEO, moving chart, two stacks.
Constant restructuring makes a quiet default feel expensive. The new CEO is still learning the floor. The chairman is new. The people who bought the coaching may no longer be in the building. A few hundred people is enough scale to need one operator (leadership development for 500-person companies). Two stacks with no named owner is how the acquired group feels forgotten and the parent feels billed for a mystery.
Post-acquisition culture fights show up as busyness and muddy promotion rules (busyness as success, raises vs promotions). Transitions need resilience, not a second catalog (resilience during transitions). If the parent still has no people-ops owner, that is a launch gate, not a reason to copy the room upward (do not launch people programs while head of people is empty).
No seat percentage. We will not estimate how many inherited chairs went unused. Optional-and-encouraged that never became the default is enough. Unused-seat math is how this page turns into a worksheet and leaves the decision.
Continue, expand, or fold.
Continue means the acquired group keeps the room, with a parent sponsor, while the rest of the company waits on a written decision. Expand means the parent wants that shape and will own matching, comms, and the week. Fold means the inherited stack ends on a date, or joins a parent progression you can already name. Recommendation, not a deal thesis: pick one this quarter.
Years of overlapping rooms inside one company is catalog work (rationalize a reactive L&D catalog). Do that after inheritance has an owner. Onboarding into the parent is not the same as cloning coaching (onboarding with coaching).
What this is not.
| If you are actually deciding | Go here instead |
|---|---|
| Years of overlapping rooms need a stage cut | Rationalize a reactive L&D catalog |
| Opt-in inside a live program collapsed | Coaching as expectation, not an add-on |
| Who is invited versus waitlisted | Nomination vs open enrollment |
| Head of people is empty and someone wants a wide launch | Do not launch while head of people is empty |
A history of yes is catalog rationalize. An empty people-ops chair is the launch gate. Come back here when the program arrived with the deal and nobody has said what the parent wants.
Name an owner and a default.
Write the three options on one page
Continue for the acquired group only. Expand a parent-owned version. Fold into whatever the parent already runs, or into nothing. If you cannot pick one this quarter, you are already orphaning it.
Say who owns it after the founders left
A new chairman and a new CEO do not automatically own a coaching stack that arrived with thirty people. Name a person. If people ops is thin, treat that as a launch gate, not a reason to copy the stack upward.
Reset optional-and-encouraged on purpose
If the inherited room never became how everyone grew, do not import that design as the company default. Expected, nominated, or benefit: pick the policy. Do not keep "encouraged" because that is how the deal found it.
SCALE can hold a parent-owned manager layer if expand is the call. GROW can hold a first-line room once the inherited shop is not a mystery stack. Do not buy either to sit beside a deal leftover you refused to decide.
What good looks like. Someone can say continue, expand, or fold in one sentence, with a name and a date. The acquired group knows whether their room survives. If the only change is another quarter of optional-and-encouraged, you orphaned it.
Decide the inherited room before it becomes a mystery.
Bring the acquired program, who still sits in it, and whether the parent wants that shape. We will map continue, expand, or fold. We will not invent a seat percentage.
Book a strategy callFrequently asked questions
We acquired a company that already had a coaching program. What should we do with it?
Decide on purpose: continue it for the acquired group, expand a version the parent will own, or rationalize it into one stack. Leaving it running because the deal included it is how you get two programs and no owner. Do not clone it company-wide by default.
Is this the same as rationalizing a reactive L&D catalog?
No. Catalog rationalize is years of overlapping rooms inside one company. This page is a live program that arrived with a deal. You may later cut twins. First you have to say continue, expand, or fold. Inheritance is not a history of yes.
The inherited program was optional and never reached everyone. Should we kill it?
Not on a utilization story. Optional-and-encouraged that never became the default is a design fact, not a seat percentage we will invent. Decide the parent's job for coaching, then keep, widen, or fold. Do not run unused-seat math on the acquired shop.
Is this an M&A integration playbook for a coaching cadre?
No. We will not write a post-merger integration curriculum or a vendor bakeoff. The job is the inherited program in front of you: who owns it now, who it is for, and whether the parent wants that shape.