Chapter 17 — Managing and Being Managed: Leadership That Translates

A British team lead named Alan inherits a high-performing team in Seoul. He arrives with the leadership style that earned him three promotions back in Manchester: flat, hands-off, empowering. He tells his new reports, in his very first all-hands, exactly what he'd tell a team in England. "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, and tell me what you need. I trust you to run with it." He means every word as a gift. He is handing them autonomy, respect, and his confidence.

He watches the gift land like a dropped plate. Polite nods, a few uneasy glances, and over the following weeks a team that grows visibly more anxious, not less. Projects stall waiting for approvals he never said they needed. People start cc'ing him on everything, asking permission for decisions he'd assumed were theirs. His most senior engineer requests a one-on-one and asks, carefully, "What is your direction for the roadmap?" Alan, baffled, says, "That's what I'm asking you." The engineer leaves looking more worried than when he came in.

Alan has just discovered that the leadership behavior he experiences as generous — stepping back, empowering, trusting the team to self-direct — was read by his Korean team as something closer to absent. A leader who won't give direction, in a steep hierarchy, doesn't look liberating. He looks like he doesn't know what he's doing, or worse, like he's quietly making the team responsible for his own job so he has someone to blame.

The WHY. In the modern West — and especially in the Anglo and Nordic worlds — good leadership has drifted toward a flat, facilitative ideal: the leader as coach, the leader who "empowers," the manager whose proudest boast is "my team doesn't need me." That ideal is not universal. It is a specific cultural answer to a specific cultural question: what does a junior person need from a senior one? In much of the East, built on Confucian or hierarchical foundations (Chapter 6), the senior person's job is to provide clear direction and protection, and the junior person's role is to execute it well and with loyalty. In that system, the "empowering" Western boss who refuses to direct isn't being generous — he's abdicating the duty of his rank. Same behavior; opposite meaning. This chapter is about managing, and being managed, across that gap — in both directions.

What this chapter unlocks

• The core mismatch: why Western "empowerment" can read as weak leadership in hierarchical cultures, and what to do instead.
• The four moves of managing Eastern team members well: give face, save face, give clear direction, build the relationship — not just the role.
• The China-praise anchor in full — why public recognition of one person backfired, and the precise fix.
• How "yes" may mean "I heard you," and how a manager confirms understanding without making anyone lose face.
• The flip side most books skip: being managed by an Eastern boss — what's expected of you, and the moves that earn trust.
• Why loyalty and job-hopping are weighted so differently, and how that should shape what you promise and how you stay.
• A leadership-style spectrum you can place yourself and your counterpart on — so you can adjust the dial instead of guessing.

The empowerment trap

Start with the trap Alan fell into, because it is the single most common way good Western managers fail in the East.

Western leadership culture spent the last half-century moving away from command-and-control toward something flatter and more facilitative. The admired manager today is a coach, a "servant leader," someone who pushes decisions down, asks more than tells, and measures success by how independent the team becomes. "I empower my people." "I don't micromanage." "My door is always open." These are not just techniques; they are moral claims — to a Western ear, a directive boss who tells people exactly what to do sounds controlling, insecure, even a little authoritarian.

Now run that ideal into a steep hierarchy. In a Confucian-influenced workplace (China, Korea, Japan, Vietnam) or many other hierarchical Eastern settings, the relationship between a senior and a junior is not a partnership of equals temporarily arranged by an org chart. It is closer to a relationship of mutual obligation between unequal ranks — and both sides have duties. The junior owes diligence, respect, and loyalty. The senior owes something specific in return: clear direction, decisiveness, and protection of the people below. A good boss, in this frame, is one who knows the way and says so — who takes responsibility, gives unambiguous guidance, and shields the team from blame when things go wrong.

So when the Western manager says "you're the experts, you decide, I trust you to run with it," he believes he is elevating the team. But through the hierarchical operating system, several alarming things have just happened at once. The leader has signaled he may not actually know the direction (incompetence). He has pushed the responsibility — and therefore the risk and the potential blame — downward onto people who, by their rank, should have been protected from it. And he has left a vacuum where guidance should be, forcing juniors into an impossible bind: act without direction and risk overstepping, or freeze and look passive. The "gift" of autonomy can feel like being handed a hot pan and told it's a privilege.

Watch Out. The Western phrases that feel most generous are often the ones that land worst in a steep hierarchy. "What do you think we should do?" can read as the boss has no plan. "I'll leave it to your judgment" can read as the boss is dodging responsibility. "There are no stupid questions / push back any time" can read as a trap — surely the senior person doesn't really want to be contradicted. None of this means you must become an autocrat. It means you cannot assume that hands-off equals respectful. In many Eastern contexts, clarity is the respect. Direction is a gift, not a constraint.

This does not mean Eastern teams are incapable of initiative, or that they secretly crave a tyrant — that would be flattening a huge, varied world into a cartoon. Younger employees in Seoul, Shanghai, or Bangalore, especially in startups and global firms, may want and expect plenty of autonomy. The point is narrower and more useful: you cannot assume that "empowering" reads as "respectful" the way it does at home. Direction, in a hierarchical culture, is not the opposite of respect. It often is the respect — the senior person doing the job their rank obliges them to do.

Managing Eastern team members: the four moves

If you manage people in or from these cultures, four moves will carry you most of the way. None requires you to stop being yourself; each is an adjustment to the interface, in the language of Chapter 1.

Move 1 — Give face: praise in public, generously and correctly

Face — the social standing a person holds in the eyes of others, the master concept of Chapter 3 — is the currency you are constantly paying or withdrawing as a manager, whether you mean to or not. The first move is to give it deliberately.

Giving face means publicly affirming someone's competence, status, and value in front of the people whose opinion matters to them. Praising the team's success in a meeting; crediting a senior person's experience in front of juniors; thanking a host warmly in front of their colleagues; deferring, visibly, to someone's expertise in their domain. These are not empty flattery. In a face culture, public recognition is a real and valued form of compensation — sometimes valued more than money — and a manager who gives it skillfully builds enormous loyalty.

But — and this is the whole anchor story of the chapter — how you give face matters as much as that you give it. Which brings us to the lesson the West gets most reliably wrong.

The praise that backfired in China

Here is our second anchor story in full, because Chapter 17 is its home.

A Western manager — call him David, a composite drawn from a pattern that recurs constantly — takes over a team in China. David is a warm, encouraging leader who believes in catching people doing things right. In his first month, one engineer, Mei, does exceptional work on a difficult problem. So David does what has motivated every team he's ever run: in the next team meeting, in front of everyone, he singles Mei out for lavish praise. "I want everyone to see what great work looks like. Mei absolutely nailed this — she went above and beyond, and the rest of us should be learning from her. Outstanding job, Mei."

Back home, this is rocket fuel. The praised person glows; everyone else is inspired to earn the same recognition; morale rises. David expects exactly that.

Instead, the opposite happens. Mei doesn't glow — she looks down, visibly uncomfortable, and mutters something deflecting. Over the following weeks, the team's performance dips. Mei herself becomes quieter, less collaborative, oddly withdrawn. David is bewildered. He did something nice. He rewarded excellence. Why did it make things worse?

Because David, reading through his own operating system, made three invisible errors at once.

Decode This. Through the Western system, "publicly praising the standout" is pure positive: it rewards the individual and motivates the group. Through the Chinese (and broadly Confucian) system, the same act does three damaging things. First, it broke group harmony — by elevating one person above the collective, David disrupted the wa-like balance of the team and implicitly criticized everyone else ("the rest of us should be learning from her"), making the whole group lose face at once. Second, it cost Mei face with her peers — singled out by the boss, she now risks being seen as a glory-seeker, a teacher's pet, someone who made her colleagues look bad; in a culture where fitting into the group is paramount, being conspicuously elevated is not a reward but an exposure. Third, it put Mei in an impossible social position — accept the praise and look arrogant, or deflect it and seem to contradict the boss. Mei withdrew not because she didn't value David's regard, but because his way of expressing it cost her something with the people she works beside every day. The individual reward, in a collectivist system (Chapter 2), became a collective wound.

So what should David have done? The fix is counterintuitive, precise, and worth memorizing, because it inverts the Western default:

Praise the team in public; praise the individual in private.

In public, David credits the group: "This team did outstanding work on a hard problem — I'm proud of all of you." That gives face to everyone, reinforces harmony, and lets Mei share in collective pride without being dangerously singled out. Then, privately — a quiet word, a one-on-one, a message just to her — David tells Mei specifically and warmly how much her individual contribution meant: "I know how much of this was you. That was exceptional work, and I noticed. Thank you." Now Mei gets the personal recognition she's earned, with none of the social cost, and her standing with her peers is untouched.

Framework — Recognition, inverted. The Western default and the Eastern-savvy move, side by side: ``` WESTERN DEFAULT HIERARCHICAL / FACE-AWARE MOVE Public praise the individual praise the TEAM arena ("great job, Mei!") ("great work, everyone")

Private (often skipped — praise the INDIVIDUAL arena the public praise ("that was you — exceptional, was the reward") thank you")

Result West: star motivated, star motivated, group inspired group inspired Result East: star EXPOSED, star rewarded safely, group's harmony bruised group's harmony intact ``` Flip the arenas. Group glory goes public; individual glory goes private. It feels strange the first time. It works the first time.

One caution, so we don't flatten: this is a strong general pattern across collectivist, face-conscious workplaces, but it is not an iron law, and it is changing. A young salesperson at a competitive Chinese tech firm may genuinely want public recognition; some modern, individualized, KPI-driven workplaces have absorbed Western-style "employee of the month" rituals. Read the specific person and the specific firm. But when in doubt — and especially with anyone senior, modest, or embedded in a tight team — default to: team in public, individual in private. It is the safer error by a wide margin.

Move 2 — Save face: criticize in private, always, and softly

If giving face is the reward, protecting face is the duty — and the place Western managers do the most accidental damage. The rule is blunt and nearly exceptionless across these cultures: never criticize, correct, or contradict someone in front of others.

Public criticism in a face culture is not "tough but fair feedback." It is a small public humiliation, and its costs vastly exceed whatever the feedback was worth. The person criticized loses face; everyone watching recalibrates ("if the boss will do that to her, no one is safe"); and the lesson the team learns is to hide problems, never volunteer bad news, and never admit a mistake early — the exact opposite of what you wanted. The Western manager who "calls it like it is" in the meeting thinks he's building a culture of candor. He's building a culture of concealment.

The fix is to move all correction off the public stage. Criticize privately, one-on-one, with the door closed. And even then, soften — frame it as a shared problem ("how can we make sure this doesn't slip next time?"), as a question rather than a verdict, as guidance from a senior who wants the junior to succeed rather than a scolding. The goal is for the person to receive the correction and keep their dignity, so they fix the issue and stay loyal, rather than fixing the issue and quietly resenting you.

Try This / Script. When you must correct someone from a face-conscious culture, take it private and frame it as protection, not punishment: - (privately) "I wanted to talk one-on-one so this stays just between us. I think there's a problem with the X report — walk me through it, and let's figure out how to fix it together." - (softening a correction) "You did a lot right here. There's one thing I'd adjust — and I might be missing context, so tell me if I am." - (if you slipped and corrected publicly) circle back privately and repair: "I was too blunt in that meeting — that's on me. You're doing good work, and I should have raised that one-on-one." The repair script matters: even seasoned managers misstep under pressure. A private, face-restoring follow-up undoes most of the damage and, oddly, can deepen trust.

Move 3 — Give clear direction (the gift the West forgets)

We have already met the empowerment trap, so this move is its remedy. In a hierarchical culture, direction is a gift. Provide it generously.

Concretely: when you delegate, be specific about what you want, the standard it must meet, and the deadline — don't hand over a vague goal and call it autonomy. When a decision is yours to make, make it, visibly, rather than throwing it back ("what do you think?") in a way that reads as indecision. Set clear priorities so people aren't guessing which fire to fight. And take responsibility when things go wrong rather than distributing blame downward — protecting your people is part of the senior role you've accepted, and it is watched closely.

This is not a license to micromanage every keystroke, and it is not a contradiction of everything good about empowerment. It's a recalibration: in these cultures, clarity and decisiveness are forms of respect, and a leader who provides them earns trust precisely where a hands-off leader loses it. You can still grow people, invite input, and delegate real ownership — but do it through specific, sanctioned invitations ("Wei, you've run this before — you own the vendor decision, here's the budget and the deadline, come to me if you hit a wall"), not through a vague "you all figure it out" that leaves a vacuum.

By Culture. The dial isn't set the same everywhere — adjust it: - Japan — direction matters, but so does process: decisions are often built bottom-up through quiet pre-alignment (nemawashi, Chapter 15) before they surface. Be clear about goals, but don't ram a decision through without letting the groundwork happen. Over-directive and impatient is the worst combination here. - Korea — among the steepest hierarchies; ppalli-ppalli (fast-fast) speed culture plus strong deference means clear, decisive top-down direction is genuinely expected, and ambiguity from a leader is read harshly. Lean clear and decisive. - China — pragmatic and increasingly fast-moving; the boss is expected to lead and decide, but guanxi (relationship) underwrites everything — direction from a trusted leader lands very differently than from a stranger. Build the relationship and give the direction. - India — hierarchical and respectful of the "boss," yet often more comfortable with vigorous verbal exchange than East Asia; expect questions and discussion within a clear hierarchy. Give direction, but be ready to engage, not just decree. - Southeast Asia — varies widely (Chapters 32–33); Thailand and Indonesia tend toward gentle, face-protective hierarchy where a harsh or blunt directive style backfires even though hierarchy is real. Clear and soft. Even here, treat each line as a hypothesis to check against the person in front of you — not a stereotype to apply.

Move 4 — Build the person, not just the role

The last move is the one Western managers most often skip and most need. In relationship-first cultures (the heart of Chapter 14), the bond between a manager and a report is personal, not merely professional. People work hard for a boss they have a real relationship with — one who knows their family situation, asks how their parents are, shares a meal, shows interest in them as a human being — far more than for a boss who is merely fair and competent but distant.

To a Western manager raised on a sharp work/personal boundary, this can feel intrusive or even improper ("I don't pry into my reports' private lives"). But the boundary itself is cultural. In much of the East, a manager who keeps things strictly transactional — efficient, professional, but uninterested in the person — is not admired for respecting boundaries; he is experienced as cold, and he never earns the discretionary loyalty that makes teams go the extra mile. The team dinner, the genuine question about someone's child's exams, the remembered birthday: these are not distractions from the management job. In these cultures, they substantially are the management job.

Culture Bridge. A Dutch manager prides herself on treating work and private life as completely separate — she'd consider asking about an employee's family slightly inappropriate, a boundary violation. Her Indonesian report experiences that same boundary as coldness: a boss who doesn't ask about your family doesn't care about you, and a boss who doesn't care hasn't earned your loyalty. Neither is wrong. The Dutch manager is being respectful (of privacy); the Indonesian report is reading distance (lack of relationship). The bridge: the boundary that protects in one system signals neglect in the other. In relationship-first cultures, the personal interest is the respect — exactly inverted from the Dutch instinct.

"Yes" may mean "I heard you"

A manager's nightmare: you give a clear instruction, your report says "yes," and then it doesn't happen. You were clear. They agreed. What went wrong?

Often, nothing went wrong with their willingness — and everything went wrong with your reading of "yes." As Chapter 16 explored at length, in high-context, hierarchical, face-conscious cultures, a junior person's "yes" to a senior person frequently does not mean I agree and will do this. It can mean I heard you — an acknowledgment of your words and your status, not a commitment to the content. Saying a flat "no," or "I don't understand," or "I think that's wrong" to a superior would itself cause a loss of face — yours and theirs — so the polite, respectful response is an affirmative sound that keeps harmony intact, even when the real answer is no, I'm confused, or I don't think that will work.

This is not lying, and it is not passive-aggression (those are Western frames). It is a different protocol for handling disagreement and confusion upward, one that protects the relationship while it transmits a softer signal you're expected to read. The recurring anchor — pushing for "yes" in Japan after three soft "no"s (Chapter 4) — is the negotiation version; this is its daily-management version.

The managerial fix is not to demand "do you really mean yes?" (which corners people) but to build confirmation into the process in a face-safe way:

Try This / Script. Instead of trusting the "yes," verify understanding without implying anyone failed: - "Just so I know I explained it well — can you walk me back through how you'll approach this?" (Puts the burden of clarity on you, the senior, not on them.) - "What might get in the way of this? What do you need from me to make it happen?" (Invites the real obstacles a flat "yes" was hiding.) - "When do you think is realistic for this — and tell me honestly if the timeline's tight." (Gives explicit permission for a soft "no" on the deadline.) - For anything important, follow up in writing with the specifics, and treat a private channel as where the real answer lives. The principle: don't ask people to contradict you (hard); ask them to describe the plan and name the obstacles (easy, and face-safe). The gaps will tell you what the "yes" really meant.

The flip side: being managed by an Eastern boss

Most guidance stops at managing down. But plenty of Westerners now report to an Eastern boss — a Japanese division head, a Korean or Chinese executive, an Indian manager — whether in an Eastern firm, a multinational, or an acquired company. The same system that shapes how you should manage shapes what's expected of you. Here is the other half of the bridge.

Expect a more directive style — and don't mistake it for distrust. Your boss may tell you what to do more specifically than you're used to, check in more closely, and leave less to your discretion. To a Western employee raised on "empowerment," this can feel like micromanagement or a lack of confidence in you. Usually it isn't. In a hierarchical system, that's simply what a manager does — providing direction is their role, not a verdict on your competence. Reframe it: this is engagement and ownership, not a leash.

Show respect for seniority — visibly. Hierarchy is not just real here; it's meant to be seen. Defer appropriately to those above you, use the proper forms of address and respect (Chapter 6), don't barge past rank, and don't treat your boss as a peer just because you'd do so at home. This isn't servility; it's competence at the social game, and it's noticed.

Never challenge publicly — disagree privately. This is the single highest-value move, and it's the mirror of "save face" from the other side. If you disagree with your Eastern boss, do not do it in the meeting, in front of others — that causes them to lose face and marks you as disrespectful or arrogant, however reasonable your point. Instead, raise it privately, one-on-one, framed with respect: "I had a thought about the plan — could I run it by you when you have a moment?" The same disagreement that would damage you in public can be welcomed in private. Westerners who "speak truth to power" in the room, expecting to be admired for candor, often torch their standing without ever knowing why.

What Would You Do? Your new Chinese manager presents a plan in a team meeting that you're fairly sure has a flaw. Back home, you'd raise it right there — that's what engaged professionals do. Do you (a) point out the flaw in the meeting, politely but clearly; (b) say nothing, ever, to avoid trouble; (c) say nothing in the meeting, then raise it privately afterward with respect; (d) email the whole team your concerns later? Option (a) costs your boss face publicly and can brand you as disrespectful, even if you're right. Option (b) wastes a real insight and helps no one. Option (d) is (a) in writing, often worse because it's on record. Option (c) — the private channel — lets you be both useful and respectful: the flaw gets surfaced, your boss can act on it without public embarrassment, and you've shown you can be trusted with disagreement. In most of these cultures, (c) is not just the polite choice; it's the effective one.

Demonstrate loyalty and commitment. This is where the deepest mismatch lives, and it deserves its own section.

Loyalty, commitment, and the job-hopping gap

In much of the Western professional world — Silicon Valley especially — changing jobs every two or three years is normal, even admired: it signals ambition, market value, and growth. Loyalty to a single employer can read as a lack of options. The implicit deal is transactional and mutual: the company owes you nothing beyond your contract, and you owe it nothing beyond your notice period. "It's just business."

In much of the East, this is not how the relationship between employee and employer is understood — and a Westerner who behaves "normally" by job-hopping can be judged far more harshly than they expect. The older model, strongest in Japan but influential across the region, treats employment as something closer to a long-term, quasi-familial bond of mutual obligation: the company invests in, trains, and protects the employee over years; the employee returns loyalty and long commitment. Within that frame, leaving after eighteen months for a 15% raise doesn't look like savvy career management — it can look like a betrayal, evidence of someone who can't be trusted, who took the investment and ran.

Honesty Box. This model is genuinely shifting, and it's important not to freeze a moving picture. Lifetime employment in Japan has been eroding for decades; younger workers in China, Korea, and India job-hop far more than their parents did; competitive tech sectors across Asia now see Silicon-Valley-style mobility. So the gap is narrowing — but it has not closed, and it is widest exactly where you might be judged: by older managers, in traditional firms, in the more conservative cultures. The safe read is that loyalty is still weighted more heavily than in the West, that visible commitment buys you more here, and that a pattern of short stints will be viewed with more suspicion. You don't have to stay forever. But understand that how you stay, and how you leave, is read more morally than you're used to.

What does this mean practically? If you're being managed in such a setting, demonstrating commitment — staying long enough to deliver, not visibly shopping yourself around, leaving graciously and with ample notice when you do go, preserving the relationship on the way out — pays dividends that a Western "it's just business" exit forfeits. And if you manage people in these cultures, understand the flip side of the same coin: they may expect you to invest in and protect them over the long term, and a purely transactional, "you're only as good as your last quarter" stance will not earn the loyalty the system is built to reward.

Placing yourself on the dial

Pull it together with a single mental tool. Leadership style runs along a spectrum from directive (the leader decides and tells) to facilitative (the leader enables and asks). Cultures cluster differently along it, and so do individuals — so the skill is to locate both yourself and your counterpart and adjust the gap.

  DIRECTIVE  <-------------------------------------------->  FACILITATIVE
  "I decide and tell"                                "I enable and ask"
  clarity = respect                                  autonomy = respect

  Korea ----- Japan* --- China --- India ----------- US/UK/NL
  (steep)    (*group-      (boss      (hier. but      (flat, "empower,"
             consensus      decides,   discussion-     coach, hands-off)
             within         relation-  friendly)
             hierarchy)     ship-based)

  YOU (typical Western manager) are likely near the FACILITATIVE end.
  Adjusting toward clarity and direction is not becoming an autocrat —
  it's closing the gap so your respect is *legible* to the other system.

The asterisk on Japan is the chapter's warning against flattening: Japan is hierarchical and consensus-built — direction matters, but so does the patient, bottom-up groundwork that precedes a decision. The dial is a starting hypothesis, not a verdict. A thirty-year-old at a Shenzhen startup sits far from a sixty-year-old at a traditional Tokyo manufacturer, even though both are "East Asian." Locate the person, not just the country.

Portfolio Prompt. In your Cultural Intelligence Portfolio, open a section titled "My leadership interface." First, locate yourself honestly on the directive–facilitative spectrum above — where does your instinctive style sit? Then, for your chosen culture, write three concrete adjustments you'd make to manage someone from it well: one about giving face (how would you handle recognition?), one about saving face (how would you deliver a correction?), and one about direction (where would you be more specific than your instinct wants to be?). If instead you expect to be managed by someone from this culture, write three things you'd do differently as a report — about deference, about disagreeing privately, and about demonstrating commitment. Keep it specific enough to actually use on a Monday.

Summary: clarity is the respect, privacy is the kindness

Gather the chapter, because it carries one inverted idea you'll use constantly.

Western leadership has drifted toward a flat, "empowering" ideal — and that ideal does not translate cleanly into steep hierarchies. There, the hands-off boss who refuses to direct doesn't look generous; he looks absent, even incompetent, because the senior role obliges clear direction and protection. Clarity is the respect. Direction is a gift, not a constraint.

Managing Eastern team members well comes down to four moves. Give face — praise publicly and skillfully, knowing that in a face culture public recognition is real compensation. Save face — never criticize in public; take all correction private and soft, or you teach your team to hide. Give clear direction — be specific, decisive, and protective, because that's the duty of your rank. Build the person, not just the role — the personal relationship a Western boss might skip is, in much of the East, the management job. And remember that "yes" may mean "I heard you": don't trust surface agreement; build face-safe confirmation into the process.

The chapter's anchor — David's public praise of Mei that backfired in China — distills the whole inverted lesson: an individual reward, dropped into a collectivist, face-conscious system, became a collective wound. The fix flips the Western default: team in public, individual in private.

And the flip side most books forget: if you are managed by an Eastern boss, expect more direction (it's engagement, not distrust), show visible respect for seniority, disagree privately, never publicly, and demonstrate the loyalty and commitment a system that weights job-hopping more harshly is built to reward.

In the next chapter, we take everything about managing across cultures and move it into the medium where most cross-cultural work now actually happens — not the conference room but the inbox, the group chat, and the 6 a.m. video call. Chapter 18 is about communication in international teams: how a blunt email reads to a high-context colleague, why the CC line is a status minefield, who stays silent on video and why, and how to keep a team fair when half of it is always asleep. The principles you just learned — face, direction, the soft "yes" — don't change. The challenge is running them across a screen, an ocean, and twelve time zones.

Turn the page. The team is online — and so are you.