By Shivacha Engineering
The multi-year plan problem
Large transformation programmes often begin with a comprehensive plan and a long period before anything changes for customers or staff. By the time delivery starts, priorities have moved and confidence has faded.
Organise around value streams
Structure the programme around specific journeys and processes — opening an account, handling a claim, onboarding a supplier — rather than technology layers. Each value stream gets an owner, a baseline and outcome metrics.
Foundations that pay for themselves
API layers over legacy systems, shared identity and a cloud platform are foundations worth building — but only alongside the first value stream that needs them, so they are shaped by real use rather than speculation.
- Build foundations with the first use case, not before it
- Reuse them for the next value stream
- Measure outcomes, not activity
Adoption is part of delivery
A new system nobody uses has not transformed anything. Training, process changes and feedback loops belong in the delivery plan, with adoption measured like any other outcome.