Org TopologiesThe home of modern org design
Visit the Academy

Case study · Public sector

Analyzing The Transformation Of A SAP Group At A Large Public Authority (Deloitte)

2 Elevating Katas in this case ↓
Analyzing The Transformation Of A SAP Group At A Large Public Authority (Deloitte)
Listen · 3 min

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.

Four icons summarizing the starting point: a large SAP area of a public authority, hierarchical, with a transformation ordered

Hover over or tap any text on the drawing to read it.Tap any text on the drawing to read it.

Timeline 2022 to 2024: the C-level organizational transformation runs alongside the SAFe agile transformation of 25 teams

Hover over or tap any text on the drawing to read it.Tap any text on the drawing to read it.

Mind map of the client context at the purchasing department: organization, strategy, customer, change, goal, program environment

Hover over or tap any text on the drawing to read it.Tap any text on the drawing to read it.

Diagram of four structure misfits, from 8 hierarchy layers and many handoffs to a blocked purchase process

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.Org Topologies mapping of SAFe Team Topologies implementationThe three different team topologies in SAFeINCOMPLETECOMPLETEOUTCOMESOUTPUTSNARROWERBROADERSCOPE OF SKILLS MANDATENARROWERBROADERSCOPE OF WORK MANDATETASKS-1TASKS-2TASKS-3TASKS-4CAPS-2CAPS-3CAPS-4PART-1PART-2PART-3PART-4WHOLE-1WHOLE-2WHOLE-3WHOLE-4FUNCTIONALMULTI-SKILLEND-TO-ENDEXPANDINGTASKSCAPABILITIESPARTIAL SOLUTIONWHOLE SOLUTIONDIRECTINGDRIVINGDELIVERINGEnablingteamsStream-aligned teamsComplex subsystem teams &platform teams
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.

Original drawing

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.Org Change MADE Real: Assessing the GapsAssessing the Value Gap and the Capability GapINCOMPLETECOMPLETEOUTCOMESOUTPUTSNARROWERBROADERSCOPE OF SKILLS MANDATENARROWERBROADERSCOPE OF WORK MANDATETASKS-1TASKS-2TASKS-3TASKS-4CAPS-1CAPS-2CAPS-3CAPS-4PART-1PART-2PART-3PART-4WHOLE-1WHOLE-2WHOLE-3WHOLE-4FUNCTIONALMULTI-SKILLEND-TO-ENDEXPANDINGTASKSCAPABILITIESPARTIAL SOLUTIONWHOLE SOLUTIONDIRECTINGDRIVINGDOINGDELIVERINGValue gapCapability gapCapability gapBOsDev & Test
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.

Original drawing

4x4 map: BOs stay in PART-1; Dev & Test moves from CAPS-1 (as-was) to CAPS-2 (as-is) along the Step 1 arrow.Org Topologies Roadmap for the business area3 step approach to reach target state (Step 1)INCOMPLETECOMPLETEOUTCOMESOUTPUTSNARROWERBROADERSCOPE OF SKILLS MANDATENARROWERBROADERSCOPE OF WORK MANDATETASKS-1TASKS-2TASKS-3TASKS-4CAPS-1CAPS-2CAPS-3CAPS-4PART-1PART-2PART-3PART-4WHOLE-1WHOLE-2WHOLE-3WHOLE-4FUNCTIONALMULTI-SKILLEND-TO-ENDEXPANDINGTASKSCAPABILITIESPARTIAL SOLUTIONWHOLE SOLUTIONDIRECTINGDRIVINGDOINGDELIVERINGStep 1BOsDev & Test
4x4 map: BOs stay in PART-1; Dev & Test moves from CAPS-1 (as-was) to CAPS-2 (as-is) along the Step 1 arrow.

Original drawing

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).Org Topologies Roadmap for the business area3 step approach to reach target state (Step 2)INCOMPLETECOMPLETEOUTCOMESOUTPUTSNARROWERBROADERSCOPE OF SKILLS MANDATENARROWERBROADERSCOPE OF WORK MANDATETASKS-1TASKS-2TASKS-3TASKS-4CAPS-1CAPS-2CAPS-4PART-1PART-2PART-3PART-4WHOLE-1WHOLE-2WHOLE-3WHOLE-4FUNCTIONALMULTI-SKILLEND-TO-ENDEXPANDINGTASKSCAPABILITIESPARTIAL SOLUTIONWHOLE SOLUTIONDIRECTINGDRIVINGDOINGDELIVERINGStep 1Step 2Step 2BOsDev & TestPilot teams
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).

Original drawing

Slide on the overall conclusion: from a dysfunctional organizational structure to an agile and adaptive organization

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.Org Topologies mapping of the SAFe structureHow to map the SAFe ecosystem in org topology archetypes ideallyINCOMPLETECOMPLETEOUTCOMESOUTPUTSNARROWERBROADERSCOPE OF SKILLS MANDATENARROWERBROADERSCOPE OF WORK MANDATETASKS-3TASKS-4CAPS-1CAPS-4PART-1PART-2PART-4WHOLE-1WHOLE-2WHOLE-3WHOLE-4FUNCTIONALMULTI-SKILLEND-TO-ENDEXPANDINGTASKSCAPABILITIESPARTIAL SOLUTIONWHOLE SOLUTIONDIRECTINGDRIVINGDELIVERINGPotentialimprovementspaceSAFe-ecosystems with moreautonomous teams that candeliver customer valuewith fast flowSAFe-ecosystems ofinterdependent componentteams working sequentiallyand relying on externallymanaged dependencies
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.

Original drawing

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.Org Change MADE Real: Assessing the GapsAssessing the Value Gap and the Capability GapINCOMPLETECOMPLETEOUTCOMESOUTPUTSNARROWERBROADERSCOPE OF SKILLS MANDATENARROWERBROADERSCOPE OF WORK MANDATETASKS-1TASKS-2TASKS-3TASKS-4CAPS-1CAPS-2CAPS-3CAPS-4PART-1PART-2PART-3PART-4WHOLE-1WHOLE-2WHOLE-3WHOLE-4FUNCTIONALMULTI-SKILLEND-TO-ENDEXPANDINGTASKSCAPABILITIESPARTIAL SOLUTIONWHOLE SOLUTIONDIRECTINGDRIVINGDOINGDELIVERINGValue gapCapability gapCapability gapBOsDev & Test
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.

Original drawing

Future structure of the IT purchasing teams at C2 level: four teams with a Product Owner and a shared P2P backlog in a SAFe ART

Hover over or tap any text on the drawing to read it.Tap any text on the drawing to read it.

4x4 map: BOs stay in PART-1; Dev & Test moves from CAPS-1 (as-was) to CAPS-2 (as-is) along the Step 1 arrow.Org Topologies Roadmap for the business area3 step approach to reach target state (Step 1)INCOMPLETECOMPLETEOUTCOMESOUTPUTSNARROWERBROADERSCOPE OF SKILLS MANDATENARROWERBROADERSCOPE OF WORK MANDATETASKS-1TASKS-2TASKS-3TASKS-4CAPS-1CAPS-2CAPS-3CAPS-4PART-1PART-2PART-3PART-4WHOLE-1WHOLE-2WHOLE-3WHOLE-4FUNCTIONALMULTI-SKILLEND-TO-ENDEXPANDINGTASKSCAPABILITIESPARTIAL SOLUTIONWHOLE SOLUTIONDIRECTINGDRIVINGDOINGDELIVERINGStep 1BOsDev & Test
4x4 map: BOs stay in PART-1; Dev & Test moves from CAPS-1 (as-was) to CAPS-2 (as-is) along the Step 1 arrow.

Original drawing

Roadmap in 6-month steps: stabilize A2 for dev teams, reach B2 with business experts, then reach and maintain C2

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).Org Topologies Roadmap for the business area3 step approach to reach target state (Step 2)INCOMPLETECOMPLETEOUTCOMESOUTPUTSNARROWERBROADERSCOPE OF SKILLS MANDATENARROWERBROADERSCOPE OF WORK MANDATETASKS-1TASKS-2TASKS-3TASKS-4CAPS-1CAPS-2CAPS-4PART-1PART-2PART-3PART-4WHOLE-1WHOLE-2WHOLE-3WHOLE-4FUNCTIONALMULTI-SKILLEND-TO-ENDEXPANDINGTASKSCAPABILITIESPARTIAL SOLUTIONWHOLE SOLUTIONDIRECTINGDRIVINGDOINGDELIVERINGStep 1Step 2Step 2BOsDev & TestPilot teams
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).

Original drawing

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.Org Topologies Roadmap for the business area3 step approach to reach target state (Step 3)INCOMPLETECOMPLETEOUTCOMESOUTPUTSNARROWERBROADERSCOPE OF SKILLS MANDATENARROWERBROADERSCOPE OF WORK MANDATETASKS-1TASKS-2TASKS-3TASKS-4CAPS-1CAPS-2CAPS-4PART-1PART-2PART-4WHOLE-1WHOLE-2WHOLE-3WHOLE-4FUNCTIONALMULTI-SKILLEND-TO-ENDEXPANDINGTASKSCAPABILITIESPARTIAL SOLUTIONWHOLE SOLUTIONDIRECTINGDRIVINGDOINGDELIVERINGStep 1Step 2Step 2Step 3BOsDev & TestPilot teamsTarget state
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.

Original drawing

Overall conclusion slide: challenges of a dysfunctional structure versus realized improvements in speed and motivation

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.

More framework mappings: SAFe →

Elevating Katas in this case

The routines from the Katalog that this case study describes, identified from its text.

Applied 2

  • 2.2Forming a Team-of-Teams

    Teams were grouped into three release trains, a team-of-teams structure.

    “resulting in 25 agile teams organized into three Agile Release Trains (ARTs)”
  • 3.2Sharing the Same Cadence Across Teams

    All teams plan and review in the same Program Increment rhythm.

    “Teams began working in shared Program Increments (PIs)”
See the full Katalog →

More case studies

ACADEMY

Learn the Org Topologies approach

All dates →

Practitioner (C-OTP) and Consultant (C-OTC) classes, live online and in person.

Visit the Academy →

Community

TALK TO THE AUTHORS LIVE

Learn with community

Practitioners share maps, and the authors join the conversation live in Slack.

Join Slack

ASK OUR AI

“How do I map my org?”

Learn with Aiden

Upcoming classes and events, announcements and new material for your org design practice. Now and then, never spam.

Unsubscribe anytime. Privacy →

Or follow Org Topologies on LinkedIn.