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. Automattic is known for using internal blogs called P2s for most work-related conversations. How and why did that happen?
A. In Automattic’s early days, we collaborated a lot directly in the code, or on IRC (Internet Relay Chat), a Slack precursor. We quickly realized that it wasn’t great for asynchronous discussions, and when we tried email instead, it didn’t allow for the transparency that is the hallmark of open source (it also brought a lot of noise with it). Finally, we ditched email and moved to an internal blogging system. P2 is the evolution of the blog for the purpose of working within and across teams. It’s organized much like a Yammer or Facebook stream, but on the back end it still operates like a blog, allowing for archiving, advanced search, and rich media embeds.
Conversations on P2s take place in line, update in real time, and provide space for threaded replies. We’ve stuck with P2 for years now, and it has ultimately evolved into a rich source of institutional wisdom and collective company memory.
I would encourage anyone working in a distributed setting to spin up a P2 by starting a blog at WordPress.com, which you can then use as your company’s internal blogging system.
At its core, P2 is organized, searchable knowledge. For example, we write up notes from every meeting, and tag attendees by name. I can search for any person’s name tag and pull up all conversation history related to the individual in question. It’s an invaluable resource.
To learn more about Automattic’s distinct culture, listen to “Inside the Grand Meetup,” an episode featuring several Automatticians talking about their experiences at a fully distributed company.