Value Creation Plans That Actually Deliver

Every PE-backed business has a value creation plan. The plan is a condition of the investment - it documents the thesis, identifies the levers, and sets the targets that the business is being measured against. Most plans are competently written. A smaller proportion are genuinely operational. A smaller proportion still actually get executed.

The gap between a value creation plan that is signed off at the first board meeting and one that delivers the returns it projects is not primarily a question of ambition or market conditions. It is a question of whether the plan was designed to be executed or designed to satisfy investors.

Specificity that enables accountability

A value creation plan that identifies "operational efficiency" as a lever has identified a category, not a lever. The category describes where value might be found. A lever describes the specific action, the mechanism by which it generates value, the person accountable for delivering it, and the timeline.

"Operational efficiency: reduce direct labour cost by 8% through process improvement in the fulfilment function, led by the Operations Director, target achieved by Q3 of investment year one" is a lever. "Operational efficiency: cost reduction across operations" is not.

The test of a plan's specificity is whether you can read each initiative and know immediately who owns it, what they are supposed to do, when they are supposed to have done it, and how you will know if they have succeeded. Plans that pass this test can be managed. Plans that do not pass it cannot be - and will not be.

The specificity also serves a diagnostic function. When a plan is written at the level of mechanism rather than category, the constraints become visible. Some initiatives that look achievable at category level turn out to be interdependent, under-resourced, or dependent on a capability the business does not have when the specificity is applied. Better to discover this during planning than during execution.

Sequencing that reflects operational reality

Value creation plans often treat initiatives as independent parallel workstreams that can all begin simultaneously at close. Operational reality is rarely that convenient.

Some initiatives are prerequisite for others. You cannot improve the quality of management information to support better pricing decisions until the management information infrastructure is rebuilt. You cannot improve customer retention through service improvements until the operational capacity exists to deliver the improved service consistently. You cannot realise acquisition synergies in a bolt-on until the integration of core systems and processes is complete enough to enable shared operations.

A plan that ignores these dependencies produces a timeline that the operational team knows is unrealistic from the moment it is presented. Teams that know their plan is unrealistic find ways to report against it without actually being bound by it - which produces management information that tells the board what they want to hear rather than what is happening.

Resource allocation that is honest about capacity

A value creation plan that assigns initiatives to existing leadership team members without accounting for their current operational responsibilities will not be executed. The operations director who is running a 24-7 operation is not available to lead a process improvement programme on top of their existing role, regardless of how important the programme is to the investment thesis.

The plans that get executed are the ones that either explicitly free up the capacity needed to execute them - by restructuring responsibilities, hiring programme leadership, or using fractional resource to fill specific gaps - or are scoped to what the existing team can realistically deliver alongside their operational responsibilities.

Over-ambitious plans that rely on an unrealistic assessment of available capacity do not fail because of bad execution. They fail because no one can execute them without the execution creating something else failing. The right response is to be honest about capacity during planning, not to try harder during execution.

A governance cadence that catches problems early

The value creation plans that deliver have a management rhythm designed around them - a weekly or fortnightly review of progress against the key milestones, at the level of operational detail rather than traffic-light summaries, attended by the people accountable for delivery and the people who can remove blockers.

The plans that do not deliver typically have a governance structure that was designed for reporting to the investor board rather than for managing the programme operationally. Monthly board-level reviews of RAG status catch problems a month after they emerged. By that stage, problems that could have been resolved in a week have had four weeks to compound.

The distinction is between governance that creates accountability for delivery and governance that creates the appearance of oversight. A management team that reviews its value creation programme weekly against specific milestones and takes immediate action when milestones slip will outperform one that reviews at monthly intervals and discusses what happened in the past month.

The people dimension that plans consistently underweight

Value creation plans are financial and operational documents. They specify revenue targets, cost reductions, and process changes. They rarely specify with equal rigour the people capabilities required to execute them.

The operational improvements in most value creation plans require capabilities that the existing team may not have. A lean manufacturing programme requires lean expertise. A data strategy requires data capability. A customer success function requires customer success leadership. Plans that assume the existing team will develop these capabilities through execution typically see the capabilities arrive late, if at all.

The plans that deliver either build the required capability explicitly - through targeted hiring or fractional resource in specific areas - or scope themselves to what the existing team can execute with their current capabilities. The worst outcome is a plan that is scoped beyond what the existing team can execute and does not provide the resource to close the gap.

How do you know if a value creation plan will actually be executed?

The question a management team should ask of any value creation plan is not whether the targets are achievable in theory. It is whether the plan as written - with these initiatives, this sequence, these resources, and this governance - is something the team can actually deliver.

If the honest answer is no, the right response is to revise the plan until the honest answer is yes. A plan that cannot be executed is not a plan. It is a target with commentary.