Case Study 1 — The Proposal That Wouldn't Stay on the Slide

A composite case, assembled from the common experiences of Western consultants and executives pitching to East Asian decision-makers. Names and details are illustrative.

The situation

Daniel is a strategy consultant, very good at what he does. He has flown to Seoul to present a market-entry recommendation to the executive committee of a large Korean manufacturer — a potential client his firm has courted for a year. He has prepared the way he always does, and the way that has won him deals across the U.S. and Europe: a tight, decision-ready deck. Slide one frames the question. Slides two through five lay out three options, scored against clear criteria. Slide six is the recommendation, in bold. Slide seven is the ask: approve Option B today, and we begin Monday. It is, by Western standards, an excellent piece of work — logical, focal, efficient, built to drive a clean decision.

The meeting does not go to plan. Daniel gets through slide one and his recommendation slide is never really reached on its own terms. The senior executive — a composed man in his late fifties whom everyone defers to — keeps pulling the conversation outward and backward. How long has Daniel's firm worked in Korea? What does Daniel understand about their company's history, its founding family, its obligations to its suppliers and its workforce? How does this fit a ten-year horizon, not a three-year one? Who else in the industry is moving, and what are the relationships among them? Every time Daniel tries to walk back to his option matrix, the conversation drifts again into context, history, the wider field.

Two hours later Daniel leaves with no decision and a sinking feeling. He writes in his notes: They wouldn't engage with the actual proposal. Lots of philosophizing about history and "the long view," no interest in the options. Either they're not serious, or they can't make a decision.

He has just badly misread the most engaged people in the room.

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

Run the meeting through Daniel's analytic, linear, time-is-money software and his frustration is reasonable. In his world, a good decision is made by isolating the central question, laying out the options, weighing them against criteria, and choosing — fast, on the merits. The recommendation slide is the heart of the meeting; everything else is preamble. So when the executive keeps circling into company history, supplier obligations, and a ten-year picture, Daniel reads it exactly as it would read if a Western committee did it: avoidance, inability to focus, a group that won't grapple with the actual choice in front of them. "The history isn't relevant," his instinct says. "Let's focus on the options."

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

The 'after': what was actually happening

The executive committee was not avoiding Daniel's decision. By their own coherent rules, they were assembling the only thing that makes a decision possible — the field around it.

• The holistic mind can't evaluate the object until it sees the field. To a thinking style that attends first to context and relationships, a recommendation floating free of its surrounding web is literally not yet evaluable. The executive wasn't dodging Option B; he was building the context within which Option B could be judged at all — the market's relationships, the company's history and obligations, the long arc. Daniel's "preamble" was the analysis (the chapter's holistic-cognition section).
• They were pricing a decade, not a deal. A high long-term-orientation culture doesn't weigh this transaction in isolation; it weighs a relationship that might run for many years. The questions about Daniel's firm's history and commitment to Korea weren't idle — they were the executive evaluating a partner, not just a proposal (the long-term-orientation section; and Chapter 14).
• "It depends" was hovering over the whole room. To this committee, whether Option B was "right" genuinely depended on conditions Daniel's clean matrix had abstracted away — supplier relationships, the moves of other players, the political and market field. Their circling was them tracking exactly those contingencies. It wasn't fog; it was a wider-angle accuracy.
• Slow to decide is not unable to decide. They were building the shared understanding from which a fast, unanimous execution would later follow — not failing to choose, but choosing in a different order than Daniel's culture does (the "slow to decide, fast to act" point; and Chapter 15's nemawashi).

The committee's "philosophizing" was, in their system, the responsible and sophisticated way to approach a consequential choice. Daniel had been grading expert behavior as failure — because he was using a rubric built for an analytic, single-quarter, object-first mind, and never noticed he was holding a rubric at all.

The deeper point

This is Chapter 5 in one room. Daniel's failure had nothing to do with ignorance of Korea; he could have recited facts about Korean business all day. It went one level deeper — to the invisibility of his own cognitive and temporal defaults. He experienced "a good decision isolates the question and chooses fast" not as a cultural habit of mind but as plain clear thinking, the way any competent person decides. Because that default was invisible to him, he couldn't switch registers, and so he misread a committee that was doing careful, field-first, long-horizon analysis as one that "couldn't focus."

And notice the second theme, quietly present: even the direction of the misread is specific. This wasn't generic "Asian indirectness." It was a particular configuration — holistic field-first cognition plus a decade-length time horizon plus the relational evaluation of a long-term partner — that an analytic, quarterly, object-first mind is almost designed to misperceive. The fix is not "be vaguer in Asia." It is to recognize the other configuration and feed it what it actually needs.

The better approach

Daniel doesn't need to abandon rigor — his analytic clarity is a real asset, and a holistic committee will ultimately want the crisp recommendation too. He needs to make his own defaults visible so he can re-sequence the meeting to the way a holistic, long-view mind builds a decision. Concretely:

• Lead with the field, land on the recommendation. Flip the deck. Open with the wide-angle: the market's relationships, their company's history and obligations, the ten-year arc, where the industry's players stand — then arrive at the options and the recommendation as the natural convergence of all that context. Same content, holistic order.
• Make the long horizon explicit and sincere. Speak to the decade, not the quarter; signal your firm's commitment to Korea and to them as a long-term partner, because that's a large part of what they're actually evaluating.
• Treat their context questions as the real meeting, not interruptions to it. Follow them outward willingly. The more completely you help them assemble the field, the faster and more durable the eventual "yes."
• Replace "the history isn't relevant" with curiosity about the history. To this room, the history is among the most relevant things; dismissing it reads as both crude and a little insulting.

Scripts Daniel could use: - (opening, instead of slide one) "Before I get to our recommendation, I'd like to make sure I understand your company's situation and the wider picture as you see it — because the right answer really does depend on that. May I start there, and ask a few questions?" - (when they circle into history/the long view) "That's exactly the context I want to get right. Tell me more — how should a ten-year view, and your obligations to your suppliers, shape this?" - (arriving at the recommendation) "Given all of that — the long horizon, the relationships, where the other players sit — here's where we think it points, and why. But I'd genuinely value where your read differs."

Within a meeting or two of changing the sequence rather than the substance, consultants in Daniel's position typically find the same committee perfectly capable of a clear, committed, fast-executing decision — once they've been allowed to build the field first.

Discussion questions

1. Identify the exact moment Daniel's own cognitive style became invisible to him. What habit of mind did he mistake for "clear thinking"?
2. The chapter says the committee's circling was the analysis. Make the strongest case you can for field-first, context-before-recommendation as superior decision-making for a consequential, interdependent choice.
3. Daniel re-sequenced the meeting rather than diluting his rigor. Where in your own work could you get a better result by changing the order in which you present, rather than the content?
4. Where is the line between adapting to a holistic, long-view counterpart and losing the analytic discipline that is genuinely valuable? Could Daniel over-correct into pure context with no recommendation?
5. Two clocks were in the room: Daniel's quarter and the committee's decade. Whose responsibility is it to bridge that gap — the consultant's, the client's, or both? Does your answer change with who needs the deal more?

Portfolio link. In your Cultural Intelligence Portfolio, add to your "Behaviors I might misread" list: a counterpart circling into context, history, and the long view before engaging my recommendation is likely doing the analysis, not avoiding it — feed the field first. Then add one line under "Cognition & Time": for my chosen culture, the order is __ before ____ (e.g., field before object; relationship before transaction; decade before quarter). You'll reuse that ordering every time you prepare to present.