Exclusive: How Clorox Planned Its SAP S/4HANA Transformation

ERP transformations rarely unfold on a clean timeline. Yet media coverage of The Clorox Company’s five-year, $580 million transformation program, which included a migration to SAP S/4HANA, suggested otherwise.

Industry reporters and stock analysts parsed earnings statements, seeking short-term signals on the company’s transformation that could influence markets.

“The framing was often incomplete,” said Chau Banks, chief information and data officer at Clorox. “It missed the fact that large-scale technology and operating transformations are multiyear journeys that don’t fit neatly into a quarterly report.”

The coverage did not reflect how the company approached the transformation. “We did not position this as a risk-free or frictionless change, and we consistently reinforced that short-term volatility would not distract us from the long-term strategy,” Banks said.

In this exclusive interview with SAPinsider, Banks offers a closer look—alongside implementation partner Johan Opperman, managing director at Accenture—at how the company planned, designed, and entered the early stages of its SAP transformation, where communication proved as critical as the technology behind it.

Why Clorox Moved Beyond Its Legacy Systems

When Banks joined the company in 2020, conversations around modernization were already underway, but the full commitment had not yet been made.

“There was a clear sense internally that our legacy systems were reaching their limits and that to support our growth ambitions and future-proof our operations, we needed a more agile and integrated technology backbone,” Banks said.

The objective extended beyond replacing aging infrastructure. Clorox needed that foundation to support growth, improve efficiency, and make better decisions over time.

Early on, leadership defined clear boundaries for the transformation. “Our non-negotiables were clear: we needed to maintain the integrity of our core business processes and protect the trust our customers and partners place in us,” Banks said.

The shift required alignment across functions – finance, supply chain, and manufacturing. Each faced different constraints, but shared a common challenge: how to operate within a more integrated system where data and decisions were increasingly linked.

“Building internal alignment required open communication and collaboration across functions. While there were healthy debates, a shared understanding that modernization was essential to our continued success helped us rally around common goals,” Banks said.

How Clorox Designed Its Transformation for Enterprise Reinvention

Opperman said: “From the beginning of the program, we believed success would depend on treating this as an enterprise reinvention—not a technology ‘go-live.’”

That perspective guided a structured planning phase. Clorox and accenture analyzed end-to-end processes, systems, and performance, using process mining and stakeholder input to establish a baseline. They then benchmarked Clorox against consumer goods peers and cross-industry programs to build a credible business case and realistic plan.

The partners then recalibrated benchmarks to reflect Clorox’s operating reality—its product breadth, manufacturing diversity, and supply chain complexity. That recalibration shaped deployment, including piloting strategy, sequencing, and readiness.

Each deployment, or wave, was anchored not just in timelines, but in operational constraints such as seasonality, product availability, and supply network dependencies.

Opperman said a key differentiator was how each wave was tested before and during deployment. “We used end-to-end scenarios to validate not just system performance, but business performance, and we continuously refined subsequent waves based on lessons learned—raising execution readiness and reducing risk as the program progressed.”

What the First Wave Revealed About Adoption at Scale

Clorox’s first wave focused on global finance and a Canada-based rollout, designed to test how the system and organization would perform under real conditions. The goal was to validate technical readiness and understand how changes would hold across processes and teams. That phase quickly clarified where risk would concentrate.

Adoption depended less on system performance than on how employees adjusted to new ways of working. “While we anticipated technical challenges, it was clear that investing in an expansive training curriculum, along with early and often two-way communication made a meaningful difference in adoption,” Banks said.

As Opperman noted, the challenge was behavioral as much as technical. “Changing behaviors and ‘muscle memory’ built over decades is difficult.” Clorox supported that shift through a change network embedded across the organization. Banks said the network “allowed for change to be driven from ‘within’ and to iterate quickly based on feedback.”

Those lessons carried into the next phase. As scope expanded, the challenge shifted from proving the model to sustaining it—scaling support, maintaining alignment, and ensuring processes held under greater volume and complexity.

Where Execution Reshaped Work Across the Business

As the program moved into execution, sequencing and capacity had to adjust.

Opperman explained stabilization for the first wave overlapped with the build of the second wave, which carried more scope. That overlap created constraints across both business and technical teams, forcing adjustments to timing, sequencing, and decision-making.

In his view, the hardest trade-off was protecting stability while maintaining momentum.

Teams had to be disciplined about what could move forward and what had to wait, focusing on key gating factors such as timely product owner decisions, active business participation in testing, and sustained end-user engagement.

As execution expanded, the impact varied by function. “Finance benefited from increased automation and real-time data, while supply chain and manufacturing saw more integrated workflows and improved visibility across the value chain,” Banks said.

“The greatest impact was on how teams collaborated and accessed information; work became more connected and efficient,” Banks said. “This experience reinforced my belief that technology is fundamentally about empowering people.”

How Clorox Defines Success After Go-Live

Clorox anchored the transformation around an idea from the beginning. “We anchored as much on the motto of new ‘ways of working’ vs simply a new technology,” Banks said.

Go-live then marks a transition rather than an endpoint.

According to Banks and Opperman, the focus is shifting from implementation to stabilization and continuous improvement, where success is measured not just by system performance, but by how effectively the organization operates within it. Metrics like process discipline, data quality, and user adoption rise in importance.

Opperman said this phase reflects a broader shift in how ERP programs are evaluated. Maturity is defined by fewer repeat issues, faster resolution times, and a move from reactive support to structured optimization. The goal is continuous improvement.

While the effort is unlikely to deprive reporters and analysts of headlines, it is likely to make their job more difficult over the coming years, as the transformation continues to unfold.

Banks said that complexity reflects the nature of the work itself. Large-scale transformation does not resolve cleanly at go-live, and its impact is not always visible in the metrics external stakeholders prioritize. Instead, it plays out over time as new processes take hold and the organization adapts to new workflows and solutions.

That experience reinforces a broader lesson for technology leaders.

“Communicate openly with all stakeholders, remain patient and focused on the long-term vision, and ensure that operational changes are closely aligned with strategic goals,” Banks said. “Building trust through transparency and demonstrating incremental wins can help balance the pressures of transformation and investor expectations.”

What This Means for SAPinsiders

• SAP transformation projects create a visibility paradox. Companies must execute deep operational changes that do not map cleanly to quarterly reporting cycles. That gap creates tension between internal and external stakeholders, as long-term transformation progress is often interpreted through short-term financial signals.
• Communication is a core execution capability. Sustained dialogue across functions and stakeholders is required to maintain alignment through uncertainty and disruption. Without it, even well-designed programs risk losing momentum as priorities diverge under pressure, making communication the mechanism that keeps execution aligned to strategy.
• Adoption architecture determines long-term impact. Technical architecture enables transformation, but adoption structures determine whether it persists. Change networks, training systems, and feedback loops act as operational infrastructure that sustains new ways of working and embeds continuous improvement into how the organization operates.