Plan

Plan operationalises the guiding policy into the Transformation Plan: the document the organisation will actually execute against in Remake: Transform. It is the design of action — which moves matter, in what order they should occur, and how they reinforce one another.

What Plan protects against

The most common death of strategy: ambition that never becomes activity, or activity that does not compound. Plan equally protects against its opposite failure, the over-engineered programme plan with hundreds of dependencies and false precision that becomes a delivery artefact in its own right. The subtlest failure it prevents is the substitution of project planning for the design of action: a Gantt chart is not a plan in the sense the motion requires.

What planning really means

Three characteristics distinguish the design of action from project planning. Sequencing is deliberate: early moves are chosen because they create the conditions for later moves to succeed — building capability, generating evidence, surfacing resistance, unlocking dependencies. A plan in which the order of moves is interchangeable is not yet a plan; it is a list with dates. The plan is focused, not exhaustive: it identifies the critical path and concentrates resources where they create compound effect. And governance is designed, not assumed: decision flows, escalation paths, and review cadence are specified as part of the plan, at a cadence that matches the pace of the work. Quarterly reviews will not govern weekly decisions.

Plan is also where capability investment is designed alongside delivery. Initiatives are not just things to be done; they are vehicles for building the capability the strategy requires. A plan that schedules delivery but ignores capability produces dependency, not durable change.

How Plan runs

Plan begins when the guiding policy is stable, when leadership commitment to the direction has survived the first piece of bad news, and when the diagnosis remains the agreed foundation; without these, planning becomes the re-litigation of Remake: Advise. The work identifies the critical path of moves, specifies each with enough clarity to be owned but not so much that planning becomes delivery, justifies the sequence by capability and dependency rather than convenience, and stress-tests the whole against organisational reality: pace, politics, and capacity. Detailed work-package designs and technical architecture decisions are deliberately excluded; they belong inside delivery.

The output

Plan produces the Transformation Plan: the integrated deliverable of the middle stages, assembling the diagnosis from Remake: Diagnose, the guiding policy and verdicts from Remake: Advise, and the validated Investment Case from Remake: Align, with the executable blueprint on top — the sequenced moves, their owners, the governance operating model, the capability build, and the measurement framework. The plan is short, focused, and explicable: if it cannot be summarised on a page, it is not yet ready.

The assets in play

The capability picture assembled through the Five Pillars at Diagnose shapes the capability build the plan schedules, and Minimum Lovable Governance governs the governance design itself: just enough structure to enable the work, never so much that it inhibits it. The Six Board Concerns carry through into the measurement framework.

Plan committed, the motion moves to Remake: Transform: how does the change endure?