Business Strategy as Code
The method, in four parts
A strategy review can end on pillars nobody in the room can trace back to evidence, or on a problem statement nothing has put under test; either way, a conclusion has been asserted, not shown to hold. Business Strategy as Code is a method for making that record auditable and testable — for consultants and advisers, strategy and transformation leads, and the decision-makers who rely on the result. It does not replace judgement, and it does not claim to produce better decisions, better strategy or improved outcomes: it records how a conclusion was reached, so that someone other than its author can check it. It is a method description for consultancy and advisory work, not legal, financial or investment advice. That checking rests on one rule.
The governing rule
No output without a traceable input.
When it applies
The method has a cost, and all four chapters name where that cost is owed and where it is not; the conditions below hold across the series.
Use it when
- the decision is costly and hard to reverse, so getting it wrong is expensive to have run with
- evidence exists in more than one source, and there is time to gather and use it
- the work will change hands, and whoever inherits it needs the record of how the conclusion was reached, not only the conclusion itself
Lighten it, or choose another approach, when
- events move at a pace where deliberation costs more than it returns
- the decision is operational, reversible and already well understood, so the method costs more than it returns
- evidence sits in one place only — a partial pass, named as such, is more defensible than running the full method on evidence that thin
Why four parts
Business Strategy as Code is published in four parts. The first, diagnosis, produces one sourced problem statement. The second, the analysis chain, takes that statement through fifteen ordered stops to a set of strategic pillars. The third, the digital-transformation chain, takes those pillars through ten ordered Links to a governed transformation strategy. The fourth, the execution chain, takes that strategy through eleven ordered Moves to benefits realisation. Reading the diagnosis chapter does not require the analysis chain, though the chain has nothing to open on until a diagnosis has produced a statement for it.
The figure below shows how the four parts hand off to one another: each line names the output that meets the next part's entry contract.
Solid line = specified interface.
Chapters
- Diagnosis Chapter 1
Diagnosis is a method for producing and testing a scoped problem statement before an analysis chain may open on it.
It serves consultants and advisers scoping an engagement, strategy and transformation leads opening a piece of work, and the decision-makers who will be asked to commit to what the statement claims.
A statement is admitted only once it has survived a fixed set of adversarial challenges, put by named challengers accountable for what it measures or costs, which is what makes it falsifiable rather than merely well-worded.
The statement it produces is the only connection to the analysis chain that follows: Chapter 2's entry contract admits it, and nothing else crosses.
- The Analysis Chain Chapter 2
The analysis chain takes an admitted problem statement through fifteen ordered stops to a set of strategic pillars, with every finding coded and every downstream claim citing the codes it derives from.
It serves consultants and advisers, strategy and transformation leads, and the executives, boards and investors who rely on the result, for decisions that are costly to reverse, face outside scrutiny, or change hands.
Each stop carries its own contract check, and the chain makes an analysis auditable; its sequence is reasoned, not empirically benchmarked.
It opens only once diagnosis has produced a statement meeting its entry contract, and it hands its own pillars on to the chain that follows.
- The Digital-Transformation Chain Chapter 3
The Digital-Transformation Chain takes an admitted set of strategic pillars through ten ordered Links to a single governed, metricated digital-transformation strategy, with every step bound by a stated check.
It serves transformation leads scoping a piece of work, technology and operations leaders choosing an operating model, and the governance forums that fund or halt what it stages.
An entry contract admits or refers each pillar on four named clauses, and a pillar whose admitted assumption is later falsified returns to Chapter 2, never repaired in-chain.
It opens only once the analysis chain has admitted a pillar meeting that contract, and it hands a bounded strategy pack on to Chapter 4, never a delivery plan.
- The Execution Chain Chapter 4
The Execution Chain takes an admitted strategy pack and turns it into an auditable record of mobilisation, delivery, adoption and benefit, never a claim that a transformation succeeds.
It runs eleven ordered Moves across four acts, naming a sponsor and rollout posture, opening a risk register before funding continues, and building the coalition the change reaches.
A cadence reviews exposure weekly, delivery and adoption monthly, and releases each wave's funding quarterly on one of three verdicts, closing on a benefits ledger checked against Chapter 1's success criteria.
It claims no more than an execution auditable end to end: no study shows this chain, a sponsor or a governance cadence raises a transformation's success rate, and no base rate for change failure is defensible.
Each chapter is dated and cited independently; follow the link to a chapter for its own colophon, which carries the citation form and update date that apply to it, not to the series as a whole.
Shared conventions : the RFC 2119/8174 key words every chapter uses are defined once.
strategyascode.org