One Company, Many Cultures, and the Survey That Nearly Gave Me a Heart Attack

HR ran one of their Pulse Surveys, the kind meant to measure whether the org has a pulse and mostly measures whether mine spikes when the results land. Normally I skim them and forget them by lunch. This one came back with a section scoring me as a manager, and the numbers weren't soft. They were bad. My heart rate, fittingly, did the exact thing the survey was named after.

It took me a day to stop sulking and pull the team together. Why, I asked, did none of this surface before a form dragged it out of you? About three minutes in, my pulse came back to earth, because the answer was hiding in the question design. We run a matrix; half my people deliver under a peer of mine, and the "your manager" questions never said which manager. Every one that unmistakably meant me had scored fine. The cratered ones were the vague ones, answered by people picturing someone else. False alarm. But it pointed straight at the thing I'd spent two years failing to explain to anyone above me.

Some backstory. I once built an offshore team from nothing, months of flying back and forth, five engineers and a lead ramped onto our stack. Then a French company bought us, and over the next year the gravity reversed: I wound that same team down, because by then we were the offshore team, and they had become the offshore of the offshore. So I've stood on both sides of that border, the one issuing instructions and the one receiving them with no vote. Most people only see one side and conclude the other is being difficult. They almost never are. They're running a different default, and what everyone calls friction is mostly two defaults grinding against each other while each side insists its own is just "normal."

The friction is predictable, not personal

Here's the kind of thing that breaks. A strong developer wanted to move into my group. Light on big-data experience, heavy on drive, so the executives approved the move over a six-month ramp where he'd keep his old job and close the gap. One month later he was gone, hired elsewhere into the role he wanted. The plan wasn't stupid where it was written. At headquarters the notice period is three months, so six months of overlap reads as generous. Where I sit, notice is one month, so six months reads as "we are not serious about you." Same number, two cultures, opposite meaning, and nobody noticed they were speaking different languages.

Another one I watched up close. One of my people joined a project run out of another site, and I did what I always do: asked the product manager to walk me through it. The project's tech lead tensed. To him, a manager who wasn't in his chain taking a close interest read as an audit, the opening move of someone coming to take something. To me it was curiosity and a chance to learn. Neither of us was wrong about our own world; we were running opposite assumptions about what a senior person poking around your work means. If I hadn't eventually noticed the tension and named it, it would have calcified into "that guy doesn't trust me."

It runs down to cadence too: my people get twitchy if a week passes without a 1:1, while an engineer at the other site expects their group manager once a quarter and calls that plenty. Export your own default as if it were physics and you'll spend years baffled at why people keep reacting "wrong."

The model, used lightly

Trompenaars and Hampden-Turner interviewed something like sixty thousand managers and boiled the mess down to seven dimensions of culture. You don't need to memorize them, just the idea underneath: these differences are predictable, not random noise. Take recognition. I praise good work loudly and in the open, because where I come from that's fuel. Do that to someone whose culture reads public singling-out as exposure, and you've punished them for doing well.

And here's the payoff. A multi-culture team, managed by someone who's done the work, beats a monoculture one, and not for the reasons that go on the diversity slide. It wins because a monoculture shares one blind spot, perfectly, across every person in the room, and never sees it. The friction you feel on a cross-culture team, once you stop misreading it as people being difficult, is the sound of someone approaching the problem from an angle your default would never have found. The cost is the translation. The upside is you stop being unanimously wrong.

So the survey never proved I was a bad manager. It proved that headquarters and I had been grading the same team with each other's rulers and acting shocked at the scores. My pulse settled in three minutes. The cultural gap took the full two years, and the only thing that ever moved it was the unglamorous habit of asking instead of assuming, in private, before I decided I already knew what someone meant.