---
title: "Remake: Transform"
date: 2026-08-23
description: Remake: Transform — the final stage of the ADAPT motion. Deliver the plan and embed the capability so the change endures.
author: Mario Thomas
canonical: https://mariothomas.com/remake/adapt/transform/
---

Transform delivers the Transformation Plan and produces the outcome agreed at Remake: Align. It is where strategy is proven in practice, and where the discipline shifts from doing things to being changed by them.

## What Transform protects against {#protects data-toc="What it protects against"}

The substitution of activity for change. Initiatives can be delivered without the organisation transforming; pilots can succeed without scaling; capability can be built in pockets without being absorbed. Transform also protects against the failure organisations rightly fear from external delivery: dependency. A successful Transform does not merely produce delivered initiatives; it produces an organisation that can continue without outside support.

## What transformation really means {#in-practice data-toc="In practice"}

Four characteristics distinguish transformation from busy delivery. Execution and capability building run in parallel, not in sequence: the capability required to operate a delivered solution is built during delivery, and initiatives are designed as vehicles for capability transfer. Governance is operational, not nominal: the decision flows designed at Remake: Plan are actually used, and when delivery exposes what planning could not foresee — and it will — governance absorbs and acts rather than collapsing or deferring. Ownership transitions progressively: external involvement is directive early, advisory later, and peripheral by the end; if it remains central at the close, capability has not transferred. And the stage is alert to its own completion: when a new strategic problem surfaces mid-delivery, the disciplined response is to name it and open a new motion against it, not to absorb it and pretend the engagement is still the same one.

## How Transform runs {#how-it-runs data-toc="How it runs"}

Transform begins when the plan is owned, governance is operational, resources are aligned, and a clear ownership model exists inside the organisation — with explicit acceptance that delivery will surface new information. Each move is run with paired execution and capability transfer, risks and dependencies are managed actively, and feedback loops carry what is being learned into both the current work and the broader strategy. Nothing re-opens decisions that were properly closed in earlier stages: new evidence that genuinely invalidates earlier work triggers a disciplined return to the relevant stage; new evidence that merely makes earlier choices uncomfortable does not.

## The output {#output data-toc="The output"}

Transform concludes not with a closing event but with a state: delivered initiatives with measurable outcomes against the Investment Case, embedded capability across people, process, and technology, an operating model adjusted to support the strategy, and reduced reliance on external support. Completion is not marked by the end of activity. It is marked by the presence of capability — a transformed organisation able to sustain progress on its own rather than renting it.

## The assets in play {#assets data-toc="The assets"}

The [AI Stages of Adoption](/remake/library/ai-stages-of-adoption/) measures the maturity progression the stage exists to produce, [Minimum Lovable Governance](/remake/library/minimum-lovable-governance/) keeps the operational governance proportionate as the work scales, and the outcome is judged against the Investment Case set at [Remake: Align](/remake/adapt/align/) — success measured against the criteria set before the work began, not against the activity completed.

The motion complete, the framework endures: [Remake](/remake/) is what the organisation holds, and the next remaking enters through the same gate.