0:0033:34

Localizing in the world of global operations

Sangeetha Parsan 33:34 2026

Data localization laws can split the central platform your AI depends on

When Saudi Arabia's data localization rules reach Informa in 2023, its live global data platform rests on the opposite principle: centralize everything. Sangeetha Parsan, Vice President of Customer Data Solutions and Services with more than 20 years in data, must split people, process and technology apart without breaking the business, often with only double-digit days to comply. When the same demand lands on your team, where do you start?

Get a four-pillar playbook for localizing data while keeping global operations and AI running

Watch on YouTube

In short

Sangeetha Parsan explains how Informa responded when Saudi Arabia's data localization requirements collided with a centralized global data platform that a live business depended on. She presents a practical four-pillar framework (technology capabilities, data compliance mapping, process change and people readiness) with a phased day 0 to day 180 plan, and discusses how local models and federated learning can keep AI strategies alive when borders fragment data.

“Don't start with what you have centrally. That could end up misleading you because it's built for the entire global organization, not for one region.”
“But people don't move in a project timeframe.”

What you will learn

  • Start localization work from the capabilities a region needs instead of pulling apart the existing central architecture.
  • Build a data compliance map with legal and privacy teams to define exactly which data must stay in-country.
  • Prioritize process changes by impact rather than difficulty, using a day 0, 60, 90 and 180 plan.
  • Plan change management, training, a managed services model and a longer hypercare period for the people running the new stack.
  • Protect AI capability with local models and federated learning when borders fragment training data.

Key takeaways from the speaker

  • Strategic approaches to building compliance-ready technology at global scale

Details

Level
Intermediate
Format
Tech talk
Technical depth
Practitioner
For
Senior individual contributor, People manager, Executive
Length
33:34
Published
August 2026

Questions this talk answers

What is the first step an organization should take when preparing for data localization requirements?

Identify the capabilities needed in the region, the data that powers them and the technology required. Do not start from the central stack, because it was built for the whole global organization, not one region.

How should a team prioritize localization work under a tight deadline?

Prioritize by impact, not difficulty: critical in-scope data isolated with no violations on day zero, secondary processes by day 60, edge cases by day 90 and full maturity with a playbook by day 180.

What happens to AI when data has to be localized?

Training data fragments, inference can miss regional nuances and governance becomes harder across many models. She suggests local small language models alongside global models and federated learning on gradients rather than raw data.

Why can't a company simply stay non-compliant?

Non-compliance means losing trust with local entities, possible penalties or even a shutdown, and losing the AI advantage built over years.

Does every new country require repeating the full process?

No. India's requirements focused mostly on financial transactions and keeping a copy, which is very different from 100 percent localization.

About this talk

Working with data teams before and AI teams now, the common thread has always been: standardize and centralize to enable analytics, insights, data products, and AI. I was deep into this path, building infrastructures meant to centralize, scale, and power enterprise-wide capabilities. Then data localization hit. Working for a truly global business with shared systems and processes for cost optimization, I faced a critical question: how do we decouple people, technology, and process all at once without breaking a successful business that depends on all three pillars? In this session, I'll share the lessons I learned and the framework built to stay compliant while maintaining business continuity. You'll learn how to architect for geographic requirements without sacrificing centralization—and what actually happens to your AI when borders fragment your data. My framework includes laying the foundational steps and getting compliant efficiently through a layered approach. The foundational layer starts with data—introspection from data cataloging to understanding data flows. What data do you have? Where does it live? Where does it move? The next layer uncovers the processes—where does data get transformed, where are the storage points, who interacts with it, and critically, which AI models are consuming it? The final layer is technology, viewed through the lens of what can be retained and reused. What infrastructure is portable? What creates vendor lock-in? Then the puzzle starts to take shape. The outcomes of these three layers help you define a cloud-agnostic, vendor-agnostic, compliant data platform that can continue powering local businesses while keeping AI dreams alive for global organizations. Now, as more countries view their digital infrastructure and citizen data as sovereign assets to protect, this same formula can be quickly replicated without massive disruption or excessive costs. You're not starting from scratch each time—you're applying a proven framework that scales geographically while maintaining the centralization benefits that make modern data and AI possible.

Topics

Related talks

Browse the library