Case Study 1 — The Consultant Who "Already Knew the Subcontinent"
A composite case, assembled from the common experiences of Western professionals who succeed in India and then assume the rest of the region is the same. Names and details are illustrative.
The situation
Ben is a supply-chain consultant from Manchester with three genuinely successful years working with manufacturers in Mumbai and Bangalore. He is good at this. He has learned, the hard way, to budget time for relationships, to read the head-wobble as rapport rather than agreement, to navigate hierarchy, to not mistake an enthusiastic "yes, yes" for a commitment. He is, by any reasonable measure, culturally competent in India — and justifiably proud of it.
His firm now sends him to Pakistan to assess a potential manufacturing partner in Karachi and Lahore. Ben is pleased rather than nervous. I know the subcontinent, he thinks. Pakistan is just India with a different religion — I've basically done this. He packs his India playbook and flies in confident.
The early signs seem to confirm him. His host, Mr. Iqbal, embraces him warmly, sweeps him into a magnificent lunch before any business is mentioned, and asks with real interest about Ben's family and his journey. Exactly like Mumbai, Ben thinks, relaxing fully. And then, midway through the meal, reaching for friendly conversation, he says the sentence that quietly costs him the trip: "You know, it's really all one culture across the border, isn't it? You and India — basically the same place, historically speaking."
He is wrong in a way he won't understand for weeks — and the error is two-layered, which is what makes it instructive.
The 'before': how it felt through Ben's operating system
Run the trip through Ben's software and his confidence is reasonable — up to a point. He has correctly transferred the substrate: he knows hospitality is sacred here, that business is relationship-first, that hierarchy and family matter, that he shouldn't rush to the deal. All of that is right, and it's why the lunch felt familiar. His India competence is real and a lot of it genuinely carries over.
But Ben has made the deeper error the whole chapter is built to prevent. He has assumed that because the substrate transferred, the whole culture transferred — that Pakistan is "India with a different religion," a minor variation on a theme he's mastered. And from inside that assumption, his fatal sentence felt not just safe but warm — a generous acknowledgment of shared heritage, even a way of signaling "I get this region."
Through his own operating system, "you're basically the same as India" is a compliment. He genuinely cannot feel why it would land any other way.
The 'after': what was actually happening
Two things went wrong, at two different depths.
The surface error: he flattened a nation into its neighbor. Pakistan was founded in 1947 as a separate homeland — its entire reason for existing as a country is that it is not India. To tell a Pakistani "you're basically the same place" is to dissolve the founding premise of their nationhood. It is roughly as welcome as telling a proud Irishman that Ireland is "basically just part of Britain, historically." Mr. Iqbal's warmth didn't vanish — subcontinental hospitality is robust, and a guest is still a guest — but something cooled, and the rest of the visit ran a half-degree more formal than it began.
The deeper error: he treated a wound as small talk. "Across the border" and "basically the same place" don't just flatten — they brush against the single most charged subject in the region: Partition, three wars, and the unresolved agony of Kashmir. For many families on both sides, this is not geopolitics; it is displacement, loss, and grief within living memory. Ben, breezing in with a friendly generalization, had no idea he was stepping onto a grave. (Chapters 24, 30.)
Notice the cruel mechanism: Ben's India success is precisely what set up his Pakistan failure. Because so much transferred, he assumed everything did — and his confidence kept him from noticing the cooling, or asking why. The better Ben had gotten at India, the more certain he was that he'd "already done" Pakistan.
The deeper point
This is the chapter's central theme — never flatten (theme #2) — dramatized at civilizational scale. Ben didn't fail from ignorance of the substrate; he had the substrate cold. He failed because he mistook substrate competence for whole-culture competence, and because his Western frame couldn't feel that proximity to a giant breeds an intensified need to assert difference, not a sense of sameness.
And notice the second lesson, about charged history. Ben's instinct — to make warm, informed-sounding conversation about the region — is a Western virtue (engaged, knowledgeable small talk) that becomes a liability the moment it touches third-rail history. In this region, on these subjects, the competent move is not the informed opinion but the humble silence of the listener.
Both systems, in their own contexts, are sensible. Ben's "show you're engaged and informed" works beautifully in low-stakes Western small talk. Mr. Iqbal's sensitivity to "you're basically India" is entirely reasonable given his nation's hard-won, contested identity. The collision happened below the waterline — in Ben's invisible assumption that competence in one subcontinental culture is competence in all of them.
The better approach
Ben doesn't need to throw away his India skills — most of the substrate genuinely transfers, and that's a real asset. He needs to add two disciplines: treat each nation as itself, and stay off the third rails.
- Lead with substrate, learn the exceptions. Use what transfers (relationship-first, sacred hospitality, hierarchy) — and go in expecting Pakistan to be its own country, with its own language story, its own biraderi networks, its own pride. Ask, observe, don't assume.
- Praise the country as itself, never "as India." The fix for the fatal sentence is to admire Pakistani hospitality, Lahori food, Urdu poetry, the warmth of the welcome — on their own terms, with no comparison to the neighbor.
- Never raise Partition, Kashmir, or India relations. If they come up, listen, acknowledge the pain, decline to adjudicate. Curiosity about the country is welcome; opinions about the conflict are not.
- Read cooling, and course-correct. When warmth dips, don't barrel on — register it as data. A simple, humble reset can repair a great deal.
Scripts Ben could use: - (admiring, on its own terms) "I have to say, the welcome here has been extraordinary — and the food in Lahore is something I'll be talking about for years. Tell me what I should make sure not to miss." - (if conflict-history arises) "I know this history runs very deep and touches real families. I won't pretend to understand it from the outside — I'd honestly rather listen." - (a humble reset, if he senses he's misstepped) "Forgive me if I generalized clumsily earlier — I'm here to learn how things really are here, not to assume I already know."
Within a single trip, a Ben who treats Pakistan as Pakistan — leaning on the transferable substrate while honoring every exception — typically finds the same warmth that won him Mumbai, deepened rather than cooled, and a partner who trusts that he sees them, not a smaller copy of their neighbor.
Discussion questions
- Ben's competence in India was real. Explain precisely how that real competence caused his failure in Pakistan. What's the general lesson about transferring skill between adjacent cultures?
- The chapter calls the sentence "you're basically the same as India" an erasure. Make the strongest case you can for why a proud Pakistani (or Irishman, or Nepali) experiences it that way, even when it's meant as a compliment.
- Ben treated charged history as small talk because, in his culture, informed conversation signals engagement. Where else might a "good" Western conversational instinct become a liability abroad?
- Ben never noticed the room cool. What habit would help a traveler register that kind of subtle, high-context signal — and what should they do when they catch it?
- Where is the line between usefully transferring substrate skills across the region and lazily assuming one culture equals another? How would you know which one you're doing?
Portfolio link. In your Cultural Intelligence Portfolio, under "Behaviors I might misread," add this entry: the warmth of subcontinental hospitality is a substrate I can rely on — but it does NOT mean the cultures are interchangeable; I will treat each nation as itself and never praise one "as a version of" its neighbor. Then add a personal trigger-list: three "friendly generalizations" you might be tempted to make about a region you work in, and why each could erase rather than flatter.