Wolf&Grayson EditorialTransformation specialist Roland U. Hoffmann says enterprise strategy rarely fails where executives go looking for failure. It gets approved, resourced, and communicated, and then produces far less than it promised, with no single decision anyone can point to as the moment it went wrong. “Strategy isn’t failing in the C-Suite,” he says. “It’s absorbed by complexity on its way to the market.”
The absorption follows a pattern Hoffmann traces back to growth itself. A startup of five or six people makes decisions in real time because everyone can see the whole picture and personal relationships carry direction without formal structure. Scale makes that impossible, so relationships give way to policies, divisions, and documented agreements between groups.
Structures solve coordination problems, and together they accumulate into something nobody designed. Authority stays with leadership while control migrates to wherever the work gets done, which means an executive can own a direction completely and still lack the ability to move an organization toward it. SODA, the System of Disciplined Adaptability built by Hoffmann, is aimed squarely at that gap.
Where Value Leaks Between Functions
Hoffmann locates loss at handoffs, the points where information, responsibility, and risk pass from one function to another. Marketing hands to sales, sales hands to operations, and each group evaluates the same work through its own priorities, incentives, and standards. Every transfer creates an opening for delay, rework, misunderstanding, and renegotiation.
“Nobody wakes up setting out to slow down the company,” Hoffmann says. “They’re simply protecting the value of their part.” Teams optimize the portion of the workflow they control and defend the quality they have built, which is what a well-run function is supposed to do. The end-to-end outcome erodes anyway, because local excellence and enterprise value are different objectives.
Why Modernizing First Rarely Works
The conventional response to organizational drag is modernization, replacing the aging systems that are assumed to be causing it. Hoffmann treats those systems as evidence rather than cause. Legacy infrastructure is usually a symptom of accumulated complexity, and the workflows running on it encode years of agreements, controls, and business decisions that were reasonable when they were made.
Replacing all of it at once introduces substantial risk and, in his experience, rarely changes behavior, since the same handoffs and incentives survive the migration intact. “The goal isn’t to replace everything old,” he says. “It’s to unblock value in movement.” He advises improving how value moves through the organization first, then modernizing the infrastructure carrying it. A company that rebuilds its systems without addressing how work changes hands has bought faster machinery for an obstructed process.
Automation Amplifies Whatever It Finds
The same reasoning shapes how Hoffmann approaches automation and AI. “Automation scales predictable standardized processes,” he says. “It doesn’t improve them; people do that.” An inefficient workflow, once automated, becomes an inefficient workflow running considerably faster.
The failure he sees most often is automation applied to individual activities before anyone has mapped the end-to-end outcome. Workflows need to be visible, measurable, and stable first. There is also a distinction worth drawing between scaling work an organization already understands and doing something new. Work performed once, in order to learn, cannot be automated at all. Technology is only infrastructure; transformation is changing how work gets done. If you treat the first as though it delivers the second, you get expensive systems running unexamined processes.
What Makes Change Survive Its Own Launch
Organizations drift back toward established behavior. Hoffmann’s answer to that is “You don’t scale a transformation; you scale a way of working.” Change persists when the new approach is easier, faster, and better performing than what it replaced. This is also why new capability cannot be installed by decree. It has to start small, stay protected while it develops, and grow over a quarter or two until it is strong enough to survive the organization’s instinct to eliminate anything unfamiliar.
Transformations that work eventually stop being special projects and become ordinary operations. That is what SODA is built to install, not a finished transformation but the capability to keep adapting, which is the only version of momentum that holds. To learn more, connect with Roland U. Hoffmann on LinkedIn.
