The Culture Map

Decoding How People Think, Lead and Get Things Done Across Cultures

By Erin Meyer

The Beard

I grew a beard for professional reasons.

I was running maritime security teams, anti-piracy work, boarding commercial vessels in high-risk waters. I was usually the team leader and I was usually the youngest man in the team.

The pattern was always the same. Get aboard, meet the master and the crew, and somebody would ask who the team leader was. I'd say me. And there'd be a pause. Then some version of: oh, you're very young.

Nothing hostile. Just a recalibration happening in front of me, and three days of proving myself before anyone relaxed.

Then I grew a beard, and it stopped.

Not gradually. It stopped. The same job, the same competence, the same voice, and I was being accepted the moment I came up the gangway.

Nothing about me had changed. Only the signal had.

I didn't have a framework for that at the time. I just knew it worked and kept doing it. Erin Meyer's book is where I finally found the explanation, years later, and it reframed a decade of work I'd done on instinct.

What The Book Actually Is

Erin Meyer teaches at INSEAD. The book came out of watching very capable managers from different countries misread each other in her classroom, not over values or competence, but over unstated rules about how you communicate, decide and disagree.

She maps culture on eight scales. Each one is a spectrum.

Communicating. Low-context, where meaning is stated explicitly, to high-context, where meaning sits in what isn't said. The US, UK, Netherlands and Germany sit low. Japan, China, Korea and Saudi Arabia sit high.

Evaluating. Direct negative feedback to indirect. The Netherlands, Germany, Russia and France are direct. Japan, Thailand and Indonesia are indirect.

Persuading. Principles-first, where you build the theory then apply it, to applications-first, where you lead with the example. France, Germany and Russia are principles-first. The UK and US are applications-first.

Leading. Egalitarian to hierarchical. Denmark, the Netherlands and Israel are egalitarian. Japan, Korea, Russia, Nigeria and India are hierarchical.

Deciding. Consensual to top-down. Germany and Japan build consensus. The US and China decide at the top.

Trusting. Task-based, built on competence and reliability, to relationship-based, built on knowing someone properly.

Disagreeing. Confrontational, where open debate is healthy, to conflict-avoidant, where it damages the group.

Scheduling. Linear time, one thing at a time against a deadline, to flexible time, where several things run at once and interruption is normal.

The single most important thing in the book is not any individual scale. It's that positions are relative, not absolute.

Her example is a software team at KPMG. The British found their French colleagues disorganised. The Indians found the same French colleagues rigid. The Germans found the British chaotic. Nobody was wrong. They were each standing somewhere different and describing the view.

That's not a footnote. That's the whole discipline. Your normal is not neutral. It's a position.

Why I Read This Differently

Most people who read this book are trying to stop a product launch slipping. The cost of getting it wrong is a delay, an awkward meeting, a quarter of lost revenue.

I spent three years in hostile environment security. Somalia, the Horn of Africa, Nigeria, West Africa, the Middle East. Building, training and leading multinational teams where trust and execution were life-critical.

I worked an East African port with an Indian chef, a Filipino crew, a Ukrainian engineer and a British team. One deck. No shared frame. No HR department.

So I read this book as a stress test. Her examples are boardrooms. Mine weren't. And the framework holds, which is the strongest thing I can say about it.

Nigeria: Blunt Isn't Always Blunt

Working in Nigeria with Nigerian police and Nigerian contractors, my first read was that people were blunt. Very direct. No cushioning.

That read was half right and the half I had wrong is the interesting part.

Meyer puts Nigeria toward the high-context end on Communicating, while sitting fairly direct on Evaluating. That's an unusual combination and she flags it specifically, because Russia has it too. Two cultures can both deliver blunt feedback and still misread each other completely, because one expects you to read the room and the other expects you to say it out loud.

So I wasn't dealing with British-style bluntness at all. I was getting direct feedback inside a high-context frame. Plain on the surface, and a great deal going on underneath that a British ear simply doesn't pick up.

Add in hierarchical on Leading, top-down on Deciding and flexible on Scheduling, and Nigeria sits four scales away from British norms at once. That's not a difficult culture. That's a long way from where I was standing.

And once you see it that way, the thing people describe as bluntness turns out to be the easiest part of working there. It was everything they weren't saying that I was missing.

Russians: Coconuts, Not Peaches

Her Trusting chapter gave me the frame for something I'd experienced repeatedly and never had words for.

The metaphor isn't hers originally, it comes from Trompenaars and Hampden-Turner, and it's the most useful thing in the book.

Peach cultures, which includes the Americans and Brazilians, are soft on the outside. Warm, open, friendly fast. Then you reach a hard pit, and you discover the warmth was courtesy rather than friendship.

Coconut cultures, which includes the Russians, Germans, Poles and French, are hard on the outside. Reserved with strangers, slow, no small talk. Then the shell gives, and what's inside is genuine and it lasts.

Get that backwards and you make two mistakes. You read Russian reserve as hostility, and you read American friendliness as a relationship.

I've worked with Russians who were, by British standards, borderline rude for the first week. Those same men I'd trust with anything now. Nothing had changed except that the week had passed.

Where I Got It Wrong: India

The honest one.

I was in India, called up to the captain's office. The authorities had come aboard. One of them turned to me and asked who I was. I told him I was Tom Frearson, the security team leader.

He had my company's documentation in his hand. It said Tom.

He asked for my passport. The passport said Thomas.

"It says Thomas. So you're Tom?"

"Yes."

"Where is Thomas?"

"No, I'm Thomas."

"You're Thomas. Where is Tom?"

This went round a few times. And I knew full well the paperwork was wrong and should have read Thomas. So I said, fairly casually, that in my country Tom is just an abbreviation for Thomas and the two are used interchangeably all the time.

He raised a finger at me and said: "No, no, no, my friend. We are not in your country now."

He was right, and it took me a long time to understand how right.

That man was not confused. Three rounds of "where is Tom?" from an official holding your passport is not a man struggling with a nickname. He knew exactly what had happened. He was giving me room to own the error.

India sits hierarchical on Leading and middle-to-high on Communicating. Which means two things at once. Deference to authority is expected, and criticism arrives as a question rather than a statement.

The repeated question was the feedback. I heard a literal question and went looking for the literal problem.

And the answer I gave carried something I never intended. "In my country, Tom is an abbreviation" says: your rule is a technicality, and here is how it's properly done. Delivered to an official in his own port, in front of the ship's master.

Own it in one line and he has room to be generous. Explain it and you've made his job harder and queried his authority in the same breath.

I had the information. I chose to explain rather than apologise. That's the bit I'd want anyone reading this to take, because it isn't about India at all.

The Handshake

A smaller one, and it makes a different point.

Walking into an East African port as team leader, I was met by an army captain. Big man. Very tall, imposing, serious bearing.

Right, I thought. Need to go in hard here.

I nearly took his hand off.

He hadn't come to meet me with a crushing grip. East African handshakes tend to be soft and often prolonged, sometimes carrying on while the conversation starts. Right hand only, and placing your left hand on your own right forearm adds respect when greeting an elder or a senior figure. In Tanzania there's a formal register for seniors too, shikamoo answered with marahaba, and you generally let the senior man offer his hand first.

So the error wasn't the grip. It was the assumption under it. Big man, army captain, imposing, therefore firm handshake. That's a British military read of what size and rank signal, projected straight onto someone operating in a different frame entirely.

Which is the uncomfortable lesson. You can know the framework exists, you can be perfectly aware that other people read these things differently, and you will still default to your own wiring on reflex.

Knowledge doesn't change the reflex. Only repetition does.

The Small Things That Aren't Small

Three that aren't in Meyer's book, and all three mattered more than anything that was.

Afghanistan. You take your glove off to shake a hand. Every time, however cold it is, however much kit you're wearing. It's a small physical cost and it says that this is a person rather than a transaction. Get it wrong and you've given an insult you'll never be told about.

The Indian yes. When a lot of Indian colleagues agree with you, the head moves side to side rather than up and down. A sort of wobble. If nobody has told you that, it is genuinely disconcerting, because every signal you've ever learned says that a head moving sideways means no. You ask again. They agree again. You still think they're refusing.

That's Communicating, high-context, and it's a good illustration that gesture carries meaning the words don't.

Facial hair, again. Beards, in several of the cultures I worked in, read as age, seniority and standing. It's the same mechanism as the handshake running in the other direction, and it's why the beard worked.

None of these are in the book, and all of them sit squarely inside what the book is arguing.

Inshallah, And The Mistake That Cost Me A Country

I should be straight about something, because it affects how I read this book.

I'm not subtle. The military trained that out of me. I don't dress up instructions, I don't hint, and I don't ask a question when I mean to give an order. If I want the fuel checked I say: check whether we've got enough fuel, and if we haven't, go and get more.

So I was never the man being misunderstood for being too delicate. I was at risk of the opposite, and once it cost me properly.

A Gulf port, late at night. End of a twelve-week stint. I had my team and another team to move, and we needed transport to the airport for a flight that was the difference between going home and losing another night and another day. I had a date I wanted to be back for. Twelve weeks was enough.

The man responsible for arranging it wasn't moving at the pace I needed. And every time I pushed, I got the same word back.

Inshallah.

God willing. It's a genuine expression of faith, not a dodge, and it carries something a British manager finds very hard to sit with: the outcome is not wholly in human hands. Depending on the moment it can mean yes, or I hope so, or no in a way that lets everyone keep their dignity.

I heard none of that. I heard an obstacle I needed to find a solution for.

So I was blunt. Direct, orderly, and entirely clear. I told him we weren't doing inshallah today. We were doing this, now.

Then I went around him, found another route, arranged the transport myself, got both teams to the airport and made the flight.

By every standard I'd been trained in, I did that right. Problem identified, obstacle removed, mission complete, men home.

The man I'd gone around turned out to be a relative of a family about as senior as it gets in that country.

I was banned. I had to write a letter of apology to someone very senior indeed before any of it could be put right.

Here's the part that took me years to properly understand. The bluntness wasn't really the offence.

That region sits hierarchical on Leading and relationship-based on Trusting. In that frame, a man with standing expects his position to be acknowledged, and the way you get something difficult done is to make him the one who gets it done. Ask for his help. Let him solve it. Let him be the reason it worked.

I did the exact opposite. I demonstrated, in his own port, in front of two teams and whoever else was watching, that he had been an obstacle rather than the solution. In British task-based terms that's initiative. In his terms it was a public humiliation, and it was entirely avoidable.

And I'll own the other half of it too. I'd been away twelve weeks and I wanted to be home for a particular date. That urgency was real, and it was mine. It wasn't his, and I behaved as though it should have been.

The same pattern runs through flexible-time cultures generally. Across much of sub-Saharan Africa you'll come across Africa time. It'll happen when it happens. Meyer puts Nigeria and Kenya at the flexible end of Scheduling alongside India and Saudi Arabia, and her point is that this isn't disorganisation. It's a different relationship with the clock, where people and events take priority over the time printed on the schedule.

I could be as clear as I liked. It changed nothing, because the problem was never that my instruction was unclear. The problem was that I was hearing a commitment where one hadn't been offered, and then treating the gap as defiance.

What actually works is unglamorous. Confirm what has happened rather than what will happen. Build in slack and stop pretending the slack is contingency. Check in without making the check-in feel like an accusation. Separate out the few things that genuinely cannot move, say those once, clearly, with the reason attached, and let everything else breathe.

And where someone has standing, go through them rather than round them, even when round them is faster. Especially when round them is faster.

If everything is urgent then nothing is. And in a flexible-time culture a long list of deadlines reads as a British preference rather than a set of hard constraints.

Upgraders, Downgraders And The British Problem

The funniest part of the book, and the part most likely to make a British reader wince.

Direct cultures strengthen criticism with what Meyer calls upgraders. Absolutely. Totally. Completely unacceptable. Indirect cultures soften it with downgraders. A bit. Slightly. Maybe. Perhaps we could consider.

She names the British as the world's masters of understatement, and she reproduces a circulating Anglo-Dutch translation guide that should be pinned up in every international office.

"I was a bit disappointed" means I am furious. The Dutch hear that it doesn't really matter.

"Very interesting" means I think this is rubbish. They hear that you're impressed.

"That's an original point of view" means that's stupid.

There's a case in the book of a German manager whose British boss "suggested that he think about" changing something. He thought about it, decided against it, and was reprimanded for insubordination.

I've never had that problem, for the reasons above. What I have seen, many times, is British colleagues having exactly that problem, and having no idea it was happening. They came away thinking the other party was difficult. The other party came away thinking nothing had been asked of them.

If you take one practical thing from this book, strip the downgraders out of anything that actually matters. Say it once, plainly, with the reason. You can be warm and unambiguous at the same time. Most people think they have to choose.

How I Use This Now

Two ways.

The first is that it gave me language for something I'd been doing on instinct for a decade. That sounds minor and it isn't. You cannot teach a reflex, and you cannot hand an instinct to a facilitator or a client. You can hand them a model.

The second is that we use the same discipline one level down. In team development we use DiSC profiling to read the culture inside a business, the players in it, where the strengths and the limiters sit, and how those people land on each other. Meyer maps national culture. DiSC maps the individual. They're the same skill at different scales, and they work for the same reason.

Both of them stop you treating your own normal as neutral.

That's the entire value. Not a lookup table of countries. A permanent, slightly uncomfortable awareness that the way you communicate, decide and disagree is a position on a spectrum rather than the correct way of doing things.

Where It Gets Criticised

Worth saying, because the criticisms are fair.

The methodology is thin. There's no peer-reviewed research underpinning the eight scales. It leans heavily on anecdote from her own INSEAD cohort, with identifying details changed, which asks you to extend a lot of trust. She also draws on Hall, Hofstede, Trompenaars and Hampden-Turner without always crediting them clearly.

The coverage is uneven. Europe, Asia and the Anglosphere are served well. Africa and Latin America much less so, though Nigeria does feature properly in the Scheduling chapter. Given where I worked, I noticed the gaps.

And the obvious risk. Describe a national norm without strong evidence and you are one step from a stereotype. Her defence is the relative-positioning point, and the honest version is this: the framework gives you a starting hypothesis about a person, never a conclusion. The moment you use it to predict an individual rather than to question your own reading, you've broken it.

Every scale in this book has to survive contact with the actual human in front of you. Some of the most direct people I've worked with were from indirect cultures. The map is not the person.

A Fracture Clinic In North London

This is the one that convinced me the book matters outside my old job.

I dislocated my shoulder climbing a few years back. A few weeks later I was in for a follow-up at the fracture clinic. I walked in, sat down, and the consultant looked up at me and said:

"What is the problem?"

That was it. No preamble, no how are you getting on. Deep Nigerian accent.

Ten years earlier I'd have come out of that appointment thinking he was rude. Abrupt at best, dismissive at worst. I might well have said something to somebody about it.

Instead I thought: right, fair enough. And I answered the question.

Because look at what he actually said. What is the problem. Four words, no softeners, straight to the medicine. He was being entirely normal, and he was being efficient with an NHS appointment slot.

That same sentence out of a British consultant would have carried an unspoken second half. And why are you taking up my morning. Out of his mouth it carried nothing at all. It was a question, and it wanted an answer.

The rudeness was never in the room. I'd have brought it in with me.

That's the part that should interest anyone leading a team in this country. I learned that in Nigerian ports with Nigerian contractors, at a certain amount of expense. I used it in a hospital in north London on a weekday morning, as a patient, with nothing at stake and no reason at all to be thinking about culture.

The cultures in this book are not abroad. They are in your building. The NHS alone employs people from the best part of two hundred countries, and if you lead a team in London you are doing cross-cultural leadership whether you've noticed it or not.

Most people haven't noticed. They've simply, quietly, decided that one or two of their colleagues are rude.

Why This Matters For Every Leader

You don't need to work in Mogadishu for this to apply.

When someone agrees with you, how do you know they've committed rather than acknowledged?

When you give a difficult piece of feedback, how much of it is downgraders, and would the person be able to repeat back what you actually want changed?

When a deadline slips, do you reach for a character explanation or a frame explanation?

What are you signalling about your own authority, and is it the signal you think it is?

And the one that takes longest. Which of your professional instincts are actually competence, and which are just where you happen to be standing?

Who This Book Is For

Anyone leading people who weren't raised where they were raised. Which, in London, is most people leading most teams.

Anyone who has a colleague or a client they've privately decided is difficult, disorganised or rude.

Anyone who gives feedback across a language or a border.

And anyone who has concluded that the problem in a relationship is the other party. That's the one. If you've landed there, the frame is worth checking before the person is.

Final Thought

I spent years in environments where reading people wrong had consequences I couldn't undo, and I got good at it by trial, error and a reasonable number of mistakes like the two in this review.

This book didn't teach me that. It explained it, which is a different and in some ways more useful thing, because an instinct helps one person and a model can be handed to a team.

The beard worked because it sent a signal I hadn't earned, in a frame I didn't understand, to people who were reading me far more accurately than I was reading them.

That's worth sitting with. In most rooms you walk into, somebody is reading you better than you're reading them.

And there's a line I didn't notice for years.

In India, an official pointed a finger at me and said: we are not in your country now.

In a Gulf port, I pointed at a man with more standing than I understood and told him we weren't doing inshallah today, we were doing this now.

Same sentence. Same error. I was just on the other end of it, and only one of us was right.