HAVRIONCAPITAL
Back
Portfolio Strategy15 January 20268 min read

A Working System for Post-Investment Value Creation: Three Priorities and Ten Declines

The first-hundred-days plan feels reassuring, but most operating improvement takes a multi-year effort rather than a checklist compressed into three months. This piece examines how to pick three priorities genuinely worth pursuing after an investment closes, decline ten others that sound reasonable, and why organizational development is often the highest-return work that gets skipped.

The moment a new investment closes, someone almost always asks what the first hundred days should look like. The answer rarely holds up under scrutiny. Most items on a hundred-day plan are things the investment team already spotted during diligence and that look easy to fix at a glance — swap in a new reporting template, roll out a procurement approval system, adjust a few reporting lines. These are simple to execute and photograph well in an update, but rarely the variables that determine how well a company runs three or five years out. What actually determines that is whether management's judgment improves, whether incentives keep the people who matter, and whether reporting lets leadership see a problem before it turns serious — none of which fits inside a hundred days, or even one year.

I rarely use the phrase first-hundred-days plan, not because a hundred days is too short but because it implies the wrong working rhythm — an intense diagnostic phase, followed by intense execution, followed by a shift into maintenance mode. Real post-investment work looks more like a continuously adjusted operating agenda: one quarter's focus might be organizational restructuring, the next might shift to pricing, and after that, some piece of the supply chain. Priorities change, but the intensity of the work should not fade the longer an investment has been held. If a portfolio company stops hearing new questions from us two years in, that is usually not because the company has become good enough — it is a sign something has gone wrong with how we are working.

Choosing three, declining ten

The first time I walk into a new portfolio company and follow the operating team through its main processes, the list of issues I can compile is never short — usually more than a dozen, and every one sounds reasonable. Inventory could turn faster. Complaint response could be more standardized. Performance evaluation in some department clearly has gaps. Putting a dozen items into the work plan is the easiest mistake to make and the least effective one. A management team's bandwidth is limited, and pushing ten improvement projects at once usually produces ten moving slowly, not ten completed in parallel.

So with every new portfolio company, I make myself narrow the list to three priorities, while writing down, just as explicitly, the seven to ten things we will not do for now — and telling the management team why, not because those items do not matter, but because doing too many things at once is itself a risk. The criteria for choosing the three are simple: does the issue's reach extend broadly enough that fixing it moves other things too; is management already prepared to give it real attention, rather than needing to be talked into grudging cooperation; and does solving it open space for the next round of work, rather than being a one-off, isolated fix. Rarely do more than three issues satisfy all three conditions at once, which is why three is not an arbitrary number to land on.

  • Reach: once this problem is solved, does it also improve several other, seemingly unrelated problems, or does it only make one metric look better in isolation?
  • Whether management is genuinely ready: did they raise the issue themselves, or does it take repeated persuasion before they reluctantly agree to commit resources? The latter usually means ongoing resistance during execution.
  • Whether solving it opens space for what comes next: an improvement that only makes one metric look better briefly has limited value; one that also leaves the team with the capability or confidence to tackle the next problem keeps paying off.
  • State the reason for declining clearly, not vaguely: management needs to understand this is a resource trade-off, not a rejection of the issue itself — otherwise it is easy for them to conclude the investor simply does not care about the problem.

Organizational development: the highest return, and the easiest to skip

If I had to pick the single highest-return item across all post-investment work, I would pick organizational development — specifically, the combination of management-bench depth, incentive design, and whether the reporting rhythm is healthy. It carries the highest return because it determines whether a company can find and fix its own problems without outside intervention. It is also the easiest to skip, because its effect is almost never visible within one quarter and is hard to attribute to any single intervention. Most management teams would rather talk about visible operating metrics; organizational development usually has to be put on the table deliberately, or it never comes up at all.

Bench depth means whether, if a key executive left tomorrow, someone could reasonably take over within a sensible window, rather than the whole function stalling. Many portfolio companies that look like they are performing well are actually fragile on this point — performance depends heavily on one or two key people's ability and relationships, and once they leave, metrics visibly decline within a short period. To assess bench depth, I do not weigh whether an org chart shows a written succession plan. I would rather observe directly: when a key person takes two weeks off, does the team keep operating normally, or does every decision wait for that person to return?

Incentive problems are more hidden, because most companies already have an assessment system that looks complete on paper. The trouble sits in the gap between what a metric measures and the behavior it is meant to produce — a regional manager evaluated on sales volume tends to cut prices to chase volume, eroding margin; an R&D team evaluated on project count spreads itself across small projects rather than concentrating on one that matters. Finding this gap takes time understanding what actually drives behavior in each role, not just reading an evaluation form. Reporting rhythm determines whether leadership sees a signal before a problem turns serious — and higher frequency is not automatically better. What matters is whether content reflects the parts of the operation most prone to trouble, not a stack of numbers that are easy to tabulate but do not matter much.

When to help, and when to stay out of the way

The portfolio operations team has no natural authority inside a portfolio company, and the sooner that is accepted, the better. We are not the shareholders and hold no day-to-day decision rights; whether we get taken seriously depends entirely on whether our advice is useful. That premise makes one thing more important than knowing what advice to give: judging when to step in and when to stay out of the way. Stepping into a problem management can solve on its own disrupts their rhythm and signals distrust. Involvement is worth something only when a problem sits beyond the team's current capability, or when the full picture requires experience drawn across several portfolio companies at once.

The method I use to judge that line is plain: ask management how they plan to solve it first. If their thinking is sound and execution simply needs time, step back and put attention elsewhere. If their approach has an obvious blind spot, or if they are themselves unsure and are only waiting to be asked before admitting the real difficulty, that is when to step in. There is no fixed rule that applies across cases — the judgment depends on knowing the specific team and the specific industry. That is also why post-investment operating work cannot be reduced to a generic checklist. A checklist creates the illusion that value gets created by following steps in order, when the real judgment is always specific to the situation in front of you.

The continuous cycle of a post-investment operating agenda
  1. Follow actual process, find the bottleneck
  2. Narrow to three priorities
  3. State ten declines, with reasons
  4. Judge when to help, when to step back
  5. Assess progress honestly, not just report it
  6. Reset priorities for the next phase

Follow actual process, find the bottleneck: 1; Narrow to three priorities: 2; State ten declines, with reasons: 3; Judge when to help, when to step back: 4; Assess progress honestly, not just report it: 5; Reset priorities for the next phase: 6

Measuring operating progress honestly

The biggest trap in measuring post-investment progress is mistaking completed actions for achieved results — rolling out a new system, restructuring a department, are actions, not outcomes. An honest measure goes back to the specific question that justified choosing a priority in the first place, and asks whether it has genuinely been resolved: has inventory turnover actually improved, or has the accounting method simply changed? Has succession risk in a key role genuinely dropped, or is there now just a spreadsheet with a name written into a box? Progress on most operating improvements is slow and uneven — some quarters show almost no visible change, others show a sudden, clear breakthrough. That unevenness is normal. A report showing smooth, predictable progress every single quarter is the one that deserves more suspicion, not less.

At Anyue Living, post-investment work has stayed focused for a long stretch on the shared supply chain's capacity-forecasting mechanism rather than any single brand's marketing, because supply-chain responsiveness determines the marginal cost of incubating a new brand — a variable with reach across the business — while marketing is better left to each brand's own team. At Mingchuan Logistics, the focus has instead sat with capital expenditure approval and site discipline for cold-chain expansion, while customer relationships and fleet scheduling have remained with management throughout. The industries differ, but the logic is the same: find the piece that moves the whole business and where management needs support, keep attention there, and for everything else, state the reason and let go.

Further Reading