Most value creation plans are directionally correct and operationally useless. They name the right levers, size the prize plausibly, and then stop precisely where the difficulty begins — at the question of who does what, in what order, with what taken off their plate to make room. The first hundred days is where that gap either closes or hardens into a plan nobody runs.
A plan with nine workstreams and no sequence produces nine partially-started initiatives and one exhausted commercial team. Sequence is the plan. The list of levers is only the raw material.
Why good plans stall
The plan is usually not wrong. It stalls for reasons that have nothing to do with analysis quality.
- It has no owner inside the business. Written by advisers, presented to a board, and landing on a commercial team that first encounters it as a set of expectations rather than a set of decisions they helped make.
- Everything starts at once. Nine workstreams launched in month one, each sponsored by someone with a day job, none finished by month six. In practice most businesses complete one or two in year one, and more than that needs someone whose actual job is running the plan.
- It ignores capacity. The plan assumes the team that is currently missing its number will simultaneously rebuild the process by which it misses it.
- Nothing is taken away. New initiatives are added; nothing is stopped. The implicit assumption is that there was slack, and there never is.
These are all sequencing and ownership problems rather than analytical ones, which is why more analysis rarely fixes a stalled plan.
Sequence by dependency, not by size of prize
The instinct is to start with the largest opportunity. That is usually wrong, because the largest opportunity is often the one most dependent on foundations that do not yet exist.
A more reliable ordering runs in three waves:
| Wave | What belongs here | Why first |
|---|---|---|
| Days 1–30 Instrument | Definitions of stages and segments. One agreed source of commercial truth. A weekly rhythm with named owners. | Everything downstream needs measurement. Improvements made before this cannot be attributed, defended or sustained. |
| Days 30–60 Recover | Discount control, renewal motion, qualification discipline. The things that stop value leaking. | Fast, cheap, largely within existing headcount, and they build credibility for the harder work. |
| Days 60–100 Build | Pricing redesign, new segment entry, channel build, team restructuring. | These need the instrumentation from wave one and the credibility from wave two. Started earlier they consume the year. |
The uncomfortable implication is that the first month produces no revenue impact. It is nonetheless the month that determines whether months four through twelve produce any.
What a workstream needs to be real
The difference between a workstream and an aspiration is specificity on six points. If any is missing, it will not survive contact with a quarter.
A single named owner
Not a function, not a committee. One person, who has agreed to it out loud, and whose other commitments have been adjusted.
A measurable first milestone inside 30 days
Something that can be shown, not reported. Workstreams whose first checkpoint is at 90 days are usually 90 days behind by then.
An explicit statement of what stops
To make room. If nothing stops, the plan is asking for unpaid overtime and will be quietly declined.
The number it moves, and by how much
Tied to a line in the model. Workstreams that cannot be connected to a number are hobbies, however sensible.
A named dependency, or none
If it needs wave one complete, say so and schedule it accordingly rather than starting it anyway.
A defined end
Workstreams that never close consume attention indefinitely. Every one should have a condition under which it becomes business as usual.
The rhythm matters more than the plan
A mediocre plan reviewed weekly outperforms an excellent plan reviewed quarterly. The operating rhythm is what converts intention into progress, and it is the element most often left to form on its own.
What works, in our experience, is deliberately unglamorous. A weekly commercial meeting of forty-five minutes with a fixed agenda, chaired by the CRO rather than the sponsor. Each workstream owner reports movement against their milestone, not activity. Anything off track gets a decision in the room rather than an action to discuss it later. The same numbers, in the same format, every week — because changing the format is how businesses avoid noticing a trend.
Monthly, the same group looks at the model rather than the workstreams and asks a harder question: is the value we assumed still available, and has anything we have learned changed the sequence? Plans should be revised. What they should not do is drift without anyone deciding.
Where outside help earns its place, and where it does not
Implementation support is easy to buy badly. Two patterns are worth avoiding.
The first is a team that arrives, builds, and leaves. The capability goes with them, and eighteen months later the business has reverted, because nothing was transferred. The second is open-ended presence, where advisers become a permanent extension of the commercial function and the business never develops the muscle itself.
The useful version sits between the two: doing the work alongside the people who will inherit it, with an explicit handover point, and measuring success by whether the rhythm survives the exit rather than by what was delivered during it. That is also the honest test of whether a value creation plan was ever real — not whether the workstreams completed, but whether the business still runs that way a year after nobody is being paid to make sure it does.
Frequently asked questions
What should happen in the first 30 days after completion?
Instrumentation rather than initiatives. Agreed definitions for pipeline stages and segments, one source of commercial truth, and a weekly operating rhythm with named owners. Improvements made before this exists cannot be measured or sustained.
How many workstreams can a mid-market commercial team run at once?
In our experience most complete one or two in the first year after a deal. More than that generally requires a project management office, or at least one person whose job is running the plan rather than sponsoring it.
Should the value creation plan be shared with the management team?
Yes. A plan the team has not seen, or has seen but not shaped, is a set of expectations rather than a plan. Management endorsement is the strongest single predictor of whether it gets executed.
When should a value creation plan be revised?
Monthly against the model, and materially whenever a sequencing assumption proves wrong. Revision is healthy; what is damaging is drift, where the plan quietly stops being followed without anyone deciding to change it.
Ready to aim higher?
If you have a value creation plan and need it turned into workstreams a management team will actually run, that is the work we do alongside the team rather than for them.