What a World-Class Value Creation Plan Actually Looks Like: The CVC Ten Tests

CVC Capital Partners distilled something most sponsors are learning the hard way into a single discipline: a value creation plan is no longer an aspirational document. It is an execution instrument. CVC's ten tests are a diagnostic for whether a plan can actually be run — or whether it is a well-formatted hope.

The tests are useful precisely because they are unforgiving. Each one targets a specific way value creation plans fail in the field: vague diagnosis, political attachment, a thesis no one can repeat, ownership that evaporates after the kickoff. Read together, they describe what value creation plan execution looks like when it is built to survive contact with the operating reality of a company.

ST · 01Diagnosis before ambition

The first four tests are about honesty. Fresh-Eyes and Root-Cause exist because plans built by people attached to the business tend to describe the outcomes they want rather than the mechanisms that would produce them. The Momentum Baseline is the most commonly skipped: if you don't know where the business goes with no intervention, you can't tell which part of your projected upside is your work and which part is the tide. The Full-Potential Test then forces the upside to be decomposed into credible, traceable sources rather than a single confident number.

ST · 02A thesis people can repeat

The One-Sentence Thesis Test is deceptively hard. If the value creation thesis cannot be said in one sentence that a frontline employee can repeat, it cannot guide the thousands of daily decisions that actually determine whether the thesis compounds. Radical Transparency extends the same logic: a thesis known only to the board governs nothing on the floor. These two tests are where strategy becomes alignment.

ST · 03Ownership, speed, and the execution machine

The last four tests are where most plans quietly die. Leadership Fit asks whether the team can execute *this* thesis at pace — not whether they are good leaders in the abstract. The Bottom-Up Roadmap test insists the plan be built by the people who will run it, because borrowed plans are never owned. The Speed Test reflects the new reality that holds are uncertain and value front-loaded in the first one to two years rewards decisive action.

Then the Execution Machine Test, which is the whole framework in one line: install a central engine with clear ownership, cadence, incentives, and reconciliation to reported results. A plan that passes the first nine tests and fails this one produces motion without progress. The execution machine is what converts a sequence of priorities into a number the CFO can stand behind — and it is the test most companies are least equipped to pass on their own.

ST · 04Where most plans fail the tests

In practice, plans don't fail all ten tests — they fail two or three, and those failures are predictable. The Momentum Baseline is the most skipped, because defining where the business goes with no intervention feels like an admission that some of the upside isn't yours. But without it, every projection conflates management's work with the market's drift, and the plan loses the ability to prove it created anything. A plan that can't separate signal from tide can't be defended in diligence.

The second common failure is the gap between the One-Sentence Thesis and Radical Transparency. A board may have a crisp thesis, but if it never travels past the boardroom, the organization runs on improvised interpretations. The thesis governs nothing it doesn't reach. And the third recurring failure is the Bottom-Up Roadmap: plans built top-down by people who won't execute them are never truly owned, and ownership is what survives the first quarter when reality intrudes.

ST · 05The tests describe a system, not a document

Read in sequence, the ten tests trace the full lifecycle of value creation: honest diagnosis, a communicable thesis, an aligned and capable team, an owned and sequenced roadmap, and a machine that reconciles activity to results. That is not the description of a plan. It is the description of an operating system. The plan is the artifact; the tests measure whether the system behind it exists.

This is why so many companies pass the early tests and fail the late ones. Diagnosis and ambition are intellectual work that a capable team can produce in a few weeks. Leadership fit, bottom-up ownership, front-loaded speed, and a functioning execution machine are organizational capabilities that take deliberate construction. The first half of the framework can be written. The second half has to be built — and building it is the work that separates a value creation plan that compounds from one that decorates a board deck.

ST · 06Speed is built into the framework for a reason

The Speed Test — designing the plan to deliver the majority of value in the first one to two years — is not an arbitrary preference for haste. It reflects the reality that hold periods are uncertain and exit windows can't be timed. Value delivered early is value secured; value scheduled for later is value exposed to a market no one controls. A plan that backloads its impact is a plan betting on conditions staying favorable long enough to realize it, and that bet has gotten far worse.

Front-loading is also where sequencing and the execution machine meet. Delivering most of the value early requires knowing which moves come first, staging them so each unlocks the next, and running a cadence disciplined enough to keep them on a compressed timeline. The Speed Test, the Bottom-Up Roadmap, and the Execution Machine are not independent criteria — they are three views of the same capability to execute decisively and in the right order.

ST · 07Using the ten tests as a live diagnostic

The most practical use of CVC's framework is not as a one-time grading exercise but as a recurring diagnostic. A leadership team can ask, each quarter, which tests the current plan is still passing. Has the thesis stayed expressible in one sentence as the business evolved, or has it accreted complexity? Is the roadmap still owned bottom-up, or has it drifted back into a top-down list? Is the execution machine actually reconciling activity to reported results, or has the cadence quietly lapsed into status updates?

Used this way, the ten tests become a maintenance schedule for the value creation plan rather than an autopsy performed after it has already failed. The tests that a plan most often loses over time are transparency, ownership, and reconciliation — the operating disciplines, not the analytical ones. A plan rarely fails because the original thinking was wrong. It fails because the system that was supposed to run it gradually stopped running. The ten tests are how a disciplined team notices that drift before it shows up in the numbers.