Management Assessment · Project Halyard
So this is an honest read on whether they can. Who scales with the thesis, who is in the wrong seat, and the two seats that decide your first year.
The read
Placed against the plan you are underwriting, this team splits cleanly. Three you back without hesitation. Two you support and strengthen. One is the right person for last year. And one seat has to change before the value creation plan has anywhere to land. The grid is where each of them sits.
Two of the seven decide your first year: the COO you cannot lose, and the HR seat you have to change. Everything else is a question of sequencing, not survival.
The team, one by one
Got the business here. Reads the market, sets direction, and people follow him. The gap is a real number two, so he can stop running operations by reflex. Back him, and build the bench underneath him in year one.
The reason the business runs, and the single largest key-person risk on the deal. Backs the plan and scales with it. Cannot be lost in the transition, which means retention and documentation come before the announcement.
A strong controller running a finance function built for reporting, not for a sponsor. Trustworthy with the numbers, not yet a value-creation partner. Support with a stronger FP&A layer, or plan the upgrade by year two.
Delivers the number today and will tell you that is enough. It is not. The commercial engine is him, not a system, and the plan needs a repeatable motion he has never built. The right person for last year.
The most underrated person on the team. Runs the hardest region, quietly, and is ready for more than the org has given her. The one to promote into the number-two conversation the CEO needs.
Administrative, not operational. Keeps the function compliant and the tickets closed, which is not the same as running people as a lever. This seat has to change for the value creation plan to have anywhere to land.
Stretched across systems bolted on with each acquisition. Capable, and quietly the highest flight risk on the team, because the market wants him more than the business has noticed. Retention conversation belongs in month one.
The seven above are only the top of it. The manager layer that actually delivers the plan is thin and was trained to hit a number, not run a business. That read sits in the diligence memo and the operating model, not here.
Where it breaks
Lose her in the transition and the operating memory goes with her. This is the retention conversation you have in week one, before the announcement, not the one you get to in month three.
An administrative function cannot deliver an operating plan. Upgrade the seat to an operator, or the value creation work has no owner and quietly becomes a slide nobody actions.
He hits the number now and blocks the system that scales it. Move before the growth plan depends on a motion he has never built, and move on your timeline rather than his.
The moves · if you proceed
Protect the COO in week one. Retention agreement and a documentation sprint, before the announcement makes her a target for every recruiter watching the deal.
Promote the VP of Operations toward the number-two seat. The bench the CEO needs is already in the building. Back her before the market notices her first.
Upgrade the HR seat to an operator. Not a bigger administrator. The person who owns whether the value creation plan clears the management layer.
Plan the CRO transition on your timeline. Keep the number this year, build the engine underneath him, and make the move before the plan is betting on it.
Have the IT retention conversation in month one. The highest flight risk on the team is the one holding systems nobody else understands. Do not let that surprise you in quarter two.