Case study 03 · S/4HANA / RISE preparation
Preparing 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 week.
Anonymised — reconstructed from missions listed in my CV. No client document, figure or outcome is disclosed.
Business contextThe programme needed to establish what had to be true before a move to S/4HANA under RISE could even be scoped: which prerequisites were met, what depended on what, and which custom objects had no future.
Challenges
- Prerequisites scattered across teams with no owner
- Dependency map missing between custom objects and business processes
- Migration preparation competing with run-the-business releases
- Readiness reported as an opinion rather than a status
My responsibilitiesMigration readiness: structuring the prerequisite register, dependency mapping and the reporting that made progress visible.
MethodologyA prerequisite register with an owner and an evidence link per line, a dependency map across custom objects and processes, and a readiness dashboard reviewed in the same governance as the release calendar — so both were planned together.
Deliverables
- Prerequisite register with owners and evidence
- Custom object dependency map
- RISE readiness tracker
- Monthly readiness dashboard
Business valueThe programme could state its readiness line by line instead of by adjective. Preparation and run-the-business releases were planned on one calendar, which removed the collision that had been silently accepted.