Digital transformation in retail is often framed as a technology upgrade, but in reality it is an operating model redesign problem. Retailers are expected to operate at high speed while managing massive complexity across finance, supply chain, merchandising, workforce planning, and customer operations.

Automation is frequently positioned as the solution to rising operational complexity, cost pressure, and workforce constraints, yet many organizations quickly discover that scaling automation across an enterprise is significantly harder than deploying it in isolated pilots.

What initially works well in controlled environments often breaks down when exposed to the realities of large organizations, where processes vary across business units, legacy systems remain deeply embedded, and ownership of workflows is fragmented across multiple teams.

As a result, automation efforts that begin with strong momentum in small use cases frequently struggle to maintain consistency, governance, and long-term adoption when expanded beyond their initial scope.

The Challenge

The key challenge faced by the big-box retailer was not a lack of digital ambition or investment, but the persistence of deeply embedded manual processes within its finance operations.

Despite broader efforts to modernize the enterprise, many critical finance activities still relied on fragmented systems, spreadsheet-driven workflows, and labor-intensive reconciliation processes. This created a structural bottleneck where work was technically supported by digital tools, but still executed in a highly manual and inconsistent way across teams and business units.

As a result, the organization struggled with inefficiencies that limited both speed and scalability. Reporting cycles were slowed by repetitive data preparation, operational visibility was constrained by disconnected systems, and finance teams were spending significant time on transactional work rather than strategic analysis. These challenges became increasingly problematic as the business grew in complexity, making it difficult for the retailer to respond quickly to changing conditions or fully leverage its digital transformation investments.

Building Around Existing Processes

The case of how PwC helped the large big-box retailer scale automation is useful because it shows what happens when automation is treated not as a tool rollout, but as a structured transformation strategy.

What makes this case especially instructive is the underlying strategy. Instead of focusing on isolated efficiency wins, the approach centered on redesigning how work is structured, how decisions flow, and how employees participate in improvement.

PwC did not simply introduce automation technologies into existing workflows. It applied a layered transformation model built around process simplification, citizen enablement, and governance-led scaling. Each of these layers plays a distinct role in ensuring automation moves from experimentation to enterprise capability.

The Real Constraint: Process Debt, Not Technology

Most enterprise inefficiency is not caused by a lack of software capability. It is caused by what can be described as process debt. Over time, organizations accumulate layers of approvals, workarounds, spreadsheets, and localized practices that were once introduced to solve specific problems but were never fully retired or standardized.

In a large retail finance organization, this often looks like duplicated reconciliation steps across systems, manual adjustments made at the end of reporting cycles, inconsistent approval chains across business units, and heavy reliance on email-based coordination.

These processes persist not because they are optimal, but because they are embedded in daily operations. Automation alone cannot solve this. If a flawed process is automated without redesign, the organization simply executes the same inefficiencies faster and at larger scale.

This is why PwC’s first strategic move was not automation deployment but process rationalization. The goal was to reduce unnecessary variation in workflows and eliminate redundant steps before introducing automation. This approach reflects a key principle in enterprise transformation: efficiency is designed, not automated.

The Solution

The solution centered on empowering the retailer’s finance organization to move beyond passive participation in technology change and instead become active designers of automation.

Rather than positioning automation as an externally delivered system, PwC introduced a citizen-led model that enabled the controllership team to identify, design, and build automation workflows themselves.

The initiative began with a focused pilot aimed at creating 20 automation workflows within the financial controllership function, establishing a controlled environment to validate the approach before scaling it across the enterprise.

To accelerate adoption and build capability quickly, PwC applied its BXT methodology, which integrates Business strategy (B), Experience design (X), and immersive Technology (T). This approach ensured that automation was not treated as a purely technical exercise, but as a rethinking of how work should be experienced and executed.

Business leaders defined priorities and pain points, experience design shaped how workflows should feel and function for end users, and technology enabled rapid prototyping and deployment. This combination helped translate abstract automation goals into practical, user-centered workflows that employees could engage with directly.

A key part of the solution involved structured sprint-based delivery. Functional leaders and finance teams identified their most time-consuming manual processes, including areas such as lease accounting and ERP-based payment reconciliations. These processes were then mapped in detail, allowing teams to rebuild them as automated workflows.

PwC played a critical role in guiding this mapping and redesign effort, ensuring that processes were not simply digitized but meaningfully improved. Within just six weeks, the teams successfully built and deployed 20 automated processes, followed by rigorous testing and refinement that led to strong adoption across the controllership function.

Beyond the technical build, the solution placed strong emphasis on capability building, cultural adoption, and sustained engagement. Employees worked closely with PwC teams to co-design and refine workflows, which increased ownership and reduced resistance to change.

Strategy Layer One: Process Simplification Before Automation

Process simplification is often the least visible but most impactful part of automation programs. It involves mapping how work actually happens across teams, identifying unnecessary complexity, and redesigning workflows so they reflect current business needs rather than historical decisions. In practice, this means challenging assumptions that tend to go unquestioned in large organizations.

For example, a multi-step approval chain may exist simply because it was introduced during a past compliance concern, even if modern systems now provide better controls. Similarly, different business units may perform the same financial reconciliation in slightly different ways, even though there is no longer a functional reason for variation.

PwC’s approach focused on standardizing these workflows so that automation could operate on clean, consistent processes. This step is essential because automation systems are sensitive to variation. The more fragmented a process is, the harder it becomes to scale automation across it. Once processes are simplified, automation becomes more reliable, easier to maintain, and significantly more scalable.

Strategy Layer Two: Citizen-Led Automation as a Scaling Mechanism

Once processes were simplified, the next strategic layer involved enabling broader participation in automation development. This is often described as citizen-led automation, where business users outside of traditional IT or engineering teams are empowered to create and manage certain types of automated workflows.

This approach is not about decentralizing control entirely. It is about distributing capability while maintaining governance. In many large enterprises, one of the biggest barriers to scaling automation is that innovation becomes concentrated within a small number of technical teams that cannot realistically support every operational request across the organization.

The rationale behind this strategy is grounded in proximity to work. The individuals who experience process inefficiencies daily are often best positioned to identify where automation will have the greatest impact. A finance manager who spends hours preparing recurring reports has direct visibility into which steps are repetitive, which inputs are redundant, and where delays occur.

Traditional centralized automation models often struggle to scale because they rely on a limited number of technical teams to identify, prioritize, and build solutions for the entire enterprise. This creates bottlenecks and slows down adoption.

By contrast, citizen-led automation expands the pool of contributors. It allows operational teams to participate directly in identifying automation opportunities and, in some cases, building solutions themselves using governed platforms. However, this model requires careful design. Without structure, it can lead to fragmentation, duplication, and compliance risk.

The key strategic balance here is empowerment within constraints. Too much control slows innovation. Too little control creates operational chaos. Effective automation scaling requires both speed and structure.

Strategy Layer Three: Governance as an Enabler, Not a Restriction

Governance is often misunderstood in automation programs. It is frequently viewed as a compliance requirement or a set of controls that slow down innovation. In mature transformation programs, however, governance functions as an enabler of scale.

Without governance, automation initiatives remain isolated. Different teams build solutions in different ways, using different assumptions and standards. Over time, this creates an ecosystem that is difficult to maintain and impossible to expand consistently.

PwC’s approach embedded governance into the design of the automation ecosystem from the beginning. This likely included defining how automation workflows are documented, how they are reviewed, how risk is assessed, and how ownership is assigned.

Governance also plays a critical role in sustainability. Automation is not a one-time build activity. It requires ongoing maintenance as systems change, processes evolve, and business requirements shift. A governed automation model ensures that changes do not break existing workflows and that improvements can be propagated across the organization without rework.

Strategy Layer Four: Workforce Enablement and Behavioral Change

Even the most well-designed automation systems fail if employees do not adopt them. This is why workforce enablement is a core part of successful transformation strategies. In this case, PwC’s approach extended beyond technical implementation into behavioral change. Employees needed to understand not only how automation tools worked, but also how their roles would evolve as repetitive tasks were removed.

This is an often-overlooked dimension of automation programs. Technology changes are relatively straightforward compared to behavioral changes. Employees must shift from executing tasks manually to overseeing, validating, and improving automated processes.

This transition requires training, communication, and trust-building. Without it, employees may continue using legacy processes out of familiarity, even when better systems are available.

Effective enablement also involves reframing automation not as a replacement for human work, but as a reallocation of effort toward higher-value activities. In finance functions, this often means moving away from transactional work and toward analysis, forecasting, and decision support. When employees understand this shift, adoption improves significantly.

The Results

The results of the transformation demonstrate a clear shift from incremental efficiency gains to scalable enterprise impact. Through PwC’s support, the big-box retailer achieved more than 20,000 hours of manual effort saved annually, translating into approximately $8 million in projected savings over three years.

This outcome reflects not just cost reduction, but the removal of large volumes of repetitive work from finance operations, allowing the organization to reallocate capacity toward higher-value activities.

In addition to time and cost savings, the organization automated 39 core finance use cases, establishing a structured foundation for scalable automation within the finance function. Importantly, the transformation did not stop at these initial deployments.

More than 250 additional automation opportunities were identified for future rollout, signaling a pipeline-based approach to continuous improvement rather than a one-time efficiency program. This indicates that automation was embedded as an ongoing capability rather than a finite project.

A particularly notable outcome is that 90% of the implemented automations are now used to enable faster and more informed decision-making. This shifts the narrative of automation beyond task reduction and toward decision enhancement.

Instead of simply reducing manual workload, the automation layer is increasingly supporting real-time insights, improved operational visibility, and more responsive financial planning processes.

PwC also played a central role in enabling this outcome by launching a citizen-led automation program designed to reduce costs, empower teams, and accelerate innovation across the organization.

By allowing employees closer to the work to actively participate in identifying and building automation solutions, the program helped embed automation into day-to-day operations. This approach ensured that automation scaled not only through technology deployment, but through sustained organizational engagement and ownership.

Why Scaling Automation Is Harder Than Starting It

Many organizations successfully launch automation pilots but struggle to scale them across the enterprise. The reason is that scaling introduces complexity that pilot programs do not face.

Pilots typically operate in controlled environments with motivated teams and well-defined scopes. At scale, however, automation must function across multiple systems, business units, and operational contexts.

This introduces challenges related to consistency across processes, integration across systems, ownership across teams, maintenance across changes, and compliance across jurisdictions.

PwC’s strategy addressed these scaling challenges by treating automation as an enterprise capability rather than a series of discrete projects. This means building foundational structures that support continuous expansion rather than one-time deployment.

What This Means for Other Organizations

The most important lesson from this case is that automation is not primarily a technology problem. It is a systems design problem. Organizations that focus only on tools tend to achieve short-term gains but struggle with scalability.

Organizations that focus on process redesign, workforce enablement, and governance are more likely to achieve sustained transformation. Each layer is necessary. None is sufficient on its own.

Conclusion

At its core, this transformation illustrates a broader shift in how enterprises are thinking about automation. It is no longer about replacing manual tasks with digital equivalents. It is about redesigning how organizations function so that work flows more efficiently, decisions happen faster, and employees spend more time on meaningful contributions.

The success of PwC’s work with the retailer highlights an important reality. Automation at scale is not achieved through isolated technical deployments. It is achieved through structured transformation that aligns people, processes, and platforms into a coherent operating model.

Organizations that understand this distinction are far more likely to turn automation into a durable source of competitive advantage rather than a series of disconnected efficiency gains.

If your organization is struggling with fragmented processes, manual workarounds, or automation efforts that aren’t scaling beyond pilots, now is the time to take a more structured approach. Book a consultation to explore how a strategic, governance-led automation framework can help you simplify operations, accelerate execution, and unlock sustainable enterprise-wide efficiency.