Direct answer
Business Transformation designs the operating model a transformation has to run on: target organisation, decision rights, governance cadence and the change path. It ends with a model the executive committee has signed and a value ledger tracked to a number rather than to a milestone.
What the mandate decides
- Target operating model and decision rights
- Governance cadence and committee design
- Transformation roadmap, sequenced in waves
- The business case each wave is accountable for
- Change, adoption and the metrics that prove it took
- A value realisation ledger with an owner and a baseline
Seven sub-capabilities, seven proven
- Operating model and governance
- Change management
- Operational excellence
- Digital transformation
- Data-driven enterprise
- Value realization
- Innovation and portfolio management
What it is not
It is not a programme. Business Transformation decides the target model; a Programme reaches a destination against it. This page describes no phase plan and no delivery cadence — those belong to the programme that follows.
It is also not the right entry point when the constraint is genuinely technical and the organisation already knows what it wants. A governance workstream in front of a migration that has already been decided adds a quarter and no clarity.
How the mandate runs
It starts with the model that exists, not the one on the org chart. Who actually decides, on what evidence, at what cadence — and where the two diverge, which they always do, the divergence is the first finding.
From there the target model is designed against the transformation it has to carry, rather than against a reference framework. Decision rights, the committee cadence, the RACI across business and technology, and the change path with the adoption measures that say whether the new way of working took.
The value ledger is the part clients underestimate. Benefits per wave, each with a baseline and an owner, so a claimed saving can be checked against the P&L rather than asserted in a steering committee. Without it a transformation reports progress in milestones, which is a measure of activity rather than of value.
The mandate ends when the executive committee has signed the model and the governance has run without ARCHITEKT chairing it.
What it is not
It is not a programme. Business Transformation decides the target operating model; a Programme reaches a destination against it. This page deliberately contains no phase plan and no delivery cadence — those belong to the programme that follows, and describing them here would let a buyer think they had bought the execution.
It is not change communication. A stakeholder map and a comms plan are part of the adoption work, but the mandate is the model itself: who decides what, on which cadence, against which measure. A transformation communicated well and governed badly fails on schedule.
When it is the wrong entry point
When the constraint is genuinely technical and the organisation already knows what it wants. A governance workstream in front of a migration that has been decided adds a quarter and no clarity, and the collective says so rather than selling the wider scope.
Also when the executive committee is not aligned on whether a transformation should happen at all. This mandate designs how one runs; it does not manufacture the mandate to run it, and starting without that agreement produces a model nobody signs.
The measure
Value tracked to a number rather than to a milestone. Each wave carries a baseline, an owner and a benefit the P&L can be checked against, so the question at the end is not whether the programme finished but whether the model produced what it was funded to produce.
Who it is bought by
A chief executive, a chief transformation officer, or an investor who has funded a transformation and can see the organisation around it cannot carry the plan. The common signal is a business case that everyone has approved and nobody can name the owner of.
Exit
An operating model that runs without the operator: decision rights written down, a governance cadence that survives the next reorganisation, and a change path whose next three steps are already sequenced.
Questions
- What does a business transformation mandate actually change?
- Who decides what, on which cadence, against which measure. At Opella, Sanofi's consumer-health business, design was repositioned from a service function into a governance function across a ten-brand ecosystem, and delivery accelerated by 40% through insourcing. Nothing was rebuilt; the authority to decide moved.
- How is value realisation made real rather than claimed?
- By putting a number on the outcome and holding it to the end of the mandate. At Adeo, dismantling legacy systems released EUR 9.5M in FinOps savings, supplier referencing lead time fell from 124 days to 15, and more than 7,000 suppliers were onboarded with a supplier NPS up 50 points. Those four figures come from one operating-model change, not four projects.
- How long does it take?
- A diagnostic runs three to six weeks. An advisory cadence runs two to six days a month for as long as the governance needs chairing. Where the mandate has to be owned end to end, it becomes an interim seat instead.
- How is this different from Technology Strategy?
- Business Transformation decides how the organisation is run. Technology Strategy decides what the technology estate invests in and what it costs. A transformation usually needs both, in that order.