Automattic has rebuilt its board after a failed September attempt to put founder-CEO Matt Mullenweg on paid leave, installing four new directors and several advisers at the parent company of WordPress.com, WooCommerce and Tumblr. TechCrunch reported that the new board includes author Hugh Howey, author and entrepreneur Amy Chan, and IRL co-founders Henry Khachatryan and Krutal Desai; Mullenweg confirmed the additions. Why it matters is larger than one company’s org chart: Automattic sits inside a broad web-publishing and commerce ecosystem, so a board fight at the center raises practical questions about who can check the CEO, how succession works, and what customers and partners should assume in a crisis.
The short answer is that the reset is more likely to restore speed than to restore independent oversight. A founder who says he controls about 84% of the company’s voting power can end ambiguity quickly. That same concentration of control makes it harder for outsiders to know how serious disagreements will be handled when directors and the founder do not agree.
Control returned faster than transparency
The immediate sequence was unusually stark. In September, Automattic’s prior board voted to place Mullenweg on leave and sought to remove him from the board. According to Automattic’s own statements as reported by TechCrunch, he returned to control roughly 33 hours and 20 minutes later. He then removed or accepted the resignations of directors involved in the action and replaced other senior leaders, including CFO Mark Davies and chief legal officer Andy Missan.
The prior board included Toni Schneider, General Ann Dunwoody and Sue Decker. Schneider resigned after the failed leave attempt, Mullenweg removed Dunwoody, and Decker also resigned. Davies had been named interim CEO during the attempted leave, but Mullenweg returned and Davies was later let go. The company also changed litigation counsel amid its continuing dispute with WP Engine.
The unresolved point is the most important one: the earlier board never publicly explained why it tried to sideline Mullenweg. That gap limits how much confidence anyone should place in a simple hero-or-villain version of events. What is clear is the mechanism. Legal voting control and board oversight are not the same thing. A board can attempt to intervene, but a founder with overwhelming voting power may still decide the outcome if the company’s governance documents and vote structure allow it.
That can be a strength when the main danger is paralysis. It is less comforting when the risk is that a board may need to press a hard challenge to the CEO. The new advisers — former Woop CTO Jaime Waydo, June co-founder Matt Van Horn, and KISSmetrics co-founder Hiten Shah — may help restore operating and product counsel around Mullenweg. They do not answer the questions the episode exposed: why the leave was attempted, how the new directors were selected, what their mandate is, whether the company has committee structures with real teeth, and how conflicts will be handled.
Automattic’s public board page has not necessarily kept pace with the internal changes. That does not prove the old board still governs. It does show a disclosure lag at a moment when outside stakeholders are being asked to trust that a fresh governance structure is in place.
Why this matters beyond one private company
Automattic is not a typical private software company that can absorb a governance rupture with little outside notice. Founded in 2005, it says it has more than 1,447 employees across 81 countries. Mullenweg co-created WordPress and has served as Automattic’s CEO since 2014. The company runs WordPress.com and owns or operates WooCommerce, Tumblr and other products used by publishers, merchants, agencies and developers.
That does not mean Automattic owns the open-source WordPress project. The software project has a separate community and governance structure, and there is no public evidence in the supplied reporting of a WordPress.com outage or an immediate change to the open-source project itself. Even so, the distinction does not make Automattic’s governance problems irrelevant. Commercial hosting, support, plugins, payments, commerce tooling and enterprise relationships sit alongside the open-source ecosystem, and confidence in those businesses depends in part on whether the company can handle internal conflict without a cascade of executive departures.
This is where founder control cuts both ways. Supporters can reasonably look at the past month and see continuity: Mullenweg regained authority quickly, named a functioning board and advisers, and said the mission and priorities remain unchanged. For employees and customers who mostly care about product delivery, that kind of clarity can be reassuring.
But the same facts also support the opposite concern. Multiple directors and senior officers left or were removed, the reasons for the original intervention remain undisclosed, and the replacement board appears to have been assembled through a process the company has not publicly explained. That is not proof that the new board lacks value or capability. It is a reminder that outside stakeholders have limited visibility into how challenge, dissent and succession will work in practice.
What employees, customers and partners should watch
The next signals are likely to come from operating behavior, not rhetoric. First, watch senior-leadership turnover. Founder-led companies can work well with concentrated control, but repeated exits in finance, legal, product or people functions would suggest the September rupture is still moving through the organization.
Second, watch formal governance disclosure. An updated board roster, clearer committee responsibilities, conflict-of-interest standards and any public succession planning would do more to rebuild trust than broad assurances about mission. The new board may stabilize operations; it has not yet shown how it would provide visible oversight.
Third, watch whether commitments to customers and partners remain boring in the best sense of the word. WordPress agencies, merchants and enterprise buyers should distinguish Automattic’s commercial services from the open-source project, then review contingency plans for hosting, plugins, payments and support. No public record now shows a service disruption. Risk management here is about resilience if leadership turnover, litigation pressure or strategy shifts later begin to affect roadmaps, partner policies or support quality.
The WP Engine lawsuit belongs on that watchlist, but carefully. The litigation adds pressure, and the change in counsel shows that legal strategy is also in motion. What the public record does not show is that the lawsuit caused the board rupture. For now, those are parallel stressors, not a proven chain of cause and effect.
In the short run, Automattic’s founder-controlled board reset looks stabilizing because it settles who is in charge. The longer-run test is different. It is whether the company can show employees, customers and the wider WordPress business ecosystem that it can survive disagreement with credible oversight, clearer succession planning and less reliance on one person’s voting power and intervention.
By
By
By
By
