Case Study 2 — The Icebreaker That Reopened a Wound (Sri Lanka)

A composite case illustrating how a well-meaning Westerner can mishandle a recent, raw national trauma — and how the same indirect communication that protects the wound also hides a missed deadline. Names and details are illustrative.

The situation

Sarah is a project manager at a European software firm, setting up a development partnership with a vendor in Colombo, Sri Lanka. She is thoughtful and prepares well — she has even read a little about the country's history. On her first visit, she meets the vendor's team over the famous tea, finds everyone gracious and softly spoken, and feels things are going beautifully.

Wanting to show she's done her homework and to "connect on something real," she raises, over lunch, the subject she read most about: the civil war. "I read about everything your country went through with the war," she says, with sincere sympathy, to the mixed Sinhalese-and-Tamil team. "It must have been terrible. What was it actually like for all of you?" She means it as empathy — as treating them like real people rather than just a vendor. The table goes quiet. The two most senior people exchange a brief glance. Someone changes the subject gently, and the warmth, though it doesn't disappear, never quite returns to where it was.

Later that week, a second, quieter problem surfaces. Sarah had asked, at that same lunch, whether a critical first milestone could be ready in three weeks. The team had smiled and said, "Yes, yes, we will try our best, no problem." Three weeks later, it isn't ready — and Sarah is blindsided. They said yes.

Two different mistakes, at two different depths — and both are pure Chapter 31.

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

Run both moments through Sarah's home software and her choices feel not just defensible but kind and competent.

On the war: in Sarah's culture, acknowledging someone's hardship is empathy — it signals you see them as human, you've taken the trouble to learn their story, you're not treating them as a faceless supplier. Raising a difficult shared topic is how Westerners often demonstrate depth and care. So bringing up the war felt, to her, like the opposite of a misstep — like reaching past the small talk to something real.

On the deadline: "yes, we will try our best, no problem" is, in low-context Western English, a commitment. Sarah heard a clear affirmative and reasonably planned around it.

Through her own operating system, Sarah was being empathetic and was given a clear yes. Both readings are fluent — in the wrong language.

The 'after': what was actually happening

The war question reopened a wound and forced an impossible position. The Sri Lankan civil war (1983–2009) is recent, raw history, touching ethnicity, language, religion, and unresolved questions of justice — and it ended in a final phase whose events remain internationally contested and profoundly painful. By raising it to a mixed Sinhalese and Tamil group, Sarah did something even more fraught than a generic faux pas: she invited people from communities that were, in the war, on opposite sides of a national tragedy to discuss it in front of one another and a foreigner. There was no safe answer. Any response risked someone's grief, someone's politics, or the fragile professional peace of a mixed team. Their silence wasn't coldness; it was the only protective move available. (See the chapter's Watch Out on the Sri Lankan war.)

The deadline answer was a face-saving soft "no." "We will try our best, no problem" was not a commitment; in Sri Lanka's high-context, harmony-valuing, Buddhist-inflected communication style, an outright "no, three weeks isn't realistic" to a client would be confrontational and face-threatening. So the real message — that's very tight and probably not achievable — was delivered in the soft, agreeable, non-committal language the culture uses for bad news. Sarah heard the words; she missed the music. (Chapters 4, 30.)

Notice that the same cultural value — protective, face-saving indirectness — drove both events. The instinct that made the team go quiet rather than discuss a painful war is the same instinct that made them say "we'll try" rather than "no." A culture that protects people from uncomfortable directness protects them in both domains.

The deeper point

Sarah's failures weren't about ignorance of Sri Lanka — she'd even done some reading. They were about two invisible Western assumptions: that acknowledging hardship is universally kind, and that words carry their literal meaning. Both are WEIRD defaults masquerading as common sense.

And there's a painful irony in the first one: Sarah's reading caused her mistake. Having learned about the war, she felt she should engage it — that ignoring it would be shallow. But in this context, the knowledgeable move was to hold that knowledge, not deploy it: to let it make her more careful, not more talkative. Cultural intelligence sometimes means knowing a thing precisely so you can choose not to raise it.

The second lesson is the chapter's quieter one: the same indirectness that guards a national wound also guards a missed deadline. A Westerner who learns to hear the soft no in one domain has learned to hear it in the other. "We'll try our best" deserves the same careful second listen as a sudden silence about the war.

Both systems are internally sensible. Sarah's "engage the hard thing, take words at face value" works well in low-context Europe. The Sri Lankan team's "protect everyone from confrontation, including about deadlines and grief" works well in a culture optimized for harmony and face. The collision happened below the waterline.

The better approach

Sarah needs two adjustments: let painful history stay where the locals keep it, and stop trusting surface agreement.

• Don't raise the war — full stop. Connection in Sri Lanka is built through tea, warmth, the country's beauty, food, cricket, the work itself — not through its trauma. If the topic ever arises from them, listen with humility and decline to adjudicate.
• Never treat ethnicity as a topic or a "side." Sarah should let the Sinhalese/Tamil distinction stay entirely out of her mind and mouth, and simply work with individuals.
• Confirm commitments without forcing a confrontation. Instead of accepting "we'll try our best," create a face-safe path to the real answer: ask about specifics, offer an easy out, invite a counter-proposal.
• Re-listen to every soft yes. Treat "we'll try," a smile, and "no problem" as prompts to verify, not as commitments.

Scripts Sarah could use: - (connecting, safely) "Honestly, the tea, the welcome, the city — I'm a bit in love already. Tell me what a first-time visitor like me should absolutely not miss." - (surfacing the real timeline, face-safely) "Three weeks is what I'd love — but you know the work far better than I do. What would a comfortable, realistic date look like? I'd much rather have a date we can both trust than an early one we can't." - (if war/ethnicity arises from them) "I know that's painful history I can't fully understand from outside. I'm honored you'd share it — I'd rather just listen."

A Sarah who connects through warmth rather than wounds, and who reads the soft "no" inside "we'll try our best," typically finds the Colombo team relaxes, trusts her, and — freed from the impossible position she'd put them in — becomes candid with her in the private, indirect ways the culture allows.

Discussion questions

1. Sarah's reading about the war is what tempted her to raise it. When is knowledge best deployed by not using it? Where else might "showing you've done your homework" backfire?
2. The case argues that the same cultural value — protective indirectness — drove both the silence about the war and the soft "no" on the deadline. Trace that single thread through both moments.
3. Why is raising the war to a mixed Sinhalese-Tamil group worse than raising it one-on-one? What does that reveal about reading the composition of a room before choosing a topic?
4. "We will try our best, no problem" misled Sarah. What general habit would protect a manager from over-trusting agreeable, non-committal language across high-context cultures?
5. Think of a painful chapter in your own country's history. How would it feel to have a visiting foreigner raise it, sympathetically, as lunch conversation? Use that to sharpen your own rule for traveling.

Portfolio link. In your Portfolio, add to "My 'obvious' professional virtues": list "acknowledging hardship / engaging the hard topic" as a Western virtue, and beside it note the context where it backfires (recent, contested national trauma — Sri Lanka's war, Partition, and others) and the better move (let the locals decide whether and when; otherwise, hold the knowledge and connect through warmth). Then start a running entry titled "Soft no's I have heard" — phrases like "we'll try our best," "it might be a little difficult," "we'll see" — and beside each, the real meaning and how you confirmed it.