“Lessons from the Front Line of S/4HANA Public Cloud Delivery”
After more than 35 years working in SAP delivery and solution architecture, I’ve seen several major shifts in how enterprise systems are designed, implemented, and operated.
Over the past two years I’ve increasingly been asked to support organisations embarking on SAP S/4HANA Public Cloud programmes, often as an advisor or recovery specialist when programmes begin to encounter structural challenges.
What quickly becomes clear is that S/4HANA Public Cloud is not simply another SAP implementation. It represents a fundamentally different operating model compared with the highly configurable SAP environments many of us have delivered for decades.
The move to a standardised SaaS ERP platform changes how finance is structured, how architecture decisions are made, and how programmes must be delivered.
Having worked across multiple projects in this space, I wanted to share some practical lessons and top tips for delivery success, particularly for programme leaders, architects, and finance teams navigating the realities of S/4HANA Public Cloud for the first time.
If approached with the right mindset and architecture decisions early on, Public Cloud can deliver real value. But if treated like a traditional SAP implementation, programmes can quickly run into avoidable problems.
The following insights are drawn from real-world programme experience and are intended to help organisations avoid some of the most common pitfalls.
1. Establish Tight Governance
Put a clear governance structure in place from day one.
Ensure everyone understands:
Roles and responsibilities
Decision authority
Escalation paths
Quality and Gates, together with what acceptance looks like
An agile and empowered design authority
Public Cloud programmes move quickly - unclear governance causes delays and design drift.
2. Design the Support Model Early (Business and IT)
Don’t leave the operating model until the end of the programme.
Define early:
Business process ownership
IT support structure
Virtual Business COE, leveraging AI to provide the functional businss support
Incident and change management
Release governance for quarterly updates
S/4HANA Public Cloud requires a continuous operations mindset from day one.
I call this “Enterprise Kaizen”
3. Define and Own the Value Case - The Why
Identify the expected business benefits early and ensure they are owned by business stakeholders, not the programme team.
Public Cloud success is measured by process improvement and value realisation, not simply system deployment. That equates to improved productivity and liquidity.
Make sure you visibly track their progress throughout the delivery live cycle, this provides busienss owners with confidence.
Make sure the Why are we doing this change is front and centre, clear with zero ambiguity even if the truth is going to hurt……
4. Understand the As-Is Operating Model
Before design begins, understand how the organisation currently operates.
Identify:
Process fragmentation and local ways of working (and why they are different)
Process pain points
Manual workarounds
Legacy system dependencies
Data quality issues
Local Reporting and legal requirements
These are often the real transformation challenges, not the technology.
5. Clarify Customer Obligations
Make sure the customer clearly understands their programme responsibilities and dependencies.
This includes:
Process ownership
Data preparation and busienss validation
Integration readiness and need to cost for 3rd party APIs
Decision timelines
Change management engagement
Successful programmes require active customer participation.
6. Plan the Customer Resource Model Realistically
Customer teams are often expected to deliver their day jobs while supporting the programme.
Build a realistic resourcing plan linked to the RACI that factors in:
Operational workload
Impact of dead time such as period end and holidays (Europeans love a holiday)
Workshop preparation
Testing cycles
Availability constraints
Underestimating this is one of the most common causes of delivery friction.
7. Embrace Fit-to-Standard Early
S/4HANA Public Cloud is built around standard SAP best practices.
Trying to recreate legacy processes will slow the programme and create unnecessary complexity.
S/4HANA public cloud is highly configurable and can accommodate most process variants, but if you absolutely need to customise the process or analytics then look at point 8.
Successful S/4HANA Public cloud implementations focus on adopting standard processes wherever possible.
8. Control Extensibility - Customisation
Establish clear extensibility governance. I called out the need for a design authority right at the top, no benefit case then no customisation.
Use this hierarchy:
Standard functionality first
Key User extensibility
Side-by-side extensions on BTP when justified
Customisations add to your total cost of ownership.
9. Invest in Data Quality Early
Data migration often exposes:
Inconsistent master data and the authoring process
Duplicate records and dirty data
Poor governance
Lack of data ownership critical for validation
Addressing these issues early avoids major testing and go-live risks.
10. Design for Continuous Innovation
S/4HANA Public Cloud operates on a twice yearly release cycle.
Implementation teams must prepare organisations to operate in a continuous improvement / enterprise kaizen model, not a traditional upgrade cycle.
11. Focus on Process Ownership
Public Cloud programmes work best when organisations adopt end-to-end process ownership.
Success depends less on configuration and more on how well processes are governed after go-live.
12. Treat Change Management as Core Delivery
Public Cloud implementations often require significant changes to working practices.
Strong communication, training, and stakeholder engagement are essential for adoption.
You must during the design phase identify organisational change so that the necessary change plan can be defiend and delivered.
Consider the use of short you tube style training videos, consider using AI to define your new standard operating procedures to both support the business and enable busienss continuity.
Consider how AI co-pilots and WalkMe can enable the organisational change being mitigated and the new operating model being embedded and sustained.
13. The Plan, Finances and Dependency Management
Make sure you have a detailed, fully resourced plan that includes all workstreams including tech, third parties and decommissioning.
Make sure all work packages / projects are fully costed, with backfill, third party costs and agreed contingency.
Make sure the plan is linked to all dependencies.
Make sure you have a clear critical path to go live and all major gates, and make sure your reporting is metric based not word or verbal, “the math don’t lie”
Closing Line
S/4HANA Public Cloud implementations are not traditional SAP programmes, but they are not materially different either, SAP activate is a fantastic methodology but the basic rules of sucessful SAP delivery have not changed for 50 years, the tooling is better and now AI driven but the rules of the ERP universe are still the same.
Success depends on governance, process discipline, and organisational readiness, not blind confidence and group think.
Need help
That's where I come in, message me or buy me a coffee its that simple and lets have a chat
Alisdair
About the Author
Alisdair Bach is a recognised SAP Programme Director and turnaround specialist — often called a “turnaround king” by clients for his ability to stabilise and recover the most complex and failing SAP programmes. With decades of experience across global private equity and public sector portfolios, Alisdair has led high-stakes SAP S/4HANA transformations, finance and supply chain turnarounds, and complex delivery rescues.
Alisdair is also a SAP analyst working to define for investors where next with SAP, he is a author and lecturer, he defined the SAP upcycling concept as the alternate narrative to rip it out and start again clean core that is counter intuitive to AI adoption and SAPs 5X growth strategy.
Through Dragon ERP, he brings board-level assurance, forensic diagnostics, and hands-on leadership to programmes that others have written off — combining empathy with no-nonsense execution to deliver results where failure once seemed inevitable.
