Why Post-Close Leadership Teams Stall

The thesis was sound. The market was right. The management team had the résumés to back the growth plan. And eighteen months later, the numbers still came in short. Ask most operating partners what happened and the explanation usually lands on execution: the team moved too slowly, missed a hire, didn’t adapt fast enough. What rarely gets named is why execution slowed in the first place.

The Blind Spot in Standard 100-Day Plans

A typical 100-day plan is built around initiatives: systems to implement, roles to fill, processes to standardize. It answers what needs to happen. It rarely answers a quieter question that determines whether any of it happens on schedule: does this leadership team currently have the capacity to carry what the plan is about to ask of them.

Financial diligence tells a buyer whether the numbers are real. Commercial diligence tells a buyer whether the market opportunity is real. Neither one tells a buyer whether the organization sitting underneath the deal has room left to absorb a demanding value creation plan, or whether it is already running close to its limit before the ink on the deal is dry.

That gap is not carelessness. It is a measurement problem. Quality of earnings has a method. Market work has a method. Capacity has mostly had adjectives. Management assessment, where it happens at all, tends to be about individuals: is this the right CFO, can this COO scale. Fair questions. They are also questions about people rather than about the system those people work inside, and a strong operator inside a depleted system still returns a slow quarter.

A Value Creation Plan Is a Demand Schedule

Read the plan that way and it starts to look different. An ERP implementation is a demand. A pricing overhaul is a demand. Three add-on integrations, a new board reporting cadence, a rebuild of the sales comp model: each one is a demand, and each one lands on somebody who already had a full job the day before the deal closed.

The plan usually adds resource too. New hires, a new finance leader, a systems budget, outside help. The timing is the problem. Demand arrives on day one. Resource arrives on a hiring timeline. The months in between are the months the model assumes are productive.

Then there is the load nobody writes into the plan at all. Diligence questions keep arriving after close. The sponsor needs reporting the company has never produced. The board rhythm changes. Somebody has to explain the transaction to every layer below the leadership team, repeatedly, in the specific way that keeps people from leaving. None of that appears as an initiative. All of it is paid for in hours by the same handful of people the plan is counting on.

What Strain Looks Like Before It Shows Up in the P&L

Organizational strain has a well-established structure in the research literature. The Job Demands-Resources model, developed by Demerouti, Bakker, Nachreiner, and Schaufeli (2001) and refined over the two decades since (Bakker & Demerouti, 2007), describes every role and every organization in terms of two forces: the demands placed on it and the resources available to meet those demands. When demands consistently outpace resources, strain builds. It does not build evenly, and it does not show up on a dashboard right away.

Demands are the parts of the work that cost sustained effort: decision pace, competing priorities, ambiguity about who actually owns what. Resources are what make that effort payable: authority to decide, the information needed to decide well, enough people, real support from above. The more useful part of the model is the interaction between the two. Resources do not simply add to the good side of a ledger. They change what a given demand costs to carry.

So a demanding plan is not automatically a bad plan. The model says nothing about whether a demand is worth taking on. It says the demand has a price, the price is paid in resource, and a thinly resourced company pays more for the same plan.

What strain produces first is slower decisions, more rework, and leaders quietly absorbing load that should be distributed. Only later, once that strain has compounded, does it surface as missed targets, turnover in key roles, or a stalled initiative that never got the attention the plan assumed it would.

This progression matters because it means the P&L is a lagging indicator of leadership capacity, not a leading one. Alarcon’s (2011) meta-analysis, which reviewed 231 samples on the relationship between job demands, resources, and workplace attitudes, found demands to be a consistent and significant predictor of the kind of strain that eventually shows up as attrition and disengagement. In a portfolio company, that translates directly into missed milestones long before it shows up as a revised forecast.

The Signals That Arrive Before the Forecast Revision

If the sequence holds, the earliest evidence is not in the numbers at all. It is in the behavior around the numbers. These are the things worth watching in the first two quarters, before anything has moved enough to be worth a call with the deal team:

• Decisions that used to close inside a function start coming back up to the CEO.
• Initiatives get re-scoped rather than delivered, and the re-scope is described as prioritization.
• The same two or three names appear as the accountable owner on every workstream in the plan.
• A hire the plan depends on stays “in process” across a full quarter and nobody escalates it.
• Meetings get longer while the follow-through gets shorter.

No single item on that list proves anything. Each one has an innocent explanation, and any honest operator can name a company where all five were true and the year came in fine. The reason to watch them is cost. They are free to observe, and they are observable months earlier than the revision to the model.

Naming the Cost: Execution Drag and Commitment Drift

Two mechanisms tend to account for most of this gap between plan and delivery. The first, Execution Drag, is what happens when decision-making slows under strain, initiatives take longer than scoped, and leaders default to what is familiar instead of what the plan requires. The second, Commitment Drift, is what happens when key leaders start to disengage from the plan itself, still present, still capable, but no longer fully invested in seeing it through.

Execution Drag is not a discipline problem, and treating it as one makes it worse. Under load, the familiar option is cheaper to run and easier to defend, so that is the option a loaded system chooses. The practical consequence is specific: a team running near its limit will still hit its recurring commitments, because those are rehearsed. What slips is the part of the work the team has never done before. That happens to be most of what a value creation plan is made of.

Commitment Drift is quieter and more expensive. The failure mode is not conflict. It is agreement without intent. A leader who has privately concluded the timeline is not achievable stops arguing about the timeline, and the arguing was the signal. Nothing in a status report distinguishes a leader who agrees from a leader who has stopped pushing back.

Neither shows up as a line item. Both show up as Revenue at Risk: the dollar value of a value creation plan that is technically sound but is being executed by a team that does not currently have the capacity to deliver it on the assumed timeline.

Pricing it in dollars is a deliberate choice, and it is worth being blunt about why. Organizational strain competes for attention against every other item on an operating partner’s list, and it loses that competition every time it is described in the language of morale. Priced against the plan it is delaying, it becomes a sequencing decision, which is the only form in which it tends to get acted on.

Why the Same Plan Lands Differently in Two Companies

This is not an argument for slowing down deal timelines. It is an argument for adding one more lens to the ones already in use. Bloom and Van Reenen’s (2010) research across thousands of firms found that management practices vary enormously, even within the same industry and even among similarly resourced companies, and that this variance is one of the more persistent predictors of firm performance. Ownership structure matters here too: their data found that private equity-owned firms tend, on average, to be better managed than family-owned or founder-led firms, but “on average” leaves considerable room for the individual portfolio company that is the exception.

For anyone holding more than one company, the variance is the finding, not the average. If two businesses of similar size in the same sector, running comparable plans, can differ that much in how they are actually run, then the plan is not the variable doing the explaining. Something about the organization underneath it is. And a sponsor does not own the average. A sponsor owns this company, with this leadership team, at this level of load.

What Operating Partners Can Measure in Month One

The practical takeaway is that leadership capacity is not something that has to be inferred after the fact from missed targets. It can be measured directly, in the first 100 days, using the same framework Trajectory’s research is built on. Doing so gives an operating partner something a standard 100-day plan does not: an early view of which parts of the plan the current team can carry, and which parts will need additional resourcing before the timeline the model assumes is realistic.

Mechanically it is an anonymous survey the whole organization is invited to take, roughly fifteen minutes per person. The output is not a temperature reading. It is an Organizational Strain Index: a unit-level view of where strain sits, what is driving it there, and how severe it is, expressed in Revenue at Risk so that the sequencing argument can be had in the same units as everything else on the agenda. The full methodology lays out what the instrument measures and how the output is built.

Month one is the right moment for a reason that has nothing to do with urgency. Run it before the plan has changed anything and you get a baseline. Run it again later and the movement between the two readings is its own finding, which beats a single reading taken once somebody already suspected a problem.

What This Gives an Advisor Walking Into a Post-Close Engagement

Coaches and advisors brought in after close usually inherit the same starting position: a leadership team that has been told it needs support, a sponsor with a timeline, and no shared account of what is actually wrong. The first several sessions get spent building one out of whoever spoke most candidly.

A diagnostic run before the engagement changes what the first conversation is about. Instead of proposing a hypothesis and asking the room to validate it, an advisor arrives with a unit-level reading the room can argue with. Disagreement with the data is a better opening than agreement with a hunch, because it is specific. The Invisible Tax works through what that looks like for coaches in practice. For a single leader rather than a whole organization, Leadership Under Pressure is the 31-item version, and it returns a 4R capability profile and a depletion stage rather than a score.

This is also why Trajectory was built by two people rather than one. Matt Wilhelmi spent fifteen years in M&A advisory and fractional CFO work, across roughly 40 buy-side diligence engagements and about 5,000 owner intake interviews, which is a lot of exposure to the moment a company’s condition and its financials stop agreeing. Amy Wilhelmi came at the same problem clinically, through qEEG brain mapping and neurofeedback with executives who were stuck. One lens explains why the number moves. The other explains what is happening to the people it is moving through. The assessment they built together needed both.

Where to Start This Week

Before commissioning anything, there is a version of this you can run yourself in an hour, with no instrument at all.

Take the value creation plan. Write out every initiative in it, one per line. Next to each, put the name of the single person genuinely accountable for delivering it, not the sponsor and not the committee. Then count the repeats. In most post-close plans, a small number of names carry a disproportionate share of the list, and that concentration is visible immediately once it is written down.

Then add a second column. For each initiative, write what that person got that they did not have before the deal closed: headcount, authority, budget, a decision they no longer have to escalate, an hour back somewhere. If the second column is mostly empty while the first column keeps repeating the same three names, the plan is a demand schedule with no resource schedule attached, and the timeline in the model is a hope rather than a forecast.

That exercise will not tell you how severe the strain is or which unit is carrying it. It will tell you whether the question is worth measuring properly. If it is, the measurement is available before the first quarterly review, not after the third. Revenue at Risk shows the full version of that measurement run across a multi-site platform, including how the strain was translated into dollars.

Diagnose the system before it has a chance to quietly determine the return.

References

Alarcon, G. M. (2011). A meta-analysis of burnout with job demands, resources, and attitudes. Journal of Vocational Behavior, 79(2), 549-562.

Bakker, A. B., & Demerouti, E. (2007). The Job Demands-Resources model: State of the art. Journal of Managerial Psychology, 22(3), 309-328.

Bloom, N., & Van Reenen, J. (2010). Why do management practices differ across firms and countries? Journal of Economic Perspectives, 24(1), 203-224.

Demerouti, E., Bakker, A. B., Nachreiner, F., & Schaufeli, W. B. (2001). The job demands-resources model of burnout. Journal of Applied Psychology, 86(3), 499-512.