After working through the value, the risks, and the complexity of moving to SAP S/4HANA, many organisations arrive at a similar point.
They are ready to move forward, but unsure how.
At this stage, the challenge is no longer whether transformation is needed. It is deciding what the right path looks like.
When Every Answer Sounds Right
In today’s market, organisations are presented with multiple approaches to SAP S/4HANA.
Each comes with its own rationale:
- Start fresh to simplify and standardise
- Convert existing systems to minimise disruption
- Take a more balanced path between the two
On paper, each of these options can make sense.
However, when viewed in isolation, they can also be misleading.
What works well for one organisation may not be suitable for another, particularly when business priorities, system complexity, and operational constraints differ significantly.
Why Decision-Making Becomes Difficult
The difficulty is not the lack of options. It is the abundance of them.
Different stakeholders often have different perspectives:
- IT may prioritise technical simplicity or speed
- Business leaders may focus on continuity and outcomes
- External partners may recommend approaches aligned with their strengths
As a result, organisations can find themselves comparing approaches without a clear way to evaluate which one truly fits their situation.
The conversation becomes centred on choosing between options, rather than defining what success should look like.
The Risk of Starting with the Approach
One common pattern is to begin the transformation journey by selecting an approach early.
While this may create initial momentum, it can also introduce challenges later:
- Important business requirements may not be fully considered
- Certain constraints may only become visible during execution
- Adjustments may be required mid-way, increasing complexity and risk
In these cases, the approach drives the transformation rather than the business needs guiding it.
A Different Way to Decide
A more effective starting point is not to ask, “Which approach should we choose?” but:
“What does the business need to achieve and what constraints do we need to work within?”
From there, decision-making becomes more structured.
This typically involves:
- Understanding the current system landscape in detail
- Identifying key business priorities and constraints
- Evaluating which parts of the organisation require change, and which require continuity
- Mapping transformation scenarios that reflect these realities
Only then does the choice of approach become clearer and more aligned with the organisation’s needs.
Clarity Before Commitment
Organisations that navigate this phase successfully tend to prioritise clarity before committing to a specific path.
Clarity in:
- The current landscape and its complexity
- The business outcomes that matter most
- The trade-offs between speed, risk, and transformation depth
With this level of understanding, decisions are less about choosing between predefined models and more about defining a path that fits the organisation.
Precision in Execution
Once a clear direction is established, the focus shifts to executing with precision.
This includes:
- Planning transformation steps in a structured and controlled manner
- Governing changes across systems, processes, and regions
- Ensuring alignment between business and IT throughout the journey
At this stage, execution is not just about delivering a system; it is about delivering outcomes that were defined at the start.
What This Looks Like in Practice
Consider a common scenario.
An organisation operating across multiple countries has built its SAP landscape over many years. Core processes are largely stable, but there are layers of custom developments and regional variations that support specific business needs.
As they evaluate SAP S/4HANA, they face conflicting recommendations.
- One option is to start fresh, simplifying processes but requiring significant change across the business.
- Another is to convert everything as it is, minimising disruption but carrying forward existing complexity.
Neither option fully addresses their situation.
What they often need instead is a more balanced approach:
- Retain core processes that are tightly integrated into day-to-day operations, such as order-to-cash, production planning, or financial closing, where stability is critical
- Simplify or standardise areas that have grown inconsistent across regions, such as master data structures, reporting logic, or duplicated workflows
- Selectively adjust or redesign specific processes, such as procurement approvals or inventory handling, where inefficiencies are clear, without requiring a full redesign of the entire system
This allows organisations to focus on change where it creates measurable value, rather than applying it across the entire landscape unnecessarily.
More importantly, it shifts the conversation from choosing between predefined approaches to defining a path that fits the organisation.
Aligning the Right Capabilities
At this stage, transformation is no longer just about selecting an approach. It is about aligning the right capabilities to deliver the desired outcome.
This often involves coordination across:
- Business strategy and transformation priorities
- Data and information management
- Infrastructure and platform considerations
Ensuring these elements are aligned helps reduce fragmentation and supports a more cohesive transformation journey.
Moving from Choice to Confidence
The presence of multiple approaches is not the problem.
The challenge is making a decision with confidence, knowing that the chosen path reflects the organisation’s needs, constraints, and long-term objectives.
In reality, most organisations do not fit neatly into predefined models. The right approach is often a combination, designed around the business, not the framework.
When decisions are grounded in clarity and executed with precision, transformation becomes less about choosing the “best” approach and more about delivering the right outcome.
Setting Up What Comes Next
Once the path is defined, the next question becomes more important:
What does success actually look like after SAP S/4HANA?
Beyond the transition itself, how do organisations ensure they are positioned for long-term value, particularly in areas such as data, automation, and AI?
In the final article, we will explore what it means to move beyond implementation and how SAP S/4HANA serves as the foundation for future-ready, AI-enabled enterprises.
