How Google Scaled Agility Without Sacrificing Reliability: Interview with Supriya Iyer

At Google, supply chain agility is not measured by how quickly teams react. It is measured by how reliably they can prevent disruption before anyone notices it happened.

That distinction sits at the center of how Supriya Iyer, who leads Google’s networking supply chain and operations, thinks about supply chain management. Her team supports the infrastructure behind Google’s global network, ensuring the materials, services, and capabilities powering billions of daily interactions arrive on time, at scale, and without interruption across more than 100 countries.

“In networking, a small issue, one small part, can cascade fast,” she explained. “You can have a site ready, the deployment team scheduled, a narrow access window, and if a single component in a ship set doesn't show up, the entire deployment schedule slips.”

At Google’s scale, those slips do not remain isolated for long.

That is why, as Iyer put it, “supply chain is not just efficiency, it’s reliability. And it’s a strategic function.”

Redefining agility in a constrained world

Agility is often treated as shorthand for speed. In Google’s networking supply chain, the definition is narrower and far more demanding.

“When people at Google talk about agility in the context of hardware, networking, we do not mean move fast at any cost,” Iyer said. “We mean velocity with reliability, safety, and compliance.”

That distinction matters because the operating environment is deeply constrained. Google manages global deployments across varying regulatory environments, country-of-origin restrictions, compliance rules, remote sites with narrow access windows, and highly interdependent ship sets where a single missing component can delay an entire deployment.

Agility, in this context, is not about improvisation. It is about sensing issues early, separating real signals from noise, and translating insight into action quickly enough to avoid disruption altogether.

“Agility isn't just about dashboards,” Iyer said. “It shows up in real-time decision making.”

That includes substitutions when parts become unavailable, reallocating constrained inventory, adjusting lead times, balancing inventory positions, and making rapid commit-date decisions while still maintaining confidence in the outcome.

The limits of fragmented planning

Several years ago, Google’s supply chain organization faced a challenge familiar to many large enterprises. The company had grown rapidly, but its operating model had evolved incrementally.

“We built what we needed to solve the immediate problems,” Iyer said.

Over time, that created a landscape of spreadsheets, homegrown tools, point solutions, and disconnected planning logic. Systems worked locally but lacked end-to-end integration. Data reconciliation became labor-intensive. Standardization became difficult.

“Our planning cycle was weekly, not because weekly was ideal, but because refreshing a plan more frequently was just too heavy,” she explained.

That cadence introduced structural latency into the business. In an environment where conditions change daily, weekly planning meant teams were constantly reacting to yesterday’s reality.

Scenario analysis presented another limitation. Supply shortages, substitutions, alternate sourcing paths, and workaround decisions depended heavily on tribal knowledge.

“When decision quality depends on which expert happens to be available, that agility is not scalable,” Iyer said. “That’s risk.”

Visibility was fragmented as well. Teams struggled to quickly identify constraints, understand root causes, evaluate alternatives, and assess downstream fulfillment or compliance implications.

The organization could still deliver results, but only through intense manual effort.

“It required heroics,” Iyer said. “It wasn't repeatable, it wasn't scalable, and it wasn't the best use of expert capacity.”

Moving from reactive planning to continuous response

The transformation that followed fundamentally changed the rhythm of planning.

“A few years back, our cadence pushed us into a familiar pattern,” Iyer explained. “Build a plan, react to whatever breaks. Today, it shows up as a continuous loop, refresh, detect, decide, act, and repeat.”

Planning is no longer locked into rigid weekly cycles. Depending on business needs, plans may be refreshed daily or multiple times within a single day. That shift has had operational consequences well beyond speed.

“Less time stitching together data, rebuilding plans, and more time talking to your customers and making more high-quality trade-offs,” Iyer said.

The impact became visible in both qualitative and quantitative ways. “One of the strongest signals was qualitative feedback,” she said. “Material availability or lack thereof simply stopped being one of the top five issues.”

Stakeholders stopped escalating supply availability concerns because they assumed material would be there. That confidence translated into measurable improvements, including double-digit gains in on-time, in-full delivery performance over consecutive years.

One senior executive summarized it in a way Iyer considers the highest compliment possible: “Supply chain has become boring.”

Embedding agility into the system

A major part of Google’s progress came from codifying decisions that had previously depended on individual judgment.

Substitution management provides a good example. Historically, when a component became constrained, teams manually validated alternatives, debated options, aligned stakeholders, and then made decisions.

“That process works until time becomes your biggest enemy,” Iyer said.

Today, substitution logic is embedded directly into the system. When constraints emerge, the platform evaluates feasible alternatives automatically, while respecting policy, compliance, and ship-set dependencies. “Routine complexities [are] handled by the system,” she explained. “Humans step in when judgement actually matters.”

Inventory management evolved similarly. Rather than treating inventory as a passive outcome of planning, Google increasingly treats it as an active lever.

“When we see excess building in one hub, shortages forming another, we don't wait for the mess to happen,” Iyer said. “We rebalance earlier.”

Those moves often happen before downstream teams even realize there was risk in the network. In one example, proactive inventory rebalancing improved on-time delivery by roughly 6% simply by repositioning supply earlier.

The operational impact extended further. Inventory turns improved significantly. Excess and obsolete inventory declined by double digits. Inventory became more appropriately balanced at country, regional, and global levels.

“It freed up cash. It freed up space,” Iyer said.

Why culture matters as much as technology

Technology played a major role in enabling this shift, but Iyer was equally clear that systems alone do not create agility.

“Technology can enable agility, but culture determines whether it actually sticks,” she said.

Without changes in operating behavior, teams naturally revert to spreadsheets, local workarounds, and parallel processes under pressure.

One of the biggest lessons, according to Iyer, was moving agility away from individual heroics and into the operating model itself.

“We had to replace this with shared routines, clear decision rights, and repeatable ways of working,” she said.

Cross-functional coordination became equally important. Planning, procurement, logistics, and operations could no longer operate as sequential handoffs if the company wanted speed.

“In a volatile environment, that model is just too slow,” she explained.

Trust became another foundational element. “Trust is a real speed multiplier,” Iyer said. “People have to trust their data, the plan, and the decision logic.”

When trust is absent, organizations create parallel processes “just in case.” When trust is present, teams stop working around the system and agility becomes sustainable.

Building agility for the long term

For Iyer, the most important realization is that agility is not a one-time initiative.

“This is a marathon,” she said. “It's not one and done. It's not a go-live. It's definitely not a one-time project.”

The investment only makes sense if the business truly operates in a world defined by rapid change, global constraints, and constant volatility. For organizations in that environment, agility becomes a long-term capability rather than a short-term project.

“If you want calm, repeatable performance, predictable execution, and the ability to adapt without constant firefighting,” Iyer said, “then agility is worth that investment.”

But only if leadership is willing to commit to the long game. “That’s what makes it real,” she said. “And that’s what makes it last.”

See the entire Google aim10x Digital 2026 video below.

Watch