First commit: 2021-12-01

Last updated: 2022-12-28

Linked Notes

Modern Internal Communication Practices

A couple of notes on internal communication tools and practices for organizations that are either distributed, or working in a hybrid model, or are in need of structured ways of sharing information.

  1. The problem with hybrid or distributed work
  2. The curious case of Automattic
  3. Why is Microsoft moving in the opposite direction?
  4. Practices
    1. Agile Communication
    2. Amazon‘s six pager
    3. Living docs
  5. Tools
  6. Related Articles from other smart people

The problem with hybrid or distributed work

One problem of distributed/remote/hybrid work is the missing bandwidth of face-to-face communication or as a study of 60,000 Microsoft employees found

Our results show that firm-wide remote work caused the collaboration network of workers to become more static and siloed, with fewer bridges between disparate parts. Furthermore, there was a decrease in synchronous communication and an increase in asynchronous communication. Together, these effects may make it harder for employees to acquire and share new information across the network.

A 2020 study by Atlassian aptly titled “Reworking Work” arrived at similar conclusions.

  • Meetings in a distributed environment became more formalized and structured. Unstructured, free-floating communication almost vanished completely and with it the exchange of topics, information, and ideas not tied to the work at hand.
  • The collaboration in teams got better up thanks to this formalized approach but suffered across team or department borders.
  • Individual workers fear their work might become invisible and thus their careers may suffer without the ability to show off projects or network with higher-ups and peers. (This problem is especially pronounced for new higher of young workers.)
  • “work time” in a distributed and remote team tends to fracture even with workers located within the same timezone, country of even city. Housework, children, private tasks and even hobbies tend to collide with the time allocated to work — without impacting productivity but availability.

The curious case of Automattic

Automattic, the company behind WordPress is an interesting case study. It employs 1.700 people across multiple continents and time zones since 2005 and has an interesting work culture.

  1. Asynchronous — there are no meetings, e-mail, or PowerPoint presentations. Everything happens via written communication.
  2. Transparency — this written communication is (with exceptions) open for every employee to read, comment, and share internally.
  3. Document everything  — obviously. (Meeting notes, project updates, new hires, etc.)

To accomplish this the company uses a custom version of WordPress called P2 as an internal forum/intranet/task-managment/documentation-tool: “P2 or it didn‘t happen.

In conclusion: if a company wants to work as a distributed/hybrid organization, in the long run, it might have to rethink its communication infrastructure and adopt one that is:

  • open for every employee to contribute to
  • transparent
  • and most importantly: written

Why is Microsoft moving in the opposite direction?

Microsoft has dominated offices around the globe with its software, lately bolstered through “Microsoft Teams” a chat/video-call tool build for communication inside teams and organizations. But its features and internal logic are not built to ideally support a written communication culture.

  • subgroups (also called “teams“) are often slow to navigate.
  • content can not be easily shared across such groups. (Thus they tend to create and reinforce silos within an organization)
  • these subgroups are often hard to find without either an invitation or a detailed name since they often exist to represent either actual teams, projects, or open forums without distinction.
  • users are often highly restricted in their use of teams by their managers. (For example: if they‘re not allowed to edit their own title or which part of the organization they belong to, the company as a whole become unreadable and impossible to navigate after some time)

And of course:

  • The editor of Teams is not built for longer written texts. In fact, it‘s pretty bare-bones without features such as tagging, drafts, or pre-planned publishing of content.

Microsoft has lately also been more focused not on solving these issues but instead working on the video components of the software and even integrating its version of the “Metaverse” (formerly called “3D” or “VR“) in the form of virtual spaces.

Microsoft seems more interested in creating a skeuomorphic digital office than actually helping people do good work in a distributed team. (And you can guess which tool the 60,000 Microsoft employees most likely used from the study at the top.)

Honestly, Microsoft… just force people to add agendas to their meetings. It would make a bigger difference than starring at the feet-less avatars of my colleagues.


Okay, let‘s talk about some interesting practices that fit the mold of asynchronous and written communication.

Agile Communication

While not explicitly written for distributed teams, “agile communication” is a great way to structure communication inside companies.

Your comms strategy should simply be “Show the thing. Be clear. Be brief.” Any time you spend trying to come up with something that says broadly the same thing, only using many more words, is probably wasted time.

It argues in favor of blogging at the speed of work with a heavy focus on quick, short posts, showing the artifacts of work, and building up a archive of posts.

The practice is described in a great piece on the blog as well as in the book of the same name by Giles Turnbull.

Amazon‘s six pager

According to myth: Amazon banned PowerPoint presentations in 2004 and instead installed a culture of written memos.

Powerpoint-style presentations somehow give permission to gloss over ideas, flatten out any sense of relative importance, and ignore the innerconnectedness of ideas.

One format that caught on is the “six pager”. A narrative document used to develop and pitch ideas, product, and project. And yes, it should be six pages long.

The main goal of authoring this kind of document is to craft the entire thing as a narrative. That doesn‘t mean it needs to be an entertaining story. It merely means there are no bullet-point lists, no graphics, and no fluff in the document‘s core 6-pages.

Meetings thus consist mainly in the form of reading circles in which these documents a read, critiqued, and discussed.

You are usually given 20–25 minutes at the beginning of a 60-minute meeting to read the doc from beginning to end. Most people write down questions or feedback directly on the printout since using a computer during this time is frowned upon.

All print outs are handed back to you at the end of the meeting. The rest of the time consists of everyone in the room challenging your position, questioning your tactics, and digging through the data to make sure it is valid. It‘s incredibly stressful, and when the meeting is over, it‘s your responsibility to update and recirculate the document to everyone as a final version. There is no ideation or brainstorming during these kinds of meetings.

These documents are interesting because:

  • They force a team to spell out their thoughts and ideas on paper.
  • The use of a speculative press release gives them the chance to develop a common vision of the future of said project.
  • Because narrative and hard facts are at the forefront of any new project, it forces teams to be precise and agree on the same base truths.

Living docs

I already have a short note on living docs in this garden, so I won‘t repeat myself too much here.

In short: living docs are shared multiplayer-edited documents (think: Google Docs) that work as growing documentation of every project. Instead of having dozens of different documents, everything gets sorted into one big one.

You‘ll find research, contact information, to-dos, etc. in there.


Some tools and platforms I find currently interesting:

  • Pulse — similar to P2 but with a (in my opinion) nicer design
  • Notion — slow but still the go-to if you want to build a wiki for your team
  • Coda — focussed on documents, this one is pretty much “living docs, the tool“
  • Abstract Notebooks — focussed on distributed design teams.
  • Axios HQ — Axios writing style but as a B2B SAAS platform.
  • Twist — Work communication as threaded discussions organized around channels. (“Long-form slack“)