Case Study 1 — The Empowering Boss Who Looked Absent

A composite case, assembled from the common experiences of Western managers taking over hierarchical Asian teams. Names and details are illustrative.

The situation

Alan is a British engineering manager with a track record built on a single conviction: the best managers get out of the way. Across a decade in Manchester and London, he earned a reputation as the boss everyone wanted — flat, trusting, allergic to micromanagement. His teams loved the autonomy; his bosses loved the results. So when his company asks him to take over a thirty-person product team in Seoul, he's confident he knows the formula. He'll do what he's always done: empower them.

In his first all-hands, he says exactly what worked at home. "I'm not going to micromanage you. You're the experts — you know this product better than I do. Bring me your ideas, own your projects, tell me what you need, and I'll back you. I trust you to run with it." He sits down feeling he's made a great first impression. He has handed his new team autonomy, respect, and his open confidence in them.

Over the next six weeks, everything quietly goes wrong. The team grows more anxious, not less. Projects that he assumed were owned and moving stall, waiting on approvals he never said they needed. People begin cc'ing him on routine emails and asking permission for small decisions he'd considered theirs. His most senior engineer, Jun-seo, requests a one-on-one and asks, with visible concern, "What is your direction for the roadmap?" Alan, genuinely baffled, says, "That's what I'm asking you — you know it better than I do." Jun-seo nods slowly and leaves looking more worried than when he came in. By week eight, Alan's read on his celebrated new team is grim: talented but strangely passive, can't make a decision, no initiative.

He is wrong on every count — and the harder he leans on the style that made his name, the worse it gets.

The 'before': how it felt through Alan's operating system

Run the events through Alan's home-culture software and his conclusion is reasonable. In his world, autonomy is a gift and a compliment; a self-starter receives it gratefully and runs. Asking "what do you think we should do?" is how you show respect for someone's expertise. A flat structure where the boss stays out of the details is the modern, enlightened way — command-and-control is for dinosaurs. So when his Seoul team responds to his generosity with anxiety, hesitation, and a stream of permission-seeking, Alan reads exactly what those behaviors would mean if a British team did them: passivity, timidity, a worrying inability to own decisions.

And Jun-seo's question — "what is your direction?" — confirms the diagnosis for Alan. To his ear, a senior engineer asking the boss for direction is a senior engineer who lacks confidence. He doesn't hear what's actually being said.

Every word of his interpretation is fluent — in the wrong language.

The 'after': what was actually happening

Alan's team was not passive, and Jun-seo was not timid. They were responding, correctly and competently, to a leader who — by the rules of a steep Confucian-influenced hierarchy (Chapter 6) — had just failed to do his job.

• The senior role carries a duty to direct. In this system, a manager is not a facilitator among equals; he is the person whose rank obliges him to know the way and say so. By refusing to give direction — by tossing it back as "you decide" — Alan didn't signal trust. He signaled that he either didn't have a direction (incompetence) or wouldn't take responsibility for one (worse). The team's anxiety was a rational response to a leader who appeared not to be leading. (Chapter 6.)
• "You decide" pushed risk downward, against the rules. In a hierarchy, juniors are supposed to be protected by seniors, not exposed. By making the team own decisions above their station, Alan handed them the risk and potential blame that should have sat with him. The permission-seeking and cc'ing were the team trying to push that risk back up where it belonged — to get cover before acting. (Chapter 3, face.)
• Jun-seo's question was a senior person doing his job, not failing at it. "What is your direction for the roadmap?" wasn't a confession of weakness. It was an experienced engineer correctly asking the leader to lead — to provide the strategic clarity that was the leader's to give — so that the team could then execute it excellently. Alan heard a lack of confidence; Jun-seo was modeling exactly right behavior and quietly alarmed that the new boss didn't reciprocate. (Chapter 6.)
• The stalls were caution, not laziness. Without sanctioned direction, acting boldly risked overstepping — and overstepping a superior's unspoken intent is dangerous in a face culture. Freezing was the safer error. The team wasn't lacking initiative; it was lacking the green light only the leader could give. (Chapter 4.)

What Alan graded as passivity was, in their system, a display of competence and respect colliding with a vacuum where leadership should have been. He'd been marking expert behavior as failure because he was using the wrong rubric — and never noticed he was holding a rubric at all.

The deeper point

This is the chapter's central inversion in a single story. Alan's failure had nothing to do with ignorance of Korea; he could have recited facts about Korea all day. It had to do with the invisibility of his own leadership culture. He experienced "good managers get out of the way" not as a cultural belief but as a plain fact about good management everywhere. Because that assumption was invisible to him, he couldn't switch it off — and so the very behavior that made him beloved in Manchester made him look absent in Seoul.

Notice, too, that both systems are internally sensible. Alan's empowering style genuinely works in the UK, where it surfaces ideas, builds ownership, and signals respect. His team's expectation of clear direction genuinely works in Seoul, where the senior-junior bond runs on the senior providing guidance and protection in exchange for diligence and loyalty. Neither is the "real" way to lead. They are two operating systems optimized for different things — and the collision happened below the waterline, in a clash between two unspoken definitions of what a good boss owes the people below him.

The better approach

Alan doesn't need to become an autocrat, or to abandon everything good about empowerment. He needs to recognize he's running a leadership culture, and adjust the interface so his respect becomes legible to his team. Concretely:

• Provide the direction first, then delegate within it. Instead of "you decide," Alan sets a clear roadmap and priorities — this is where we're going, these are the bets — and then delegates real ownership of pieces within that frame: "Jun-seo, you own the platform migration; here's the goal, the standard, and the date; come to me when you hit a wall." Now there's both clarity and autonomy, in the order this system needs them.
• Decide visibly when the decision is his. When something is genuinely his call, he makes it and says so, rather than reflexively throwing it back — which read as indecision, not humility.
• Take responsibility upward and shield the team. He makes clear that the risk sits with him, not them, restoring the protection a senior is supposed to provide. That alone dissolves much of the permission-seeking.
• Re-read "asking for direction" as competence, not weakness — and re-read the stalls as caution awaiting a green light, not a lack of initiative.

Scripts he could use: - (setting direction) "Here's where I want us to go this quarter, and why. Within that, I want you to own your pieces and make the calls — and if you're ever unsure how far your decision-making goes, ask me. I'll always tell you." - (to Jun-seo) "Good question — that's mine to answer, and I should have led with it. Here's the direction. Now I want your expertise on how we get there." - (restoring protection) "If a call you make in good faith goes wrong, that's on me, not you. I'd rather you move than wait. Here's the boundary so you know what's yours to decide."

Within a quarter of providing direction and delegating within it — rather than abdicating in the name of empowerment — managers in Alan's position typically find their "passive" team was full of capable, decisive people all along, just waiting for a leader to do the part of the job their system reserves for him.

Discussion questions

1. Identify the exact moment Alan's own leadership culture became invisible to him. What belief did he mistake for a universal fact about good management?
2. The chapter says both systems are "internally sensible." Make the strongest case you can for the Seoul team's expectation of clear direction as good professional behavior, not timidity.
3. Alan's instinct was that hands-off equals respectful. Where in your own work might "getting out of the way" actually read as "not doing your job" to someone from a different system?
4. Could Alan over-correct — become so directive that he crushes the very initiative he wants? Where's the line between giving clear direction and micromanaging?
5. Whose responsibility is it to bridge this gap — the manager's, the team's, or both? Does your answer change depending on who holds more power, or who is the "newcomer" to the culture?

Portfolio link. In your Cultural Intelligence Portfolio, add to your running list "Behaviors I might misread" the entry from this case: a report asking me for "direction," or hesitating to act without it, may signal correct deference in a hierarchy — not a lack of initiative. Then add one line to "My leadership interface": name the one situation where your instinct to "get out of the way" would most likely backfire in your chosen culture, and what you'd do instead.