Case Study 2 — The Clock That Wouldn't Behave

A composite case illustrating how the time axis of this chapter — monochronic vs. polychronic, and the long view — plays out differently across two cultures. Names and details are illustrative.

The situation

Sarah is a sharp, well-organized project lead at a European engineering firm. She prides herself on running things "on rails": agendas circulated in advance, meetings that start and end on time, deadlines that mean what they say. This is not pettiness to her — it's respect. Wasting someone's time, in her world, is a small theft, and a missed deadline is a broken promise.

She now runs a build-out with two key partners. One is a family-owned firm in Dubai; the other is a vendor in Mumbai. In her first month she experiences the same shock twice, in two flavors. Her 10:00 meeting in Dubai begins at 10:35, after a long, warm session of coffee, dates, and questions about her family and her flight — and is then interrupted three times by phone calls and by two cousins who wander in on unrelated business. Her Mumbai vendor cheerfully agrees to "Friday" deadlines that arrive, gently, the following Tuesday, with no apparent alarm. Her head office is now asking, pointedly, for "firm dates and firm progress."

Sarah writes the email she's been resisting: Partners are lovely people but the time discipline is a real risk. Meetings don't start on time, the Dubai sessions are chaos, and Mumbai treats deadlines as suggestions. Recommend we tighten the schedule hard and enforce it.

She is about to "fix" something that isn't broken — and in the process, damage the very relationships the project runs on.

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

Run all of this through Sarah's monochronic, linear, time-is-a-resource software and her alarm is reasonable. In her world, time is a single line of separate slots; you do one thing at a time; the schedule is a commitment, and lateness is a small disrespect. A meeting that starts 35 minutes late, takes three phone calls, and admits wandering cousins isn't a meeting — it's chaos. A "Friday" that means "Tuesday" isn't flexibility — it's a broken word. So she reads exactly what these behaviors would mean if a German or British partner did them: disorganization, unreliability, a worrying lack of respect for her time and her plan.

Every word of that interpretation is fluent — in the wrong temporal language. And note: it also flattens two genuinely different cultures into one "they."

The 'after': what was actually happening

Sarah's partners weren't disorganized or disrespectful. They were running coherent — and different — relationships with the clock.

In Dubai (polychronic time). The late start and the coffee-and-dates were not a delay before the meeting; to her host, they were the meeting's necessary beginning — the relationship being honored before any business could properly sit on top of it (the polychronic-time section; and Chapters 14, 21). The phone calls and the wandering cousins weren't rudeness, either: in a polychronic system the human being in front of you outranks the schedule, so taking a relative's call mid-meeting is honoring a relationship, not insulting Sarah — and the same flexibility would be extended to her without a second thought. The schedule serves the relationships; the relationships do not serve the schedule. What looked to Sarah like chaos was a clear, consistent priority order she simply didn't share.

In Mumbai (elastic time, holistic field). The cheerful "Friday" that arrived Tuesday was not a lie. In a more elastic temporal culture, a date is often a sincere intention and a gesture of optimism and goodwill, not a hard contractual line — and the field of real-world contingencies (the things a holistic mind is always tracking) is understood by everyone to bend it. The vendor's calm when Friday slipped wasn't indifference; it was the shared assumption that dates flex with circumstances, and that the relationship — not the calendar — is what guarantees the work gets done.

The "time indiscipline" Sarah saw was, in each system, a coherent and even relationship-protecting way of being. She'd been grading two different clocks as a single broken one — using a monochronic rubric, and never noticing she was holding a rubric at all.

The deeper point

This is the time half of Chapter 5, dramatized. Sarah's failure had little to do with ignorance of the Gulf or India; it went deeper, to the invisibility of her own temporal default. She experienced "the schedule is a commitment and lateness is rude" not as one culture's relationship with time but as plain professionalism, the way responsible people everywhere treat a clock. Because that default was invisible, she couldn't switch registers, and she misread two sets of partners who were behaving, by their own rules, perfectly well.

And here is the second theme, sharp as ever: the East is not one thing — not even on a single dimension. "They're bad with time" collapses two genuinely distinct systems. Dubai's polychronic, relationship-first clock is not the same as Mumbai's elastic, intention-and-field clock — and neither is the precise, to-the-second punctuality Sarah would meet in Tokyo, which would shame her own. A manager who learned one rule ("Asia and the Middle East are relaxed about time") and applied it as a blanket would be wrong about Japan, crude about Dubai, and imprecise about Mumbai. There is no single "Eastern clock" to set yourself to. There is the Gulf, and there is India, and there is the specific partner in front of you.

The better approach

Sarah doesn't need to abandon her organization — her discipline is a genuine asset, and a project does need to ship. She needs to make her own clock visible to herself so she can adapt the interface without surrendering control. Concretely:

• Build slack into everything; treat start times as regions, not points. Plan for the 10:00 to begin at 10:35 and you arrive relaxed instead of fuming. Never stack appointments so tightly that one fluid meeting collapses the day.
• Lead with the relationship, then let business arrive. In Dubai especially, accept the coffee, ask about the family, be in the human opening — and watch the business go faster, not slower, because the foundation is being laid. Forcing linear efficiency reads as cold and usually backfires.
• Separate "soft" target dates from genuine hard deadlines — and explain the constraint, not the rule. Don't lecture anyone on punctuality. When a date is truly immovable because of an external force, name that: "I'm sorry — this one I can't move, because the regulator's window closes that day." People in both cultures respond to a real external constraint; they bristle at being told their relationship with time is wrong.
• Make commitments concrete where it matters, via the relationship. With Mumbai, instead of treating "Friday" as a contract, build in a friendly mid-week check-in and frame critical dates around shared consequences — "if this one slips past Friday, the crane crew we've booked sits idle and it costs us both" — letting the relationship and the real-world field, which the holistic mind already tracks, carry the deadline.
• Calibrate per culture, not per "region." What honors Dubai's polychronic flow (don't rush the human opening; expect interruptions) and what secures Mumbai's elastic dates (relationship-anchored check-ins; consequence-framing) are related but not identical moves.

Scripts Sarah could use: - (in Dubai, arriving) "Please — no rush. I've been looking forward to seeing you; how is the family?" (Then let business surface on its own.) - (flagging a genuine hard date, to either partner) "Most of our dates can flex, and I'll never make a fuss over a few days. This one's different — it's fixed by [external constraint], so let's make sure we protect it together." - (with Mumbai, mid-week) "Just checking in as friends, not to chase — how's it tracking for Friday? Anything getting in the way I can help clear?"

Within a project cycle of adapting the interface rather than "enforcing discipline," leads in Sarah's position typically find their "unreliable" partners deeply reliable — on the things that genuinely matter — and the relationships, which are the real engine of delivery, intact and warm.

Discussion questions

1. Identify the moment Sarah's own relationship with time became invisible to her. What habit did she mistake for universal professionalism?
2. The case shows one Western temporal instinct ("the schedule is a commitment") clashing in two different ways. What does that reveal about advice like "be relaxed about time in the East"?
3. Make the strongest case you can that a polychronic, relationship-first clock is better than a monochronic one — for what kinds of work and relationships?
4. Where is the line between adapting to polychronic/elastic time and genuinely losing control of a delivery that has real, hard external deadlines? How would you hold both?
5. Think of a piece of your own "time discipline" you treat as obviously right (back-to-back scheduling, punctuality-as-respect, deadlines-as-promises). How might it read, and what might it cost you, in a polychronic system?

Portfolio link. In your Cultural Intelligence Portfolio, under "Cognition & Time," classify your chosen culture as leaning monochronic, polychronic, or elastic, with one concrete piece of evidence — and write a single adjustment you'll make to your own scheduling because of it (e.g., build 30 minutes of slack around start times; lead with the human opening; reserve hard-deadline language for genuine external constraints). Add one caution to your "Behaviors I might misread" list: a late start, an interruption, or a slipped "soft" date is about a different clock, not disrespect — verify the real constraint before reacting.