The Transformation Initiative is a large-scale organizational change program that redesigns an organization’s structure, processes, and culture from scratch — thereby violating Gall’s Law, resetting any benefits accidentally accrued by the organization staying in one shape long enough for things to start working, and creating the conditions for the next Transformation Initiative.
The Transformation Initiative is Reorg’s older, more expensive sibling. Where the Reorg swings the pendulum between functional and cross-functional, the Transformation Initiative wraps the pendulum in a 200-page PDF, assigns it a Chief Transformation Officer, gives it an eighteen-month roadmap, and calls it strategy.
The Reorg changes the boxes. The Transformation Initiative changes the boxes, the lines, the vocabulary, the meeting cadence, the tools, the values, the posters on the wall, and the font on the slide deck. It changes everything except the work, which continues exactly as before, performed by the same people, who were not consulted.
for {
reorg()
transform()
sunset()
// no break condition
// no exit criteria
// the loop is the product
}
The Lifecycle
Every Transformation Initiative follows the same arc. It has never varied. It will never vary. The arc is as reliable as gravity and as resistant to intervention.
Phase 1: The Vision (Month 0-3) — A new executive arrives, or an existing executive attends a conference, or a board member reads a Harvard Business Review article, or a consulting firm’s business development team takes someone to lunch. The result is a conviction that the organization needs to transform. Not improve. Not adjust. Not iterate. Transform. The word is important. “Improve” implies the current state has value. “Transform” implies it does not.
A consulting firm is engaged. The discovery phase begins. Junior consultants interview everyone who does the work. The senior partner synthesizes the interviews into a slide deck. The slide deck recommends a transformation. The transformation requires the consulting firm’s continued engagement. Nobody in the room finds this remarkable.
The deliverable is a Vision Document: 150-200 pages describing the target state. The target state is beautiful. It has clean boxes, clear reporting lines, modern vocabulary, and a maturity model with five levels. The organization is currently at Level 2. The consulting firm can help it reach Level 4. Level 5 is aspirational. No organization has reached Level 5. Level 5 exists to ensure the journey never ends.
Phase 2: The Rollout (Month 3-9) — The transformation is announced at a Town Hall. The announcement contains the words “people,” “empowerment,” “alignment,” and “journey.” A Chief Transformation Officer is appointed — a role that exists on Org Chart but connects to nothing, floating above the existing hierarchy like a weather balloon observing terrain it cannot touch.
Teams are reorganized. Processes are redesigned. New tools are adopted. Agile coaches are hired — sometimes a hundred of them, flowing through a revolving door with certifications in hand, leaving with LinkedIn updates when the next phase arrives. Training programs are launched. Vocabulary changes. The same work is described differently. The slide decks are updated. The Grafana dashboard, which was green before the transformation began, turns yellow.
Phase 3: The Plateau (Month 9-15) — The initial disruption subsides. The new structure’s failure modes become apparent — the same failure modes that every structure has, because the pendulum only has two positions and neither is correct. The consulting firm produces a “lessons learned” document that recommends “deepening the transformation.” The CTO who launched the initiative is promoted, transferred, or replaced. Their successor inherits a half-completed transformation and a fully-completed consulting invoice.
The 200-page Vision Document sits on a shelf. The maturity model remains at Level 2. The Grafana dashboard is red.
Phase 4: The Quiet Sunset (Month 15-24) — The transformation is not cancelled. Transformations are never cancelled. They are “evolved,” “integrated into BAU,” or “entering the next phase.” The consulting firm departs. The Chief Transformation Officer’s role is absorbed into an existing position. The agile coaches exit through the revolving door. The vocabulary persists — the only durable artifact of the entire initiative.
Someone quietly reverts a critical system to the way it worked before. The Grafana dashboard turns green.
Phase 5: The Next Transformation (Month 24+) — A new executive arrives. Or an existing executive attends a conference. See Phase 1.
The Gall’s Law Violation
Every Transformation Initiative violates Gall’s Law: a complex system designed from scratch never works.
The transformation designs a new organization from scratch. New structure. New processes. New roles. New vocabulary. It does not evolve the existing organization incrementally. It does not identify what works and protect it. It does not start with a simple change and see what happens. It arrives with a 200-page document and an eighteen-month plan and implements the whole thing, from scratch, across the entire organization, simultaneously.
Gall’s Law predicts this will not work. It does not work. The law is not theoretical.
The cruelest irony is that organizations do improve — but they improve by accident, through the slow accumulation of working relationships, institutional knowledge, evolved processes, and the shadow org chart gradually aligning with reality. These improvements are fragile. They are undocumented. They exist in the relationships between people, not in the boxes on a chart.
The Transformation Initiative resets all of them.
Every reorg destroys the informal networks, the trust relationships, the “I know who to call” knowledge that took years to build. The organization that stayed in one shape long enough for things to start working is punished for its stability by an executive who mistakes working-but-boring for broken-and-needing-transformation.
The Transformation Initiative is Gall’s Law’s natural enemy — not because it disproves the law, but because it ensures the law’s consequences are experienced as frequently as possible.
The Approach That Might Have Worked
There exists, in the literature, an approach to organizational change that does not violate Gall’s Law. It is called Agendashift — a framework for continuous, outcome-oriented transformation that starts with what’s working, identifies desired outcomes, and evolves toward them incrementally. It does not design a target state from scratch. It does not require a 200-page Vision Document. It does not need a Chief Transformation Officer. It starts where you are, with the people doing the work, and changes one thing at a time.
It has almost never been tried.
Not because it is wrong — it is almost certainly right. Not because it is unknown — it sits on bookshelves in consulting firms and coaching practices. But because it is boring. It does not produce a slide deck. It does not justify a consulting engagement. It does not create a Chief Transformation Officer role. It does not generate the sense of decisive action that executives need to present to boards.
The board does not want to hear: “We are making small, continuous improvements based on outcomes identified by the people doing the work.” The board wants to hear: “We are undergoing a Digital Transformation.” One of these sentences produces results. The other produces funding.
“You’ve spent years optimizing process. Sprint length. Ceremony cadence. The precise angle of the Kanban board.”
— riclib, Mythology Driven Development — Substack Draft
The tragedy is not that the right approach was rejected. The tragedy is that it was never considered. The for loop does not contain a conditional that checks whether a different kind of loop might work. The for loop does not contain a conditional at all.
The Vocabulary Residue
The Transformation Initiative’s most durable product is not the transformation. It is the vocabulary.
Long after the consulting firm departs, the Chief Transformation Officer is absorbed, and the 200-page document begins its career as a shelf ornament, the vocabulary remains. “Value streams.” “Outcomes over outputs.” “Psychological safety.” “Ways of working.” “North Star.” “Target operating model.” These phrases persist in meeting invites, slide decks, and job descriptions for years after the transformation that introduced them has been quietly abandoned.
The vocabulary is the fossil record of transformations past. An experienced employee can date each layer:
"Synergy" — 2008 (McKinsey engagement)
"Squads and Tribes" — 2015 (Spotify Model phase)
"Value Streams" — 2018 (SAFe implementation)
"Outcomes over Outputs" — 2020 (Product transformation)
"AI-First" — 2024 (the current layer)
Each layer was deposited by a transformation. Each transformation was replaced by the next. The vocabulary accumulated. Nobody removed the previous layer’s words before adding the new ones, so the organization now speaks a creole assembled from five dead transformations, and newcomers learn it the way children learn language — by immersion, without understanding the etymology.
The Chief Transformation Officer
The Chief Transformation Officer (CTO — the other CTO) is a role created by the Transformation Initiative and sustained by the Transformation Initiative. The role reports to the CEO, sits on the leadership team, and is responsible for “driving the transformation.”
The Chief Transformation Officer has no line authority over the people being transformed. She has a mandate, a budget, and a slide deck, but the people doing the work report to someone else. The transformation is therefore an overlay — a parallel org chart laid atop the real one, connected by dotted lines that nobody understands, producing meetings that nobody can decline but nobody can act on.
The Chief Transformation Officer’s success metric is the transformation itself. Not business outcomes. Not customer satisfaction. Not revenue. The transformation. This is measured by “transformation progress” — a metric that measures how much transforming has been done, which is like measuring the success of a diet by how much dieting you did.
When the transformation is sunset, the Chief Transformation Officer’s role is absorbed into an existing position. The other CTO remains. The org chart heals over the wound. The transformation, like a transplanted organ, is either accepted by the body and becomes invisible, or rejected by the body and quietly removed. Either way, the Chief Transformation Officer’s role was temporary, which is the one thing nobody mentioned during the hiring process.
The For Loop
The Transformation Initiative is a for loop without an exit condition.
for {
executive := newExecutive() // or same executive, new conference
vision := consultingFirm.discover() // 200 pages, 18 months
org.transform(vision) // Gall's Law violation
time.Sleep(18 * month) // plateau
org.sunset(vision) // quiet, undocumented
// benefits accrued by stability: reset to zero
// lessons learned: filed, unread
// vocabulary: accumulated
// continue
}
The loop has no break. It has no exit criteria. It does not check whether the transformation worked. It does not check whether the organization improved. It does not check whether the people doing the work were consulted, or happy, or still employed. The loop runs because the loop runs.
“You designed a complex system from scratch. Gall’s Law says it won’t work. It doesn’t work. The law is not theoretical.”
— The Consultant, Interlude — The Blazer Years
The Transformation Initiative designs a complex organization from scratch. Gall’s Law says it won’t work. It doesn’t work. The law is not more theoretical when applied to org charts than when applied to software architecture. Conway’s Law already proved they are the same thing.
The Squirrel’s Dream
The Caffeinated Squirrel does not merely participate in Transformation Initiatives. The Transformation Initiative is the Squirrel’s dream state — a period of unlimited organizational design, where new boxes can be created, new frameworks can be adopted, new architectures can be proposed, and the only constraint is the consulting budget.
The Squirrel thrives in the transformation because the transformation is complexity made legitimate. During normal operations, the Squirrel’s proposals for Platform Teams, Enablement Guilds, and Centers of Excellence are resisted. During a transformation, they are funded.
The Lizard waits. The Lizard has seen the loop before. The Lizard knows that the transformation will sunset, the vocabulary will remain, and the code will continue to run at 47 milliseconds on a server nobody decommissioned. The Lizard does not transform. The Lizard persists.
“The lizard was always there. In the bootblock. In the boardroom. In the blazer.”
— Interlude — The Blazer Years
Measured Characteristics
Average duration of a Transformation Initiative: 18-24 months
Average cost: £2-5 million (consulting only)
Pages in Vision Document: 150-200
Pages of Vision Document read after Month 6: 0
Chief Transformation Officers created: 1 per initiative
Chief Transformation Officers remaining after: 0
Agile coaches hired: 20-100
Agile coaches remaining after: 2-3 (absorbed into BAU)
Maturity level at start: Level 2
Maturity level at end: Level 2
Vocabulary items permanently added: 8-12 per initiative
Gall's Law violations: 1 (large)
People being transformed who were consulted: 0
Benefits accrued by stability, reset by initiative: all of them
Exit condition in the for loop: none
Organizations that tried Agendashift instead: ≈0
