Keystone

Programmes fail in Build & Test because the front end was rushed.

Keystone is an opinionated, openly published methodology for ERP and digital transformation programmes. It refuses to skip the front end — Pre-Programme and Selection — because that's where outcomes are decided.

Pre-Programme Selection Setup & Design Build & Test Deploy Post-Programme

Six phases divided into 20 stages. Twenty-six years of working out what holds and what doesn't.

Read it

Open the methodology

Six phases, twenty stages, the gate scheme, the eight testing levels, the role catalogue, the adoption workstream. Structured for a sceptical reader who wants to drill in where it matters.

Open the methodology →
Try it

Or dive into the interactive dashboard

The Command Centre is the methodology turned into a tool. Walk it against your own programme to see where you sit, where you diverge, and what the next move looks like. No sign-up, no gate.

Open the Command Centre →
Use it

Or take the templates

Pre-drafted artefacts for every phase — Vision & Strategy, RFI, Solution Design, Test Strategy, Cutover Runbook, the three Governance Packs and more. Editable Word, PowerPoint and Excel. Free, no gate, fork them into your organisation's templates.

Go to Supporting Documents →
01

What it is

Twenty stages organised across six governance phases, from problem definition to benefits realisation. Two real board gates. One executive Go/No-Go before cutover. Phase checkpoints between, where the work is reviewed but the programme keeps moving.

Four business case (BC) checkpoints across the lifecycle, not one at the end — the labels on the diagram below. Eight testing levels with explicit role distinctions, including non-functional testing as a level in its own right. Adoption treated as a governed workstream, not a soft-skills afterthought.

BC checkpointS2 · Benefits BC checkpointS6 · Funding Envelope BC checkpointS9 · SI ROM BC checkpointS12 · Full Business Case Pre-Programme Selection Setup & Design Build & Test Deploy Post-Programme Stages 0–5 6–9 10–12 13–14 15–17 18–19 Four business case checkpoints across the lifecycle — not one at the end
Fig. 01 Keystone lifecycle, with four BC checkpoints overlaid. Source · Middleton Dynamics, 2026

Opinionated, ERP-agnostic, built from real multi-site programme experience. Free to use, adapt, or teach.

02

What most methodologies blur, Keystone names

  1. 01

    Role distinctions most methodologies blur.

    Process Owners are not SMEs. Programme Managers are not Project Managers — and Project Managers don't show up until Programme Setup & Mobilisation (S10), because there are no workstreams to run before then. Benefit Owners are named at Value Definition & Case for Change (S2), not at the end.

    Read the role catalogue →
  2. 02

    Pre-drafted artefacts, not blank pages.

    Workshops arrive with structured starting points — vision drafts, value definitions, governance terms of reference, RFI templates. The conversation is "is this draft right?", not "what should we do?".

    Read the artefacts page →
  3. 03

    Adoption as a governed workstream.

    Stakeholder analysis, comms strategy and training are work products with stage-gate criteria, not a culture-and-engagement vibe at the end.

    Read the adoption page →
03

Proof of practice

Twenty-six years on the front line of ERP delivery. Thirty-plus programmes and projects — large to small, across multiple platforms — delivered both from the SI side and Client-side. Fifteen years of programme-board exposure across PLC-scale clients. Keystone is what's left after stripping out the things that didn't hold under load.

04

Three ways to start

Try the methodology on your own programme.

Open the Command Centre →

Want to talk it through?

Book a 30-minute call →

Just want the overview?

Download the framework →