This case study by Karl Thomas and Nico Liedl from Deloitte explores a large-scale transformation initiative within a public authority’s SAP department.
The department, initially structured in a traditional and hierarchical manner with over 500 employees working in waterfall mode and six annual releases, embarked on a dual transformation journey.
On one side was a C-level driven organizational transformation, and on the other, a SAFe-based agile transformation with multiple Agile Release Trains with a Team Topologies design inside.
Hover over or tap any text on the drawing to read it.Tap any text on the drawing to read it.
Hover over or tap any text on the drawing to read it.Tap any text on the drawing to read it.
Hover over or tap any text on the drawing to read it.Tap any text on the drawing to read it.
Hover over or tap any text on the drawing to read it.Tap any text on the drawing to read it.
4x4 map: Enabling teams fill PART-1 and CAPS-1, Stream-aligned teams fill CAPS-2 and CAPS-3, and Complex subsystem and platform teams fill TASKS-1 and TASKS-2.
4x4 map: the as-was Dev & Test unit sits in CAPS-1, the as-is BOs in PART-1 and an as-is unit in CAPS-2; vertical value-gap arrows reach up from the BOs and the CAPS-2 unit, and horizontal capability-gap arrows reach right from them.
4x4 map: BOs in PART-1 move along the Step 2 arrow into the pilot teams in PART-2, while the Dev & Test unit moves from CAPS-1 to CAPS-2 (Step 1) and up into the pilot teams (Step 2).
Hover over or tap any text on the drawing to read it.Tap any text on the drawing to read it.
4x4 map: a Potential improvement space cloud covers WHOLE-2, WHOLE-3, PART-2 and PART-3, SAFe ecosystems with more autonomous teams fill CAPS-2 and CAPS-3, and SAFe ecosystems of interdependent component teams fill TASKS-1 and TASKS-2.
4x4 map: the as-was Dev & Test unit sits in CAPS-1, the as-is BOs in PART-1 and an as-is unit in CAPS-2; vertical value-gap arrows reach up from the BOs and the CAPS-2 unit, and horizontal capability-gap arrows reach right from them.
Hover over or tap any text on the drawing to read it.Tap any text on the drawing to read it.
4x4 map: BOs in PART-1 move along the Step 2 arrow into the pilot teams in PART-2, while the Dev & Test unit moves from CAPS-1 to CAPS-2 (Step 1) and up into the pilot teams (Step 2).
4x4 map: the pilot teams in PART-2 move up along the Step 3 arrow into the target state in WHOLE-2; the Step 1 and Step 2 moves from CAPS-1 and PART-1 lead into the pilot teams.
Hover over or tap any text on the drawing to read it.Tap any text on the drawing to read it.
Download the Full Case Study in PDF Format Here
Outcomes
The outcomes of the Org Topologies transformation case with Karl and Liedl were a mix of progress and persistent challenges, highlighting both the power and the limitations of typical agile transformations when not systemically aligned.
On the positive side, the SAFe implementation was completed across four waves, resulting in 25 agile teams organized into three Agile Release Trains (ARTs). These teams achieved a CAPS-2 level (formerly A2) in the Org Topologies map. This shift led to tangible benefits such as increased delivery speed, greater team flexibility, and the successful implementation of an agile pilot across an entire business area. Teams began working in shared Program Increments (PIs) and adopted modern methods like Scrum and Kanban.
However, deeper organizational alignment was not achieved. Major systemic misfits persisted, such as a misalignment between the organization’s structure and its actual work processes, siloed budget control, a lack of clear ownership, and a significant product gap. While teams had improved locally, the overall ecosystem remained fragmented. The dual transformation approach—one top-down (C-level led) and one bottom-up (SAFe implementation)—was not integrated, leading to confusion and disconnected efforts.
In summary, the outcome was that the teams improved operationally (speed and flexibility), but the organization did not yet achieve higher-level adaptability or business agility. The transformation stalled at the CAPS-2 level, and to unlock further gains, a shift toward PART or WHOLE-level archetypes is necessary. This will require a more integrated, systemic change effort guided by Org Topologies’ full MADE method.