SAP S/4HANA rollout
The team shape and the sequence for an S/4HANA rollout: who is on in which phase, and the roles that are always scoped too late.
Intelligence
What an enterprise programme actually needs on it, phase by phase. The streams, the sequence, and the roles that are reliably scoped too late.
Why it exists
A method tells you the phases. It does not tell you who has to be in the room during each of them, or which role will be discovered late enough to move a date. That is the part we are asked for most often, so it is the part we published.
Each archetype below is drawn from programmes we have staffed, and names phases the way the vendor method names them. Team sizes, effort and hiring times are held back rather than estimated.
Archetypes
The team shape and the sequence for an S/4HANA rollout: who is on in which phase, and the roles that are always scoped too late.
The team shape and the sequence for an Oracle Fusion implementation, including the two streams that most often delay a pilot.
The team shape and the sequence for a Salesforce multi-cloud programme, including the skills most often assumed to be interchangeable.
Ask
Tell us the shape you are running and we will come back with the staffing plan against it.