Case Study 1 — The Deal That Was Scheduled Into Ramadan

A composite case, assembled from the common experiences of Western executives doing business in Muslim-majority Asia and the Gulf. Names and details are illustrative.

The situation

Greg runs business development for a mid-sized industrial-equipment firm, and he has spent four months courting a major distributor in Jakarta. The relationship is warm, the numbers work, and both sides want to close. Greg's calendar is brutal, so when his counterpart's office offered a window in the third week of March, Greg's assistant grabbed it without a second thought, booked the flights, and blocked three days of intensive meetings plus a "big closing dinner" on the second night at the best steakhouse in town. Greg flies in confident. This is the easy part, he thinks: the hard work of relationship-building is done; now they just sit down and get it across the line.

The trip goes quietly, strangely wrong. The meetings feel sluggish, especially after midday — his counterparts are courteous but visibly low-energy, and decisions that should take an hour seem to drift. When Greg suggests grabbing lunch on the first day to "keep the momentum going," there's an odd pause and a vague deferral. The closing dinner he'd built the whole trip around gets gently moved, twice, to a later and later hour, and when he proposes the steakhouse, his host smiles and counters with "a place my family loves" instead. Greg leaves with a soft, non-committal "we'll be in touch very soon" and no signed deal. Back home, he tells his boss the distributor "seems to have cooled off" and "wasn't as ready as we thought."

He is wrong, and the entire problem is sitting in plain sight on a calendar he never thought to check.

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

Run the trip through Greg's home-culture software and his read is reasonable. In his world, business runs on a roughly fixed daily rhythm — coffee, morning meetings, a working lunch, afternoon push, a deal dinner with drinks to seal the bond. A counterpart who's low-energy in the afternoon is tired or losing interest. One who dodges lunch is being evasive. One who keeps pushing the celebratory dinner later and steers away from the great steakhouse is cooling off, or playing some negotiating game. And a non-committal goodbye means the deal's slipping. Greg isn't being dim; he's reading every signal fluently — in the wrong language, against a daily rhythm he assumed was universal.

What Greg never registered is that the third week of March that year fell squarely inside Ramadan, the Islamic holy month of dawn-to-sunset fasting — and his counterparts, like most people in the world's largest Muslim-majority nation, were fasting from food and water through every one of those sluggish afternoons.

The 'after': what was actually happening

Almost every "warning sign" Greg logged was actually a sign of people doing their absolute best to host him well under conditions he didn't know existed:

  • The afternoon slump wasn't waning interest. By mid-afternoon his counterparts had gone without food or water since before dawn. The dip in energy was physiological and completely normal for the season — and they pushed through it to keep meeting with him at all. (Chapter 11.)
  • The dodged lunch wasn't evasion. They were fasting; they couldn't eat, and hosting a guest at a midday meal they themselves couldn't touch would have been awkward for everyone. The vague deferral was politeness protecting Greg from an uncomfortable scene — high-context communication doing its job (Chapter 4).
  • The drifting dinner wasn't a game. During Ramadan the real meal — and the real social life — happens after sunset, at iftar, the fast-breaking meal. Moving dinner later and later was an attempt to align with the only time they could actually eat and celebrate properly. The host was trying to give Greg a better evening, not stall him.
  • The steakhouse swap was a quiet rescue. A Western steakhouse means alcohol at the bar, pork on the menu, and non-halal meat — a poor fit for an iftar with a fasting Muslim family. "A place my family loves" was the host steering, graciously and without making Greg feel his mistake, toward somewhere the meal would actually work. (Chapters 9 and 21.)
  • The soft goodbye wasn't cooling. It was the normal indirectness of a relationship-first culture (Chapter 14), made softer still because closing a major deal in the depleted final days of Ramadan, rather than over a proper celebratory iftar once everyone could focus, simply wasn't the right moment.

The distributor hadn't cooled at all. They had bent over backwards to accommodate a guest who'd scheduled the most demanding week of his year into the one month they fast — and Greg, unable to see the architecture, had graded their gracious hosting as a loss of interest.

The deeper point

This is Chapter 11 in a single trip. Greg's failure had nothing to do with ignorance of Islam as theology; he could have passed a quiz on the Five Pillars. It had to do with the invisibility of religion as the architecture of the working day. Greg experienced "business runs on this daily rhythm" not as a cultural fact but as a plain operational fact, true everywhere — so it never occurred to him that a religious calendar he didn't share was, that very week, reshaping the energy, the meals, the timing, and the mood of every person across the table. The error wasn't disrespect. It was a wall he couldn't see, and so walked straight into.

Notice, too, that nobody behaved irrationally. Greg's instinct to build momentum and seal a deal over dinner is sound — at home. His hosts' fasting, their late iftar, their gentle redirections were equally sound — for the season they were in. Two coherent systems met on a calendar, and because only one party knew both calendars were in play, the meeting quietly failed below the waterline.

The better approach

Greg doesn't need to become Muslim, or to walk on eggshells. He needs to see the architecture and plan around it — which, done right, would have turned the whole trip into a relationship-deepening win. Concretely:

  • Check the religious calendar before booking anything. A thirty-second check (Appendix C) would have flagged Ramadan and let Greg either move the trip or plan for it deliberately. This is now a standing item on his travel checklist.
  • If you must travel during Ramadan, flip the schedule. Put substantive sessions in the morning, when energy is highest; keep afternoons light; and make the centerpiece an iftar dinner after sunset — which, far from a problem, is one of the warmest, most relationship-rich settings in the entire culture.
  • Don't eat or drink in front of fasting hosts, and never schedule a daytime "working lunch." Eat privately if you must, briefly and without fuss.
  • Let the host pick the venue, and accept the steer. When a host gently redirects you away from your steakhouse, follow — they're protecting the evening, and you.
  • Open with a seasonal grace note, which signals you see and respect the architecture before a word of business.

Scripts Greg could have used: - (before booking) "Before we lock the dates — I want to make sure we're not landing in Ramadan or right on Eid. Would another week be easier on your team?" - (if traveling during Ramadan anyway) "I know it's Ramadan, so let's do the heavy lifting in the mornings and keep the afternoons light. And I'd be honored to join you for iftar — you choose the place." - (on arrival) "Ramadan Mubarak. Thank you for making time during such an important month — it means a lot, and I'll try to make this as easy on everyone as I can."

Handled this way, the very thing that sank Greg's trip becomes its strongest moment: sharing an iftar with a counterpart's family, after a respectful and well-timed day, builds exactly the trust on which the deal depends. Executives who learn to read the calendar don't just avoid the landmine — they discover the holy season is one of the best relationship-building opportunities they'll ever get.

Discussion questions

  1. Identify the precise assumption that made the religious calendar invisible to Greg. What "operational fact" did he mistake for a universal?
  2. Every signal Greg read as a warning was actually a sign of good hosting under hard conditions. Pick two and explain how the same behavior means opposite things in the two systems.
  3. Greg's hosts never told him directly, "You scheduled this into Ramadan, and that's a problem." Why not — and what does their indirectness (Chapter 4) reveal about face and hospitality?
  4. The chapter argues the holy month is a relationship opportunity, not just a hazard. How could Greg have turned Ramadan into the best part of the trip?
  5. Where in your own work do you assume a "neutral" operational rhythm — meeting times, meal customs, the work week itself — that is actually a cultural or religious artifact someone else may not share?

Portfolio link. In your Cultural Intelligence Portfolio, add to your "The Architecture" section a dated, country-specific note of the major religious observances that move each year (Ramadan and Eid shift roughly eleven days earlier annually; lunar festivals move too). Beside each, write one line on how it changes the working rhythm and one line on how you'd turn it into a relationship opportunity rather than an obstacle. Greg's whole mistake was a calendar he never opened — make sure yours is always open.