Why value creation plans stall: the hours nobody counted

Most value creation plans read well. The initiatives are the right initiatives, the sequencing is sensible, the owners are named, and the diligence underneath it was real work done by people who know the business. Read one again at the six-month review and the plan itself is rarely what went wrong.

What shows up instead is a status column. Two workstreams complete, three in progress, two that have not started. Nobody missed a deadline in any dramatic way and nobody is underperforming. Every initiative in the plan has a named owner, and every named owner already had a full-time job running the company before the plan arrived. The plan has a line for the initiative, a line for the owner, and a line for the date. It rarely has a line for the hours.

Why value creation plans stall in portfolio companies

They stall because the plan and the base business draw on the same people, and only one of the two can slip quietly.

The base business runs on hard dates. The month closes, customers call, payroll runs, product ships, and the lender package goes out on a schedule nobody controls. Miss any of those and the consequence lands immediately and in public. The initiatives carry dates too, and the cost of a deferred workstream arrives two or three quarters later, inside a number that gets explained by market conditions. So when a week gets tight, the base business wins. That is correct triage, and a team that ran it the other way would be a worse team.

The stall is not a motivation problem and not a capability problem. It is the arithmetic of a week that was already full before the plan was written.

What a 100-day plan actually requires in hours

More hours than the plan implies, and most of them come from the few people least able to give them up.

The reason is what the initiatives are made of. A pricing initiative is not a pricing decision. It is weeks of transaction data pulled out of systems that disagree with each other, cleaned by hand, cut by customer and by product, then rebuilt every time somebody asks a better question. A reporting build is defining the metric once and then chasing its source every month afterward. A systems evaluation is requirements gathering, vendor calls, reference checks, and a scoring model somebody has to keep current.

Very little of that is the strategic judgment the plan was written to apply. It is the assembly work underneath the judgment, and assembly work lands on whoever sits closest to the data. In a middle-market company that is the controller, the FP&A lead, or the operations director. The plan sizes the initiative. It almost never sizes the assembly.

Where the hours actually come from

They come out of the narrow margin of the week that used to hold the improvement work, and on most middle-market teams that margin was spent long before the deal closed. Whether a given team still has that margin is a read worth running before the plan is written.

There is a reason for that worth saying plainly. The company is worth writing a plan for because a small group of people has been holding the base business together by hand. When two systems do not reconcile, somebody reconciles them. When a report does not exist, somebody builds it in a spreadsheet over a weekend. When a process has no owner, the most senior person in the room owns it by default. That absorption is why the numbers came in, and it is why the business looked good enough in diligence to buy.

Operational Alpha has a name for that absorption. Coping is what capable operators do when the work around them was never designed, and the one-line definition sits in the Operational Alpha lexicon. The word carries no criticism. It describes the most reliable people in a company closing gaps the structure left open, and the particular shape it takes on a given team is worth reading closely, which is the subject of how capable teams end up firefighting. The part that matters for a plan is simpler. The margin the plan is counting on is the same margin already being spent holding the base business up.

A value creation plan is not competing with the base business for priority. It is competing with it for the same Tuesday afternoon.

How to get initiatives executed without adding headcount

By putting capacity in the plan as a workstream rather than leaving it underneath the plan as an assumption, and by building it before the first initiative starts.

Three questions do most of that work.

• Which hours does each initiative consume every week it is live, and whose hours are they? Written next to the initiative, in the plan, at the same level of seriousness as the milestone date. The answer is usually two or three names, and the same two or three names appear against most of the workstreams.
• What are those hours doing today? They are committed. The plan is asking for a reallocation rather than for spare capacity, and the thing being reallocated away from is usually the base business.
• What holds the assembly work once the plan is live? The recurring pull of data, the reconciling, the follow-up, and the reporting that every workstream generates has to sit somewhere other than the leadership calendar, or the plan runs on borrowed hours from the first week.

Headcount is the usual answer, and its clock is the problem. A search, a notice period, and a ramp are measured in quarters. A 100-day plan is measured in weeks. The two clocks do not meet, which is most of the reason the first hundred days run on the margin instead of on capacity.

The more useful reframe is that this is a design question before it is a hiring question, which is the fuller version of the case that a hiring problem is usually a design problem. Work that has no designed home does not acquire one when a person is added to the same structure. It climbs back onto the calendar it came from, usually inside a quarter.

Where Kayana fits

Kayana builds that capacity for PE-backed middle-market companies. The operators arrive already senior, recruited out of the capability centers the Fortune 500 built, embedded in one company and working inside its own cadence. What makes a seat hold is the environment around it, designed and run on purpose. Grown one seat at a time it becomes a small embedded operating team. That is the Mini-GCC model, and it takes no entity, no real estate, and no multi-year build.

At one $75M PE-backed company the team that got built was three people, at roughly $125K a year. What that bought showed up six months later, when two of its senior leaders had enough of their week back to stand up two new product lines. That is what a reclaimed calendar does when there is a plan waiting for it. Voluntary turnover across the teams we build runs 3–5% in year one, and the people who stay carry the context the next workstream needs.

Quick answers

The design system behind an operating layer that compounds is the book. Operational Alpha →