Distributed FAQ: What Are the Key Tools for Creating an Effective Remote Work Environment?

In Distributed FAQ, Matt Mullenweg addresses some of the most common issues companies, executives, and individuals face as they consider transitioning to a distributed model.


Q. What are the necessary tools and processes to create an effective remote work environment?

A. There’s a lot to say here, of course, so let’s start with a few fundamentals:

  • Choose a small set of core applications for the entire organization, for example Zoom for video calls, Slack for day-to-day conversations, and G Suite for documents, spreadsheets, and (if you choose to use it) email. 
  • Foster a strong sense of autonomy. Give individual teams a lot of freedom to choose the rest of their stack, whether it’s GitHub for development, Asana or Trello for project management, InVision or Figma for design, and so on.
  • Try out a no-email approach. At Automattic, our secret sauce is that we don’t use email within the company. Instead, we have an internal blogging system called P2. P2 displays all conversations on a team or project’s homepage, updates in real time, and comes with the built-in benefit of being a searchable blog. You can also tag individuals and teams on P2. This system creates rich conversations that happen asynchronously and then become the collective wisdom of Automattic. We publish well over 1,000 posts and comments every day.
  • Default to public. At Automattic, we’ve developed a very valuable instinct: always default to everything being public (within the company, that is) — always default to trust.
  • Invest in solid video conferencing tools. Having a good setup for video calls is very important. Audio quality is essential if you’re on a lot of calls, so go for a good headset or use noise-cancelling software. A good desk lamp to illuminate your face can make a real difference. And give some thought to the background people will see behind you — it can have personality, but you’ll want to keep it from getting too cluttered. 

For a comprehensive list of recommended hardware and software for remote workers, check out our Tools and Gears page, as well as Matt’s “What’s in My Bag?” posts.

Distributed FAQ: How to Transition to Remote Work

In Distributed FAQ, Matt Mullenweg addresses some of the most common issues companies, executives, and individuals face as they consider transitioning to a distributed model.


Q. With the rapid rise of distributed work, what are your top pieces of advice for someone going through the transition from a traditional work environment to a remote one?

A: There are many things individuals can do to make the switch successful, but here are five pointers to get you started.

  • Make a list of all the things you like and don’t like about previous work experiences and use it to design — and implement — micro-habits to increase your health and happiness. Remote work comes with the autonomy to build your own bespoke work environment.
  • Writing ability is crucial, and distributed work only amplifies its importance. Assume positive intent when using written communication.
  • Look at the outcomes you’re producing, not the time you spend at your laptop. It can be powerful to self-track and document what you’re working on. At Automattic, we encourage self-analytics — taking agency over the assessment of one’s own outcomes.
  • It’s important to structure your day. A little more schedule actually helps, whether it’s to keep a normal grooming routine in the morning or to set a firm time at which you turn off everything. Set a time to stop as well as to start, and find a dedicated workspace. Implement systems that help you maintain focus (e.g. the Pomodoro Technique for time management).
  • Implement self-care and opportunities to interact socially.

For more insights on how to design your own distributed work environment, listen to Matt’s conversation with Lydia X. Z. Brown, or browse our gear and tools recommendations.

Written Communication Tip: Assume Positive Intent

It’s not news that 90% of communication is non-verbal, and that nuance and subtlety are lost over written messages. Be conscious of this.

With lots of our communication now written (when previously you might’ve popped over to someone’s desk) it’s good to head off the risks of such interaction with a wise interpretive principle through which to view your exchanges: Assume Positive Intent. 

The Memrise team

In a recent Zoom chat, Matt Mullenweg shared work-from-home advice with the team at Memrise. They’ve compiled Matt’s 10 top tips, including advice for teams who are likely communicating much more in written form than they’re used to. Read and listen to more best practices on the Memrise blog.