Ztalent | The Clean Core Battle: Why True Resistance to the Standard Stems from the Comfort Zone
The Clean Core Battle: Why True Resistance to the Standard Stems from the Comfort Zone

The Clean Core Battle: Why True Resistance to the Standard Stems from the Comfort Zone

24 September 2026

Embracing the standard in S/4HANA is not a software challenge, but a mindset shift. We analyze the human reasons behind the addiction to custom code, the shared inertia between clients and consultants, and how specialist criterion is key to breaking the habit.

The biggest obstacle in S/4HANA migrations lies not in the technology, but in work inertia. After decades of using earlier SAP versions, the ecosystem became accustomed to solving every operational nuance by creating custom transactions and tables (custom Z code). The result is an accumulation of customizations that currently holds back innovation and hinders system evolution.

Although the current market directive is to maintain a clean core (Clean Core), the temptation to replicate the past remains present. Achieving a true transformation requires understanding that resistance to abandoning customizations is not merely a client posture; frequently, it also stems from a dynamic deeply rooted in the traditional way projects are approached.

The two sides of resistance: client and consultant

Understanding the root of these barriers is the only way to transform design methodology on a day-to-day basis.

  • Client resistance (fear of change and perceived security): End users often cling to familiar screens and developments because they provide a sense of control. Embracing standard processes means questioning how their department has worked for years and facing the learning curve of a new environment.
  • Consultant resistance (the technical comfort zone): Designing custom Z code has historically been the path of least resistance. Researching how S/4HANA resolves a process natively requires time, study, and stepping outside routine practices. Specifying a familiar custom development may seem quicker than educating the client on standard adoption.
  • The inertia of large volume-based projects: As addressed when analyzing the massive outsourcing model, dynamics geared toward hour accumulation favored custom solutions over in-depth process analysis. Breaking that inertia requires shifting toward a model based on criterion and quality.

Breaking the habit in decision-making

Overcoming the addiction to customization requires elevating the conversation during the analysis and design phases.

  • Questioning necessity before designing: The first question facing a requirement should not be "how do we program this," but "why does the current standard not satisfy this business need."
  • The consultant as a change enabler: The value of a Senior professional does not lie in validating every user request, but in guiding them. Explaining the long-term impact of a customization and demonstrating native alternatives is the hallmark of signature consulting.
  • Embracing the standard as a development opportunity: Mastering standard processes and S/4HANA analytics capabilities is the best investment for consultants, positioning them as strategic business advisors and moving them away from purely mechanical tasks.

From design by habit to value-driven consulting

Success in Clean Core adoption does not depend on enforcing strict rules, but on evolving project culture.

When both clients and consultants move beyond the comfort of "doing things as they have always been done," organizations not only achieve a cleaner, more agile system, but also revalue the role of architecture and specialization across the entire community.

Debate system architecture, standard adoption, and Clean Core strategies with the Ztalent specialist community.

Comments