Building a management team you didn't hire

A management team that did not choose you is loyal to the person who sold the business, and that is normal rather than a warning sign. It is also information: the loyalty is a measure of how the previous owner led, and understanding that style tells you which of your own behaviours will read as reassuring and which will read as a threat. An owner who never delegated leaves managers who wait for instruction; one who delegated everything leaves managers who resent being asked questions.

The listening round is the instrument. Every manager, individually, with a consistent question set: what works here, what is broken, what have you wanted to change and not been able to, what would you do first if you were me, and what do you want from the next two years. Ask it before you form a view, because you only get honest answers once. Have a short list of things you will not promise — job security, no changes, specific pay — and hold it, because a promise made in a first-month conversation is remembered for years.

'Change nothing for ninety days' is folklore and it circulates as advice because it is directionally protective. The useful content is its exceptions: cash bleeding, a safety issue, a departing key person, and an actively toxic manager. The last is the one people hesitate on longest, and the hesitation is expensive, because a toxic manager in a fifty-person business is visible to everyone and your tolerance of them is being read as a statement about you.

Run the key-person concentration question in parallel. Which individuals, if they left in month two, break the business? The answer often includes people who are not on the management team at all, and it changes the retention conversation from a general one into a specific one about four or five names.

The mistake that costs the most is assessing inherited managers against the people you would have hired. You did not hire anyone; you bought a business that already works, and it works partly because of these people. The useful comparison is between the manager and the seat: write the accountabilities for the seat first, in the terms the business actually needs, and then ask whether this person can own those outcomes with support that is realistic to give.

Writing the seat first also fixes a common misdiagnosis. Many inherited managers look weak because they have never had a defined seat — they hold three functions that pull against each other, no written decision rights, and no basis on which to say no to the owner. Give them one seat with clear accountabilities and a stated authority limit and a meaningful proportion of them become visibly competent within a quarter. That is a cheaper outcome than replacement and a better one.

Where the gap is real, name it precisely. The most common genuine gap in this band is the technician who was promoted for being the best at the work: excellent practitioner, uninterested in and unequipped for managing people. That is a structural problem you created by having only one promotion path, and the fix is a technical ladder that pays for excellence at the craft alongside a management ladder that requires different competencies.

For the general-manager seat specifically — the second-in-command who runs the business day to day — treat it as the decision that determines whether you bought an asset or a job. It is worth being slow and explicit about, it is worth an interim appointment with a review date, and it is worth interviewing external candidates even when you intend to promote, because the comparison is what makes an internal appointment defensible to everyone including the person appointed.

Written decision rights do more for an inherited management team than any development programme. Most of these managers have operated for years inside an unwritten understanding of what they could decide, and that understanding died with the ownership change. Restating it explicitly — what each seat decides alone, what it decides and reports, what it recommends and waits on — removes an enormous amount of hesitation that looks like passivity and is actually uncertainty.

A performance review in a business this size is not the instrument the software vendors describe. There is no human-resources department, the reviewer is the owner, and the person being reviewed may have been there nineteen years and have watched the reviewer arrive. What works is short, frequent, specific and forward-looking: what the seat achieved against its stated outcomes, what changes next period, and what support is needed. Annual, form-heavy, backward-looking review processes designed for large employers fail here for structural reasons rather than because anyone executed them badly.

The management cadence is the container in which all of this becomes real. A weekly leadership meeting with the seat owners present, a standing agenda and a protected block for solving issues does more to build a management team than any offsite, because it is where accountability is exercised in front of peers rather than in private. Introduce it slowly and run it identically for a quarter before changing it.

The same logic applies to process adoption. Getting an inherited team to follow a written procedure is a different and much harder problem than writing one, and the mechanism is the same as the scorecard's: the procedure is referenced in a meeting the owner attends, compliance is visible, and deviation has a consequence. Every framework publishes the artifact; almost nobody publishes the adoption failure modes.

Retention arrangements for inherited managers are worth designing rather than improvising. A stay arrangement tied to a date buys time and buys nothing else; a revised compensation structure tied to the outcomes of a newly defined seat buys engagement, because it tells the manager what the job now is as well as what it pays. If you are going to revise comp anyway, revise it against the accountability chart rather than against tenure.

One legal point that is worth getting right, because getting it wrong is an active liability. Restrictive covenants on your management team are governed by state law. The federal rule that received enormous coverage was not left standing — the Commission acceded to its vacatur in September 2025 — and any plan built on the assumption that a national standard now applies, in either direction, is built on sand. Check the law in the states where your people actually work before relying on any covenant you inherited.

Compensation banding is where this page has to stop short of what would be most useful. Honest bands need occupational wage data by role and metro, and the agency that publishes it is currently unreachable. What is publishable is the internal discipline: similar seats paid similarly, a ladder that makes sense when employees compare notes, and any legacy anomaly either justified or corrected deliberately rather than left to be discovered.

Measure turnover from your first month, split voluntary from involuntary, and read it against your own trend. There is no sourced figure for what turnover is reasonable after an ownership change, and every number circulating for it is a general workforce statistic applied to a situation it does not describe. Your own baseline is more informative than any of them, and after four quarters it is the only thing that tells you whether the team you have built is holding.