Case Study 1 — The Deadline That Was Always "Yes"
A composite case, assembled from the common experiences of Western managers running engineering teams in India. Names and details are illustrative.
The situation
Greg runs product for a mid-sized U.S. software company. Two years ago the firm opened an engineering center in Bengaluru that has quietly become its largest, staffed by sharp, English-fluent engineers and led by Anika, a calm, well-regarded senior engineer Greg likes enormously. Greg has a marquee client demo locked for a Friday three weeks out — it's on the CEO's calendar — and a feature that has to be ready for it. On the kickoff call, Greg lays out the timeline and asks the question he always asks: "Can the team have this ready for the Friday demo?"
Anika tilts her head in that smooth side-to-side motion Greg has gotten used to, smiles, and says, "Yes, yes — we'll do our best. No problem from our side." A couple of the other engineers nod along warmly. Greg writes "BLR confirmed — Fri" in his notes, tells the CEO it's handled, and moves on, pleased. This is exactly why he likes working with this team: no drama, no excuses, just yes.
Three weeks later, on the Wednesday before the demo, Greg asks for a build to test. There's a slightly-too-long pause on the call. Then: "It's almost there, just some final integration." Thursday: "We are working on it, a few issues came up." Friday morning, hours before the CEO is to stand in front of the client: it is not ready, and it is not close. Greg is blindsided, embarrassed in front of his CEO, and — underneath the panic — genuinely hurt. They told me yes. Three times. Why would they lie to me?
They didn't lie to him. Not once.
The 'before': how it felt through Greg's operating system
Run the events through Greg's home-culture software and his anger is reasonable. In Greg's world, "yes, no problem" is a commitment — a discrete, reliable data point that means "I have assessed this and I am telling you it will be done." If there were a problem, a competent professional would say so, plainly and early, because flagging risk is part of the job and "managing up" means delivering bad news fast so the boss can plan. Silence or softness about a slipping deadline reads, to Greg, as either incompetence (they didn't see it coming) or evasion (they saw it and hid it). And a "yes" that turns into a "no" three weeks later feels like the one unforgivable thing: being misled.
Every word of that interpretation is fluent — in the wrong language.
The 'after': what was actually happening
Anika and her team were operating, in flawless English, by a completely different and internally coherent set of rules:
- "Yes" preserved the relationship. To Anika, a respected senior leader had asked for something important, on the CEO's calendar. Responding to that with a flat "no, Friday isn't realistic" on a group call would have felt disrespectful and face-threatening — to Greg, to herself, and to the team. "Yes, we'll do our best" was the relationship-correct response: it honored Greg, kept the group's harmony, and committed the team to genuinely trying. (Chapters 3, 28; the soft "yes" of this chapter.)
- The head-wobble was rapport, not a contract. Greg had learned to read Anika's wobble as "yes." It wasn't a content answer at all — it was I hear you, I'm with you, we're in this together (anchor story #3). He'd been treating a relationship signal as a delivery guarantee.
- Bad news doesn't travel upward easily. As the integration problems mounted, the steep-but-warm hierarchy made it hard for the team to march bad news up to Greg unprompted. The hope — sincere, not cynical — was that jugaad would save it: that the team could improvise a fix in time and the difficult conversation would never be needed. "It's almost there" wasn't evasion; it was optimism plus a reluctance to deliver disappointment to a senior before it was absolutely unavoidable.
- Greg never made "no" safe. At no point did Greg ask in a way that gave the team permission and cover to say "Friday is tight." His yes/no question begged a face-saving "yes," and his pleased reaction to it confirmed that "yes" was the answer he wanted. The system did exactly what he'd set it up to do.
The team's "yes" was, in their system, a display of respect, commitment, and goodwill. Greg had been grading sincere relationship-maintenance as dishonesty — using the wrong rubric, and never noticing he was holding one.
The deeper point
This is the chapter's most expensive lesson in a single story. Greg's failure had nothing to do with ignorance of India's history or religions — he could read a guidebook all day. It had to do with the shared language masking an unshared communication style. Because the whole exchange happened in fluent, idiomatic English, Greg assumed the meaning was Western too — that "yes" carried the same low-context, literal, commitment-grade payload it carries in California. It didn't. The words were transparent; the context underneath them — hierarchy, face, relationship-first communication, the difficulty of bad news flowing up — was high-context and invisible to him.
Notice, too, that both systems are internally sensible. Greg's "say it straight, flag risk early" norm genuinely works in his home office, where it surfaces problems fast. Anika's "honor the senior, try hard, don't deliver disappointment prematurely" norm genuinely works in her context, where it preserves the relationships and harmony the team runs on. Neither is the "real" way professionals communicate. They're two operating systems optimized for different things — and the collision happened below the waterline, in the gap between a Western "yes" and an Indian one.
The better approach
Greg doesn't need to demand that his Indian team start blurting bad news like Californians, and he doesn't need to stop trusting them. He needs to recognize he's running a system and change the interface so the real answer can reach him without anyone losing face. Concretely:
- Never ask the yes/no question. Replace "Can you have it by Friday?" with "Walk me through what has to happen for Friday, and where the real risk is." A how/what question makes the truth easy and face-safe to deliver.
- Make "no" explicitly safe, repeatedly. Tell the team, in plain words and more than once, that a realistic "this is tight" is more valuable to him than an optimistic "yes" — and that he will never hold an honest risk against anyone.
- Build a private, recurring risk channel. Bad news struggles to travel up the group hierarchy, so create a low-stakes one-on-one with Anika — "between us, what's the honest status, and what would help?" — where she can be candid without performing it in front of the team.
- Confirm by playback, not assent. Ask the team to re-state the plan and the date in their own words, and to name the top risk themselves. A commitment they construct is real; a "yes" they hand back to please him may not be.
- Read the wobble as rapport, get content elsewhere. Enjoy the warmth of the head-wobble for what it is — connection — and never again mistake it for a delivery guarantee.
Scripts Greg could use: - (reframing the ask) "I don't need a 'yes' today — I need the real picture. Walk me through what Friday requires and what could get in the way." - (making no safe) "Genuinely: 'this is tight, we might need to Monday' is the most useful thing you can tell me. I'll plan around it and I'll thank you for it. A 'yes' that slips costs us both far more." - (private channel) "Anika, just between us — forget the group call. What's your honest read on this date, and what do you need from me to hit it?"
Within a release or two of changing the interface rather than the people, managers in Greg's position typically discover their team had a precise, sober read on the timeline all along — and was simply waiting for a way to share it that didn't require anyone to refuse a respected leader to his face.
Discussion questions
- Identify the exact moment Greg's own communication style became invisible to him. What did he assume "yes" meant, and why did the fluent English make that assumption so easy?
- The chapter says a soft "yes" is "not lying." Make the strongest case you can that Anika's "yes, we'll do our best" was the honest and respectful response within her system.
- Greg changed his interface, not his team. Where in your own work do you ask yes/no questions that beg a face-saving answer — and how could you convert them to how/what questions?
- Could Greg over-correct — pressuring the team so hard for "honesty" that he damages the relationship the team runs on? Where's the line between making "no" safe and interrogating people?
- Whose responsibility was the missed deadline — Greg's, Anika's, or the system's? Does your answer change depending on who held more power in the relationship?
Portfolio link. In your India section, add an entry to your "Behaviors I might misread" list: a fluent "yes / no problem / we'll try" — especially to a senior — is not a reliable commitment; surface the real answer with how/what questions and playback. Then rewrite one yes/no question you actually ask an Indian colleague into a face-safe version, and note it as the single most useful India habit you'll build this month.