Cultural sensitivity in product design

We were designing a feature at Talkdesk for emergency-services calling. The first instinct was to pick a universal symbol: the red cross. It’s what shows up on ambulances, hospitals, first-aid kits. Seemed obvious.

It wasn’t. The red cross has specific connotations in several cultures, particularly in Muslim contexts where the cross can evoke historical narratives that are offensive. The Red Crescent is the equivalent symbol in Muslim-majority countries, and the Red Crystal serves as an international neutral.

We switched to plain text (“9/11”, the local emergency number), and the problem disappeared. The cost of the change was minimal. The cost of not seeing the problem could have been much higher.

This story sums up what cultural sensitivity in design is: surfacing meanings before the product reaches the people who carry them.

Where the problem shows up

Four main categories:

1. Symbols. The red cross is just one example. Thumbs-up is offensive in some Middle Eastern cultures. The OK sign with thumb and index can mean zero, or be an offence, depending on the country. Colours too: white is weddings in the West and mourning in China.

2. Dates and formats. 04/05/2026: is it May 4th or April 5th? Depends. Numeric formats, decimals (comma vs. period), currencies, metric vs. imperial. Each can lead to real confusion.

3. Language and translation. Literal translation rarely cuts it. “Schedule a call” translated word-for-word can sound too formal or strange depending on the country. Idioms are a trap.

4. Cultural references. Images of people celebrating Christmas in a global product, examples with only Anglo-Saxon names, prices only in USD. Signals that the product thinks within a single culture.

What I learned to do

Research before design. When a symbol, colour, or reference is central, I spend 30 minutes checking connotations across at least 5 cultures relevant to the product. Cheap and catches obvious traps.

Review with people from other cultures. Not just “read this copy”, but “do you see anything here that bothers you or doesn’t make sense?”. The open-ended question catches more than checklists.

Test locally. I don’t trust automated translation alone. When the product enters a new market, talking to local users is non-negotiable. The translation looks correct in Google Translate and wrong in real life.

Conservative defaults. When in doubt, I pick the more neutral path. Text over a contested symbol. ISO formats over assumed local formats. Diverse imagery over homogeneous.

Colours and their meanings

Worth knowing the main connotations:

• Red: luck and celebration in China, danger in the West, mourning in South Africa.
• White: purity in the West, mourning in China and Japan.
• Green: money in the US, fertility in the Middle East, danger in Indonesia.
• Yellow: joy in the West, sacred in some Asian cultures, sickness in others.
• Purple: royalty in the UK, mourning in Thailand.
• Blue: trust and peace in most cultures (one of the few relatively universal).

Doesn’t mean you avoid colour. Means big choices (a brand’s primary palette for a market, error vs. success colour) deserve verification.

Images and illustrations

Three principles:

Visible diversity. When you illustrate people, illustrate several. Different skin tones, ages, abilities, contexts. Not a box to tick; real representation.

Avoid stereotypes. Woman as mother, man as CEO, older person as confused. Lazy defaults. Think before picking.

Visible cultural context. If the product is global, show global scenarios. Not just Silicon Valley offices. European cafés, homes around the world, varied clothing.

The real case: red cross → plain text

Back to the Talkdesk case. The catch came from a colleague who made the observation during review. It wasn’t a formal audit, it was a conversation: “this could be an issue in Muslim markets, consider changing”.

The change took half an hour of design. Another hour aligning with engineering. Total: less than two hours to avoid a bad launch in markets where the feature would be used.

Lessons:

• Team diversity is the first line of defence. Homogeneous teams catch fewer of these.
• Informal conversations are as valuable as formal audits. Make space for “this doesn’t feel right” without hierarchy.
• Cost of change rises with time. Catching now is free. Catching after launch is expensive.

What to do in your flow

Three concrete actions:

1. Add a cultural review to design review, especially when the product is multi-market. Five minutes scanning the visible signals.
2. Talk to a user from each important market before any major feature. Short, informal, but regular.
3. Build a small “library of cultural pitfalls” with your team. Every time you catch something, log it. Compounds over time.

More on the background in the Inclusion and Diversity guide. On the cognitive biases often behind these decisions, see Cognitive biases explained. On how a team internally cultivates the sensitivity that catches these things, see Inclusive design teams.