What separating without disruption taught us about outcomes and AI readiness

Everyone wants to talk about AI. I do too.

But before AI accelerates anything, there’s a harder question leaders need to ask: can your organization actually move?

I talk a lot about velocity. Not speed for speed’s sake, but the ability to move decisively without breaking things.

In today’s environment, velocity is the real currency of success. Nothing tests it more than a large-scale separation.

Over the past year, WD executed one of the most complex transformations in our company’s history, a full separation from Sandisk, and within that, a complete ERP separation that underpinned how the business runs day to day.

Most separations take a minimum of 12 to 18 months, come with transition service agreement (TSA) extensions, and quietly drain momentum from the business. That’s the accepted norm. We chose not to accept it.

WD completed its system separation from Sandisk in eight months, under budget, with zero business disruption.

That result didn’t come from focusing on speed. It came from redesigning how the business works. By evolving mindsets, data sets, tools, and skills together, we created the velocity that delivered the outcome—and the foundation for what comes next, including AI.

Leading with outcomes, not urgency

Separations expose how an organization actually operates.

Unclear ownership, slow decisions, fragile systems, and unnecessary complexity surface quickly. When those issues aren’t addressed early, timelines stretch, costs rise, and TSAs linger. The disruption may not make headlines, but the drag on the business is real.

So, we took a different approach. The focus wasn’t speed, it was outcomes.

Instead of reacting as issues emerged, we set direction early and led the system separation from the front. Progress never came at the expense of stability.

Velocity came from clarity, not urgency, and that’s what allowed us to move faster than industry benchmarks while keeping the business steady.

That also meant being willing to redesign work itself, not just deliver against timelines.

What we did differently

We made the right decisions early and stayed focused on the few priorities that mattered most.

That meant building a new muscle. We shifted from being a “yes” team to saying “no” often—to scope creep, distractions, and anything that didn’t drive the outcome.

Saying no reduced friction. And friction, not technology, is what slows organizations down.

That focus showed up in practical ways:

• We moved 12 critical business processes to Oracle Cloud in a single coordinated cutover instead of spreading risk across multiple quarters.
• We exited TSAs by reducing external users from more than 7,000 to zero in eight months, giving WD full ownership of its systems and data.
• We replaced layered approvals with daily war-room decisions so leaders closest to the work could act without waiting.

Those actions modernized our systems. More importantly, they forced us to redesign how the business operates.

• We reshaped roles and workflows across every major value stream—Lead-to-Cash, Plan-to-Fulfill, Source-to-Pay, and Engineering—aligning ownership to outcomes.
• With every attrition, we asked hard questions: Should this work be automated, augmented, or fundamentally redesigned?
• We used AI intentionally to capture and codify expertise, especially in deep, esoteric domains where knowledge is scarce and unevenly distributed, reducing reliance on institutional memory and individual heroics.

The result was uncommon in the industry: Completed ahead of typical industry timelines, with no disruption to employees, customers, or manufacturing, and under budget.

One system, not silos

This worked because the company operated as one system.

IT, Finance, Operations, Manufacturing, and HR moved together with shared goals, shared accountability, and trust in one another’s decisions. That alignment is what allowed the business to keep running while foundational systems were changing underneath it.

Employees didn’t feel disruption. Customers didn’t experience disruption. Manufacturing didn’t slow down. Not because the work was simple, but because the outcomes were designed to hold under pressure.

Why being under budget matters

Finishing under budget wasn’t incidental. It was a result of discipline.

By eliminating duplication, simplifying systems, and making decisions that held, we avoided the cycle of overruns and recovery that often follows large separations. That mattered because it gave us options.

Instead of spending the next year unwinding complexity, we could reinvest with intention. That’s where velocity compounds.

Why this matters for AI

This is where the conversation around AI becomes real.

AI doesn’t scale well on fragmented systems. Disconnected data, weak security, and slow decisions create friction and risk. AI exposes that fast.

Because of the successful completion of our system separation, WD now fully owns our systems, data, and automation roadmap. That gives us control and speed without increasing risk.

But we’re not done. AI readiness is a journey, not a milestone.

Next comes focus. We will prioritize critical value streams, redesign work, reshape roles, and apply AI where it drives measurable outcomes.

That means asking critical questions:

• What should be automated?
• What should be augmented?
• What must stay human?
• What capabilities do we need to build next?

Redesigning how we operate is what creates velocity. Done right, AI multiplies that velocity. Done poorly, it multiplies complexity.

The bigger lesson

Success isn’t about chasing every new technology or moving fast for the sake of speed. It’s about designing the business to absorb change and convert it into outcomes—without breaking, slowing down, or adding unnecessary complexity for people.

That’s what this work required. It wasn’t easy. It asked a lot of the teams involved and tested how we operate under pressure. But by evolving mindsets, data sets, tools, and skills together, we built the capability to move differently, and the velocity that delivered results.

Now, we’re not just talking about AI, we’re scaling it deliberately across the business. We have clear ownership, strong foundations, and teams that know how to move together.

That’s what velocity looks like when it’s built to last, and why this work matters as we scale what comes next.