Automattic's board forces CEO Matt Mullenweg into leave of absence

9 hours ago (techcrunch.com)

> “And the biggest news: I won't be able to make the ELT tomorrow,” Matt wrote in an Announcement Slack. He continued, writing that Mark Davies, current Automattic Chief Financial Officer, has “conspired” with Automattic Board of Directors members Ann Dunwoody, Toni Schneider, and Sue Decker “behind my back and they voted to put me on a paid leave of absence. I voted against that.”

If you’re doing this type of accusation in the company wide announcements channel, odds are you’re never coming back. A board coup rarely happens without a good reason, but a “leave of absence” isn’t a firing. It’s still pretty bad, but it’s not a firing. However, crashing out and waging war on the board will lead to that outcome.

  • In recent memory of companies I've worked for, even the absolute WORST executives haven't gotten fired. They always announce that "it's time for another adventure" or "I am taking a break". So I am not shocked they didn't fire him, although the board is now probably wishing they did.

    • Had a President make a big ordeal about leaving "for health reasons". His LinkedIn had him at a new company within a couple months doing the same thing.

      Had a CISO leave for "personal" reasons. Talked to him a couple years later and yeah, he was fired.

      Steal 20$ out of a cash register and make the local news. Waste a billion dollars at a corp and make insane decisions and ride out on a golden parachute. Its a fucked up world.

      18 replies →

    • Those phrases often imply that they were fired or asked to resign - although the deniability can be useful, which is why they’re so often used. As a recent example, Fidji Simo went on leave from her role at OpenAI several months before leaving. Although I don’t know for sure, I would suppose that she was essentially fired when she went on leave, and the subsequent success of Codex after she went on leave confirmed the decision to fire her. It’s possible that, if Codex hadn’t been a success, she might have been brought back, so putting her on leave was useful for optionality.

      3 replies →

    • Firing a CEO makes your company look bad. Even if you are firing them, you don't say you're firing them.

  • He is surely very evidently mentally ill.

    This is a man who, to be fair to him, has been beneficially bullish and iconoclastic in the WP community's favour for decades, as well as writing a big chunk of what was "early modern" WP. Before he came unglued.

    The fact that he looked, sounded, talked the way he did, was involved, put his own money where his mouth is, and was press-available to the extent he was is a lot of why WordPress was ever taken seriously. Given the level of control he has, it was used pretty judiciously for the longest time.

    I am of the opinion that his broad charge against WP Engine was valid; I think he handled it insanely.

    But as I say, he has come unglued. I'd be surprised if he returns to the job. I wish him well as I think anyone who has made money because of WP should. Things have gone wrong but there was a long run of things going remarkably well.

    I do think this was overdue, for everyone including Matt, even though he evidently cannot see it. I hope, but am not hopeful as it were, that he sees that this is a message from the world to change track. I would instead expect to see a bit of revenge.

    • > He is surely very evidently mentally ill.

      I don’t think that’s accurate or helpful.

      I think he found himself in a situation that he could not cope with in a rational manner. I suspect that many people, myself included, would struggle in similar situations.

      Occasionally a person can find themselves in a place where quitting is the best option for everyone involved, but the person at the centre is so dug in that they don’t even consider the possibility.

      6 replies →

    • > He is surely very evidently mentally ill.

      I agree and upvoted your post. But can I just say that it is super-reddit to diagnose someone based on your B- undergrad psych classes.

      We should go back to the classics like "he went off his rocker!", or "he's totally unhinged!" or "completely delulu!"

      (of course the people who know, know, and they shouldn't tell you.)

    • I am saying this as someone who has had repeated and ongoing issues with WP Engine as a hosting platform: no, Matt Mullenweg was not even valid in his basic assumptions motivating his lawsuit against WP Engine. The idea that a hosting platform is leeching off the WordPress ecosystem is absurd, for two reasons:

      1. WordPress is free and open source software, developed under reciprocal licensing (GPL). Hosting companies are neither legally nor morally obligated to contribute back to WordPress core. They are already a beneficial part of the ecosystem.

      2. WP Engine was contributing back to the WordPress ecosystem, just not Matt Mullenweg's corner of it.

      WordPress is a modular platform and plugin and theme developers are just as important to WordPress's continued success as core development is. WP Engine happens to own Advanced Custom Fields (ACF), which is basically WordPress's answer to the Drupal Fields API[0]. ACF is what lets you add arbitrary fields to WordPress's page edit screen without having to write a bunch of custom metabox hooks and forms. It was a huge timesaver before things moved to page builders[1] and it's still useful even if you're using a page builder.

      [0] Formerly Content Construction Kit

      [1] Full disclosure: I hate Gutenberg. It is not WordPress, it's a React development kit tumor shoved inside WordPress. Any other page builder would be preferable.

      1 reply →

    • There's no need to diagnose Mullenweg when his behavior could easily be explained by being a run-of-the-mill arrogant asshole.

      He never seems to have broken from reality or suffered a mental breakdown. He seems to just treat people (including his employees, customers, and competitors) like garbage who are beneath him.

  • I think his recent screwing over of that custom fields plugin team and cutting off access to the plugins repo for WPengine was really a dumb move that has lead him to where he is now.

  • You very rarely fire execs these days, the main reason being you don't want them to sue the company over their loss of reputation.

    You want to keep-up appearances and leave some plausible deniability, even if it's generally BS.

  • I'm surprised that founders still care about all that stuff. They already made tons of money, who cares. None of it means anything. Nothing is fair in this society.

    They don't mind the system working unfairly in their favor; they only have an issue with it when it starts working against them. At that point, it's too late; you have no voice.

> One person speculated that the timing may have something to do with Mullenweg’s annual trip to the Burning Man festival, after which he tends to return “with ideas.”

This line is so perfectly on the nose it could be in a McSweeney's article and yet here it is in reality. We are truly on the weirdest timeline.

  • Many Burning Man guides, including the original arctic monkey guide that I first read about 20 years ago, specifically warn against making any life altering decisions for weeks after Burning Man.

    Decompression is a bitch when coming down from half a dozen psychedelics.

  • Given the long lines and the mud this year my "idea" would be to skip future festivals.

Unfortunately, this is for the best. WordPress powers a large percentage of the internet, and I'm not sure what's going on with Matt (who I've always liked) but something turned the past few years.

He's been behind unforced error after unforced error as CEO, and I hope a break helps him gain some perspective (although I don't see him being brought back).

WordPress has been his life for 23 years. Doing the same thing for 23 years likely makes it difficult to have a proper perspective.

  • "Unfortunately" for whom? I'm pretty ok, even happy, with him out.

    • The unfortunate part is that he became someone you’re happy to see out. I think he’s absolutely become a net negative for Wordpress, but that wasn’t always the case.

    • it just sucks to see someone who helped popularize something so many people care about change (at least publicly) for the worse.

  • "Unfortunately"??

    • "Unfortunately", because Matt did a lot of good for the internet over the past two decades. WordCamp is (or was) really amazing, the community he built is really great, the Automattic Lounge was cool, he's donated millions of dollars to good causes, and WordPress powers a large portion of the Internet.

      6 replies →

    • He read the commit logs and understood much of what he read. That's deep understanding of the product. That alone puts him in the top few percent of CEOs.

      IMO.

  • em-dash by Cloudflare looks interesting in terms of replacing Wordpress.

    by garnering enough of an ecosystem to cause a migration will be the bigger challenge.

    of course some people will say in the age of agents will people need to visit websites ;)

    • Am I looking at the right thing?

      https://github.com/emdash-cms/emdash

      > EmDash depends on Dynamic Workers to run secure sandboxed plugins. Dynamic Workers are currently only available on paid accounts. Upgrade your account (starting at $5/mo) or comment out the worker_loaders block of your wrangler.jsonc configuration file to disable plugins.

      Seems like a pretty poor replacement for WordPress, which will run on pretty much whatever random system happens to be within eyesight.

      1 reply →

  • > Doing the same thing for 23 years likely makes it difficult to have a proper perspective.

    Preach.

    Seems to twist perception that reality is a fractal when it's recursive and eventually exits (everything dies).

    Explains religion, politics, and similar longtermism memes.

I think it is easy to underestimate how big of a deal this is. Matt has a stranglehold on Automattic and Wordpress, it is not possible to remove his control over the ecosystem and he is volatile. Ousting him as CEO is almost certain to cause a major reaction from Matt, so, for Automattic to make this decision is a very big deal. The right decision for the long term but the hard decision. I expect we will see Matt try to punish Automattic’s board, it will get worse for Automattic before it gets better.

Here is Matt talking about his control: https://news.ycombinator.com/item?id=42657150

  • If he has 84% voting share, can't he just fire the board?

    • Firing the board is the least Matt-like option. He has absolute control and ownership over the WordPress project, I think it is more likely that he starts his own Automattic splinter company and removes Automattic from the WordPress project. I’d guess he is already filing incorporation docs for Antimatter Inc. or some other Matt themed name.

      1 reply →

    • In most venture-backed companies no, because board seats are one of the things you give major investors in exchange for their money.

      In this case? Possibly! Ann Dunwoody and Sue Decker look like independents, and he might be able to unilaterally replace either or both of them.

    • If Mullenweg attempts to fire the board that just suspended him, he would be weaponizing proxy votes against the very investors who originally granted them. While founder proxies are often structured to be irrevocable, using them to purge the board would almost certainly trigger a massive legal battle, attempts by investors to breach or revoke the proxy agreements, and severe financial instability for the company.

      While he technically holds the votes required to disband the board, executing that move would ignite a corporate civil war rather than a clean transition of power.

      1 reply →

  • I'd definitely take away his access having seen how vindictive he has been throughout the WPE saga, for everyone's sake

Long overdue. Matt needs to get some professional help or support, some of his actions have been incredibly harmful to the WordPress community.

Here is the whole saga until May 2025: https://gist.github.com/adrienne/aea9dd7ca19c8985157d9c42f7f...

I briefly worked in the web agency SaaS space and hoooo boy, I have never known a more gossipy or dramatic industry.

That’s not to pass comment either way on Mullenweg

It’s just WordPress folk are nuts.

They should have voted on if pineapple deserves to be on pizza while they were at it. The guy had to go.

I’m a bit relieved. Only knowing it superficially through its larger public actions, Automattic used to be one of the “good guys” companies to me. I envisioned myself applying there at some point. This has obviously changed over the last 1-2 years.

I don’t doubt that the good parts were largely Matt’s work, but well ... I think a lot of us followed his semi-recent public actions.

I’m a bit surprised they didn’t pull the plug earlier given they could have. Hasn’t he already caused vast damage?

Still, he has done a lot of good for the internet and world at large. I don’t want to discount that. I just hope he manages to chill a bit.

Enforced by checkboxes on every login form, no doubt. Less sarcastically: I hope his corporate access is thoroughly controlled; we've seen him in 'full force', before.

Article says no change for .org... this will almost surely become interesting.

I'm shocked. I always thought that Matt held the majority of the voting shares, and that the board of directors was mostly there as a rubber stamp.

  • Voting shares and board of directors are two different mechanisms. Just because he holds 80%+ of voting shares, doesn't mean he can control who runs the company. Shareholders can make up (elect/remove) directors on the board, the board decides who can run the company (or other officials). His vote against was likely true, but if the board is 4 seats and he only has one vote, that's 25%.

    A lot of this is pretty typical, but what's interesting is what happens next. He could just remove members of the board with his 80%+ control, and build a board that backs him. I assume they have investor agreements that prevent that.

    • Regardless of who he puts on the board, directors have legal obligations to the SEC and all shareholders. If he wants that level of control he would need to take the company private, and various investor agreements probably prevent this.

      3 replies →

I am surprised it has taken the Automattic board so long, just don't understand that.

I am so curious why now, what changed? The WPEngine saga was started two years ago.

  • from my own observations:

    a) you don't want the WPEngine case going to trial and that is coming to a decision point soon. chances are the new CEO and board settle.

    b) wordpress is being absolutely obliterated by ai. work for commercial plugin authors and agencies has dried up while the platform and ecosystem see major security issues and worms exploit a large number of sites every week.

    wordpress and automattic haven't responded to this well, at all. at times it is often straight denial.

    founder CEO distracted by expensive lawsuit while facing existential threat to project that will require complete attention and a lot of skill to steer out of

    • How is the WPEngine case going anyways?

      Glancing at the docket [1] in an attempt to answer this myself... looks like the trial is scheduled for a bit over a year from now [2].. A ton of fighting over discovery... a motion asking for fairly monster sanctions for spoilation of evidence [3] (to be argued on the 30th). Claiming in [3] with what appear to be pretty solid receipts (as far as we can see through the redactions anyways) that Matt was willfully destroying communications related to the case and subject to the discovery - and Automattic's lawyers lied to the court that they preserved them (naturally Automattic's lawyers have a reply with an entirely different interpretation of events if you go look for it... but at least at a glance WPEngine seems more convincing).

      [1] https://www.courtlistener.com/docket/69221176/wpengine-inc-v...

      [2] https://storage.courtlistener.com/recap/gov.uscourts.cand.43...

      [3] https://storage.courtlistener.com/recap/gov.uscourts.cand.43...

    • Just side note that AI is not destroying one of the largest e-commerce platform, Woocommerce on top of Wordpress.

  • Unless there's a full on scandal or emergency, boards don't force CEOs out quickly. This would have been building for years with multiple rounds of trying to de-escalate and get the situation under control.

  • Probably back room deal between Wordpress board/management and WPEngine board/management. It's a safe bet that WPEngine was destroying Wordpress legally simply because their CEO doesn't suffer from verbal diarrhea and actually shuts up when the lawyers tell him to.

    If you get Matt out of the way, you can ink a deal and resolve everything so that even if Matt pulls something else, there are contracts in place that can't be gotten rid of so easily.

This is fantastic news. Matt is an ass and unfit to lead a small HOA, let alone a company and open source project.

> One person speculated that the timing may have something to do with Mullenweg’s annual trip to the Burning Man festival, after which he tends to return “with ideas.” This year’s festival ended on September 7.

HN needs to allow some html in comments so we can put ‘lmao’ in <blink> and <marquee> tags

>Most recently, Automattic attempted to claim it owns the word “automatic.”

What is wrong with these people?

Good, get him the fuck away from Wordpress. Though frankly, a better solution might be for businesses to ask themselves whether or not they need Wordpress anymore.

In the mean time, if you're unable to derisk Mullenweg out of your business stack, this is a good first step.

  • WordPress dominance of the web has certainly peaked, but history indicates there will be several years in which to continue to extract comfortable profits while riding it down. e.g. Oracle, a database that almost no business has actually needed in decades.

    • I'm not convinced that sort of legacy lock in exists in the web space. It moves fast and its value is in the content. In the age of AI, migrating that data makes it trivial to move away from a risky platform. I cut my development teeth on WP and managed some fairly large sites. There are far more interesting and well developed alternatives out there.

      3 replies →

The best line was buried at the bottom. Did Automattic really attempt to claim it owns the word “automatic?

  • This is better explained elsewhere in this thread, but it boils down to a totally valid trademark dispute over a company calling itself Automatic.css which supplies services for WordPress installs.

If the board is going behind his back... then how does he know he was put on leave?

Anyone could have forked WordPress at any time or spun up their own multi tenant instances if they were truly concerned, this just seems personal. It’s a bad day for founders IMO.

  • it's personal only in the sense that Matt had been doing an absolutely awful job leading the company for several years, and the board had fiduciary obligations to intervene

    this is not a bad day for founders; it's Matt having gotten to the end point of his value as a leader

    Don't get me wrong: getting to a point where you have 2,000 employees and a 7 billion dollar valuation is a massive accomplishment. He was clearly very effective at various parts of the company's history. But it scaled beyond the point where his skillset and personality could continue to credibly steer the ship

  • The entire saga started due to WP Engine "forking" WordPress.

    • So problem solved? My only criticism is that 1) Mr. Mullenweg should have held tighter controls over the IP and 2) the direction to the community that they are encouraged to use "WP" as a prefix for their business names and products was ultimately a bad one leading to this mess..

      2 replies →

    • WP Engine's "forking" consisted of disabling the revisions feature by default.

      As someone who's personally been bitten by this particular WP Engine misfeature, describing this as a "fork" is disingenuous at best. The average Linux distro ships way more out-of-tree changes than WP Engine ever did.

      1 reply →

> Most recently, Automattic attempted to claim it owns the word “automatic.”

Real austin powers vibes

> He would make outrageous claims like he invented the question mark.

  • It's a little less dramatic than that. They did send a demand letter to automatic.css saying that since 'automatic' and 'automattic' differ by only one letter, are pronounced the same, and are marketed to similar groups the name is likely to cause confusion, hence automatic.css should change its name.

    Which is not the same thing as claiming the word automatic generally.

    Personally it sounds like a loser if they took it to court since (a) automatic is a common word and (b) they already asked automatic.css to add a "not affiliated with word press" disclaimer (which automatic.css did add). IANAL.