Four-year capability cadence
Operating context
Government & Public Sector / Digital Transformation / Live and ongoing / 2023-2026
Operating problem
SPL Group committed to becoming the national operator in its sector. The role required, among other things, an operating layer it did not yet have: digital transformation capabilities at international standard, a unified institutional structure, faster development of new electronic products, and growth in advanced logistics services. The gap between aspiration and current state was substantial.
Intervention
We designed a four-year roadmap structured into four phases, each carrying twelve capability domains forward together: digital intelligence, digital IT, interoperability, security, core business, organization governance, back office, service and relationships, channels, experience orchestration, workspace, and marketing. 2023: Migration. 2024: Setting Up Growth. 2025: Scaling Growth. 2026: Accelerated Growth. The twelve domains progressed under a single program governance.
Measured change
From a standing start on the new digital estate in 2023 to operating across all twelve domains by the start of 2025. The quarterly cadence held, the single hardest thing in a multi-year transformation.
Transfer / operate model
The roadmap built a program rhythm that could hold over multiple years, with capability progress compounding across phases.
Accountability line
Program governance carrying twelve capability domains through one delivery cadence.
Capability progress, quarterly commitments, institutional structure, product development, and logistics-service growth.
Program governance over phases, domains, and cadence rather than disconnected projects.
The institution moved from near-zero digital maturity toward operation across all twelve capability domains.
Track record
A program cadence that held
Most multi-year transformations lose their cadence within twelve months. This one didn't, because the operating discipline was designed in from the start.
Capability over project
The program was structured around twelve capabilities, not twelve projects. Capabilities compound. Projects don't.