How to Manage a Remote Team: Writing, Asynchronous Work and Belonging

As a child in 1348, the Prato merchant Francesco di Marco Datini lost his mother, his father and two siblings to the plague. As a young man he went to Avignon, where he traded in arms and luxury goods until 1382. Over time the business he built took a shape that was strange for its age: separate companies in Avignon, Prato, Florence, Pisa, Genoa, Barcelona, Valencia and Majorca. Datini himself lived in Prato after 1382 and in Florence from 1386 until his death.
What held them together was the letter. According to the Datini Institute in Prato, the companies left behind about 150,000 letters and 602 account books covering 1363 to 1410. The letters came from 267 different places, from Bristol to Lisbon and from Nuremberg to Mecca. When a company closed its accounts, its books were sent to Datini, and together with the packets of letters that travelled with them, its activities and results were reviewed. Prices, exchange rates and market news arrived the same way; decisions rested on paper that had been read.
Datini died in 1410. During a renovation in the seventeenth century his papers were tied into parcels and left on a blind flight of steps in his house in Prato, where they were found in 1870. What came to light was the correspondence of a team that, more than six centuries earlier, had never met in the same room.
In a remote team, the writing is the office
Today's remote teams live with Datini's problem using faster tools. When people are not in the same room, information does not spread on its own; there is no sentence overheard in the corridor, no two-minute chat on the way out of a meeting. Maggie Leung, head of content at NerdWallet, told First Round Review how she ran a fully remote team of about 80 people spread across the United States. The team grew to 30 in its first year and 60 in its second, and at its largest reached 100. A few practical lessons come out of what she describes.
Write down the reason for a decision, and keep it current
Leung's team writes down not only what was decided but why and how; it keeps this in chat channels, in email and in a large internal wiki, and it is relentless about keeping the wiki up to date. Most meetings and training sessions are recorded so that someone who missed them, or who joins later, can reach the same information. A written decision removes the burden of explaining the same thing to ten people one by one.
Give everyone the same information at the same time
According to Leung, sharing information with some people and withholding it from others breeds favouritism, insecurity and internal competition in a remote team. The rule on her team is simple: unless there is a clear business reason, information is shared with the whole team; if something seems to be withheld without explanation, people should ask.
Make room for conversation
It is hard to see how the person on the other side of the screen is doing. Leung's team runs anonymous check-ins in which everyone writes three adjectives for how they feel, and the results are read aloud. Separate channels are opened for people facing similar issues, such as parents. If a concern comes up in a one-to-one, the person is asked whether they would share it in a common channel so that others going through the same thing can benefit. In Leung's words, one of the worst things is struggling alone.
Show what good looks like
In a remote team good work can stay invisible. On Leung's team, people who live the company's values are recognised in a dedicated shout-out channel, and in a session held every two months people explain not what they achieved but how they solved a problem. A decision tree that one team member built for a recurring piece of work was, after feedback, rolled out to the whole 80-person team.
Set early checkpoints, and test for remote work when you hire
Discovering a misunderstanding late in a new piece of work is expensive; Leung recommends early checkpoints at the planning stage, and for simple questions a ten-minute call or a short thread is enough. When hiring, asking candidates how they managed their time, how much guidance they needed and how they won over stakeholders is the way to gauge their ability to work remotely.
If you are thinking about how to build the team's shared values, the piece on company culture complements these lessons, and if you are choosing your first people, so does the piece on first hires.

Synchronous, asynchronous and fifty metres
The word synchronous comes through Late Latin synchronus from Ancient Greek súnkhronos, meaning contemporaneous, happening at the same time. Sun- means with or together, and khronos means time. Add the negative prefix a- and you get asynchronous: not happening at the same time. In a remote team, work often flows in exactly this way: one person writes, another reads hours later.
Why that matters is shown by research that Thomas J. Allen of MIT carried out in the late 1970s. Allen measured how often engineers talked to each other and found that communication fell sharply as the distance between their desks grew. The critical distance for weekly technical communication was about 50 metres; in Allen's later work this relationship, known as the Allen curve, held for tools such as email as well. In a remote team everyone is more than 50 metres from everyone else. So communication does not happen by itself; it has to be designed.

The voice of an absent friend
The English poet John Donne opens a verse letter to his friend Sir Henry Wotton like this:
"Sir, more then kisses, letters mingle Soules; / For, thus friends absent speake."
This is how absent friends speak, and this is how Datini's companies spoke to each other centuries ago. On your team today, can someone who missed a meeting find in writing what was decided, and why?
If you are wondering what to watch for when you give your team feedback, in writing or face to face, How to Give Your Team Feedback is worth a read.


