The HQ vs. Markets War: Who Should Control What

Every company expanding internationally faces the same tension: headquarters wants consistency and efficiency; local markets want autonomy and relevance. The resulting tug-of-war consumes leadership attention, slows execution, and often satisfies no one.

After building European operations across major tech and consumer brands, I've developed a framework for resolving this tension. not by picking a winner, but by clearly defining what each level should own.

The Three-Layer Model

Headquarters owns: Brand positioning, strategic priorities, technology platforms, and financial targets. These are the non-negotiables that define what the company is and where it's going.

Regions coordinate: Resource allocation, capability development, cross-market learning, and operational standards. Regions exist to create leverage. ensuring that what works in one market benefits others.

Markets control: Customer relationships, tactical execution, local partnerships, and market-specific adaptations. Markets own the how of delivery within the what defined by headquarters.

The Decision Rights Matrix

The framework only works if you codify it. Every significant decision type needs a clear owner: who proposes, who approves, who must be consulted, who must be informed.

At one ride-sharing company, we built this matrix for every major function. Marketing had one set of decision rights, product had another, operations had a third. It sounds bureaucratic, but it actually enabled speed. because people knew who could say yes without endless escalation chains.

Common Failure Modes

Over-centralization: HQ controls everything, local teams become execution arms with no autonomy. Result: slow adaptation, poor local relevance, talent flight.

Over-localization: Markets do their own thing, HQ provides funding but no direction. Result: fragmented brand, duplicated costs, no learning transfer.

Missing middle: Companies skip the regional layer entirely, creating direct HQ-to-market relationships. Result: HQ overwhelmed, markets unsupported, coordination chaos.

Building the Governance Layer

Clear decision rights are necessary but not sufficient. You also need governance mechanisms to handle exceptions, resolve conflicts, and adapt the framework as the business evolves.

This means regular forums where HQ, regions, and markets can surface tensions before they become crises. It means escalation paths that are fast enough to not block execution. It means treating role architecture as a living system rather than a one-time org design exercise.

The PE Angle

For portfolio companies, unclear role architecture is often a hidden value destroyer. The symptoms show up as slow execution, inconsistent results, and leadership churn. but the root cause is structural ambiguity about who owns what.

Fixing this architecture can unlock significant operational leverage. But it requires diagnosis before prescription. understanding where the current model is breaking before designing the replacement.