The first hundred days post-close have a standard shape. You assess the management team, confirm the thesis against what diligence couldn't see, and lock the value-creation plan. Then, once you know who's running what, the workstreams start. Diagnosis first, execution after.
That sequence feels disciplined. It's also where the hold period starts leaking time.
The problem is that the two halves run on different clocks, and treating them as one sequence forces the fast clock to wait on the slow one.
Two clocks, not one
Assessing a management team is slow work, and it should be. You're deciding who stays, who owns what permanently, where the real gaps sit under the org chart you inherited. Rushing it produces exactly the wrong calls: keeping someone you should move, moving someone you should have backed. The assessment clock runs at the speed of good judgment, and good judgment here takes most of the quarter.
The execution clock doesn't have that quarter. The value-creation plan has a return tied to a date you set at close. The initiatives diligence already confirmed, the pricing work, the cost program, the systems the thesis depends on, don't get more valuable for waiting on an org decision. Every week they sit behind the assessment is a week off the end of the hold.
When you run these as one sequence, the fast clock loses. Execution waits behind assessment because the same people are supposed to do both, and they can't.
The team you inherited is already full
This is the part the sequential model ignores. The management team running the business is running the business. They're at capacity on the day you close, because the company was operating before you owned it. The value-creation plan is net-new work landing on top of a full load, with no slack to absorb it.
So one of two things happens. The plan waits, formally or quietly, until the team has bandwidth that never materializes. Or the team carries the day job and the transformation at once, and does both at a level that disappoints. Neither is a planning failure. Both are a capacity failure wearing a planning failure's clothes.
The reframe is to stop treating the first hundred days as a window for diagnosis and start treating it as a window for capacity. The question isn't only who's good and who stays. It's who does the net-new work while you're still answering that.
Decouple the clocks with capacity that starts now
You separate the clocks by adding capacity that runs the execution clock while the assessment clock takes its time.
Where a function has no head, or a head you're not yet sure of, an interim leader owns it from week one. They run the gap while you make the permanent call without the pressure of a vacancy forcing your hand. The assessment gets the time it needs precisely because the seat is covered.
Where the work is confirmed but specialized, on-demand specialists start the diligence-backed initiatives without waiting on the org to settle. The cost program, the pricing model, the reporting build: these need a specific depth, not a permanent line on the chart, and they can be in motion in weeks rather than waiting on a search.
The permanent hires still come. They just come on the slow clock, when you actually know the shape of the team the steady state requires. You're not choosing between assessing carefully and executing fast. You're refusing to make one wait on the other.
"Isn't that premature?"
The reasonable objection is that bringing in outside capacity before you've assessed the team is getting ahead of yourself, and possibly paying twice. If the permanent hire ends up owning the work, why fund an interim or a specialist to start it.
Because the two aren't the same commitment. A permanent hire is a bet you place when you know the role and the person, and it's expensive to unwind if you're wrong. Interim and on-demand capacity is scoped to the work and reversible by design. It ends when the assessment resolves or the workstream closes, whichever comes first. That's not a hedge against the permanent decision. It's what lets you make the permanent decision well, because you're choosing the long-term team from a position where the work is already moving instead of from under a backlog.
The genuine waste isn't the capacity you add in week one. It's the month-four scramble, where you pay a search premium under time pressure, accept a longer ramp because the gap is now urgent, and watch a year-one initiative slide into year two. Measured against that, scoped capacity at the start is the cheaper line.
The portfolios that miss
The portfolios that come up short on plan rarely got there with a weaker thesis. They got there on timing.
The familiar version: the plan is sound, the team is willing, and for the first quarter everyone is heads-down on integration and the day job. The capacity gap surfaces in month four, when a workstream that should be live hasn't started and the plan is already a quarter behind. That's when the permanent search begins, which means a leader lands around month seven, ramps through month nine, and the initiative that was supposed to drive year-one value starts driving it in year two.
None of that reads as a crisis in the moment. It reads as things taking a little longer than hoped. But the hold period is the one clock you don't control, and time conceded in the first hundred days doesn't come back later in the deal. It compounds the wrong way.
The first hundred days are where you bank time or lose it. The portfolios that bank it treat capacity as the day-one decision and let the assessment take the quarter it deserves. The ones that lose it run the two in sequence and find the cost in month four, when it's already spent.