Ehtesham's Substack

The Day the Cloud Said No

Mohammad Ehteshamul Haque — Sun, 14 Jun 2026 17:05:17 GMT

Picture an ordinary Tuesday a few years from now.

India has done nothing dramatic. It has carried on doing what it has done for years, buying discounted crude where it can find it, declining to sign on to a sanctions framework written in other capitals, and insisting that its foreign policy gets decided in New Delhi. None of that is illegal. All of it is sovereign. Somewhere in Washington or Brussels, a compliance committee, an export-control desk, or a national-security memo concludes that this independence carries a price.

The cost does not take the form of a missile or a blockade. It shows up as a login screen that will not load.

By nine in the morning, employees at a large refiner cannot open their email. By ten, a hospital chain finds its cloud-hosted patient records unreachable and its scheduling system frozen. Court clerks in three High Courts cannot retrieve filings. A state secretariat loses email continuity in the middle of an exchange. The spreadsheet that runs a logistics company’s entire dispatch schedule refuses to open. The AI tools that thousands of developers and analysts had built into their daily work return errors. An app used by thirty million citizens for a government service quietly disappears from a store managed on another continent. Bank back-offices running on a foreign enterprise suite slow to a crawl. Maps stop routing. The cloud console that controls all of it asks for credentials that no longer work.

“No tanks. No sirens. A country discovers, sector by sector, that the tools it treated as its own were rented all along.”

That scenario is not fiction. It extrapolates from events that have already occurred.

Two warnings, six months apart

The first case came from an unglamorous corner of the technology stack: office email.

In July 2025 the European Union placed Nayara Energy on its eighteenth package of Russia-related sanctions, largely because Russia’s Rosneft holds a stake of just under fifty per cent in the Indian refiner. Microsoft then suspended services to Nayara, reportedly cutting access to Outlook, Teams, and the company’s own hosted data, even though neither US nor Indian law required an American company to enforce an EU designation. Nayara’s licences were paid in full. The company called the move abrupt and unilateral, taken “under the guise of compliance” and without prior notice, and went to the Delhi High Court seeking an injunction to restore access to its own digital infrastructure. The court issued notice, and Microsoft restored services two days later, before the scheduled hearing. During the interval, the refiner reported logistics disruptions and cancelled cargo pickups at its Vadinar port.

Once the specifics are set aside, the lesson stands out. A company that operates in India and serves its energy economy lost access to the systems it runs on for several days, with every licence paid in full, because of a regulatory judgement made on another continent. The dispute ended within days. The underlying weakness remained.

The second case sits at the opposite end of the stack, in frontier artificial intelligence. It is only days old.

On 12 June 2026 Anthropic disabled its two most capable AI models, Claude Fable 5 and Claude Mythos 5, to comply with a US export-control directive that cited national-security authorities. According to reporting in the Wall Street Journal, Commerce Secretary Howard Lutnick had written to Anthropic’s chief executive, Dario Amodei. The order was broad. It told the company to suspend access for any foreign national, inside or outside the United States, including its own non-citizen staff. To comply, Anthropic switched the models off for everyone. They had been publicly available for three days.

Officials raised a cybersecurity concern. The models, on this account, could be pushed into finding software vulnerabilities useful for attacks on banks, government networks and other critical infrastructure, reportedly after agencies learned of a jailbreaking method. Anthropic disputed the directive. It said the vulnerabilities involved were minor and already known to other public models, and that such a standard would freeze frontier AI deployment across the whole industry. The episode followed months of friction between the company and the administration, including a Pentagon decision to label Anthropic a supply-chain risk after it declined certain surveillance and autonomous-weapons uses.

For India the timing was poor. India is reportedly Anthropic’s second-largest market. One large IT services firm had been training fifty thousand employees on the models. Another had recently begun collaborations. Thousands of developers spent the weekend migrating applications, and several startups paused launches that depended on features no longer available. The reaction in India came quickly. Zoho’s founder Sridhar Vembu called it a wake-up call and declared that “globalisation is dead”, urging India to build its own AI and, in the meantime, to lean on smaller Indian and Chinese open-source models. The investor Mohandas Pai went further, calling for an annual AI fund several times the size of India’s existing commitments. Venture investors began advising portfolio companies to reduce their exposure to a handful of foreign frontier providers.

The two cases differ in almost every detail except the one that matters. Nayara lost ordinary office email. India’s developers lost the most advanced AI models on the market. In each case the switch was thrown from abroad, for reasons unrelated to whether the Indian customer had paid or broken any law. Control over that switch sits outside the country at every level of the stack, from the mundane to the cutting edge.

The map of dependence

India’s digital dependence runs in layers. Each layer concentrates in a small number of foreign firms.

At the surface sit the productivity and consumer platforms of daily work: Microsoft 365 and Google Workspace, the leading browser, the two mobile operating systems, the default search engine and map. Beneath them run the enterprise systems that keep the economy moving, such as SAP and Oracle. Lower still is the cloud itself, where a data centre in Mumbai or Chennai can hold Indian data while its control plane, billing relationship and product roadmap stay foreign. The AI layer sits on top of that, and the deepest layers, telecom equipment, semiconductors, app stores and cybersecurity tools, sit underneath everything.

One large country treated the problem seriously about a decade ago, and its approach is worth studying despite its politics. China built domestic substitutes at almost every layer, as the comparison below sets out.

China’s censorship, surveillance and closed internet deserve rejection, and India tends to reject them. The strategic logic underneath still holds. Beijing declined to let foreign platforms become permanent dependencies before domestic alternatives existed.

The risk for India lies less in any single company. Microsoft was not the villain of the Nayara case, and Anthropic clearly preferred a different outcome in its own. The risk lies in concentration. When millions of users, thousands of firms and whole critical sectors rely on the same few platforms, the system gains efficiency and loses resilience at the same time. A single dominant supplier works well until the day it withdraws.

A single dominant supplier works well until the day it withdraws

India’s route should differ. It can remain democratic, open, interoperable and globally connected while reducing its exposure. The aim is continuity under pressure rather than isolation.

A familiar pattern of denial

One part of the record should reduce anxiety rather than raise it. The current situation repeats a long-standing feature of independent India’s technological history. On most past occasions when access was denied, India eventually built the capability itself.

The closest parallel to the present AI situation is almost four decades old. During the 1980s India needed high-performance computing for tasks that included weather forecasting. The United States blocked export of a Cray supercomputer, on the grounds that the same machine could model weapons. India responded in 1988 by setting up the Centre for Development of Advanced Computing. By 1991 C-DAC had built the PARAM 8000, an indigenous parallel supercomputer that later grew into a family of machines. A civilian requirement was refused on dual-use suspicion, and the refusal created a domestic capability that had not existed before.

Space technology followed a similar course. India signed an agreement with Russia’s Glavkosmos in 1991 for cryogenic rocket-engine technology to power its satellite launch vehicle. Washington imposed sanctions in 1992 under missile-technology-control rules, and Russia later limited the transfer of know-how under pressure. India argued, with reason, that the engines were meant for civilian satellites used in weather forecasting, telecommunications and resource mapping. It spent close to two decades developing its own cryogenic engine and flew a fully indigenous version successfully in 2014. The denial delayed India’s heavy-lift capability by years while pushing the country to develop it independently.

Navigation produced perhaps the sharpest example. During the 1999 Kargil conflict India sought GPS data for the high-altitude terrain, and the US-controlled system withheld it. Positioning, mapping and location turned out to be strategic infrastructure rather than neutral utilities, available in calm periods and conditional in a crisis. That experience became one of the reasons India built NavIC, its own regional satellite navigation system.

The United States widened the approach after the Pokhran-II tests of 1998, adding dozens of Indian scientific and defence entities to its Entity List and tightening controls on high-performance computers and other dual-use technology. Many of those entities were removed about two years later as the restrictions narrowed. An older case ran in the background. After the 1974 nuclear test, the promised supply of fuel for the Tarapur reactor became tied to supplier-country politics, and India turned to other sources to keep the plant running.

The list runs from uranium to rocket engines to supercomputers to GPS, and now to AI models, cloud accounts and office suites. The specific technology changes each time. The underlying risk stays the same. A capability that a society depends on can be withheld at the moment of greatest need, by firms answerable to a foreign government.

The response has been just as consistent. PARAM exists because a Cray never arrived. India’s cryogenic engine grew out of a blocked transfer. NavIC owes part of its origin to the GPS data withheld at Kargil. Technology denial has worked, oddly, as one of the more reliable spurs to research and development in India’s history. The events of the past year carry that same opportunity alongside the embarrassment.

Technology denial has worked, oddly, as one of the more reliable spurs to research and development in India’s history.

Where India has built its own

India already holds working sovereign capability in several areas, much of it operating at population scale.

Payments offer the clearest case. The Unified Payments Interface now ranks as the world’s largest real-time retail payments system, handling billions of transactions a month and reducing everyday reliance on foreign card networks. Together with RuPay and the public infrastructure of Aadhaar, DigiLocker and CoWIN, it shows that India can design and run platforms for more than a billion people.

Zoho matters for a different reason. Most of India’s IT services firms build software for foreign clients. Zoho instead owns its full product stack and runs its core workloads on its own servers rather than on a foreign cloud. The company is bootstrapped and profitable, competes with Microsoft and Google on features as well as price, and earns most of its revenue overseas. It shows that India can build finished software products rather than only supply technical labour.

The telecom stack has started to loosen a long-standing import monopoly. BSNL now runs an indigenous 4G stack built by TCS, C-DOT and Tejas Networks across tens of thousands of towers, with an O-RAN-compliant 5G effort and an open-source platform from leading institutes in development. A domestic video-conferencing platform, created through a government challenge, serves several High Courts.

The real weakness lies in adoption rather than capability. India often builds a domestic alternative, then treats the foreign default as inevitable. A platform exists, yet procurement renews the incumbent supplier. Ministerial endorsement of the Indian option has not displaced the habit and network effects that keep users on the global one. The distance between what the country can build and what it actually uses now counts as a security problem rather than a question of market share.

From access to assurance, and the leakage problem

India needs a working doctrine of digital sovereignty rather than a slogan. It can be set out plainly.

First, classify digital systems by sovereign criticality. Email and documents for a small private firm are ordinary business tools, while the same software running a refinery, a port, a power grid, a court, a hospital network or a state administration counts as critical infrastructure and deserves different rules. Second, mandate exitability, so that every critical organisation can export its data, documents and workflows in usable formats within a defined window, and no institution gets trapped in a system it cannot leave. Third, require tested continuity plans: fallback arrangements for email, identity, communication and operational records, whether built on Indian commercial platforms, open-source deployments or government clouds. The test there is practical rather than ideological, namely whether the institution keeps functioning when the primary vendor stops responding. Fourth, give procurement preference to credible domestic alternatives wherever they genuinely meet the bar.

Fifth, separate convenience from criticality. A foreign tool can be a sensible choice for marketing automation and a poor one as the sole operating backbone of a strategic national asset. Sixth, accelerate sovereign AI, meaning compute, models, datasets and evaluation standards strong enough to serve critical needs when foreign access is restricted. Seventh, rehearse failure. India runs military exercises and disaster simulations, and it can run national digital resilience drills in the same spirit, deliberately staging cloud lockouts, API withdrawals, app-store removals and enterprise-software outages before a real crisis does.

On the sixth point, India already has a live debate worth holding in the open. One camp, led by investors such as Mohandas Pai, argues for a national mission several times larger than today’s commitments, running into tens of billions of dollars across funds, credit guarantees, hardware and semiconductors. Another, voiced by Sridhar Vembu, cautions that spending tens of billions is the wrong instinct, and that patient research plus heavy use of open-source models can carry India much of the way. Both positions hold some truth. The point is that the choice has become urgent enough to argue about.

Most proposals for sovereignty skip the next part. Once words like “sovereign”, “swadeshi”, “indigenous” and “strategic” turn into procurement keywords, they attract the wrong applicants. A national effort of this kind tends to draw rent-seekers in its early years. Well-connected firms may wrap a thin Indian shell around foreign software and present it as homegrown. Others may win protected contracts through patronage rather than performance, build subsidised products that never face real competition, then lobby to make the protection permanent. India saw a version of this in earlier decades of protected industry, when closed markets often produced captive monopolies with little reason to improve. Any claim that a sovereignty programme will stay clean from the first day deserves scepticism. Some leakage is likely.

Leakage argues for discipline rather than retreat. Most large strategic projects, from railways to telecom to defence manufacturing, lost something to opportunists in their early stages. The projects that lasted were the ones whose rules gradually reduced that loss. The safeguards here are reasonably well understood. Preference should track performance rather than identity, triggered only when a product clears published benchmarks for security, uptime, interoperability and usability, so that a label alone earns nothing. Open standards and genuine data portability should be mandatory, which keeps the country from trading a foreign lock-in for a domestic one and makes white-labelling easier to detect. Open-source deployments deserve preference where practical, since auditable code is harder to fake and harder to capture quietly. India could adopt Vembu’s suggestion of transparent, independent annual evaluations of national capability across critical technology sectors, so that public claims can be measured against published results. Every form of protection should carry a sunset clause, so that support ends once domestic firms can compete rather than continuing as a permanent subsidy. Procurement should run in the open, with published criteria and audit trails, which leaves less room for patronage.

With that discipline in place, early leakage becomes a cost of building rather than a permanent feature. Without it, India risks swapping foreign dependence for domestic extraction, an outcome arguably worse, since the foreign supplier at least delivered a working product.

Sovereignty is the ability to continue

The test of sovereignty has little to do with using foreign technology in normal conditions, which any country can manage. The real test is whether India keeps operating when conditions change, when a foreign court, a sanctions package, an export-control desk or a company’s compliance team acts for reasons unrelated to India’s interests.

Nayara delivered a warning at the enterprise layer, and Anthropic delivered one at the AI layer. The next case may come from cloud, chips, app stores, operating systems, maps or browsers. It will probably resemble the last two, arriving not as an invasion but as a service that stops responding.

The next phase of Digital India has to shift from access to assurance. Access concerns whether citizens and businesses can use digital tools. Assurance concerns whether the country keeps running once those tools are withdrawn, sanctioned, degraded or attacked. India can keep using Microsoft, Google, Amazon, Apple and Anthropic, and it should keep using the best products available. The change required is to stop treating a paid subscription as a form of sovereign control.

The lesson is short. A capability that cannot be operated under stress is not truly owned. A nation would do well to avoid making any such capability indispensable.

When Strategic Cultures Collide: The Cultural Logic Behind the Iran Crisis

Mohammad Ehteshamul Haque — Sat, 06 Jun 2026 06:55:33 GMT

On 28 February 2026 a joint American and Israeli operation killed Ali Khamenei, who had led Iran since 1989, along with members of his family and much of the senior command. The American framing presented the strike as a liberation. Iranians would seize the moment to reclaim their country, and a system built around the Supreme Leader would fall once its head was removed.

The months since have run another way. The government held. An interim council formed within a day, and Khamenei’s son Mojtaba was advanced as successor. Mourning crowds filled the streets. Iran’s retaliation arrived faster and heavier than its careful reply of the previous summer. The war spread across the Gulf, shipping through the Strait of Hormuz fell to almost nothing, and oil rose above a hundred dollars a barrel. The assumption behind the strike, that removing the leader would remove the threat, looks more and more like a misreading.

Most accounts of the crisis reach for two familiar vocabularies. Western strategists talk about deterrence, the calculus of threats and capabilities. Regional commentators talk about power, the contest for primacy across the Middle East. Both capture something real. Both leave out the variable that explains why the same events keep producing opposite reactions. The missing variable is meaning.

Wars do not escalate merely because states possess weapons. They escalate because states assign different meanings to the same actions.

A strike that one side reads as deterrence, another reads as humiliation, and a third reads as the making of a martyr. The weapons are identical. The interpretations are not, and the interpretations decide what happens next.

Three cultures, three starting points

Israeli strategic culture begins with bluntness. The society prizes a manner of speech it calls *dugri*, a borrowed Arabic word for talking straight, and the same directness runs through its security thinking. A state with almost no strategic depth cannot rely on surviving the first blow, so its doctrine favours initiative and preemption, captured in a recurring question: “If the threat is growing, why wait?” Applied to Iran, the disposition generated a threat assessment stated in maximal terms and delivered without softening. That framing shaped how Washington came to define the problem.

American strategic culture reaches instinctively for deterrence and coercion. Force is treated as a message, calibrated to change an opponent’s cost-benefit calculation. Pressure, on this view, produces concessions, and the removal of a hostile leader counts as coercive success. Iran’s weakened position after the June 2025 war, the sanctions, the protests and the damaged network of allies, read in Washington as evidence that the pressure was working and that military means now offered more than diplomacy.

Iranian strategic culture rests on two older foundations. The first is a long tradition of honouring the righteous victim, running from the ancient mourning for the slain prince Siyavash to the central Shia commemoration of Husayn, killed at Karbala in 680 and grieved every year since. A system grounded in that tradition tends to convert the killing of a leader into a martyrdom that strengthens cohesion rather than breaking it. The second foundation was patience. For all his revolutionary language, Khamenei governed with caution, and his responses to direct attack were calibrated to satisfy honour while avoiding a war that might end the system. After the United States killed Qassem Soleimani in 2020, Iran struck back at American bases with enough advance signalling to limit casualties, which let both sides retreat. A patient centre kept Iranian reactions inside predictable bounds.

Three Cultures, Three Interpretations

The collision becomes clearer when the same events are read through each lens at once.

Three Read down the columns, three coherent worldviews appear. Read across the rows, the danger appears. The same act carries a different meaning in each capital, and each meaning licenses a different response.

Iranian restraint that Washington files under pressure working is filed in Tehran under strategic patience, a reserve of dignity rather than a sign of surrender.
A strike that Israel records as necessary preemption is recorded in Iran as humiliation demanding redress.
Leadership losses that the coalition counts as coercive success register in Iran as martyrdom, the most mobilising category its culture contains.

None of the three sides is reading the situation irrationally. Each is reading it correctly by its own grammar, and the grammars do not match.

The Missing Variable: Humiliation

Western strategic literature is built around power, interests, deterrence and capability. It leaves little room for humiliation, and humiliation sits close to the centre of Iranian political memory. The catalogue is long: the 1953 coup that removed the elected prime minister Mohammad Mossadegh with American and British help, decades of sanctions and enforced isolation, the 2020 killing of Soleimani, repeated strikes on Iranian soil, and now the death of the Supreme Leader. Each episode entered the national story not only as a loss of capability but as an injury to standing.

Recent analyses of the June 2025 war have framed its aftermath in exactly these terms, treating the regime’s exposure as a wound to honour as much as a military setback. The distinction matters for what follows. A state that has been humiliated does not calculate the way a state that has merely been deterred does. Its first priority becomes the restoration of dignity, and restoration can be valued above safety.

Culture shapes far more than how people communicate. It shapes how they read status, respect and legitimacy.

The Iranian reply to the February strike supports the reading. It came faster and in greater volume than the measured response of the previous summer, and in its opening days Iran launched a larger share of attacks than across much of the earlier twelve-day war. Analysts have taken the shift as a sign that the command structure, and its old caution, had changed.

That change is the heart of the matter. The strike removed the figure most responsible for keeping Iranian retaliation bounded, and it did so in the name of reducing the Iranian threat.

The patient calculator is gone. Left behind are a martyrdom culture, a deep memory of humiliation, and a dispersed command with less to lose. The combination tends to escalate, not fold. A strike calculated purely in the language of capability can land as an assault on status, respect and legitimacy at once, and a state reacts to that kind of injury with far less restraint than a cost-benefit model predicts.

Built to survive decapitation

The speed of the Iranian reply also has a structural explanation, and it points to a second American misreading. Iran had seen decapitation before, and it had prepared for it. The lesson came from Iraq. The rapid collapse of Saddam Hussein’s heavily centralised state

in 2003, and the wider pattern of American operations against centralised regimes, persuaded Iranian planners that a single command centre was a fatal weakness. The killing of Qassem Soleimani in Baghdad in 2020 drove the point home on Iranian flesh.

The response was a doctrine the Revolutionary Guard calls mosaic defence. Formalised from 2005 and built out by 2008 under General Mohammad Ali Jafari, it broke the Guard into roughly thirty-one provincial commands, each with its own weapons, intelligence, logistics and integrated Basij units, and each holding pre-delegated authority to act without instruction from the centre. The governing assumption was blunt: decapitation is not a decisive blow if the body keeps moving. Authority was pushed down through what Iranian officials describe as successor ladders, with named replacements several ranks deep for every senior post, ready to step up the moment a superior is killed.

The design held under the heaviest test it has faced. With the Supreme Leader and much of the high command gone, provincial units regrouped and fired on their own initiative, which accounts for a reply that arrived within hours rather than days. The same feature carries the danger the article has traced. A force built to keep fighting without its head is, by definition, a force that no head can easily call back. Decentralisation bought survivability at the cost of control. The patient centre that once bounded escalation has been removed, and the machine left in its place was engineered to continue regardless of who gives the order. Several analysts of the doctrine have made the warning explicit: the structure that prevents collapse also removes the off-switch.

Where the readings collide

The American decision applied one culture’s meaning to a situation governed by two others. Decapitation reads as victory inside a framework where the leader is the regime and the regime is the threat. It reads as martyrdom inside a framework built on the memory of Karbala. Preemption reads as prudence to a state with no depth to spare. It reads as humiliation to a state whose political identity is organised around resisting exactly that. The coalition acted on its own grammar and misread the other two, and the gap between intention and reception is where the crisis now lives.

The outcome remains open. The Iranian system may yet fracture under the strain, security forces may defect, and serious analysts disagree about the trajectory. The mechanism, though, is already visible, and it has little to do with the balance of weapons.

The Deepest Insight

Israel fears annihilation.
America fears the loss of its credibility.
Iran fears humiliation.
Each fear is rational within its own cultural framework.
When nations respond to different fears, they misread one another’s actions almost by default.
The most dangerous conflicts are not those in which one side misunderstands the other.
They are those in which every side believes it understands the other perfectly.

The Email That the Books Could Not Help Me Send

Mohammad Ehteshamul Haque — Mon, 04 May 2026 05:00:05 GMT

The shelves were full of books on cross-cultural communication. None of them helped me write the email I had to send before lunch

That was the problem.

For more than two decades, my work has lived where business, technology, and culture meet. I started as a mechanical engineer in heavy industry. Construction equipment. Cranes. Trenchless technology. Complex international operations. The work took me through India, the Middle East, Russia, China, and most of Asia Pacific.

For three years I lived in Saudi Arabia, managing multicultural teams in a demanding environment. Later, at a US multinational, I helped open offices in new markets, ran the Middle East and the Indian subcontinent, and eventually took responsibility for Asia Pacific.

On paper this reads like a career in international business.

In practice it was an education in misunderstanding.

Not the dramatic kind. Not the sort that ends up in case studies with obvious villains and clean lessons. The misunderstandings I cared about were smaller, quieter, and more expensive.

A polite sentence that read as evasive.

A direct request that read as rude.

A ‘yes’ that did not mean agreement.

A delayed reply that signalled respect to one colleague and disengagement to another.

A careful explanation that one side called professional and the other called avoidance.

These rarely look like cultural problems at first. They look like slow decisions, weak ownership, missed deadlines, or lack of urgency. Only later do you realise people were not disagreeing about the work. They were operating from different assumptions about how work should be written, framed, challenged, softened, escalated, or concluded.

That realisation became impossible to ignore when I was promoted to Director, Asia Pacific.

My remit suddenly covered multiple countries. China, the Philippines, Thailand, Malaysia, Indonesia, India and more. The Indian subcontinent stayed on my plate. The China and Philippines offices reported into me. American headquarters sat across time zones with its own expectations of speed, clarity, and decision-making.

At first I managed the way many international managers manage. By getting on planes.

Quarterly visits. Factory walks. Corridor conversations. Long dinners after difficult meetings. The real work often happened outside the formal meeting room. A tense issue softened over a meal. A hesitation became visible in someone’s body language. A disagreement surfaced only after the senior person had left. Writing mattered, but it was held up by presence.

Then COVID grounded everything.

The corridor conversations disappeared. The factory floor disappeared. The after-meeting clarification disappeared. The dinner where the difficult subject softened over a glass of wine disappeared.

What remained was a screen and a keyboard.

My day reorganised itself around writing. Early mornings with China, where every exchange carried the weight of face, hierarchy, and relationship. Daytime with India, where context mattered and a decision often needed the conversation around it to make sense. Late evenings with American headquarters, where messages were short, direct, and built for speed. The Philippines, Thailand, Malaysia, Indonesia, and other threaded through the day, each with its own rhythm of respect, caution, warmth, and indirectness.

Within weeks the cracks showed.

A short, polite email from a Japanese reseller partner read in Seattle as evasive. A direct American request read in China as aggressive. A Chinese ‘yes’ meant agreement on Monday and reluctance on Wednesday, and the difference lived not in the word itself but in the sentences around it. Velocity dropped. Trust frayed. Problems that looked operational were often embedded in writing.

So I went back to the books.

Erin Meyer helped explain cultural mapping. Richard Lewis helped explain broad communication patterns. Hofstede’s dimensions sat underneath much of the conversation. Andy Molinsky wrote about adaptation. Craig Storti wrote about crossing cultures. The frameworks were valuable. They helped me understand why a meeting had gone wrong.

They did not help me write the next email.

The academic literature held more answers. Those answers were buried behind paywalls, technical language, and hundreds of pages of theory. A practitioner drafting a sensitive reply at midnight had nowhere simple to go.

So I started keeping notes.

Patterns from my own inbox. The structure my Chinese colleagues used to deliver bad news. The way Filipino colleagues softened a refusal. The signals that suggested a Chinese colleague had a serious objection but would not state it directly. The American instinct to put the conclusion first. The German preference for context, evidence, and precision before commitment. The Indian habit of building meaning through relationship and surrounding explanation before arriving at the point.

At first the notes were only for me.

They helped me decode what I was reading and adjust what I was writing. Over time they became something larger. By 2022, during a four-week sabbatical, I started turning them into a book. By late 2023, the first draft had crossed two thousand pages. Far too long, but complete.

Two more years went into cutting it down.

The personal irritations had to go. The patterns that survived distance stayed. Theory remained only where it served the practitioner. What was left was the practical core. How to read cultural signals in writing. How to write back in a way that lands.

That book became *When Culture Collides with Language: Decode. Adapt. Transcend.*

This Substack starts from the same place.

It is not an academic newsletter, though it will draw on research. It is not a travelogue, though it will move across countries. It is not a collection of etiquette tips, though it will sometimes touch on gifts, greetings, silence, hierarchy, honour, directness, and face.

It is about the written work of crossing cultures.

Here I will write about the things that rarely get taught but often decide whether international work succeeds. Why some cultures expect the writer to be explicit and others expect the reader to infer. Why politeness can look like clarity in one place and aggression in another. Why ‘yes’ is one of the most dangerous words in global business. Why some emails begin with context and others with conclusions. Why silence, delay, hedging, apology, titles, emotion, humour, and even emoji carry different weight across borders.

I will also write what did not fit into the book.

Every book leaves material behind. Some topics were too specific. Some too playful. Some deserved their own space. Honorifics. Emoticons. Digital etiquette. Status anxiety. Apology styles. Feedback rituals. Translation traps. Meeting follow-ups. The quiet politics of ‘just checking in.’

The aim is practical.

If you run cross-cultural teams, report to a foreign headquarters, sell across borders, build international partnerships, or rewrite emails because something feels off, this is for you.

I will not promise easy formulas. Culture does not work that way. What I will offer is patterns you can recognise, questions you can ask, and small adjustments that change how a message lands.

Most global misunderstandings do not begin with bad intent.

They begin with a sentence that travelled badly.