#GenerativeArt

Out of the Ivory Tower: Architecture, Organization, and the Reality of SAP Transformations

Many SAP transformations today do not fail because of technology. SAP S/4HANA, cloud architectures, and modern integration platforms are mature and powerful. Yet in practice, end-to-end processes often remain slow and inefficient.

The root cause is frequently not the system itself, but the organization that designs, operates, and evolves it.

When SAP Architecture Meets Organizational Silos

In many enterprises, SAP organizations have historically been structured around technical modules such as SD, MM, or FI.
While these modules are technically connected through document flows, they are often organizationally separated.

This leads to familiar challenges:

·       high coordination effort across team boundaries

·       fragmented ownership along end-to-end processes

·       long lead times despite modern platforms

As a result, architecture becomes a reflection of organizational reality.

Conway’s Law: Relevant in Everyday Practice

This pattern can be explained by Conway’s Law:
Systems inevitably mirror the communication and decision structures of the organizations that design them.

For SAP customers, this means that as long as organizations are aligned around technical components, architectures will follow the same structure—regardless of how advanced the underlying technology is. Agile methods alone do not change this as long as structural dependencies remain.

A Realistic Perspective on Organizational Change

Especially in large, established SAP organizations, one thing is clear:
Breaking down organizational silos is difficult and often not fully achievable.

Governance models, reporting lines, and historically grown responsibilities impose real constraints. A radical organizational redesign is therefore rarely feasible in the short term.

Why Awareness Still Makes a Difference

The key benefit already starts with awareness of the relationship between organization and architecture:

·       dependencies become visible earlier

·       architectural decisions are assessed more realistically

·       interfaces are understood as organizational, not just technical, challenges

Even without major reorganization, this awareness enables targeted improvements—for example, clearer end-to-end ownership for critical initiatives or more deliberate team setups where it matters most.

Conclusion

SAP architecture does not emerge in an ivory tower. It is always shaped by the organizational context in which it is created.
Those who understand and consider Conway’s Law make better architectural decisions—even when organizational silos cannot be fully removed.

Architecture is organizational design.

What Does This Mean for Your SAP Transformation?

Taking a conscious look at organizational structures, responsibilities, and communication paths can significantly improve the effectiveness of architectural decisions. Not every organization needs to be redesigned—but every transformation benefits from thinking about architecture and organization together.

Common thread of this blog series:

Introduction 
Tasks of an Enterprise Architect 
Success Factors for Digital Transformation Projects 
Help of an Enterprise-Architecture-Framework 
Steps and Tips 
Artificial Intelligence Meets Enterprise Architecture
Conway’s Law

References

Hohmann, M.; Wagner, D.: Architecture Is Organizational Design, iX – Magazine for Professional Information Technology, Issue 1/2026.