Mullenweg has returned as CEO after attempted board ouster
summary
Matt Mullenweg has regained his position as CEO of Automattic after a brief and chaotic attempt by the company's board to remove him. The board initially voted to place him on leave, but Mullenweg resisted the ouster by seizing control of internal communications. This power struggle ended with the company officially confirming his return to leadership with full board support.
key points
- The board of Automattic attempted to remove Mullenweg by placing him on leave and appointing an interim CEO, but the move failed due to his refusal to depart.
- Mullenweg utilized internal Slack channels to communicate directly with employees and remove other administrators, effectively bypassing the board's authority.
- The company eventually conceded and restored Mullenweg to his role, noting that the entire conflict lasted only about 33 hours.
who should read it
People interested in corporate governance, tech industry leadership disputes, and the history of WordPress and Automattic.
discussion skeptical
consensus
Commenters generally agree that the power struggle at Automattic is driven by a disparity between legal authority and technical control. They argue that while the board may have the legal right to remove the CEO, the CEO's possession of system keys and administrative access creates a 'de facto' power that can override formal corporate governance. The sentiment is largely skeptical of the board's ability to quickly resolve the situation without significant legal or criminal intervention.
top insight
The comparison to the ARM China 'chop' incident illustrates that technical or physical possession of authorization tools—whether a digital root password or a physical seal—can supersede legal contracts in the short term. This highlights a systemic vulnerability in corporate structures where operational control is concentrated in a single individual, making the removal of a founder-CEO practically impossible without their cooperation or a slow court process.
Generated by an LLM from the article and thread. Check the sources before relying on it.