Table of Contents
TL;DR
By the end of our second transformation, everything, literally everything, ran on the new platform: accounting on SAP, HR and payroll on SaaS, merchandising on a real merchandising system. That completeness was the point. A transformation that modernizes ninety percent of a company leaves the other ten percent as permanent drag: unowned, unintegrated, and waiting to fail. “Everything” is not ambition. It is the definition of done.
People ask what our transformation covered, and the honest answer sounds like bravado: everything. By the time the second transformation at the major national retailer was complete, we had brought accounting from paper to SAP. HR and payroll ran on a SaaS model. Merchandising ran on an actual merchandising system instead of the improvisations it replaced. Every department, every major function, everybody, was on the new equipment, using the new systems. Literally everything.
I emphasize the completeness because it was the hardest-won property of the whole program, and because its absence is the most common failure mode I see in transformations today.
The gravity of “everything except”
Every transformation faces constant pressure to become “everything except.” Except this department, because they are mid-busy-season. Except that system, because it works fine and nobody fully understands it. Except the homegrown tool in the corner, because the person who wrote it left. Each exception is individually reasonable, and collectively they are how a transformation dies while appearing to succeed.
Here is what an exception actually costs. The excepted system still needs to talk to everything you modernized, so you build and maintain bridges between the new world and the old one, and those bridges are the most fragile things you own. The excepted system still needs skills to operate, so you retain expertise in a dead platform, an expense that grows as the people who have it leave. And the excepted system becomes unowned: not in the new support model, not covered by the new monitoring or disaster recovery, drifting toward the fate of the server we found under a desk, which was precisely a system that escaped the transformation’s scope because it had escaped the inventory.
How “everything” actually gets done
Completeness was not achieved by heroic simultaneity. We did not convert the company in one gesture; the platform cutover was a big-bang weekend, but the functional transformations around it, accounting, HR, payroll, merchandising, landed as their own efforts inside one program with one non-negotiable rule: the program is not finished while anything remains. Sequence is a tactic. Scope is a commitment.
The distinction matters because sequencing pressure and scoping pressure feel identical in the moment. “Let’s do accounting later” can be a sequencing decision or the first exception, and the difference is whether “later” has a date and a budget. In our program it always did, which is why later eventually arrived for everything.
Put a number on the exception tax and the scope argument wins itself. Every excepted system carries the bridge (built once, maintained forever), the skills retainer (rarer and pricier each year the platform ages), and the incident premium (unmonitored systems fail into surprises rather than tickets). In our program, whenever “leave it alone” surfaced as an option, pricing those three lines honestly made the exception more expensive than the migration in every case but genuine end-of-life systems already scheduled for retirement, which are the one legitimate permanent exception: things dying on a date do not need transforming, they need a headstone with a date on it.
A transformation that modernizes ninety percent of a company leaves the other ten percent setting the speed.Share on X
The executive’s version of this lesson
If you are sponsoring a transformation, the scope question to hold your team to is not “what are we transforming,” which produces an inspiring list. It is “what are we not transforming, and what is the plan for each of those,” which produces the truth. Anything on the second list without a date and an owner is not a deferral. It is a decision to run a two-speed company indefinitely, and the slow half of a two-speed company sets the speed.
Our program ended with the second list empty. That, and not the go-live parties along the way, is what “transformation complete” means.
For more from this series, see the The Digital Transformation Hub: real transformations, lived from the inside, decades before the term existed.
The Guides That Get Your Book Written, Published, and Sold
Four short, practical guides on writing, publishing, and selling your book, plus the occasional note when there's something worth your time. No fluff, no daily inbox clutter. Drop your email and they're yours.
We use MailerLite to manage our list and send these emails. Your address is used only to send you what you signed up for. We will not sell it, share it, or use it for anything else, and you can unsubscribe anytime.