What Global Companies Lose When Decision-Making Revolves Around Headquarters

Running a global company is a coordination challenge; in practice, it’s also a power imbalance. In many multinational organizations, the biggest factor shaping strategy isn’t market insight or expertise—it’s proximity to headquarters. Decisions get framed, debated, and often finalized by the people who happen to be awake and in the room, while equally senior leaders elsewhere wake up to outcomes they had no chance to influence. Over time, this HQ‑satellite dynamic quietly distorts priorities, sidelines regional expertise, and leaves global leaders managing the consequences of decisions they weren’t part of making.

While leaders operating remotely can help their cause by building strong rapport and trust with peers in company headquarters, this kind of ad-hoc relationship-building is insufficient. Global organizations need systemic solutions that ensure enterprise priorities and decisions reflect the full breadth of their global scope.

Over a 15-month period, my colleagues and I studied global leadership effectiveness through interviews, focus groups, and executive roundtables with more than 150 leaders across the U.S., Europe, Asia, and the Middle East. This is part of a larger, ongoing study we’re conducting on how culturally intelligent leaders navigate growing geopolitical, economic, and cultural tensions. The findings revealed two organizational strategies that consistently reduced the power imbalance between headquarters and everyone else.

Reverse the Direction of Decision-Making

In most global companies, high-stakes decisions are centralized so that C-suite executives can maintain alignment across markets, manage exposure, and ensure consistency across the company. Leaders at the periphery are encouraged to proactively speak up and make their case, yet that assumes they know a decision is even under consideration in the first place. Often, they are caught on the back foot—making their case only after deliberations (or indeed decisions).

The timing of input matters because early ideas disproportionately shape how a problem is defined and which options feel viable. Psychologists Amos Tversky and Daniel Kahneman’s research on anchoring found that the first idea introduced in a discussion often becomes the reference point against which all subsequent ideas are evaluated, regardless of its strength. This reality emerged repeatedly as we talked with leaders across industries and regions. Highly competent, relationally savvy leaders at the periphery say that decisions are unduly influenced by less experienced peers at headquarters. By the time regional input is solicited, the contours of a decision are already established and alternative perspectives are more likely to be treated as constraints to manage rather than as sources of insight. The issue is not simply who makes the decision, but where the decision process begins.

The decision-making starting point for many global organizations is also shaped by time zone realities. Key decisions are framed and debated while senior leaders in other regions are asleep. By the time leaders from the other side of the world can engage, the direction has already been shaped. This sentiment was raised repeatedly across our interviews and focus groups. One executive said, “You wake up, scroll through 200 messages, and find out a decision has already been made without you.” By that point, the conversation is no longer about shaping direction but managing it for your region.

One way an organization can effectively address the impact of proximity on decision-making is by intentionally changing where decisions begin. Rather than framing the decision at headquarters and then asking regional leaders for input, they can redesign their process so that decisions originate closer to the source of expertise. In practice, this means regional and functional leaders define the problem and set the initial direction by identifying options to be considered. The shift doesn’t eliminate headquarters’ role, but it changes when they weigh in.

Meta made this kind of shift when they recognized that too many of its engineering decisions were being shaped by assumptions rooted in Silicon Valley, despite the greatest growth happening in markets many time zones away. Teams in Latin America, Africa, and Asia repeatedly told engineers in Menlo Park that new features and applications were not viable on many of the devices and networks in their markets. Global products were being designed for a narrow set of users and then adapted for everyone else. Meta instituted a new requirement that any new application had to function on a basic flip phone in rural India before it could move forward. This was more than a technical constraint. It became a decision-making norm that forced teams to start with a market characterized by different bandwidth, intermittent connectivity, and massive opportunity. By starting with feasibility in one of its largest and most demanding markets at the outset, Meta shifted the framing of product decisions. Headquarters continued to play a central role integrating insights and setting strategic direction, but the starting point for product decisions started in select markets and moved inward from there.

A different version of this pattern emerged at Mediora Health Systems (pseudonym), a European medical device company. Mediora launched a cardiovascular device in Southeast Asia that leadership expected to be a major success based on strong clinical results and prior performance in Western markets. Sales were significantly short of expectations. Post-mortem reviews revealed that regional teams had raised concerns about how the device conflicted with local beliefs regarding invasive cardiac procedures. The concerns were acknowledged but didn’t change the launch decision. The regional leaders made the effort to speak up and defend their position but their input entered the process after key assumptions about market readiness and adoption had already been set at headquarters.

Mediora reversed its decision-making norms by requiring that decisions about whether and how a device would be introduced in a region began with regional teams. Those teams were responsible for assessing cultural expectations, patient behavior, and regulatory constraints, and for developing an initial recommendation on market viability and launch strategy. The time required to reach a decision was longer but it was worth it. Mediora reduced the need for costly redesigns and post-launch corrections and subsequent launches showed stronger performance.

Organizations can require that any major decision begins with a short brief from the region or function closest to the issue. Instead of asking for input after a direction has been proposed, headquarters can require that the first framing of the problem, the key assumptions, and the initial recommendation come from those with the most direct exposure to it. This simple shift changes not only who contributes, but when their perspective shapes the outcome.

Reversing decision-making direction does not mean abandoning centralized control. There’s a degree of headquarters-centric decision-making that is always necessary, particularly for companies with highly standardized franchise models or for businesses where brand consistency, regulatory compliance, or enterprise-wide risk needs to be tightly managed. There are a few questions organizations can ask when determining how much authority headquarters should wield in a decision, including:

• Is delivering a consistent customer experience across markets more important than adapting to local variation?

• Would different markets executing this decision in different ways create legal liability, safety risk, or brand erosion?

• Does this decision commit capital that competes with other enterprise-wide priorities?

• Is the core expertise required to make this judgment concentrated at the center or in local markets?

Answering these questions clarifies when centralized control works best, a rationale that should be shared with leaders across the enterprise, so everyone is aligned.

Make Sure Information Flows Both Ways

One of the hardest parts of global decision-making is responding to complexity and speed with incomplete information. Global leaders are expected to address shifting risks, market disruptions, and geopolitical developments without fully knowing what is unfolding. Organizations need mechanisms that ensure information moves predictably through the system rather than depending on personal networks or chance conversations. In organizations spanning vastly different time zones, the challenge is compounded by the fact that information rarely reaches all decision-makers at the same time. Across the interviews and focus groups, leaders frequently described being the last to know about critical information that would have otherwise changed a decision already made. Even leaders in very sophisticated Fortune 500 companies described access to information as often depending on who you know and whether you happen to be in the right place at the right time.

In many organizations, information flow, like decision making, occurs unevenly. Leaders in markets and regions have real-time data from distributors and customers, intel that may only haphazardly reach headquarters. The result can be enormous, missed opportunities. In several Middle Eastern and European markets, for example, mobile ordering and food delivery surged long before the trend took off in the U.S. Leaders in those regions working for a U.S.-based fast food chain saw how the shift needed to affect kitchen layout, staffing, and order flow, yet they struggled to get the attention of leaders at headquarters. Meanwhile, U.S. leaders were reviewing budgets, dining room layouts, and order flow improvements without accounting for how quickly delivery volumes were reshaping customer behavior in some of their most important markets.

Leaders from other companies repeatedly described joining late-night calls to ensure their market and perspective were represented. They would leave the call believing there is alignment, only to discover that the topic resurfaced hours later in a different meeting and moved in a new direction. None of the leaders I spoke with believed there was a conscious effort to exclude them. But the physical distance and time zones meant discussions continued without them and no one bothered to come back to talk with them about it.

Many organizations attempt to address these communication breakdowns by ensuring regular check-ins and proactive outreach. Headquarters host town halls, circulate enterprise-wide updates, and set up communication dashboards to improve transparency. Companies tell leaders working across multiple time zones to schedule meetings during overlapping work hours, rotate inconvenient time slots, and rely more heavily on asynchronous tools. And what came through most clearly in our interviews was the expectation that leaders outside the center need to over-communicate and build visibility to remain connected. These practices, as Tsedal Neeley’s research has demonstrated, succeed at increasing the frequency and consistency of communication across the enterprise, but an underlying pattern remains. Where you sit in the organization disproportionately shapes what information you give and receive. The challenge is not only access, but also the timing and depth with which information travels across the organization. The critical variable is not only if information is shared but whether it enters the early enough to inform key priorities and actions.

There are a few of ways organizations can strengthen information flow to and from the center of the organization.

First, instead of putting the primary burden on regional leaders to speak up more, companies can create low-friction mechanisms that make it easy for regional insights to reach headquarters and receive timely acknowledgment. Pulse surveys, weekly prompts, and idea channels can lower the barrier to contribution while ensuring visibility.

Next, organizations can establish small, cross-regional working groups that meet on a predictable schedule to exchange updates in both directions. Mediora, for example, established four Global Insight Councils to support bi-directional information flow. The councils represented Mediora’s four major regions and included clinical leaders, commercial teams, and at least one designated representative from headquarters. The councils meet monthly to exchange intelligence on patient behavior, regulatory changes, cultural dynamics, and operational challenges. Representatives from each council convened quarterly with the C-suite to integrate regional observations into enterprise strategy discussions while gaining insights for regional teams about evolving enterprise priorities.

The fast food company that initially ignored early signals about mobile ordering eventually created a global task force with leaders from headquarters and select markets. Each region submitted a brief, standardized update on delivery volumes, peak hours, and operational bottlenecks. A small global team reviewed the input and used the intel to adjust kitchen design and staffing models worldwide. The task force enabled headquarters to anticipate delivery growth in other markets. Given its success, the company institutionalized the task force as a standard part of global operations.

Finally, companies can engineer asynchronous information flow, which is particularly important for organizations spanning vastly different time zones, socio-demographics, and local realities. One of the most interesting success stories comes from Unilever’s Shakti Project in India, when Unilever recruited a network of rural women to become their distributors across thousands of Indian villages. The women were not only a formidable sales force, they became a goldmine of detailed, real-time observations about consumer behavior, product use, price sensitivity, and household preferences. They met regularly with area managers and provided real-time feedback. Rather than leaders in London and Rotterdam relying on market data from external consulting firms, rural insights became part of the regular flow of communication, which in turn informed brand and product development. Headquarters was able to anticipate shifts in rural markets because they received structured updates directly from the markets.

Leading Together

Distributed leadership is an unavoidable reality for any global enterprise. Yet left unchecked, proximity, rather than knowledge or ability, shapes the degree to which a leader can influence strategy, priorities, and day-to-day processes. When organizations develop systemic routines to close the gap between headquarters and everyone else, it leads to better decisions, increased information flow, and reduced frustration from working across the globe. These same systemic practices can help any company, even those operating solely within a domestic context. Someone in Arizona working for a New York company experiences many of these same challenges. As business leaders everywhere navigate geopolitical volatility, economic pressure, and rapid advances in AI, systemic practices that connect leadership across geographies and time zones better ensures that the organization benefits from the expertise and insights from all their leaders.

Copyright 2026 Harvard Business School Publishing Corporation. Distributed by The New York Times Syndicate.

Explore AAPL Membership benefits.