Operating partners and deal teams don’t always agree, particularly once an operating partner has spent real time inside a portfolio company and has developed a view that differs from the original deal thesis. 

Handling that disagreement well, without becoming the person the deal team quietly stops listening to, is aN important skill that gets less attention than it deserves. 

The pattern that damages an operating partner’s standing fastest is disagreeing in a way that implies the original deal thesis was simply wrong, rather than acknowledging that circumstances have evolved or that operational reality has revealed something the original diligence process couldn’t have caught. 

Deal teams, understandably, have some emotional investment in the thesis they built and sold internally, and a disagreement framed as “you got this wrong” tends to produce defensiveness rather than genuine reconsideration, even when the underlying substance of the disagreement is entirely sound. 

The version that tends to land better is framing the disagreement around new information rather than original error: “here’s what we’ve learned since close that the original thesis couldn’t have accounted for, and here’s what I think that implies for the plan going forward.” 

This isn’t spin, it’s usually simply true, since most operational disagreements really do stem from information that’s only become available after spending real time inside the business, not from the deal team having been careless originally. 

The other important discipline is picking genuinely substantive disagreements to raise directly, rather than raising every minor difference of opinion with equal intensity. 

An operating partner who disagrees loudly and often on small things trains the deal team to discount their input generally. An operating partner who’s selective about which disagreements genuinely warrant a direct challenge tends to be taken far more seriously on the ones that matter, precisely because the deal team has learned that when this person pushes back, it’s usually worth listening to closely.

Board packs tend to be comprehensive about the past and the present, revenue, margin, pipeline, current initiatives, and considerably thinner on one specific thing that would make almost every board conversation sharper: a slide dedicated explicitly to what the management team is genuinely uncertain about right now, laid out as openly as the confident parts of the deck. 

Most board packs implicitly present a fairly confident narrative throughout, even where genuine uncertainty exists underneath, because uncertainty is harder to present crisply than a clean number with a clear trend line. This isn’t dishonesty, it’s simply the natural pull of a presentation format toward confident, resolved statements. 

The cost is that boards end up discussing the parts of the business that are already well understood, because those are the parts that photograph well in a deck, and spend comparatively less time on the genuinely uncertain parts, which are exactly where board input is most valuable. 

A dedicated “here’s what we’re genuinely unsure about” slide inverts this default. It gives the management team explicit permission to present open questions without it reading as weakness, and it gives the board a clear, deliberate prompt to spend meeting time on the areas where genuine input, rather than passive confirmation, is actually useful. 

Management teams that adopt this habit consistently tend to report that these specific slides produce the most valuable board discussion of the entire meeting, precisely because it’s the one moment in the deck built explicitly for genuine two-way problem solving rather than one-way reporting. 

The practical version: add a standing agenda slide, “open questions we don’t have a confident answer to yet,” and populate it honestly every meeting, even when the honest answer is a short list. It’s a small addition that tends to change the character of the whole meeting. 

Funds that use operating partners across multiple deals tend to have a fairly consistent internal view, rarely stated explicitly but easy to observe, about which operating partners they’ll happily bring back onto the next portfolio company and which they quietly stop calling. 

The difference between the two groups is less about raw talent or experience than it might seem, and more about a specific, learnable pattern of behaviour. 

Operating partners who get invited back consistently tend to leave management teams in a better position than they found them, not just in terms of the specific metrics that improved, but in terms of the management team’s own capability and confidence going forward. 

They tend to solve problems in a way that builds the internal team’s ability to solve similar problems themselves next time, rather than creating a management team that becomes dependent on the operating partner’s continued involvement to function. 

This is worth naming directly because it cuts against a natural incentive: an operating partner whose value is obviously visible and ongoing has an easier time justifying their continued engagement than one who’s made themselves progressively less necessary. 

The best operating partners resist that incentive anyway, because funds notice the difference over multiple deals even if any single portfolio company doesn’t. 

The second consistent pattern among operating partners who get invited back is candour with the deal team and the board, even when that candour is uncomfortable. 

Operating partners who consistently tell the board what it wants to hear, rather than what’s actually true, provide short-term comfort and long-term risk, because a board that’s been quietly misled about the state of a portfolio company eventually finds out, usually at a worse moment than if the truth had surfaced earlier. 

Funds remember which operating partners gave them the unwelcome truth early and which ones let a problem grow before finally admitting it existed. 

Neither of these patterns requires exceptional talent. Both require a specific discipline, building capability rather than dependency, and telling the truth even when it’s uncomfortable, that’s genuinely learnable and worth deliberately practising rather than assuming it comes naturally with experience. 

Every board eventually has to have the conversation nobody’s looking forward to. 

A management performance issue that needs addressing directly, a plan that’s genuinely off track and needs to be said out loud rather than softened, a relationship between two senior people that’s become a real problem for the business.

How these conversations get handled tends to shape the trust in a boardroom for a long time afterward, in either direction. 

The most common mistake is delay dressed up as diplomacy. 

A board that senses a difficult conversation coming often finds reasons to wait one more meeting, gather one more data point, let the situation “develop a bit further” before addressing it directly. 

Almost every retrospective on a difficult board situation includes some version of “we probably should have said something a meeting or two earlier,” and almost never the reverse. 

The second most common mistake is addressing the issue obliquely rather than directly, through hints and generalised commentary rather than a specific, named concern. 

This feels kinder in the moment and is usually worse in practice, because the person on the receiving end either doesn’t register that a serious concern is being raised at all, or registers that something’s wrong without understanding specifically what, which tends to produce anxiety without producing the behaviour change the board actually wants. 

The practical discipline: when a difficult conversation is clearly needed, have it directly, specifically, and as early as the concern becomes real rather than waiting for more certainty. State the specific concern, state what change would address it, and be clear about the timeline for seeing that change. 

Boards that develop a reputation for handling this well, directly but respectfully, tend to get more candour back from management teams over time. Boards that avoid or soften these conversations tend to train their management teams to hide problems rather than surface them, which is a far more expensive outcome than any single uncomfortable meeting.

Credibility with a management team isn’t something you arrive with, regardless of your track record elsewhere, and treating your CV as sufficient credibility is one of the more common mistakes new operating partners make in their first few months on a portfolio company. 

What actually builds credibility in the first 90 days is a small number of specific, visible wins on things the management team already cared about before you arrived, not a demonstration of broader strategic capability. 

This is a point worth repeating because it cuts against instinct. The instinct, especially for an experienced operating partner, is to demonstrate range, show the management team the full breadth of what you can help with.

The management team, meanwhile, is watching for something much narrower: can this person actually help with the two or three things that have been genuinely stuck, and will they do it without making the management team feel diminished in the process. 

The sequencing matters more than most people expect. 

Spend the first few weeks primarily listening and asking specific, well-informed questions rather than proposing solutions, even where a solution seems obvious early. 

Management teams that have been burned by previous operating partners are watching closely for whether you’re genuinely trying to understand the business or whether you’ve already decided what the answer is and are just going through the motions of asking. 

Once you’ve identified one or two specific, real problems the management team already recognises as problems, solve those visibly and completely before moving on to anything more ambitious. 

Credibility built this way compounds. 

Credibility assumed on the basis of a strong CV tends to erode the first time it’s tested and found wanting.

You know the board meeting. Ninety minutes, forty slides, most of it a narrated version of numbers everyone already read in the pre-read, and about twelve minutes of actual discussion squeezed in at the end when everyone’s mentally checked out and needs to be somewhere else. 

The reason this format persists isn’t that anyone thinks it’s good. It’s that changing the format feels riskier than keeping a familiar one, even a bad one, and management teams under pressure default to the safe, familiar structure rather than the better one. 

The fix is less complicated than the inertia around it suggests. Send the deck properly in advance, with enough time that board members actually read it rather than skim it in the taxi on the way to the meeting. Then spend the actual meeting time almost entirely on discussion, not narration. If someone hasn’t read the pre-read, that’s their problem to solve before the meeting, not something the meeting should be restructured around. 

The other change worth making, and it’s a small one that has an outsized effect on meeting quality: put the hardest, most uncomfortable topic first on the agenda, not last. Boards that bury the difficult conversation at the end of a long meeting either run out of time to discuss it properly or discuss it when everyone’s already tired and wanting to leave. The uncomfortable topic deserves the freshest attention in the room, not the leftover twelve minutes. 

Boards that make these two changes tend to notice the difference within a meeting or two. The meeting gets shorter, the discussion gets sharper, and the CEO stops dreading the thing that’s supposed to be a genuine working session with the people who can actually help.

Every fund’s website says the same thing about its operating team. Deep sector expertise, hands-on support, value creation beyond capital. It’s true often enough to keep being said and vague enough to mean almost nothing to the CEO actually receiving that support. 

Ask a management team what “adding value” has actually looked like from previous operating partners and the answers cluster into two very different categories. One category is genuinely useful: unblocking a stuck hiring process, making an introduction that turned into a real customer, spotting a pricing error before it compounded, helping resolve a genuine disagreement between the CEO and CFO before it calcified into dysfunction. The other category is well-intentioned but hollow: strategy workshops that produced frameworks nobody used, dashboard requests that added reporting burden without adding insight, generic advice that could have applied to any company in any sector. 

The difference between the two categories usually isn’t intelligence or effort. It’s specificity. Value that actually lands is almost always narrow, concrete, and tied to something the management team was already stuck on, not something the operating partner decided was strategically important from the outside. Value that doesn’t land tends to start from a framework and go looking for a problem to apply it to. 

The practical test, if you want to check which category you’re operating in: after any piece of work with a portfolio company, ask yourself honestly whether the management team could describe, in one sentence, what specifically changed because of your involvement. 

If the honest answer is a strategic framework or a set of recommendations, you’re probably in the second category regardless of how sound the analysis was. If the honest answer is a specific decision that got made differently or a specific problem that got solved, you’re in the first. 

Most operating partners who get invited back to the next portfolio company are the ones who can consistently give the second answer, not the ones with the most sophisticated frameworks.

A growth story is a coherent narrative about why a business should grow, usually built around a genuine market opportunity, a real product advantage, or a defensible position with customers. 

A growth plan is a specific, resourced, sequenced set of actions that will actually produce that growth. Both are necessary. The two get conflated constantly, and a compelling growth story frequently gets mistaken for evidence that a genuine growth plan exists, when in fact the story is sound and the plan underneath it is thin or entirely absent. 

The tell that distinguishes the two is specificity about resourcing and sequencing.

A growth story can be told convincingly in a single slide, market size, competitive advantage, why now. A growth plan requires answering considerably less glamorous questions: which specific team is executing which specific initiative, in what order, with what headcount, and what happens if the first initiative in the sequence takes longer than expected, does the whole plan slip, or is there genuine parallel capacity to keep other initiatives moving. 

Growth stories rarely need to answer these questions to be compelling. Growth plans fall apart specifically at the point where these questions don’t have good answers. 

The practical test worth applying to any growth story presented with real conviction: ask for the plan underneath it, specifically who is doing what by when, and treat vagueness at that level as a meaningful gap regardless of how compelling the story itself is. 

A management team with a genuinely strong growth story and a thin growth plan isn’t being dishonest, they’ve usually just spent more time thinking about the “why” than the “how,” which is a natural imbalance worth correcting directly rather than assuming the plan will assemble itself once the story is agreed.

Management presentations are constructed, understandably, to present the business in its best light, and that’s not dishonest, it’s simply what presentations do. 

Reading them well means paying as much attention to what’s being emphasised and what’s being glossed over as to the content itself, because the shape of the emphasis is often more informative than the numbers. 

A useful habit is noticing which metrics get a full slide with trend lines and commentary, and which get a single mention in passing, folded into a sentence rather than given visual space of their own. Metrics that are going well tend to get the full treatment. Metrics that are softer tend to get mentioned briefly, in a way that’s technically transparent, the number wasn’t hidden, but structurally de-emphasised relative to its actual importance. 

This isn’t usually deliberate deception, it’s simply the natural instinct of anyone presenting to lean into the strong parts of the story, but noticing where that instinct has shaped the presentation’s structure tells you where to focus your own questions. 

A second useful habit is noticing language that’s become more qualified or more abstract over successive presentations covering the same topic. 

A metric described three months ago as “we expect this to recover by Q3” and now described as “we’re continuing to monitor this closely” without a specific update on the Q3 expectation is a signal worth pursuing directly, because the softening of specific language into vaguer language often precedes an acknowledgment that the original expectation isn’t going to be met. 

Neither of these habits requires suspicion of the management team’s honesty. They require attention to structure and language as a genuine source of information, separate from and complementary to the numbers themselves, because the way a story is told carries information the numbers alone don’t capture. 

Every add-on acquisition comes with a synergy case, usually built around some combination of cost savings from consolidating overlapping functions and revenue upside from cross-selling into combined customer bases. 

Both categories of synergy are real and achievable in principle. Both are also, in the specific cases that don’t survive contact with reality, built on an assumption that the synergy will materialise largely on its own, once the deal closes, rather than requiring genuine, dedicated execution effort that competes for the same limited management attention as everything else already in motion. 

The cost synergy case tends to fail when the “overlapping functions” being consolidated turn out to be less overlapping in practice than they appeared on a slide. Two finance teams that both do “finance” often turn out to have meaningfully different systems, different processes, and different institutional knowledge that takes considerably longer to consolidate cleanly than the org chart comparison suggested, and the interim period of running two parallel processes while consolidation happens often costs more, in time and confusion, than the synergy case accounted for. 

The revenue synergy case, as covered in more depth elsewhere, tends to fail for a related reason: cross-sell is a sales motion that has to be actively built and trained into a team, not a natural consequence of two customer bases now technically sitting under one roof. Absent dedicated effort to build that motion specifically, the two customer bases tend to remain largely separate in practice for far longer than the synergy case assumed. 

The pattern underneath both failure modes is the same: synergy cases that treat the synergy as something that happens once the deal closes, rather than something that has to be actively built afterward with dedicated ownership and real time allocated to it, are the ones that don’t survive contact with reality. 

Synergy cases that explicitly name who will build the synergy, what specifically that building looks like month by month, and what it will cost in management time to actually execute, are considerably more likely to deliver something close to what the original case promised.