Microsoft executives are rolling up their sleeves [1]. Meta did the same — reframing block-level managers as player-coaches and org leads [2]. The consulting industry calls this distributed authority. The press calls it adaptive leadership.
The market celebrates player-coach leadership as progress toward distributed authority. When Business Insider reports that Microsoft leaders are getting closer to the work after restructuring [3], the narrative frames proximity as virtue. When Meta renames management layers as player-coaches, the same narrative applies. The underlying assumption: physical or social closeness equals better, faster, more decisions through rights distribution.
That assumption has a problem. Twenty-five percent or more of executives cite lack of strategic clarity as their primary limiter [4]. They don't say "I need to be closer to decide." They say "I don't know what I'm free to decide." That question points to architecture, not capability or proximity.
More than twenty-five percent of executives cite lack of strategic clarity. They don't say "I need to be closer to decide." They say "I don't know what I'm free to decide."
That statistic comes from LHH's 2026 C-Suite Research. It names the same pattern across sectors and scales.
We believe in Distributed Authority: authority should reside where information and context exist — at the edges of the organization. Here we agree with the stated goal. This requires strategic clarity to function effectively. Without it, authority becomes chaos — people have decision rights but no coherent direction for using them.
Player-coach roles create a specific kind of chaos. They generate the appearance of distributed authority without the structural reality. The executive who rolls up their sleeves is physically near the work. But who approves the budget? Who greenlights the initiative? Who owns the escalation? Those questions remain unanswered.
The executive who rolls up their sleeves is physically near the work. But who approves the budget? Who greenlights the initiative? Who owns the escalation?
This is what we call proximity theater. The leader is present. The structure is unchanged.
We believe the distinction matters because empowerment and structural authority are different things. Empowerment implies power is given from above — revocable, conditional, tied to the leader's presence. Structural authority means decision rights are baked into the architecture: explicit boundaries, clear thresholds, defined escalation paths. Player-coach models operate in the first category. They give the appearance of trust without the structural reality of power.
The result is a patronizing dynamic. Teams see the leader in the room but still can't approve, escalate, or decide. The leader appears accessible while decision rights remain centralized. This is the illusion of authority while avoiding its exercise.
Teams see the leader in the room but still can't approve, escalate, or decide.
We believe still too many leaders fall into a trap when delegating: they either prescribe the method in detail or they abdicate entirely. The player-coach model pretends to offer a third way. It doesn't. It collapses strategic direction and operational execution into a single person, creating confusion about which hat the leader is wearing at any given moment.
We believe leadership is system design, not direction-setting. When one person is expected to both set direction and execute tasks, the structure itself creates indecision. The role ambiguity generates what behavioral research identifies as avoidant authority — the tendency to delay decisions when negative consequences are anticipated [5].
The pattern is structural, not personal. Change the executive's title to player-coach. Change their desk location. Change their meeting cadence. Without changing the decision rights architecture, the system produces the same centralized behavior. The Slinky returns to the same shape.
Without changing the decision rights architecture, the system produces the same centralized behavior.
Microsoft's reorganization is the most recent example. Meta's reframing is the same pattern, earlier in the cycle. Both ask leaders to behave differently without defining what they're free to decide. Both celebrate proximity as structural progress. Neither asks the question that determines whether distributed authority is real: who decides what, within which boundaries, with which freedoms?
That is governance design work. It happens in the architecture, not in the behavior.
Sources
- Business Insider — Business Insider Today Newsletter: Microsoft Leadership Change — Microsoft leadership restructuring coverage, "rolling up sleeves" narrative
- Business Insider — Meta Block Managers as Player-Coaches and Org Leads — Meta's reframing of block-level managers as player-coaches, broader industry trend
- Business Insider — Satya Nadella Microsoft AI Leadership Reset — Microsoft AI leadership reset narrative, proximity framing
- LHH 2026 C-Suite Research — 28% cite lack of strategic clarity; decision-making as leading organizational constraint
- Frontiers in Psychology 2023: Avoidant Authority — Behavioral research on avoidant authority patterns and decision delay
Please note: 51&even is an AI-first organization. We embrace AI at every step of our value creation and build our processes with a deep integration of human-AI capability. Humans always have the last decision. But this text was heavily built with AI.