Change

Business Transformation Done Right: A Guide for Companies

Stefan Benndorf
Partner & Founder

Business transformation is a fundamental realignment of how a company makes money: the business model, the operating model, the organisation and the culture, changed together. It is distinct from improvement work, which makes the existing model run better. The distinction decides how the work has to be governed, because a transformation has to survive a period in which the old model is still paying the bills and the new one is not.

Why the cost of postponing a transformation stays invisible

The decision to postpone a transformation is rarely taken explicitly. It happens through a sequence of quarters in which the existing model still delivers its numbers and the case for changing it carries no deadline. By the time the numbers move, the remaining options are the expensive ones.

The damage appears before it appears in revenue: in the cost of serving customers through structures built for a different product, and in the share of engineering capacity spent maintaining what should have been retired.

What separates transformation from change

Change improves what already exists: faster processes, cleaner workflows, adjustments to a market that moved. It is bounded, and its success criterion is the old one measured better. Transformation replaces the criterion. The business model, the operating model and the culture are realigned together, and the metrics that judged the previous model stop being the right ones.

The automotive industry is the visible case: vehicle manufacturers moving into mobility services. That shifts the revenue model from a one-off sale to a recurring relationship, and almost every function behind it has to change with it.

What triggers a transformation

Transformation is often triggered by external and internal drivers.

External drivers:

  • Digitalisation: AI, automation and cloud change the cost base of a business model, which changes what a competitor can afford to charge.
  • Changing customer needs: expectations are set by the best digital experience a customer has anywhere, not by the industry average.
  • New competitors: disruptive entrants that attack one profitable slice of the value chain rather than the whole business.

Internal drivers:

  • Outdated processes: manual workflows that were affordable at the previous volume and are not at the current one.
  • Cultural shift: a culture calibrated for a stable market, which reads every new proposal as a risk to be managed.
  • Growth: scale that breaks the structures and systems that got the company there.

Whether the trigger is necessity or ambition changes the programme, not the work. A transformation started under pressure has less room for a pilot and a shorter budget horizon. That is the main reason the same design costs more when it starts late.

The four obstacles that stop transformations

All four are identifiable before they bite. The reason they still bite is that each one looks like a different kind of problem at the time.

1. No target state, so no way to measure progress

Programmes get launched on a direction rather than a target state. Without one, every team resolves the ambiguity locally, and the resulting work is individually reasonable and collectively incoherent.

Solution: a transformation requires a clear target picture with three things settled: why it is happening, what the end state is, and how execution gets measured. Milestones without a target state measure activity.

2. Resistance, which is usually a rational response

Resistance is roughly proportional to what someone stands to lose. It concentrates in the middle layer, where people have to execute the change and absorb its consequences at the same time. A transformation that stays top-down gets compliance rather than adoption.

Solution: name what changes for each affected group specifically, including what gets worse for them. Involvement in the design is what turns information into acceptance, and it has to happen while the design can still change.

3. Transformation running alongside a full operating load

Transformations need time, money and expertise, and they compete for all three with an operating business that has customers waiting. Running both at full load produces two half-finished things.

Solution: prioritise explicitly, which means naming what gets stopped rather than what gets added. Free named capacity instead of asking for extra effort, define who owns each workstream, and buy in the expertise the company does not have rather than training for it under time pressure.

4. A culture that treats the change as someone else's project

Bureaucracy, low trust and silo behaviour rarely block a transformation openly. They add a review cycle to each decision, and the accumulated delay is what ends the programme.

Solution: give the transformation a decision right rather than a mandate. A team that can stop a project has weight in the organisation. A team that can only escalate has none.

What makes a transformation hold

  1. A target state specific enough to be wrong. A direction cannot be falsified, so it cannot settle an argument.
  2. Leadership that carries a cost. The signal everyone reads is which existing commitment a leader gives up for the transformation.
  3. Structures that match the new model, in particular who owns which part of the value chain once it changes shape.

The three fail together. A target state that nobody's authority stands behind gets treated as an option, and a structure that changes without one gets filled with the old behaviour.

Why a transformation has no completion date

The programme ends. The capability it builds is the part that lasts, because the next realignment tends to arrive before the current one has settled. Companies that keep that capability, the ability to change a structure and a metric set without a crisis to justify it, pay less for every change after the first.

At scaleon we have founded and scaled digital companies ourselves, so the transformation problems in this article are ones we have had to solve from the inside.

If you are weighing a transformation, the useful first conversation is about which of the four obstacles above is already present in your organisation. We are glad to have it.

Business transformation: the questions we get asked most

What is business transformation?

Business transformation is a fundamental realignment of how a company creates and captures value. It changes the business model, the operating model, the organisation and the culture together, rather than improving any one of them. The defining feature is that the metrics used to judge the previous model no longer apply to the new one.

What is the difference between change and business transformation?

The practical test is whether the work would still make sense if the current revenue stream disappeared. Improvement work would not, because it exists to make that stream perform better. A transformation would, because it is building the stream that replaces it. Scope, budget and duration all follow from that one difference.

What triggers a business transformation?

Externally: a technology that changes the cost base, customer expectations set outside the industry, and entrants attacking one profitable part of the value chain. Internally: processes that were affordable at a smaller volume, a culture calibrated for a stable market, and growth that outruns the structures behind it. Necessity and ambition both work as triggers.

Why do business transformations fail?

Four causes cover most of it. No target state, so teams resolve the ambiguity locally. Resistance treated as a communication problem instead of a loss to be named. The programme competing with the operating business while nothing gets stopped. And a transformation team with a mandate but no decision right, which the organisation reads accurately as optional.

How do you know a transformation is working?

Not from the milestone plan, which measures the programme's own activity. Three signs are harder to fake: revenue or margin appearing from the new model rather than the old one, requests in the changed area no longer routing through the people who owned the previous model, and the old workaround falling out of use because it no longer helps anyone.

Content
Share now
Link Icon
Link kopiert!
Stefan Portait

Stefan Benndorf

Partner & Founder

Stefan ist Founding Partner von scaleon und Experte für Strategie- und Organisationsentwicklung, Strategieumsetzung mit OKRs und anderen agilen Methoden sowie Digital Business Building. Vor scaleon war Stefan COO, CEO und Co-Founder verschiedener Digitalunternehmen und auf mehreren Kontinenten aktiv. Stefan arbeitete mehrere Jahre bei der Top-Management-Beratungsfirma Altman Solon für Telekommunikations-, Medien und Private Equity Unternehmen. Er hat Abschlüsse in Business und Public Administration, Public Policy von der Handelshochschule Leipzig (HHL), der London School of Economics (LSE) und der Hertie School of Governance.

Connect on:
LinkedIn
Our Insights

More articles you might like

We regularly publish practical frameworks, case studies, and strategic perspectives on the topics that matter most to digital leaders: growth strategy, value creation, execution, and transactions.

Explore all Insights
Start a conversation

Let's talk about your growth challenge.

Whether you're preparing for a fundraise, navigating a growth plateau, or evaluating a transaction we'd like to hear about it. No pitch, no pressure. Just a focused conversation about where you are and where you want to go.

Send us a message

Fields marked with * are required.
Thank you!
Your submission has been received.

We will contact you back in the next 48 hours.
Oops! Something went wrong while submitting the form.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.