Automattic's CEO Matt Mullenweg Reclaims Control After Board Overthrow Attempt

Power Struggle at the Helm

What started as a routine corporate governance issue has evolved into one of the most significant leadership conflicts in recent tech industry history. Automattic's board, which oversees WordPress.com and WooCommerce, recently attempted to remove CEO Matt Mullenweg from his position. The move, however, backfired spectacularly, resulting in a complete shake-up of the board and Mullenweg's swift return to power.

"The board's decision was based on concerns about leadership direction, but it ultimately led to a situation where Matt had to reassert control," said one insider familiar with the situation.

The conflict unfolded over several days. On September 9th, Automattic's board voted to place Mullenweg on a paid leave of absence. This action was quickly followed by a dramatic reversal: within 36 hours, Mullenweg had reasserted his authority and returned to his position as CEO.

Board Changes and Internal Reckoning

The aftermath of the failed ouster has been nothing short of tumultuous. Multiple board members have resigned or been removed, including founding CEO Toni Schneider, who had previously led Automattic before transitioning to Bluesky. His departure from the board is particularly significant given his role in the company's early days.

Additional departures include Sue Decker and General Ann Dunwoody, both of whom were vocal supporters of the vote to put Mullenweg on leave. The removal of these key figures has effectively ended the board's attempt at removing him.

The Human Cost of Corporate Battles

This dramatic episode reflects broader tensions in the open-source software ecosystem. Mullenweg, known for his role as the founder of WordPress, has long been a central figure in the community. The conflict highlights how deeply personal these issues can become when core values clash with corporate governance structures.

As one observer noted: "What we're seeing here is not just a boardroom battle, but a philosophical conflict about how open-source projects should be managed and led."

The implications of this situation extend far beyond Automattic's immediate operations. The software that powers over 40% of the web is now under new leadership following what many are calling an internal coup attempt.

Legal Tensions and Public Disputes

The board's decision to remove Mullenweg was reportedly influenced by concerns about his leadership approach, particularly in light of ongoing legal battles. Mullenweg has been embroiled in a high-profile lawsuit with WP Engine, a WordPress hosting provider that has accused Automattic of attempting to implement royalty fees on competitors.

Earlier this year, WP Engine claimed in court filings that Automattic had plans to target other competitors with royalty fees. More recently, they've alleged that Mullenweg destroyed evidence related to the case through apps like WhatsApp and Signal. These legal disputes have undoubtedly added pressure to the situation.

In a separate development, Mullenweg had deactivated several WordPress contributor accounts over allegations of planning a fork of the open-source software. While this move has been defended by some as necessary for project stability, it has also drawn criticism from community members who view it as an overreach.

Corporate Governance in the Open-Source Era

This incident raises important questions about corporate governance in the context of open-source software. Traditional board structures, designed for profit-driven enterprises, may not be well-suited to managing projects that rely heavily on community involvement and ideological alignment.

The rapid succession of events demonstrates how quickly tensions can escalate when there's a mismatch between leadership vision and board expectations. In an industry where community trust is paramount, such conflicts can have long-term consequences for a company's reputation and user base.

"We are seeing the beginning of a new model for managing open-source projects," said an analyst specializing in technology governance. "This conflict has highlighted the need for more transparent decision-making processes that account for both corporate interests and community values."

As Automattic moves forward under Mullenweg's leadership, all eyes will be on how the company navigates this delicate balance between board oversight and operational autonomy.

What Comes Next for Automattic?

The future of Automattic remains uncertain, but it is clear that the company has entered a new phase. With Mullenweg back in control, the focus will likely shift toward rebuilding trust with both employees and the broader WordPress community.

Industry observers are watching closely to see how the company's leadership approach evolves in light of these challenges. Will this be a turning point for corporate governance in open-source projects, or will it simply represent a brief episode in the ongoing evolution of digital platforms?

The board changes and internal upheaval that followed the failed ouster suggest that significant reforms may be on the horizon. As Automattic begins to chart its course forward, the lessons learned from this conflict will undoubtedly influence how similar challenges are handled in the future.

A Broader Impact

This story resonates far beyond the boundaries of a single company. It reflects the growing complexity of managing software projects that operate at the intersection of commercial interests and community values. For investors, it's a reminder that even seemingly straightforward corporate governance decisions can have cascading effects across entire ecosystems.

For users, the situation underscores how critical it is to understand not just what software does, but who controls it and how decisions are made. As WordPress powers an estimated 40% of all websites on the internet, its governance model serves as a case study for the broader tech industry.