Case Study 1 — The Launch That Was Scheduled Over the Reunion

A composite case, assembled from the common experiences of Western teams coordinating with partners and staff in Greater China. Names and details are illustrative.

The situation

Rachel is a capable program manager at a U.S. consumer-electronics company, running the launch of a new product built with a manufacturing partner in Shenzhen and a small in-house engineering team in Shanghai. The launch date has been set for months: the second week of February. It is aggressive but, on paper, achievable. Rachel has built a detailed plan, with a tight cluster of final integration calls, sign-offs, and a go/no-go review packed into the final ten days before launch.

In mid-January, as she locks the final calendar, the responses start coming back oddly. Her Shanghai lead, normally instant and accommodating, goes quiet on the integration-call invites, then writes: "Rachel, these dates are during Spring Festival — most of the team will be travelling and offline." The Shenzhen partner is blunter: "Factory closed for New Year. Nothing can ship or be tested that week." Rachel, under real pressure from her own VP, replies the way a diligent Western PM would: she acknowledges the holiday, expresses sympathy — and then asks whether, given how critical the launch is, they could arrange for "just a few key people" to be available for the most essential calls and sign-offs. She offers to keep it minimal. She offers premium overtime. She frames it as a one-time ask for an exceptional moment.

The replies grow polite, brief, and immovable. "We will see what is possible." And then: near-silence. The warm, responsive partners of the last six months have, from Rachel's side of the screen, gone cold.

She is misreading the most important week of their year — and her well-meant flexibility is quietly damaging relationships she will need long after this launch.

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

Run the events through Rachel's home-culture software and her behavior is not just reasonable — it's responsible. In her world, a holiday is real and deserves respect, but it is also, ultimately, individual time off — something a committed professional might choose to flex for a genuinely critical, once-in-a-while business need, especially if asked nicely, kept minimal, and compensated well. She has flexed her own holidays for big launches; she's asking nothing she wouldn't do herself. "Just a few key people for the essential calls" feels to her like a modest, fair request. The overtime offer feels generous. Acknowledging the holiday first feels considerate.

So when the response is firm refusal sliding into silence, Rachel reads it through the only lens she has: the team is being rigid, maybe a little unmotivated, possibly using the holiday as cover to avoid a hard crunch. She starts to wonder, privately, whether this partner is really committed to the relationship — whether they'll "show up when it counts."

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

The 'after': what was actually happening

Rachel's partners were not rigid, unmotivated, or evasive. They were doing what their culture regards as non-negotiable, and her "modest ask" was, to them, something close to outrageous — though far too polite to say so.

• Spring Festival is not "time off." It is the one annual family reunion. This is the week the scattered family physically reassembles — the chunyun migration, hundreds of millions of people crossing the country to be home. For her Shanghai engineers, being available for "essential calls" doesn't mean a quiet hour at a laptop; it means being pulled away from their parents, from the reunion dinner, from the most sacred family span of the year — possibly while travelling, possibly in another city. (Chapters 9, 25.)
• The ask put them in an impossible bind — and cost her nothing she could see. To refuse Rachel outright would risk the relationship and their face; to comply would mean failing their families. By asking at all, Rachel forced a no-win choice onto the very people trying hardest to serve her. The "polite, brief, immovable" replies and the retreat into silence were the sound of people managing an impossible request without an open confrontation. (Chapters 3, 4.)
• The factory closure was literal, not a negotiating posture. The overtime offer misread the situation entirely: it's not that the price was too low, it's that there is no price — the workforce has gone home across the whole country. Money cannot reassemble them. (Chapter 25.)
• Her "considerate" framing didn't soften the ask — it sharpened it. Acknowledging the holiday and then asking them to work through it read, to them, as: she knows exactly how sacred this is, and she's asking anyway. The acknowledgment made the request feel more pointed, not less.

Rachel had been grading immovable cultural duty as poor commitment — using the wrong rubric, and never noticing she held a rubric at all.

The deeper point

This is Chapter 25 in a single story, and it turns on the chapter's central idea: on its biggest festival, a culture shows you what it values most — and that value will not bend to your calendar. Rachel's failure had nothing to do with ignorance of Chinese facts; she could have told you Spring Festival existed and roughly when. It had to do with the weight she assigned it. Through her operating system, a holiday is an individual option that a committed person can flex. Through theirs, the great festival is a family obligation — the one annual reunion, freighted with filial duty and face — that a decent person does not betray for a product launch. Because that difference in weight was invisible to her, she couldn't switch off her own assumption, and so she misread loyal partners as uncommitted ones.

Notice, too, the asymmetry the chapter flagged. Rachel thought she was making a small, reasonable, well-cushioned request. From the other side it was neither small nor reasonable — and the cost landed not on her launch (which was always going to slip) but on six months of carefully built trust. Respecting a boundary that might have had some give would have cost her almost nothing. Pushing on one that didn't cost her the relationship's warmth — the very thing that, in a relationship-first culture, is the real foundation of the deal.

The better approach

Rachel doesn't need to abandon her launch or her standards. She needs to recognize the festival's true weight before she builds the plan, treat the dates as immovable as the laws of physics, and manage the consequences in the two directions she actually controls: her own side, and upward. Concretely:

• Build the calendar around the festival from day one. Spring Festival dates are known months ahead (Appendix C). A culturally intelligent plan never schedules a crunch into that window in the first place; it front-loads the critical work before the holiday or sets the milestone clearly after it.
• Manage upward to reset the VP's expectations. The honest message to her own leadership is not "the team won't cooperate" but "this date is as fixed as our own Christmas; here's the realistic plan that respects it." Protecting the team's holiday is part of her job, not a concession against it.
• Absorb what she can, and prepare a clean handoff. Whatever can be advanced from her own side, she advances; everything else is teed up, documented, and ready for the team's first day back — so the holiday costs the project as little as possible without costing anyone their reunion.
• Reset her read of the silence from "uncommitted / evasive" to "honoring something sacred, and too polite to tell me how out-of-bounds my ask was."

Scripts she could use: - (to the Shanghai lead, withdrawing the ask) "I've just realized our dates land right in Spring Festival — that's sacred family time and I shouldn't have asked anyone to work through it. Please ignore those invites entirely and enjoy the reunion. I'll have everything ready for your first day back." - (to the Shenzhen partner) "Understood completely — the factory should be closed and your people should be home. Let's set the realistic post-holiday timeline together. No need to be reachable during the break." - (to her own VP, managing upward) "Spring Festival is the equivalent of asking our whole team to skip Christmas with their families — it's immovable, and pushing on it would damage a partner relationship worth far more than this date. Here's the plan that respects it and still gets us there."*

Within one project cycle, PMs in Rachel's position who lead with respect for the festival — rather than negotiating against it — typically find the opposite of what she feared: a partner who, precisely because their sacred time was protected without a fight, goes to the wall for them the other fifty weeks of the year.

Discussion questions

1. Identify the exact moment Rachel's own culture became invisible to her. What belief about "holidays" did she mistake for a universal fact?
2. Rachel thought acknowledging the holiday before asking made her request more considerate. Explain why, in this system, it may have made the ask land harder.
3. The chapter stresses an asymmetry: respecting a possibly-flexible boundary is cheap; trampling a firm one is expensive. Where else in your own work do you face that asymmetry — and do you currently default the safe way?
4. Rachel could control two things: her own side and her VP's expectations. Why is "managing upward" a core cross-cultural skill here, not a way of dodging the problem?
5. Could a Western PM over-correct — becoming so deferential to every holiday that nothing ships? Where's the line between respecting a sacred span and abandoning legitimate business needs?

Portfolio link. In your Cultural Intelligence Portfolio, add to your running list "Behaviors I might misread": a firm refusal to work during a major festival is duty and family obligation, not low commitment — and a polite "we'll see what's possible" sliding into silence may be someone managing an out-of-bounds request without confronting me. Then add a forward-looking note to your "Festival Calendar I Live By" section: for each partner or team, mark their biggest festival as a no-scheduling zone and set the reminder months ahead. The cheapest way to avoid Rachel's mistake is to never build the plan over the reunion in the first place.