If your team operates remotely, there is a 98% chance you are currently stuck in a productivity purgatory known as "Level 2." You might have traded the physical office for a home setup, but your day is still defined by constant interruptions, back-to-back video meetings, and an exhausting pressure to prove you are working. In this Automattic 5 levels of distributed work case study, we will deconstruct exactly why most remote teams fail to achieve true autonomy and how the most successful distributed companies break free from these legacy habits.

The shift to remote work was supposed to unlock unprecedented freedom and focus. Instead, for many organizations, it merely digitized the worst parts of the traditional office. To understand how to fix this, we have to look at companies that have mastered the digital medium from the ground up. Automattic, the company behind WordPress, operates with over 1,100 employees spread across 75 countries without a single central office. Their success is not accidental; it is the result of intentionally moving up a specific hierarchy of operational maturity.

Understanding Matt Mullenweg Remote Work Philosophy

The foundation of this framework comes directly from the CEO of Automattic. On the Sam Harris podcast, the Matt Mullenweg remote work philosophy was outlined as the "5 Levels of Autonomy." This framework provides a crucial diagnostic tool for companies trying to figure out why their remote operations feel so painful and disjointed.

Mullenweg estimates that an overwhelming 98% of companies are currently trapped at Level 2. At this stage, organizations are simply recreating the analog office in a digital space. They port over 9-to-5 schedules, demand immediate responses on Slack, and rely on synchronous video calls to solve every problem. It is a skeuomorphic approach to work—designing a new system to look exactly like the old, outdated one.

The data backs up the pain of Level 2. Atlassian’s internal behavioral science group, the "Team Anywhere Lab," recently studied Fortune 500 executives leading distributed teams. They uncovered a staggering reality: only 13% of executives felt their teams had clarity on the work that needed to be done. Furthermore, while 71% of knowledge workers work away from an office at least once a week, only 51% are provided with dedicated remote collaboration tools by their company. Teams are being asked to do next-generation work with last-generation workflows.

To escape this trap, teams must stop mimicking the physical office and start leveraging the unique advantages of the digital medium. This requires a fundamental shift in how we view communication, tooling, and trust. If you are constantly battling Work About Work: The 2026 Coordination Crisis, your team is likely suffering from Level 2 stagnation.

The Paradigm Shift: Distributed vs Remote Work

Before a team can progress, they must understand the critical difference between distributed vs remote work. These terms are often used interchangeably, but they represent entirely different operational mindsets.

Remote work is merely a location change. It implies that there is still a "center"—a main office where the real work and decision-making happen—and that some employees are simply dialing in from afar. In a remote-first setup, the remote workers are often second-class citizens, missing out on watercooler conversations, impromptu whiteboard sessions, and vital context.

Distributed work, on the other hand, is an operational change. A distributed team assumes there is no center. The digital workspace is the office. Every process, communication, and tool is designed with the assumption that no two people are in the same room. When you shift from remote to distributed, you stop trying to replicate the conference room and start building persistent, shared digital spaces.

This is where the friction of Level 2 becomes obvious. If you are using a video tool that separates the conversation from the work (like having a Zoom window open while everyone tries to individually navigate a separate Figma or Miro board), you are enforcing a remote mindset, not a distributed one. You are forcing your team to bridge the gap between tools mentally, which leads to massive cognitive load. In fact, Context Switching Costs Remote Teams 5 Weeks a Year. Distributed work requires unified, high-bandwidth environments where the conversation and the canvas exist in the exact same space.

Escaping Level 2 in the Automattic 5 Levels of Distributed Work Case Study

Moving from Level 2 to Level 3 in the Automattic 5 levels of distributed work case study requires teams to fully embrace the digital medium. Level 3 is the crucial stepping stone where teams start to rely on shared documents, persistent workspaces, and visible workflows rather than relying on meetings to transfer information.

At this stage, organizations must confront Conway’s Law. Coined in 1968, Conway’s Law states that organizations inevitably design systems that mirror their internal communication structures. A recent empirical study by Harvard Business School on product and organizational architectures proved this true: distributed teams with fragmented communication produce highly modular, disjointed products.

"Organizations which design systems... are constrained to produce designs which are copies of the communication structures of these organizations." — Melvin Conway

For modern teams, this means that highly fragmented communication tools—using separate apps for video, chat, and whiteboarding—will result in a fragmented, disjointed product. To combat this, elite distributed teams employ the Inverse Conway Maneuver. They intentionally design their communication spaces to mirror the integrated, seamless product they want to build.

This is the core idea behind Coommit. The team meets on video in a shared room around its docs, designs and websites, so the conversation happens next to the work instead of in a separate app. People keep producing in their usual tools; what becomes shared is the moment where the team reviews that work and decides. That shared structure drives cross-functional alignment and makes Level 3 autonomy easier to reach.

Applying Gall's Law to Reach Levels of Autonomy Remote Work

As teams look toward Level 4 (asynchronous communication by default) and Level 5 (nirvana, where the distributed team outperforms any co-located team), they often make a fatal error. They try to implement massive, complex asynchronous workflows and multi-tool agile frameworks from day one.

This violates a fundamental principle of systems design known as Gall's Law. Originating from John Gall's 1975 book Systemantics, Gall's Law states:

"A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works."

Remote teams frequently fail because they over-engineer their processes. Gall's Law dictates that remote teams must start with a simple, high-bandwidth baseline and let complex async rules evolve naturally over time. You cannot force a team into Level 4 autonomy by handing them a 50-page handbook on async etiquette and a dozen specialized SaaS tools.

Instead, you must establish a simple system that works. A shared room where the team meets on video around its work is a simple baseline. It allows teams to collaborate in real-time with high fidelity when needed, establishing trust and shared context. Once that shared context exists on a persistent canvas, the team can naturally start interacting with that canvas asynchronously. The AI built into Coommit helps bridge the two modes: it answers questions during the call, and afterwards it writes a recap with the decisions, risks and tasks that the team can pick up asynchronously. If you want to dive deeper into how to structure these workflows, review our guide on Async Communication Best Practices for Remote Teams.

Actionable Steps to Level Up Your Distributed Team

Understanding the theory behind the levels of autonomy remote work offers is only half the battle. To actually move your team up the hierarchy, you need strict, enforceable boundaries around how time and tools are used.

To combat distributed fatigue and the endless cycle of Level 2 meetings, Atlassian's scientists recommend strict timeboxing. Their research suggests a highly structured week:

Implementing these caps requires a toolset that supports efficient collaboration. When your video meetings are passive, you need more of them to get everyone on the same page. When your meetings are active work sessions—where the team is moving digital sticky notes, mapping architectures, and making decisions on a live canvas—you need fewer of them. The meeting stops being a status update and becomes a high-leverage production session. For a blueprint on structuring this time, explore How to Build a Remote Work Productivity System in 2026.

Furthermore, give your meetings one home. Every time a team member has to switch from a video window to a browser tab to a project management tool in the middle of a discussion, context is lost. In Coommit, the team brings that work into the room instead: the doc, the design or the website sits on the canvas, the discussion happens around it, and the built-in AI writes a recap with the decisions, key points, risks and tasks when the call ends. The tools stay the same; the context stops getting lost between them.

Conclusion

Escaping the trap of recreating the physical office requires intentionality. As the Automattic 5 levels of distributed work case study demonstrates, true autonomy is not achieved by simply sending everyone home with a laptop and a Zoom account. It is achieved by fundamentally rethinking how communication, tools, and time intersect in a digital-first world.

By understanding the difference between remote and distributed work, applying the Inverse Conway Maneuver to your tool stack, and respecting Gall's Law by starting with a simple, unified workspace, your team can break free from Level 2. The future of work belongs to teams that use integrated platforms to turn passive meetings into productive, collaborative work sessions. Stop fighting your tools, and start building a workspace that actually works for your distributed team.