What happened at Automattic this week
it probably felt less like reading a clean corporate update and more like watching three different versions of the same announcement arrive in the wrong order, if you were trying to follow the Automattic story in real time. One moment, Matt Mullenweg was being pushed out of the day-to-day picture. A short time later, the message around his role had shifted again. By the end of the week, the basic question had become hard to answer with confidence: who was actually in charge at Automattic, and which statement should anyone believe?
That confusion came from the fact that this wasn’t just a private company squabble. Automattic sits near the center of the WordPress world, and that means any internal fight tends to spill into the open fast. Board decisions matter. Company chat matters. Public posts matter too, because people read them as signs of where control really sits. The whole thing gets messy in a hurry, when those three channels disagree.
The first version of the story was formal and cold. And the company framed it as an internal leadership change, given the board made a move that sidelined Mullenweg. Then the tone changed. Public messaging started to move around, and the picture that had looked settled for a moment suddenly seemed unfinished. Within days, the question wasn’t just whether a board had acted. It was whether that action actually held, or whether other channels inside the company were telling a different story.
When formal governance and informal communication point in opposite directions, the real dispute is often about control, not wording.
That’s what made this week so strange. A board can issue a decision on paper, but a modern company also lives inside Slack channels, social feeds and quick-fire replies that can change how a story lands before the official release’s even cooled. In Automattic’s case, those parallel spaces appear to have pulled the narrative in different directions. One audience saw a board making a hard call. Another saw Mullenweg still speaking and acting like he had influence over the company’s operations. A third saw a swirl of posts and reactions that seemed to change every few hours.
For anyone outside the company, the hard part was separating what had been decided from what had been said. That gap matters. In a normal corporate dispute, the boardroom announcement usually sets the tone and the rest follows. Here, the public-facing message and the internal posture didn’t stay neatly matched for long. That’s why the story spread so quickly through the WordPress system. People weren’t just reacting to a leadership shake-up. They were trying to figure out whether Automattic’s governance, its internal communications and its public claims were all describing the same reality.
And that uncertainty’s where the rest of the week gets interesting. The board’s action was only the first move. What happened after that, inside company channels and out in public, turned the whole episode into a test of who could actually speak for Automattic. The next part of the story starts with that board decision, because that’s where the formal version began.
The board’s September 9 move
On September 9, the Automattic board took the kind of action that sends every internal rumor mill into overdrive. Matt Mullenweg was placed on paid leave, and the company did not publicly spell out the reasons behind that decision. At the same time, Automattic’s CFO, Mark Davies, was named interim CEO.
That sequence matters because it was the first formal move in the dispute, and it arrived with very little explanation attached. No sprawling memo. No long public case file. Just a decision from the Automattic board and a quick change at the top.
By the account that later circulated, Mullenweg wasn’t given much time before the meeting. He was told only shortly beforehand and asked for more time so a lawyer could review the proposed move. That request was rejected. So whatever was discussed in the room, he did not get the sort of slow, lawyer-approved runway that executives usually prefer when a board is about to reshuffle the top job.
When a board acts quickly and says little, the silence can do as much work as the decision itself.
At the same time, the first company statement matched that mood. It was brief, formal, and careful. The message didn’t try to explain the dispute in public or walk readers through every concern behind the leave decision. Instead, it presented the change as a matter of confidence: confidence in Davies, and confidence in the rest of the team to keep the company running.
That wording does a lot of heavy lifting without sounding dramatic. By naming Mark Davies as interim CEO, the board signaled that the company still needed day-to-day leadership and that the finance chief was the person they wanted in the seat, at least for the moment. And by saying they had confidence in him and the team, the statement also tried to keep the focus on continuity rather than conflict. It read less like a public argument and more like a controlled handoff.
Of course, controlled handoffs rarely stay controlled for long when the person being sidelined is still very much part of the company’s public identity. The board’s action created a formal answer to one question, who would run Automattic in the short term, but it left a larger one hanging in the air: what exactly had changed, and how far did that change reach?
That uncertainty is what made the September 9 move so messy. On paper, the board had acted. In practice, the story was only getting started. A paid leave can sound tidy in a press release, yet it often carries awkward edges in real life. Is the person fully cut off from company operations? Is the leave temporary or disciplinary? Who’s speaking for the business, and who’s simply speaking from habit? The statement didn’t answer those questions, which meant other channels were about to fill in the blanks.
There was also the matter of tone. The first note from the company was stripped down to its essentials. It didn’t sound like a victory lap, and it didn’t sound like a reconciliation either. It sounded administrative, almost dry. That dryness may have been intentional. A plain statement can be an attempt to reduce noise, when a board is making a move this sensitive. But in a case like this, a plain statement can also invite everyone else to start guessing.
And guess they did.
For anyone inside Automattic, the board’s move set off the kind of questions that tend to travel fast in chat threads, private messages and coffee breaks. What had been decided? Who knew in advance? Why was Mullenweg told so late? And it works. Why was the request for legal review turned down? Even without public answers, those questions were already enough to turn an internal governance action into a company-wide event.
The timing made it worse. Because the leave and the interim appointment happened together, the board’s decision was not just about removing one person from active control. It was also about putting someone else in place immediately, before confusion could spread too far. That part is easy to miss. Boards usually like continuity. They dislike a vacuum even more. Naming Davies was a way to say, in effect, “the company still has a pilot.” Whether everyone accepted that framing was another matter.
All of this set up the next phase neatly enough. The formal board move happened first. Then the questions moved into the company’s own communication channels, where the situation stopped feeling like a board decision and started feeling like a live fight over who could speak for Automattic at all.
Why Slack became the real battleground
The board’s move on September 9 may have been formal, but the argument didn’t stay formal for long. Once Matt Mullenweg was put on paid leave and Mark Davies stepped in as interim CEO, the obvious question was whether that decision had actually changed who could direct the company day to day. On paper, yes, and in Slack, things looked much murkier.
That mattered because Automattic hadn’t cut Mullenweg off from its internal chat. So while the board had shifted titles. He still had a working channel into the company’s busiest room. At that point, Slack wasn’t just a messaging tool. It was the place where employees could see what looked like live leadership in real time, with all the awkwardness that comes from a fight over authority playing out in public view.
In a company dispute, the chat app can end up sounding louder than the boardroom.
From there, the story got stranger. Mullenweg reportedly removed other Slack admins and posted that he was back in charge. That kind of message does more than announce confidence. It tells everyone in the room to treat the hierarchy as settled, even when the company itself hasn’t said the same thing yet. The gap between his posts and the formal corporate position’s what made the whole episode feel so slippery. Was he actually back in control, or was he just speaking as if he were?
That distinction sounds picky until you remember how much work happens inside Slack at a company like Automattic. For a distributed business, internal chat isn’t background noise. It’s where people ask who owns what, who should answer which questions and which decisions are now valid. If the old boss is still able to post, react, and strip admin privileges, then the usual signals of a leadership handoff get blurry fast. The board can issue a statement. Employees can still be staring at a screen that tells a different story.
The weirdness was amplified by timing. Mullenweg’s messages landed before there was any matching company-wide confirmation that he had been restored to his former role. That left room for two very different readings. One was that the board’s earlier action had already unraveled behind the scenes. The other was simpler, and probably more boring: he still had access to Slack, and access can look a lot like control when you’re reading rapid-fire updates from a company founder with a long history of calling the shots.
That’s where the public confusion really came from. People watching the situation outside Automattic weren’t looking at a neat governance story with a clean before-and-after. They were watching a live dispute in which the official record, the internal messages and the social media chatter didn’t line up neatly. Some coverage treated Mullenweg’s posts as proof that he had regained authority. Others were more cautious, reading them as a sign that he was still trying to define the story before anyone else did. Both reactions made a certain amount of sense, which is usually a sign that the facts on the ground are still moving.
The open source angle added another layer to the mess. Automattic isn’t some tiny private shop where a founder can quietly disappear for a week and return with everything sorted. It sits close to WordPress, and that makes its leadership drama feel less like a standard executive shuffle and more like a question about stewardship, communication and who gets to speak for the company when the stakes spill beyond payroll and org charts. When the messaging turns chaotic inside a company tied so closely to open source infrastructure, every ambiguous post gets read two or three times.
What made Slack so useful, and so messy, is that it offered no pause button. The board could deliberate. Legal review could stall. Press statements could arrive in neat paragraphs. Slack, by contrast, rewards immediacy. A message there can sound official even when it isn’t, especially if it comes from the person who built the company’s culture or held power for years. That’s part of why Mullenweg’s posts carried so much weight. They didn’t just report a position. And they tried to create one.
For readers trying to make sense of it, the simplest summary was probably this: the company had one answer on paper and another answer in its chat windows. Until those answers matched, nobody looking from the outside could say with confidence whether the board’s move had changed the power structure or only the paperwork. That uncertainty, more than any single statement, is what kept the story moving. The next question was no longer just who had been put on paid leave. It was who was speaking for Automattic now, and who the rest of the company was willing to follow.
Support, skepticism, and what it means for WordPress
Once the Slack drama spilled outward, the replies split into familiar camps. Inside Automattic, Mary Hubbard, who leads WordPress, backed Matt Mullenweg publicly and pointed to Automattic’s role in funding and keeping WordPress running. That argument matters because Automattic isn’t just another software company with a loud founder and a busy chat app. It helps support the wider project, and any wobble at the top can raise uncomfortable questions about continuity.
When company leadership gets messy, people stop debating policy and start reading tone.
Several Automattic employees also posted supportive remarks, and Mullenweg quickly pushed those comments back out across social media. The effect was less a polished campaign than a rolling show of loyalty. One person says he has support, another repeats it, and then the whole thing gets quoted, reposted, and re-posted again until it feels like the internet’s being asked to vote by applause. That may have helped him project control, but it also invited the obvious question: if the position is settled, why does it need so much reinforcement?
A later official statement tried to close the loop by saying Mullenweg was chairman and CEO again, with board support. The tone was noticeably looser than the first announcement. Gone was the restrained, corporate language of the initial leave notice. In its place was something that read more casual, almost offhand, as if the company had decided formal phrasing was getting in the way of the message. That shift tells you a lot about how the dispute was being managed. The facts did not just change. So did the style, and style often reveals who thinks they have the upper hand.
Outside Automattic, the reaction was much less deferential. Some people in the WordPress community mocked the repeated displays of support, especially the way employees and executives seemed to be lining up to state the same thing in slightly different words. Others treated the whole episode as a pretty awkward spectacle for a project that presents itself as open, distributed and built for public trust. If the company at the center of WordPress funding and infrastructure can’t keep its own story steady for a week, people notice. They may even crack jokes about it.
That skepticism is not just gossip. WordPress sits in a strange place. It’s open source, community-driven, and widely used, yet a lot of practical support still runs through Automattic and the people who steer it. So when company leadership turns into a public squabble, the argument reaches beyond one firm’s boardroom. It touches contributor confidence, funding expectations and the basic assumption that the people with the biggest say are acting in a way the rest of the system can live with.
Naturally, by the end of this episode, the real dispute looked less like a simple title fight and more like a contest over who controls the message, who gets to define stability, and how much faith the WordPress world should place in Automattic’s version of events. Titles can be restored quickly on paper. Confidence takes longer.
