Your Design Doesn't Translate

TL;DR: Cultural cognition means users do not all read the same screen the same way. What feels clear, complete, or trustworthy in one culture can feel empty, confusing, or wrong in another.

White space does not mean the same thing everywhere. When you look at a sparse layout and feel calm, when you see a clean interface and call it good design, that reaction is real. But it does not come from some universal rule of human cognition. It comes from where you grew up, what you were trained on, and which design tradition shaped your sense of what an interface should feel like. I have had to remind myself of that too. More than once, I have looked at a product and mistaken my own training for common sense. That mistake is easy to make because your own taste always seems neutral from the inside.

Many designers working in Western tech have spent their careers inside a narrow aesthetic tradition: Scandinavian minimalism filtered through Swiss typography, refined by a decade of Apple, and reinforced by the assumption that simplicity is always clarity. That assumption does not hold everywhere. In some contexts, that polished page can read as premium. In others, it can feel unfinished, cold, or thin. I have seen teams call a page elegant when users in another market read it as half-empty and unconvincing. The page did not change. The expectations around it did.

You learned one culture’s defaults

In 2001, psychologist Richard Nisbett and his colleagues published a study asking whether people from different cultures actually perceive visual information differently. Not just interpret it differently, but attend to it differently at the level of attention and cognition.

The answer was yes. Nisbett’s team found that East Asian participants tended to process images as a whole: they attended to the full field, to relationships, to context. Western participants tended to isolate the focal object and filter out the surround. When shown a scene, Western participants remembered the foreground object. East Asian participants remembered the background too. Put simply, some people take in the whole picture first, while others focus on the main thing first. As the researchers put it,

East Asians tend to be holistic, attending to the entire field and assigning causality to it.

— Nisbett, Peng, Choi & Norenzayan

Anthropologist Edward T. Hall explained part of this in his 1976 book Beyond Culture. He described two styles of communication: high-context and low-context. In low-context cultures, people expect meaning to be clear and direct. In high-context settings, meaning depends more on situation, shared understanding, and relationships. That difference appears on screens faster than many teams expect.

A second issue sits underneath all of this. A lot of psychology and UX research was based on a narrow group of people. In 2010, Henrich, Heine, and Norenzayan called this group WEIRD: Western, Educated, Industrialized, Rich, and Democratic. Their argument was simple: this group is not the same as all humans. So some design ideas got taught as universal, even though they came from a limited part of the world. A lot of product teams still design as if that warning changed very little.

The same page can land two ways

This appears in ordinary product work fast. Take a pricing page with lots of blank space, one image, a short headline, and one button. Or a checkout step that says only “Continue” because the team thinks extra explanation makes it messy. To one user, that can read as clear and high-end. To another, it can come across as thin, like the company has not explained enough to earn trust.

I have seen that split happen in product reviews. One person says the page feels elegant. Another says it looks unfinished. Both reactions are real. They come from different learned expectations about what a serious product should show up front.

Aaron Marcus and Emilie Gould mapped this directly onto interface design in 2000. Their main point was simple: cultural values change how much hierarchy people expect to see, how much information feels normal, and what kind of structure reads as complete. That is not noise around the interface. It is part of the interface working or failing.

WeChat and WhatsApp solve different expectations

WeChat launched in 2011. By 2018 it had passed one billion monthly active users, almost all in China. Open it and you get messaging, payments, a social feed, games, mini-programs for taxis and food, a news reader, and a scanner, all close at hand. Western tech journalists and designers have been calling it overwhelming for years. Cluttered. Hard to parse. Too much.

To many Western designers, WhatsApp looks calm. To users used to a denser product like WeChat, that same sparseness can read very differently.

Neither reaction is wrong. WeChat was built for people whose habits treat density as a feature. More visible functions can suggest more usefulness. The product looks busy, but it also looks ready. WhatsApp was built for people who treat sparseness as focus. Fewer visible choices can read as clearer and calmer. One product signals usefulness through density. The other signals trust through restraint.

That is the part many Western teams miss when they judge products from outside their own market. They assume their reaction is the neutral one and everything else is clutter, bad taste, or weak editing. It is usually a much simpler mistake than that. They are reading another culture’s product with the wrong defaults loaded in their head. I have caught myself doing exactly that.

Ask what feels normal here

There is a version of the five-second test that is useful here. Before you ship a product into a cultural context you did not design for, find five people who live there and show them your landing screen for a brief glance. Then ask one question: does this feel complete or incomplete?

Not “do you like it?” People are too polite with that question. Ask if it feels incomplete. That is the real signal. Some people look at a sparse screen and think something is missing. You will usually hear it fast and in plain language too. “It looks unfinished.” “I expected more information.” “I do not know why I should trust this yet.”

It is not a full localization check. It will not catch everything. But it will catch the first thing: the instant reaction people have before they even use the product. I have found that this is often where the trouble appears first. The screen can be technically correct and still feel wrong in the first few seconds.

Your design education taught you what good looks like. So did theirs. The difference is you only learned one of those lessons.