PE Firms Spend $500K on Due Diligence and $0 on Asking Management What Is Actually Working

Every PE board meeting I have ever sat through follows the same script. The CEO presents the deck. The sponsor asks about the numbers. Everyone is polite, professional, and roughly 60% honest. The real conversation happens in the hallway afterward, or on the drive home, or not at all.

The CEO thinks the sponsor is too focused on short-term EBITDA. The sponsor thinks the management team is moving too slowly on the integration. Neither says it. Instead, the CEO adds two more slides to next quarter’s deck, the sponsor schedules another “check-in call,” and the misalignment quietly compounds for another 90 days.

I came into private equity from software. I ran Two Toasters, a mobile development firm, and later served as VP of Mobile at Ticketmaster. In those environments, the idea of working alongside a team for five years with no structured mechanism for honest, two-way feedback would be considered negligent. We had a name for the tool that prevented exactly this kind of slow-motion communication failure: the retrospective.

PE does not have one. It should.

Private equity has the most rigorous pre-investment process of any asset class. Quality of earnings. Operational assessments. Management evaluations. Market studies. Legal diligence. Environmental diligence. Insurance diligence. Firms will spend $500K or more making sure they understand a business before they write the check.

Then they govern a five-year, multi-million dollar partnership with a quarterly PowerPoint and good intentions.

The best PE boards do better than that. They maintain active communication through regular CEO calls and monthly business reviews, with quarterly meetings structured as forums for strategic debate.¹ But even the best version of this model has a fundamental limitation: it is all top-down. The sponsor sets the agenda. The management team reports against it. Information flows up. Directives flow down. There is no structured mechanism for the management team to say, “Here is what is not working in how we are working together.”

And so things fester. The CEO who feels micromanaged on hiring decisions but does not want to seem combative. The operating partner who suspects a pricing initiative is stalled but cannot tell whether the issue is execution or strategy. The CFO who is spending 20 hours a month on reporting that nobody reads but is afraid to push back on. These are not crises. They are hairline fractures. And hairline fractures, left unaddressed, become breaks.

The data bears this out. Over 70% of CEOs at PE-backed companies are replaced during the average holding period, and 55% of that turnover is unplanned.² Nearly half of PE firms say unplanned CEO turnover directly erodes their rate of return.³ And here is the number that should keep sponsors up at night: 17% of portfolio company executives report experiencing major operational challenges specifically due to a clash of working styles with their PE investors.⁴

Not a clash over strategy. Not a disagreement about markets. A clash of working styles. The kind of thing that surfaces in a 60-minute conversation, if anyone ever structures one.

Bain & Company found that just under 50% of CEO replacements at PE-backed companies were outcomes the PE firm had not anticipated when the relationship began.⁵ They did not see it coming. Which means nobody created the conditions for them to see it coming.

What Software Figured Out

In software development, we had the same problem in microcosm. A team of engineers working on a complex product, under time pressure, with imperfect information and different assumptions about priorities. If you just let them build and checked in every few weeks to review output, small misunderstandings compounded into wasted sprints, misaligned features, and frustrated teams.

The agile movement solved this with a practice called the retrospective: a regular, structured conversation where the team asks three questions. What went well? What did not go well? What should we change? It happens at the end of every sprint, whether things are on track or not. Teams that do it consistently show 24% higher responsiveness and 42% greater quality than teams that skip it.⁶

The critical difference between a retrospective and a post-mortem is timing. Post-mortems happen after the damage is done. Retrospectives happen while you can still do something about it.⁷ PE firms are full of post-mortems: the deal team debrief after an exit, the lessons learned after a management blowup, the “what would we do differently” conversation at the annual offsite. These are all too late. The question is not whether you can learn from what went wrong. The question is whether you can build a system that catches it while it is still cheap to fix.

Why This Is a Hold Period Problem

The hold period has never been longer. Median holding periods for PE-backed companies have reached 5.8 years, the longest on record.⁸ That is not a transaction timeline. That is a relationship timeline. And relationships require a different kind of governance than transactions.

Yet the governance toolkit has barely evolved. Fewer than two in five portfolio companies perform regular performance assessments. Only about a quarter have succession planning programs. As AlixPartners’ Ted Bililies put it, “For old-school PE firms, talent management is an afterthought.”²

At the same time, returns increasingly depend on operational improvement, not financial engineering. Elevated interest rates mean sponsors cannot rely on cheap debt to stretch equity value.⁹ Multiple expansion is not a plan. The firms that outperform are the ones that actually improve how portfolio companies operate. And you cannot improve operations if the people doing the operating do not have a safe, structured way to tell you what is broken.

RSM described a portfolio client that was running 75 supposedly strategic projects, many off-budget and behind schedule. With support, the executive team cut that to 20 priority efforts aligned with EBITDA and growth targets.¹⁰ That kind of initiative sprawl does not appear overnight. It accumulates in the silence between board meetings. A monthly retrospective would have surfaced the problem at 30 projects, not 75.

The Portfolio Company Retrospective Framework

Here is what I believe this looks like in practice. Three retrospectives at three cadences, each designed to catch a different kind of problem.

Level 1: The Operational Retro

Monthly. 60 to 90 minutes. CEO and functional leaders. Sponsor rep observes, does not drive.

Format: Start / Stop / Continue. What should we start doing? What should we stop doing? What is working and should continue?

This is the workhorse. It catches the operational problems that fester in the gaps between board meetings: a vendor relationship going sideways, a key hire underperforming, a technology implementation the team has lost confidence in, bottlenecks nobody wants to own. The critical rule is that the management team runs this session. The sponsor representative listens and asks questions. If the sponsor drives the agenda, it becomes another reporting exercise, and you lose the honesty that makes it valuable.

The core question: “What did we learn this month that should change how we execute next month?”

Quarterly. 60 minutes. Deal team lead, CEO, CFO. Separate from the board meeting.

This is the retrospective that almost nobody in PE conducts, and it may be the most valuable one. The board meeting is about the business. This session is about the partnership.

Schedule it the day before or after the board meeting, but keep it explicitly separate. The board meeting is about numbers. This conversation is about how the relationship is functioning. It is where the CEO can say, “I need more runway on hiring decisions” and where the sponsor can say, “I need earlier signals when initiatives are off track.” It is where you learn that the management team is spending 15% of its time on reporting they think nobody reads. Or that the sponsor team has concerns they have been discussing internally but have not raised directly.

Remember: 17% of portfolio company executives cite working-style clashes with investors as a source of major operational challenges. Those clashes build quietly. This retro is designed to surface them when they are still frictions, not fractures.

The core question: “Where are we aligned, and where are we not?”

Level 3: The Strategic Retro

Semi-annual. Half day. Full board, management team, key functional leaders.

Format: the Sailboat method. Map the business onto a sailboat and ask four questions:

Wind: What is propelling us forward? Market tailwinds, successful initiatives, advantages proving out.
Anchor: What is holding us back? Internal friction, capability gaps, resource constraints, cultural resistance.
Rocks: What risks lie ahead? Market shifts, competitive threats, regulatory changes, key-person dependencies.
Island: What is our destination? The value creation thesis and exit readiness targets.

This is the big one. It is where you pressure-test whether the original investment thesis still holds, which diligence assumptions turned out to be wrong, and whether the value creation plan needs fundamental revision. As holding periods extend, strategy pivots become almost inevitable, and PE firms need to know whether the current leadership team can deliver revised outcomes. Leadership needs space to flag when the original plan no longer fits reality.²

The core question: “Is our thesis still right, and what have we learned that should change our plan?”

The One Rule That Makes It Work

Every retrospective, regardless of level, starts with the same statement. It is called the Prime Directive, and it comes from Norman Kerth’s Project Retrospectives (2001):

“Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.”¹¹

In a PE context, where the sponsor controls the cap table and the management team knows it, this is not a nicety. It is the mechanism that makes honesty possible. It is what allows a COO to say, “The SIOP implementation you asked us to prioritize is not working because we do not have the right people to run it,” without fearing that the next board meeting includes a discussion about replacing the COO.

Without it, retrospectives produce the same sanitized, tell-them-what-they-want-to-hear feedback that board meetings already generate. With it, you get something PE governance almost never produces: the unvarnished operational truth.

How to Start

Pick one portfolio company. Choose one where the relationship is healthy. Retrospectives require trust. Do not introduce them where trust is already broken.

The facilitator cannot be the deal lead. The person running the session should not be the person who controls compensation or board seats. An operating partner, a portfolio ops team member, or an external facilitator works. The deal lead participates but does not run it.

Start with Level 1 only. Get the monthly operational retro working. Let the team build the muscle of structured reflection before layering in the more sensitive sponsor-management conversation.

Follow through on one thing. The single fastest way to kill a retrospective program is to collect feedback and change nothing. If the team raises three issues and you act on even one visibly and quickly, you earn the credibility that makes the next session ten times more productive.

Track themes, not just action items. If “communication between sales and operations” shows up three months running, that is not an action item. That is an organizational design problem. The retrospective surfaces the pattern. It is still your job to solve it.

The Question Worth Asking

PE is in a period where operational value creation is the whole game. Sponsors need to be closer to their portfolio companies than ever. But closer does not mean more board decks, more KPI dashboards, more oversight. Those are top-down instruments, and there are diminishing returns to adding more of them.

What is missing is a bottom-up feedback loop. A structured, recurring, psychologically safe conversation that catches problems while they are still cheap to fix and keeps the sponsor-management relationship honest over a five-year hold.

The next time a portfolio company CEO leaves and your deal team says they did not see it coming, ask yourself: did you ever create a space where they could have told you?

The author is a partner at Amalgam Capital, an independent sponsor focused on acquiring and operating lower middle market businesses in industrial services and manufacturing. Before entering private equity, he built and led technology teams at Two Toasters and Ticketmaster, where structured retrospectives were a core part of how teams shipped products and improved continuously.

If you have experimented with retrospectives or similar feedback loops in your portfolio companies, I would welcome the conversation. Reach out to compare notes on what is working.

NACD, “Unlock Value Through Governance in Private Equity Portfolio Companies,” 2026 Governance Outlook (December 2025). nacdonline.org ↩
Heidrick & Struggles, “Closing the Leadership Gap in Private Equity” (2025). heidrick.com ↩ ↩² ↩³
Russell Reynolds Associates, “Dispelling Common CEO Myths: Six Lessons for PE Leaders and Portfolio Company CEOs” (2025). russellreynolds.com ↩
Russell Reynolds Associates, “The Leadership Tapestry of Industrial Portfolio Companies” (October 2025). russellreynolds.com ↩
Russell Reynolds Associates, “Dispelling Common CEO Myths” (2025), citing Bain & Company research. ↩
Adobe, “Agile Retrospectives: A Complete Guide” (2025). business.adobe.com ↩
Capco, “Agile Retrospectives for Non-Agile Teams” (2025). capco.com ↩
Private Equity Info, “Holding Periods Continue to Grow, but Could Peak in 2025” (February 2025). privateequityinfo.com ↩
Brookfield, “Driving Private Equity Returns with Operational Know-How” (August 2025). brookfield.com ↩
RSM, “Professionalizing Private Equity Assets in Extended Holding Periods” (2025). rsmus.com ↩
Norman L. Kerth, Project Retrospectives: A Handbook for Team Reviews (Dorset House Publishing, 2001). ↩

The $500K Blind Spot