The transformation office: where the business case turns into results or gets lost

The problem is not the strategy

In a conversation published by McKinsey, Harry Robinson notes that academic research puts the share of corporate transformations that fail at around 70%, and attributes much of that outcome to three causes: unambitious aspirations from the top, capability gaps among the leaders who must execute, and the absence of process elements such as a transformation office, regular follow-up meetings and performance reviews (McKinsey). BCG reached a similar conclusion in its analysis of digital transformations: only 30% met or exceeded their value target, but those that got six factors right, including quantified targets, leadership commitment and rigorous progress tracking, raised their odds of success to 80% (BCG).

The takeaway for a Latin American business group is straightforward. A diagnosis, however good, does not move the income statement. What moves it is the discipline with which an organization turns ideas into initiatives, initiatives into approved business cases, and business cases into sustained operational change.

In our work with a food services business group with several business lines, the diagnosis identified dozens of opportunities in procurement, logistics, product standardization, plant processes and technology. The board’s natural temptation was to approve everything. The productive conversation was a different one: which initiatives generate direct impact, which are enablers without which the impact does not materialize, and in what order they should move forward.

From an inventory of ideas to a portfolio of initiatives

A healthy transformation advances through maturity levels. An idea has a high-level estimated impact. An initiative has a scope and an owner. A business case has a baseline, quantified impact, investment, timeline and risks. Implementation has milestones. Maturation has actual-versus-plan measurement. What changes between levels is not ambition, but the evidence behind each number.

In the food services business group, consolidating the portfolio produced a pattern we see often: the direct-impact initiatives (procurement, logistics, plant excellence, standardization) almost all depended on three technical enablers: ERP configuration, digitization of manual processes and a minimum data architecture. Once the board understood that those enablers had no return of their own but conditioned the return of everything else, the investment conversation stopped being “how much does the ERP cost?” and became “how much value stays locked up if we don’t do it?”.

The business case as an internal contract

A useful business case answers five questions: what the baseline is today, which lever moves it, how much moving it is worth and when, how much it costs and who is accountable. In our experience, the first question is the hardest. In groups that grew fast, the information exists but is scattered across spreadsheets, quality reports and the tacit knowledge of area heads. Building the baseline requires conversations with several management lines, document gathering and, often, reconciling figures that different areas report differently.

That effort has a benefit beyond the number. When the manager of a business line takes part in building their own baseline, they take ownership of the business case. When they receive it ready-made, they dispute it. The pattern we observed in the steering committee was clear: initiatives built with the process owners moved forward with less friction than those that came from the top.

We also learned to separate two curves that boards tend to mix: the gross efficiency curve and the implementation cost curve. The first is slow to start and peaks several years later; the second is concentrated at the beginning. Presenting only net efficiency hides the first-year valley, and it is in that valley that transformations lose sponsorship.

A transformation office designed to disappear

The transformation office is not a PMO by another name. Its role is to sustain a cadence: weekly initiative reviews, a monthly steering committee, documented decisions, escalation of blockers and impact measurement against the business case. Its main product is not reports, but decisions made on time.

Its main product is not reports, but decisions made on time.

In the business group we worked with, the model was designed in four handover stages. At the start, the consulting team leads the methodology and sets up governance. Next, the internal team builds capabilities and shares the effort. Then the work is owned internally and the consultant focuses on steering. Finally, the internal team leads and the consultant moves into a support role. Making those stages explicit from the outset changed the conversation with the board: the transformation office stopped being seen as a permanent cost and came to be seen as an investment in in-house capability.

The monthly progress reports taught another lesson. Service interruptions, for budget reasons or because of the board’s agenda, carry a reactivation cost that is rarely budgeted: the internal team loses momentum, baselines go out of date and owners shift priorities. Cadence is a fragile asset.

Change management: the enabler nobody budgets for

In operating teams, fear of change is rational. A new process standard or a new system alters routines, exposes deviations and redistributes power. In our experience in operations with staff spread across many service points, deviations from the standard did not stem from bad faith, but from “creative” workarounds in the absence of controls and training. The answer was not more control, but visible standards, certified training and a change management agent on each initiative’s team.

The broader lesson is that climate, culture, structure and policies are not a separate workstream, but a cross-cutting layer that accompanies every initiative. When the portfolio treats it as one more initiative, with an owner and a budget, the impact holds.