You Read the Culture Guide.
Then You Met the Actual Person.

You did the preparation. A new colleague was joining from a region you hadn’t worked with much, so you read up. The guide told you what to expect: how directly they’d give feedback, how they’d handle disagreement, whether they’d want the decision made in the room or taken away and considered.

So you adjusted. You softened your delivery, or you slowed the meeting down, or you held back the direct question you’d normally ask. You were being thoughtful.

And then you met them, and none of it fit. They were blunter than you were. They wanted the decision made on the call. The careful accommodation you’d built landed as hesitancy, and it took several awkward weeks to work out what had gone wrong.

The guide wasn’t lying to you. It was describing an average. You were dealing with a person.

What the frameworks actually measure

Cultural frameworks — the dimensions, the country scores, the comparison charts — are built from large samples and describe patterns across populations. They tell you that if you took thousands of people from one working culture and thousands from another, the two distributions would sit in different places.

What they do not tell you is where any individual sits inside their own distribution. Researchers have a name for the error of taking a group-level finding and applying it to a specific member of that group: the ecological fallacy. It is one of the most persistent problems in how cultural research gets used in practice, and it has been repeatedly flagged by the people who build these models — including Hofstede himself, who was explicit that his scores describe societies and were never intended to profile individuals.

The scale of the problem is easy to underestimate. Across most measured cultural values, the variation within any given country is considerably larger than the average difference between countries. The distributions overlap heavily. Knowing which curve someone was drawn from tells you remarkably little about where they personally land on it — and almost nothing about how they’ll behave in your Tuesday planning meeting.

Why cultural stereotypes at work survive good intentions

Here’s what makes this hard to catch: it doesn’t feel like stereotyping. It feels like diligence. Nobody in this scenario is dismissive, and nobody is operating from prejudice — the leader has gone out of their way to learn something before making assumptions.

Osland and Bird gave this pattern a name that has stuck: sophisticated stereotyping. It’s stereotyping dressed in academic clothing, built from real research rather than lazy assumption, and it’s more durable than the crude version precisely because it feels rigorous. When someone doesn’t match the profile, the crude stereotype gets abandoned. The sophisticated one gets defended — the person becomes “unusual,” “very westernised,” “not typical” — and the model survives contact with the evidence.

This is also where cultural stereotypes at work do their quietest damage. A leader who has decided in advance that a colleague won’t want direct feedback stops offering it. A colleague who would have welcomed it never gets the chance to say so. The prediction never gets tested, so it never gets corrected, and it slowly becomes the shape of the working relationship.

What actually predicts how someone works

The national pattern is one input among many, and often not the strongest one. How a person handles disagreement, deadlines, hierarchy, and directness is shaped at least as much by the organisation they trained in, the profession they came up through, the specific team they last worked on, how much time they’ve spent working across borders, and simply who they are.

Someone who spent a decade in a fast, blunt engineering culture carries that with them regardless of where they grew up. Someone who has worked across four countries has usually developed a wider range than any single profile would suggest. The colleague in front of you is a composite, and the country-level input is only one part of it.

How to use cultural knowledge without letting it harden

None of this means the frameworks are useless. Used properly, they’re genuinely valuable — they give you a vocabulary for differences you’d otherwise experience as personal friction, and they tell you which dimensions are worth paying attention to. The shift is in what you do with them:

Treat the framework as a hypothesis, not a conclusion. “This might be a difference in how directness is read here” is useful. “This person will find direct feedback uncomfortable” has already skipped a step. The first keeps you observing. The second stops you.

Ask about working preferences directly. Most people can tell you how they like to receive feedback, whether they want the decision made in the meeting, and how much notice they need before being asked to contribute. A five-minute conversation at the start of a working relationship gives you better information than any country profile, and it costs nothing but the asking.

Widen the range of explanations you reach for. When something puzzles you about a colleague, culture is one candidate explanation sitting alongside workload, role, seniority, personality, and the fact that they may simply disagree with you. Reaching for the cultural explanation first is a habit worth noticing in yourself.

Update fast, and out loud. When someone turns out not to match what you expected, that’s the model doing its job — it flagged a possibility, you tested it, you learned something specific about a person. Saying so plainly (“I’d assumed you’d want more time with this; tell me if that’s wrong”) turns a private correction into a shared understanding.

The cost of getting this wrong

When you prepare for a culture instead of a person, you spend your energy managing a version of your colleague who isn’t in the room. You accommodate needs they don’t have and miss the ones they do. And the person on the receiving end usually notices — being handled according to a script written about people like you, rather than being asked, is a specific and recognisable experience.

The frameworks earn their place when they make you curious. They cost you when they make you certain.