Three Days That Exposed a Structural Problem

On September 14, 2026, Automattic confirmed that Matt Mullenweg had been reinstated as chairman and chief executive, just three days after its own board placed him on paid leave and installed a replacement. The reversal was not accompanied by any substantive public explanation. A company spokesperson confirmed the reinstatement to TechCrunch's Sarah Perez, and that was essentially the full record. No governance post-mortem, no board statement, no disclosed rationale for either the removal or the return. For a company that operates WordPress.com and underpins a significant share of the public web's content infrastructure, this is not a minor personnel shuffle. It is a visible failure of organizational authority under conditions that are specific to algorithmically-mediated platforms.

Why Platform Governance Is Not Standard Corporate Governance

Classical organizational theory assumes that authority structures are legible to the people inside them. Principals issue directives, agents execute them, and the chain of command functions as a coordination device because everyone understands the rules (Kellogg, Valentine, and Christin, 2020). The Automattic situation breaks this assumption in an interesting way. Mullenweg's authority at Automattic was never purely positional. It was partly structural, rooted in his stewardship of the WordPress open-source project, which sits outside Automattic's corporate boundary entirely. The board's decision to remove him created an immediate competence gap that had nothing to do with his individual performance and everything to do with the fact that the platform's legitimacy is tied to a single person's standing in a community the board does not control.

This is a governance topology problem, not a governance topography problem. The board understood the organizational chart well enough to execute a removal. What it apparently did not understand was the structural relationship between Automattic's commercial operations and the open-source ecosystem that gives those operations their value. Knowing the shape of the authority structure is different from understanding how coordination actually flows through it. That distinction matters for organizational theory in ways that standard principal-agent models do not capture.

The Awareness-Capability Gap Inside the Boardroom

My dissertation research focuses on a gap that appears consistently in algorithmically-mediated environments: workers and decision-makers develop awareness of the systems they operate inside, but that awareness does not translate into effective action. The Automattic board presumably understood, at some level, that Mullenweg occupied a unique position. The reversal three days later suggests that understanding was insufficient to anticipate the consequences of the removal before executing it. This is not an unusual failure. It is structurally predictable.

Rahman (2021) describes how platform architecture creates invisible constraints on worker behavior that are difficult to see from inside the system. The inverse problem applies here: governance actors inside a platform organization may be equally constrained by invisible structural dependencies they cannot fully perceive until they test them. The board tested the constraint by removing Mullenweg. The constraint became visible. The reversal followed. This is a costly and inefficient way to map organizational topology.

What Mullenweg's Return Does Not Resolve

The reinstatement does not fix the underlying problem. What the three-day episode revealed is that Automattic has no clear governance schema for managing the boundary between its corporate authority and its open-source legitimacy. Schor et al. (2020) note that platform workers face structural precarity not because their individual positions are unstable but because the rules governing their participation can shift without warning. The same logic applies to platform executives whose authority is partially external to the organization. Mullenweg's position is structurally precarious in a way that no corporate title can fully stabilize, because the community legitimacy that makes his title meaningful is not something the board grants or withdraws.

This has practical implications for organizational design. Companies built on open-source foundations, or on any infrastructure where technical authority is distributed across a community rather than concentrated in a corporate hierarchy, cannot treat governance as a purely internal matter. The schema required to govern effectively in these settings is not a routine one. It requires adaptive expertise in the sense that Hatano and Inagaki (1986) describe: understanding why the system works the way it does, not just how to operate its formal procedures. The Automattic board appears to have had the latter without the former.

The Broader Lesson for Platform Organization Theory

The Automattic case is a useful data point for anyone thinking about authority in platform contexts. It shows that governance failures in algorithmically-mediated organizations are not always the result of bad actors or missing rules. They can emerge from a structural mismatch between formal authority and functional legitimacy, a mismatch that only becomes visible under stress. For organizational theorists, the interesting question is not what the board should have done differently in procedural terms. It is whether the governance schemas available to boards of platform companies are adequate to the structural complexity these organizations actually exhibit. Based on three days in September 2026, the answer is not obviously yes.