Why Cultural Context Matters in Information Management
Subhadra Dutta

By: Subhadra Dutta on May 7th, 2026

Print/Save as PDF

Why Cultural Context Matters in Information Management

Intelligent Information Management (IIM)  |  Women in Information Management (WIIM)

We tend to assume that data and information are binary, neutral, free of context or interpretation. But that assumption is wrong. Data carries cultural context, and information professionals working globally need to understand that.

Same Concept, Different Meanings

Consider something as straightforward as a monthly installment loan. In the U.S., it's called a monthly plan or monthly payment. In India, it's an equated monthly installment, or EMI. In other parts of Asia, it's an equal payment plan. Same concept, different terminology, and sometimes subtly different implications.

Even credit card terms and conditions look different from India to the U.S. There's commonality, but there are also finer nuances. One of my key learnings has been that even simple terms, the ones we tend to build entire analyses around, can carry very different meanings for different groups of people.

How Cultures Approach Ambiguity

Beyond terminology, cultures differ in how they handle grey areas. In my experience, some cultures tend to be more comfortable working through ambiguity, while others expect greater clarity upfront. I've seen this play out in teams across Asia, Europe, and the U.S., each bringing different expectations to how information should be defined before moving forward.

This plays out in data governance conversations. Who is the data owner? Who is the data steward? What does the difference mean? There's cultural context in how we respond to these questions. I see it happen frequently, though I'll admit the IT side tends to be more standardized than the business side, where countries and regions often develop completely separate methods and ways of working.

Normalizing Data Across Regions

When organizations grow through acquisitions, bringing different entities together, normalization gets harder. Imagine an Asian bank merging with a European bank. They have different terms. Their databases are just coming together. In that early phase, confusion is inevitable.

The good news is that most organizations are moving toward enterprise data warehouses and standardized metadata management. Over time, that normalizes things because ultimately it comes down to definitions, values, and logic. It's just the name that differs.

Contextualize Your Work

Having cultural context matters, but so does curiosity. What business are you working for? What does the world look like in that region?

When we understand the cultural context of the people we serve, we make better decisions about how to structure, present, and deliver information. We catch assumptions that might not hold across borders. We ask better questions. And we build solutions that actually work for the people using them.

Here's an example from my own experience. For years, I worked on Citibank's Thank You rewards program, a loyalty program well known in the United States. I was based in India, so I didn't really know how it felt to customers. When I finally traveled to our U.S. office and saw all the flyers and marketing campaigns I had worked on, it changed my whole perspective. I could finally see the results of my contributions, the scope of the program, and how actual customers would experience it. That visit reshaped how I thought about my work, even from a few thousand miles away.

Three Time Zones on My Calendar

Working in a global organization gives us the ability to understand other regions and cultures much better, and it helps create that general empathy. It comes from even things like having three time zones on my calendar in Outlook. Every time I’m setting up a meeting, I’m looking at the three time zones where my team or colleagues are. That also aligns with holidays and festival seasons, because a lot of what we deliver is around that, and there can be timelines around it.

It may not always be relevant only for information management, but in many different contexts, the kind of solutions you’re providing. While it may appear that “Hey, why do we need to do it by this time,” there may actually be a cultural context for the country or region you’re delivering to.

Understanding that helps.

Tip: You can add international holidays from countries around the world to your Outlook calendar through settings and options. It’s baseline Microsoft functionality and incredibly helpful for multinational teams.

 

The views expressed by Subhadra Dutta are her own and do not necessarily reflect the views of her employer.

This blog post is based on an original AIIM OnAir podcast. When recording podcasts, AIIM uses AI-enabled transcription in Zoom. We then use that transcription as part of a prompt with Claude Pro, Anthropic’s AI assistant. AIIM staff (aka humans) then edit the output from Claude for accuracy, completeness, and tone. In this way, we use AI to increase the accessibility of our podcast and extend the value of great content.

About Subhadra Dutta

Subhadra Dutta is a Senior Engineering Manager for Global Functions in Data & Software Engineering at Shell, based in Bangalore, India. She brings 20 years of experience in data and analytics spanning marketing, operations, finance, anti-money laundering, and HR. Before joining Shell two years ago, she spent 12 years at Citibank, building deep expertise in retail financial services across multiple global regions. Beyond the technical work, Subhadra is passionate about people, focused on fostering careers, nurturing aspirations, and driving equity and inclusion in organizations.