Transformation Setup Check

Before launching a transformation (a change program spanning several teams, functions or the whole organization), check the setup against what separates the minority that deliver from the majority that do not: an owner with mandate, protected time for the few roles that carry the value, and a formal program with measured outcomes.

Consulting practice, marked as such: Bain's transformation survey (2024: roughly one in eight reaches its original ambition, as rated by executives against their own targets; Bain reported the same share in 2018) and BCG's study of about 1,700 transformations 2004-2020 at large listed companies (2025: about one third succeed on growth plus shareholder-return criteria; factor effects are correlations). The failure-statistics caution is in the module overview (Cândido and Santos, via the register).

Use it when:

• A transformation is about to launch and you want to know whether it is set up to deliver.
• You are inheriting a program mid-flight and need to see where it is weak.
• A "project" has quietly grown transformation-sized: several functions, new ways of working, more than a year.

Skip it when:

• You are launching one initiative, not a program: use 8.19 Implementation Checklist (Before Launch).
• You want to understand why people resist a change: use 8.18 Change Barriers & Forces Canvas or 8.17 Stakeholder Impact & Support Map.

A transformation's outcome is largely decided before launch, by its setup, rather than during it, by effort. The support is consulting practice and should be read as such: survey and database studies from competing firms (Bain & Company, 2024; BCG, 2025) that are self-reported, definition-dependent and correlational. The factors are traits seen in the minority that delivered, not proven causes. What makes them usable anyway is convergence: firms with different methods and incentives keep finding the same pattern, a single accountable owner with a real mandate, protected capacity for the few roles that carry the value, and a formal program with baselined measures (Mankins & Litré, 2024). It also matches plain logic: a transformation competes with the daily business for attention and time, and goodwill is not a resourcing plan.

So the ambition comes first, with a number and a date, so partial delivery has something to be measured against. The factor table asks for evidence, because "in place" without it is the lanyard version of an owner. And the last step forces the honest trade: fix the red cells, or scale the ambition to the setup you have.

In consulting surveys, most transformations do not reach their original ambition (Bain, 2024: roughly one in eight does, self-reported against companies' own targets; BCG, 2025: about one third succeed on its growth and shareholder-return criteria). These are definition-dependent, self-selected samples, not natural laws, but the direction is consistent: the default outcome is partial delivery.

Strong answer: (illustrative) "Cut order-to-delivery time from 6 days to 3 in all four regions by December 2027, without raising logistics cost per order." Not: "Become a digitally enabled, customer-centric organization."

What the transformation is to achieve, in one sentence with a number and a date:

What we will do differently from the default, concretely (if the answer is "work hard and communicate", the setup below is not done):

Illustrative example: the organization is made up.

A COO at a regional food distributor inherits a "digital transformation" spanning customer service, logistics and finance. The ambition sentence takes a week to extract, because nobody had written one with a number. The factor table shows a steering committee but no owner (the program lead runs it beside a line job), unidentified value roles, and no protected time.

She negotiates. The program lead goes full time, the twelve people who carry the critical workflow redesigns get half their time formally reallocated, and the scope is sequenced: customer service first, finance deferred a year. Two red cells were cheaper to fix before launch than the stalled program they would have produced, and the deferred scope is announced openly rather than silently starved.