Digital transformation
Most transformations fail — and it takes many organizations more than one attempt to get it right. But the failure patterns are predictable. If you want to succeed, start by understanding why others keep failing the same way.
Software has transformed every industry. Every company is becoming a software company because business models transform from selling products to creating experiences. This means companies must change — not only their business model but also the way they work, the way they are organized, and the way they leverage technology.
This transformation has many names. Digital transformation. DevOps transformation. Cloud transformation. AI transformation. But they are all part of the same story. You can only succeed when you master all of them. And the hard part is never digital, DevOps, cloud, or AI — the hard part is the transformation itself.
Almost every customer I meet believes their situation is unique. "We are regulated." "Our product can kill people." "We have government contracts." "We are publicly traded." "We have legacy systems older than our employees."
They are not special. Not in the ways that matter.
Could your product kill people if it has a defect? So could cars, airplanes, trucks, and medical devices. Do you have to comply with strict standards? So do thousands of other companies. Work for governments? In highly regulated finance? With mainframes from the 70s?
The research is clear: DevOps and transformation practices work across all industries, all sizes, all regulatory contexts. The principles are universal. What differs is the courage and discipline to apply them.
This is actually good news. It means the problems you face have been solved by others. You can learn from their failures instead of experiencing them yourself.
The biggest blocker to change is complacency. If people in your business are comfortable with the status quo, they will resist change and keep doing business as usual.
You need a true sense of urgency — a deep determination to win, not anxiety about losing. Management pressure that creates fear is not urgency. It is coercion. And coercion produces compliance theater, not genuine transformation.
Urgency often arises for different reasons at different levels of the organization:
If these forces are not aligned into a single direction, they neutralize each other. The CEO pushes for "digital transformation" while teams push for "less bureaucracy" — both valid, but unless connected into one clear story, nothing moves.
It is easy to replace tools, processes, and roles. It is hard to change behavior, culture, and stories. Without a clear vision, the transformation will not yield results.
When I hear "we are not Microsoft or Google" or "we are not a cutting-edge internet company," it tells me the vision is missing or wrong. A good vision for transformation is a clear, compelling statement of where the organization is going — not a comparison to what you are not.
The Golden Circle helps here: start with WHY (purpose and urgency), then HOW (approach), then WHAT (the specific changes). Most organizations start with WHAT and wonder why people do not follow.
Do not underestimate the power of vision. When Volkswagen declared "goTOzero" with a target of carbon neutrality by 2050, or when Mercedes-Benz committed to carbon-neutral cars and production within 20 years — those statements created permission and direction for thousands of decisions. People could align their work to something larger.
Without that, transformation becomes a list of projects nobody believes in.
Every transformation encounters obstacles. Regulations. Organizational structure. Working council politics. Legacy contracts. Budget cycles. Compliance requirements.
The question is whether you treat them as problems to solve or as reasons to stop.
Many regulations that seem to require waterfall (ISO 26262, GxP, SOX) actually just require evidence of best practices. If your practices are demonstrably superior to the recommended ones, you can justify that and still pass an audit. Most "regulatory blockers" are actually internal interpretations that nobody has challenged.
The same is true for organizational obstacles. Tight job categories, departmental boundaries, procurement processes — these were all created by humans within the organization. They can be changed by humans within the organization. If the will exists.
Consultants have a bad reputation in many companies, often deserved. Their appearance is associated with layoffs, PowerPoint decks, and recommendations that ignore reality.
But transformation is like learning a sport. You do not just buy equipment and watch videos. You find a coach who has done it before and can guide you through the awkward early stages where nothing works right.
Building new organizational capabilities requires experienced guidance — not to do the work for you, but to help you build the skill to do it yourself. The goal is capability transfer, not dependency.
The cost of good guidance is almost always cheaper than the cost of a failed transformation attempt. And most organizations need more than one attempt to get this right — precisely because they try to figure it out alone.
These five reasons are not random. They cluster around the Three-Layer Transformation Model:
The organizations that get transformation right do three things:
Every one of these five reasons has been solved by other organizations in situations as complex as yours. The patterns are known. The solutions are proven. The only question is whether your organization has the honesty to diagnose itself and the courage to act on what it finds.
Next step
Pre-order the book, get the assessment, and receive practical notes on why transformations fail - and what actually works.