Case studies
Three programmes, written as they actually ran
Anonymised reconstructions grounded in the missions listed in my CV: the constraint, the method, the artefacts and the value — without client names, figures or invented outcomes.
Case study 01
Getting a fragmented release process under control
A multi-team SAP landscape where changes arrived unplanned, transports conflicted, and nobody could state with confidence what was going live on Thurs…
Read the case study Case study 02A go-live that had been rehearsed twice before it happened
Sixty dependent cutover steps across Basis, functional and integration teams — and a rollback procedure that had never actually been executed.…
Read the case study Case study 03Preparing a migration without pretending it was a project
RISE migration preparation — prerequisites, dependency mapping and readiness tracking — while the current landscape kept running and releasing every w…
Read the case study