Programme rescue
Re-establish scope, priorities, dependencies, resources, authority and the cadence through which drift becomes visible.
Programme & transformation leadership
Integrate fragmented activity into one executable enterprise outcome.
A complex programme is rarely the sum of its workstreams. Sponsors, organisations, suppliers and specialists hold different parts of the operating picture. Integration means bringing those parts into one governed plan, resolving dependencies and turning strategic intent into delivery.
Defence Training Rationalisation required integration across organisations, people, sites, capital, contracts and long-term affordability — not simply programme reporting.
Authority to integrate.
An illustrative arrival
The Fragmentation
The programme is three months in. Delivery looks good on the dashboard. Every workstream is green. The milestones are being met. The board is satisfied.
Then you sit down with the people actually leading the work.
The first says: “We are on track, but we are waiting for workstream three to hand over the systems specification.” Workstream three cannot finish until workstream seven confirms site capacity. Workstream seven is waiting for Estates to validate capacity against a capital plan that changed last month.
Nobody told you the capital plan changed. Nobody identified Estates as a new critical-path dependency. Nobody joined together the decisions that each workstream believed belonged somewhere else.
But the dashboard is green.
The scenario is illustrative, but the failure mode is familiar: individually credible reports have concealed a programme-level contradiction.
Not malice. Not incompetence. Fragmentation.
Each lead has been given a mandate, budget, people and reporting duties. Each is doing what the governance asks: delivering their own piece. What they may not have is either the information or the authority to see what a local decision does to somebody else.
The programme is structured as an addition problem: workstream one plus workstream two, plus all the others, equals transformation. But transformation is not addition. Transformation is integration.
Value appears when the pieces are sequenced, information is shared, dependencies are exposed and local decisions serve the enterprise outcome. A collection of individually green workstreams can still produce a programme that cannot be delivered.
What the green dashboard can conceal
Invisible dependencies. A workstream believes it has slack because no one has told it that another team's timetable now depends upon its output.
Contradictory decisions. One team moves a system before another team has established the infrastructure to receive it. Both local decisions seemed reasonable.
Compounding slippage. A two-week delay is absorbed silently until several downstream commitments turn it into a much larger problem.
Information latency. Finance, Estates and delivery teams are acting on different versions of the capital plan or programme baseline.
Local success, enterprise failure. A decision that protects one budget or milestone may damage the programme's overall outcome.
The dashboard measures the pieces. Who is measuring the whole?
What integration requires
One operating picture. Not a larger collection of status reports: a consistent view of scope, sequence, resources, interdependencies, capital, people, risks, delivery capacity and pending decisions. When an assumption changes, the affected teams see the same change.
Authority where dependencies meet. A Programme Director need not make every local decision. The role must, however, have the mandate to surface conflicts, bring decision-makers together, resolve sequencing and escalate genuinely reserved matters. Responsibility without decision rights is not integration.
Ruthless simplification. Remove false granularity, identify the main effort and challenge activity that does not advance it. The object is not an additional governance layer. It is clarity about the work that must move together.
Once that happens, slippage becomes visible while it is still recoverable. A changed capital assumption reaches delivery before teams commit to the wrong sequence. Reporting can become trustworthy because it describes the system rather than an assortment of local promises.
The character of an integrator
A programme administrator can collect reports and chase milestones. Those tasks are necessary. An integrator must also be able to challenge inherited assumptions, make competing interests visible, insist upon common evidence and bring specialists behind a shared mission.
That requires critical assessment, practical courage, focus and communication both upwards and across the organisation. It requires the judgement to accept that a locally inconvenient change may be essential to the whole.
What this meant on Defence Training Rationalisation
Across the Ministry of Defence programme, the integration problem encompassed 81 organisations, roughly 23,000 people and 54 sites. Around 1,200 plans had to be brought into one operating picture. The work crossed the three Armed Services and included the MOD Police, provost and Royal Military Police communities, the MOD Civil Service and intelligence organisations.
The objective was common capability, not uniformity for its own sake. Combining training and development across any two or more Services could justify integration where the operating and economic case held. Steven concentrated on what was genuinely common across organisations.
Some individual Service capability was lost in the common integration design. That was a real trade-off, not a detail to hide. The three Services were therefore given funding and authority to develop their own add-on programmes to restore the specific capability gaps. The common platform and Service-specific additions were both parts of the solution.
The programme's £4.33bn figure is a programme-level savings figure across the wider portfolio, not cash personally recovered or a result attributable solely to one individual.
The work was integration. The discipline was clarity. The objective was an executable outcome without pretending that every capability requirement was identical.
Turn institutional complexity into controlled delivery.
Steven brings specialists behind a shared mission, connects what each can see and converts institutional complexity into work they can collectively execute.
“the pragmatism to turn strategy into detailed plans”
Selected from 19 public professional recommendations on LinkedIn. Review selected supporting evidence →
- Assure the whole system Connect workstreams, resources, budgets and decisions.
- Expose dependencies Make blockage, sequencing and slippage visible.
- Stabilise execution Convert fragmented plans into one governed route.
Demonstrated: £18.6bn scale across 81 organisations, approximately 23,000 people and 54 sites, integrating around 1,200 plans into one operating picture.
Board and committee experience includes two years chairing an Audit Board and wider audit, assurance and risk responsibilities. The principal functional focus—risk, major real-estate portfolios, and HR and workforce change including TUPE and trade-union engagement and negotiation—reinforces estates consolidation, organisation design, workforce transfer and assurance at programme scale.
Location and working model: UK or international; on-site, hybrid and remote arrangements are considered according to the mandate. Opening-stage and control-recovery interventions will ordinarily require substantial on-site presence.
Mandate scope
Control
Integration
Realisation
Delivery control is its own executive discipline.
One operating picture
Connect workstreams, budgets, people, suppliers, estates, risks and decisions into an executable whole.
Benefits beyond closure
Distinguish formal completion from the operating integration required for successor organisations to perform.
Proven scale
The £18.6bn transformation was an operating system, not a headline procurement.
The territory included 81 organisations, approximately 23,000 staff and contractors and 54 sites; mechanical and electrical engineering, logistics, medical, police and intelligence training; unions and TUPE; estate, supplier and Treasury interfaces; closure, relocation, merger and the formation of six successor structures.
An initial three-month fixed-term appointment as Colonel-level (OF5) Head of Plans, Risk & Integration was repeatedly extended for five years. Chief Operating Officer was the accepted working title for the integrated responsibility; the formal-title reconciliation is set out on the Record. Within six months, the functional breadth encompassed plans, risk, finance, suppliers, people, estates and delivery across the programme. The work converted approximately 1,200 separate plans into one integrated operating picture and made dependencies, sequencing and slippage visible.
Capability trade-offs and Service-level recovery. The common programme did not preserve every specialist capability. The three Services were provided funding and authority to develop add-on training programmes to close gaps specific to their individual needs. Integration of training across any two or more Services could constitute a worthwhile common solution; it was not necessary or appropriate to impose every requirement uniformly upon all three.
Defence commercial application · 2013–2019
Evidence
Model
Decision
Thirty years of actual fleet evidence replaced an inherited cost proxy.
Build the real baseline
At MOD Abbey Wood, Steven assembled approximately thirty years of Royal Navy repair and maintenance costs and developed performance metrics for future support of Type 45 destroyers and both Queen Elizabeth-class carriers.
Test the cost driver
Rather than assume tonnage determined support cost, he tested actual expenditure against ship’s complement. The resulting unit cost was unexpectedly consistent across classes and provided a stronger whole-life forecasting basis.
Carry evidence into negotiation
The model challenged an internal provision approaching £1bn, survived independent cost challenge at two-star level and supplied the lower-cost basis used in bidder negotiations.
Public records show Babcock’s MSSP preferred-bidder position at approximately £360m over seven years and the final four MSSP contracts at £320m. Steven records an approximately £410m fully burdened MSSP and MEC position. Evidence and boundaries →
Suitable appointments
- Programme Director
- Chief Transformation Officer
- Integration Director
- Programme Rescue Lead
- Benefits Realisation Lead
- Complex Stakeholder Assurance
The mandate must provide real authority over programme governance, dependencies, escalation and decision-quality information. Responsibility without the means to control delivery is not an executable appointment.