The Challenge
The client had implemented SAP more than a decade earlier. Since then, the utility’s operating model, technology landscape and expectations of customers and employees had changed significantly.
The SAP estate had become heavily customized. Some customizations supported genuinely distinctive utility requirements, but others replicated commodity processes that could have been handled through standard SAP functionality. Over time, this increased complexity, slowed delivery and made it harder for the organization to respond to changes in regulation, customer demand and the energy market.
The organization was also carrying the cost of aging infrastructure, limited internal SAP expertise and dependence on external systems integrators. Its people needed a simpler, more accessible user experience for day-to-day utility operations.
Its customers expected more digital, personalized and self-service interactions, including easier access to account, usage, billing and outage information. Its business leaders needed better insight, faster processes and a platform that could support automation, asset performance and future innovation.
The technology case for moving to SAP S/4HANA was clear. The business case needed to be clearer.
The client needed to answer some difficult questions:
- What should the future SAP landscape help the business achieve?
- Which current pain points were symptoms of deeper process or technology issues?
- Where should the organization adopt SAP standard processes, and where did it need to protect signature requirements?
- What migration approach, timeline and investment range were realistic?
- How could the organization build leadership alignment before engaging an implementation partner?
A technology-led roadmap would not be enough. The programme needed to start with the business.
Resulting Solution
Resulting designed and delivered a business-first Phase Zero. The work connected executive priorities, operational pain points, utility processes and technology decisions into one clear roadmap for the SAP S/4HANA programme.
Phase Zero was structured around three outcomes:
- Define the scope and approach: Establish the current landscape, process scope, migration options, indicative timeline and rough-order-of-magnitude costs.
- Build the future-state direction: Translate business priorities into future process and solution principles across customer service, work and asset management, finance, supply chain and people processes, while identifying opportunities to simplify, standardize and automate.
- Prepare the organization to move: Create the evidence and alignment needed for internal approval, regulatory planning and a focused implementation partner selection process.
Start with executive priorities
Resulting began with 12 executive interviews. Rather than starting with SAP functionality, the conversations focused on what leaders needed the future ERP landscape to deliver for customers, field teams and the wider utility operation.
The themes were consistent:
- Easy: Easier for people to use, easier to maintain and better for customers.
- Standard: More aligned to SAP standard practices, with customization reserved for requirements that genuinely make the business distinctive.
- Automated: Less manual work, fewer repetitive tasks and more time for value-adding activity.
These priorities gave the programme a language the business could understand. They also created a clear test for future design decisions.
Understand the current state in detail
The team ran more than 30 workshops across five functional workstreams. These sessions brought business and technical teams together to examine current utility processes, applications, pain points, dependencies and opportunities across areas such as customer operations, work and asset management, supply chain, finance and people.
Approximately 400 pain points were captured and categorized through a common process framework. Around 200 opportunities were identified for consideration in the future state.
This work did more than create a list of problems. It showed where complexity was self-imposed, where processes could be standardized and where investment would create a material business benefit.
Define the route to SAP S/4HANA
The Phase Zero work established the migration approach and created current and future solution maps. It also developed a rough-order-of-magnitude view of programme cost and duration.
The roadmap balanced the need to establish a supported, secure and scalable SAP foundation with the need to improve how the utility operates.
It recognized that SAP S/4HANA would be the foundation for a wider digital transformation, supporting more resilient infrastructure, better customer service, cleaner energy ambitions and more efficient field and back-office operations, not a standalone technology replacement.
The team also identified the work that could begin before implementation. This included mobilizing governance, identifying programme leaders, building internal capability, agreeing guiding principles and preparing the organization for collaboration with its future implementation partner.
Create business ownership
More than 100 people from across the business were actively engaged throughout Phase Zero. That participation helped move the programme beyond an IT initiative and created a shared understanding of why change was needed.
Resulting also helped the client prepare for the market. With the scope, priorities, future direction and indicative investment understood, the organization was better positioned to evaluate implementation partners against its actual needs rather than a generic SAP brief.
Benefits Delivered
A business case the organization could support: Executive interviews connected SAP S/4HANA to utility outcomes, customer experience, operational efficiency, workforce needs, grid resilience and regulatory planning. This created a stronger basis for internal project approval and the regulatory business case.
Clear scope and direction: The client defined its migration approach, current and future solution maps, indicative cost range and expected programme duration before going to market.
Leadership alignment: Twelve executive interviews established a common view of what the future SAP landscape needed to deliver. The words easy, standard and automated gave the programme a simple and memorable design test.
A fact-based view of the current state: More than 30 workshops across five functional workstreams captured approximately 400 pain points and created a structured view of the issues holding the utility back, from customer and billing processes to asset, supply chain and finance operations.
A practical pipeline of improvement: Around 200 opportunities were identified across processes, technology and ways of working. This gave the organization a clearer view of where to focus investment and where to avoid unnecessary customization.
Stronger business engagement: More than 100 people took part in Phase Zero. The result was broader ownership and a better-prepared internal team for the next stage of the programme.
A more focused implementation partner selection: The client entered its implementation partner process with a clearer understanding of scope, priorities, constraints and expected outcomes. That reduced the risk of selecting a partner against an incomplete or technology-led brief.
Momentum before implementation: Governance, leadership, internal capability and early preparation activities were identified before the implementation programme formally began. The client could move forward with fewer avoidable delays.
Conclusion
A successful SAP S/4HANA programme does not begin with a software decision. It begins with a clear understanding of what the business needs to become and the evidence to show how SAP can help it get there.
For this US energy utility, Phase Zero created that foundation. It brought executives, business teams and technical specialists into the same conversation. It turned a complex legacy utility environment into a structured view of pain points, opportunities, scope, cost and timing.
The result was more than a roadmap. It was a programme the business could understand, support and prepare to deliver.
That is the value of doing Phase Zero properly. You create clarity before commitment, alignment before delivery and a stronger basis for value throughout the transformation.
If your SAP S/4HANA programme needs a clearer business case, stronger leadership alignment or a more reliable route to implementation, talk to us.
