Why is a status report not enough?
A report showing that an initiative is six weeks late does not answer whether it needs an extra person, a management decision, a change in the sequence of work or a fresh look at the business case. Responding to every delay the same way often increases the number of meetings without improving delivery.
McKinsey’s 2021 research shows that 55% of lost transformation value is lost during and after implementation. That is an argument for execution discipline, not proof that every delay is a resourcing problem. CVC, for its part, stresses the quality of the baseline, the interdependencies between initiatives and a credible reflection of effects in the financial results.
Seven causes: how do you tell a symptom from a blockage?
| Cause | Signal / diagnostic question | Appropriate response | Decision / mandate |
|---|---|---|---|
| 1. Lack of time | The owner keeps moving tasks. How much time do they actually spend on the initiative? | Relieve the owner or add delivery support. | CEO / resource owner |
| 2. Skills gap | Work gets done but fails acceptance. What knowledge or experience is missing? | Bring in an expert, develop the skill or use external support. | CEO / function leadership |
| 3. Dependency | The initiative waits for another team, system or supplier. Who is accountable for the dependent output? | Dependency owner, date and joint escalation. | Owners of the relevant functions |
| 4. Missing decision or mandate | Budget, scope or solution keeps coming back to meetings, or the owner passes routine decisions to board members or the CEO. Which decisions can the owner take alone? | Define the owner’s mandate (limits on spend, hiring, contracts); for decisions above the mandate, prepare the resolution, a date and options. | CEO; above the mandate, the appropriate body under the governance model |
| 5. External condition | Approval, notification, consultation or acceptance. Was the required lead time built in? | Verify the requirement and resequence the work. | Management with compliance / legal |
| 6. Wrong baseline, budget or schedule | There is operational progress but no visible benefit; the work has no budget cover or the schedule ignores the time to build the team. Were BAU (business as usual), the baseline and the budget right? | Agree measurement and budget with the CFO, replan the work, do not change the target quietly. | CFO; changes per delegated authority |
| 7. Outdated assumption | The initiative works but its value has fallen. What changed in the business case? | Recalculate the options: continue, modify or escalate. | Management; the investor if the thesis changes |
What do these causes look like in practice?
Dependencies between teams are one of the weakest points in execution. In research by Sull, Homkes and Sull covering 7,600 managers in 262 companies, only 9% said they could rely on colleagues in other functions all the time, and half most of the time. The authors note that such commitments were not much more reliable than promises from external partners.
Two delays I saw in a portfolio company where I worked came from causes that are less visible in reports. In the first, the initiative’s activities were not aligned with the budget, and the time needed to build a new team and hand skills over to it was underestimated. A delay like that is created at the planning stage and only shows during delivery.
In the second, the initiative owner was defined wrongly. There was willingness to act, but no mandate to take decisions. Most decisions therefore went to board members, and even to the CEO, who became the bottleneck. That is why a review should check not only who owns the initiative, but also which decisions they can take on their own.
What do you do when several causes occur at once?
One initiative can have an overloaded owner, a technology dependency and a pending external approval at the same time. There is no point in forcing a single “true” cause. The task is to identify the dominant blockage on the critical path, meaning the one whose removal actually allows the next step, along with the remaining risk factors.
An illustrative example: an international financial services company is delaying the move of a process to an operations centre. The initiative lead has limited time, but the start of the migration also depends on an outsourcing assessment and possible regulatory formalities. An additional project manager can speed up preparation but does not remove the required regulatory step. Management should therefore first confirm the scope of the obligation with compliance, replan the dependencies and only then decide on resources.
How do you check how much value is really at risk?
A review of causes should cover not only the schedule but also the value bridge. For each initiative, the CFO should distinguish the expected annual effect (run-rate), the planned EBITDA impact in the current period, the effect already confirmed in the results and the impact on cash and capex. The value creation plan on one page uses a similar distinction.
A purely illustrative example: an initiative is expected to deliver EUR 1.2m of annual savings once fully implemented. If benefits were assumed to start in July but start in October, the simplified EBITDA impact for the year falls from EUR 0.6m to EUR 0.3m (assuming benefits accrue evenly and with no one-off costs). The target run-rate may stay unchanged. This is a delay in value, not automatically a loss of the whole business case.
The case where the schedule is met but the financial effect does not appear needs a separate assessment. The cause may be a wrong baseline, double counting against the BAU case or a change in market conditions. These situations call for revalidating the assumptions, not for another implementation date.
How do you run an effective review?
First select the initiatives that matter most for value delivery or sit on the critical path of other work. Then compare plan and actuals and talk to the owner, the CFO and the supplier or team on which progress depends. Findings should rest on documents, dates and numbers.
For each blockage, record the confirmed cause, its effect on the milestone and the benefits, the specific action, the action owner, the person authorised to decide and the escalation date. The output of the review is not a new set of statuses but a short list of decisions needed to restore delivery.
The report to management or the board should show causes and decisions next to the status signals. One caveat matters: the review does not on its own change VCP targets, management’s mandate or the investment assumptions. Such changes are decided by the company’s governing bodies and the investor, in line with the agreed governance model.
Where do regulated companies need particular care?
In regulated sectors the schedule sometimes depends on procedures over which the project team has limited influence: qualifying an outsourcing, notifications, contractual conditions, consultation with employee representatives or client consents.
In Luxembourg, prior notification requirements of the CSSF (Commission de Surveillance du Secteur Financier) depend among other things on the type of entity, the nature of the outsourcing and whether DORA, the Digital Operational Resilience Act, applies. The CSSF describes, among others, three-month lead times and, in certain cases, one-month lead times for services from a Luxembourg support PFS. This is not a universal obligation for every migration project. The correct legal basis and timing are confirmed with compliance against current rules before the schedule is approved. Legal position: November 2026.
When is external support needed?
Not every delay justifies bringing in an external team. If the problem is a decision not taken, the authorised body has to decide. If the obstacle is inconsistent data, the credibility of measurement has to be restored. Additional resources make sense when they remove a real constraint on execution capacity or bring a missing specialist skill. We describe where the lack of execution capacity comes from in why value creation plans slow down after the deal, and the signals an operating partner can use to recognise the need for support in when operating partners should bring in external execution support.
Symmetria’s role can be to run the review, clarify dependencies and responsibilities, prepare decisions and support the team in delivering the agreed VCP. This does not replace the fund’s operating partner or the competences of management and the board.
Conclusion
A well-run review of the causes of delay does not look for someone to blame and does not replace the VCP with a new plan. It establishes what is actually holding back value delivery, how its timing changes and who has to take the decision. This lets the company restore the pace of delivery without multiplying reports and initiatives.
Symmetria supports portfolio company management teams in identifying barriers and delivering approved value creation plans. Let’s talk about what is blocking your most important initiatives today.
Sources
- McKinsey & Company (2021), Losing from day one: Why even successful transformations fall short
- Sull D., Homkes R., Sull C. (2015), Why Strategy Execution Unravels and What to Do About It, Harvard Business Review
- Kelleher J. / CVC (2026), Ten Tests of a World-Class Private Equity Value Creation Plan
- CSSF, Circular CSSF 22/806 on outsourcing arrangements (as amended by Circular CSSF 25/883)
- CSSF (2025), Definition of “ICT services” under DORA: new forms for ICT third-party arrangements and ICT outsourcing arrangements
