Our Take
The advice is sensible but unsupported: McKinsey prescribes a governance structure without data on which organizations tried it, what 'faster, stronger results' actually measured, or how often this model fails.
Why it matters
Operations leaders running large distributed networks face genuine tension between central control and field autonomy. If you're mid-transformation and gridlocked, this framing offers a directional principle, though you'll need your own metrics to know if it works.
Do this week
Operations leader: map your current decision bottlenecks (approval gates, reporting chains, planning cycles) by site this week so you can test whether centralizing strategy alone unblocks field execution.
McKinsey's governance prescription for distributed operations
McKinsey's Leading from the Field: Transformation in Distributed Operations argues that production network transformations stall when centralized command runs too tight. The firm recommends inverting the hierarchy: push decision authority to site leaders while the center sets strategic direction and measures systemwide impact.
The core claim is that this structure delivers "faster, stronger results." McKinsey does not publish the underlying data, customer count, or independent validation of the model in the available excerpt.
Field leaders versus central control is a real operational tension
Any large distributed operation faces a classic trade-off. Central teams ensure consistency, compliance, and cross-site learning. Field leaders know local constraints, customer preferences, and bottlenecks invisible to HQ. Transformation initiatives often get stuck in the gap: central mandates arrive too slow; field initiatives fragment.
McKinsey's recommendation to empower site leaders while keeping central strategy is intuitive. It mirrors successful product organizations that split product strategy (centralized) from go-to-market (distributed). Whether it works in operations depends on your baseline: how much your current delays are caused by governance versus capability, tooling, or skill gaps.
Diagnose before you restructure
Before adopting this model, audit where your transformation is actually stuck. Are decisions slow because site leaders lack authority, or because they lack data, training, or tools? Are central teams over-managing, or under-communicating? Are field teams siloed, or just resource-constrained?
McKinsey's framing is useful as a hypothesis. Your own baseline metrics—cycle time to deploy changes, variance in outcomes across sites, rework costs, staff turnover—will tell you whether decentralization fixes your problem. If your friction is information flow, not authority, restructuring alone won't help.