Turning Transformation Ambition into a Realistic Path

An organization does not change one department at a time.

Dividing an organization into domains or capabilities helps. 

Think of capabilities such as Customer Service, Sales, Data Management, Production, Logistics, or Finance. Looking at them individually makes it easier to identify where performance needs to improve and where investment is required. 

But organizations do not operate as a collection of independent capabilities. They operate as a system. 

Imagine a company that wants to significantly improve Customer Service. It invests in digital channels, AI-enabled support, new service processes, and a modern customer service platform. On paper, Customer Service is improving. But what if the company's customer data is incomplete, fragmented, or unreliable? 

At some point, weak Data Management will limit Customer Service's potential. AI cannot provide highly relevant customer support without reliable customer information to work with. This does not mean Customer Service has to wait until Data Management is perfect. It means the organization needs to understand how far Customer Service can progress before Data Management becomes the bottleneck. 

The same applies to Sales. A company can invest heavily in CRM, lead generation and sales capacity and successfully generate more business. But if Production, Logistics or Service Delivery cannot handle that additional demand, better Sales performance creates a new problem elsewhere. 

What looks like an improvement in one area can therefore put pressure on the organization as a whole. 

Instead of jumping directly from today's organization to an ambitious future state, you can define a number of realistic intermediate states. 

For example, an organization might first improve the quality and availability of customer data. Once that foundation is strong enough, it can introduce more advanced personalization in Customer Service. Sales and Delivery may need to increase their capabilities together. A shared technology platform may need to mature before several business areas can take their next step. 

Sometimes the right decision may even be to slow down investment in one area until the rest of the organization is ready. 

That is not slowing down transformation. It is preventing investment from running ahead of the organization's ability to turn it into value. 

You don't need to become world-class at everything immediately.

Another common transformation problem is that ambitions quickly become very large. Once a capability is identified as strategically important, the target often becomes “best in class” or “world class”.  But does every capability need to reach that level immediately? Or even at all? 

Consider a capability that performs poorly today. The first priority may simply be to make it reliable and fit for purpose. That improvement alone could already create significant business value. 

Moving from “poor” to “good” may be exactly what the organization needs today. Moving from “good” to “excellent” could come later, when other capabilities are ready, additional investment is justified, and the strategic need still exists. 

This matters because budgets, people, and management attention are limited. 

Trying to achieve excellence everywhere at once can result in a few initiatives consuming enormous amounts of money and attention while other important capabilities remain underdeveloped. 

Transition architecture introduces a more practical question: What is good enough for the next stage of our strategy? This is not about lowering ambition. It is about staging ambition. Improve. Create value. Learn. Then take the next step. 

Transformation is not a waterfall. 

Transition architecture does not mean creating one enormous sequential roadmap where capability A must be completely finished before capability B can begin. Organizations are too complex for that. 

Many capabilities can and should evolve at the same time. The objective is to understand how far they can sensibly progress together. 

For example, Data Management does not have to be “finished” before Customer Service can improve. But it may need to reach a certain level before another major investment in AI-driven Customer Service starts creating real additional value. Another important constraint is the organization's capacity for change. 

Two transformation initiatives may have no direct dependency and still compete for the same data engineers, IT teams, budgets, business experts or leadership attention. Individually, both projects may make perfect sense. Running both at full speed at the same time may not. 

A realistic transformation plan therefore needs to answer three questions: