Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. Communicating With a Distributed Development Team
Software Strategy

Communicating With a Distributed Development Team

Written communication is a skill, not a fallback. The habits that keep a partly remote engineering team moving without constant meetings.

Updated 2 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer — TL;DR

Default to writing, keep decisions where they can be found, and make it acceptable to proceed on a stated assumption rather than waiting. Those three remove most of the delay that distance causes.

The short answer

Write things down, put them where they can be searched, and agree that a documented assumption beats a day of waiting. Teams that do this work well across distance. Teams that rely on conversation do not, and they blame the distance.

None of this requires more meetings. Most of it reduces them.

Default to writing

A decision made in a conversation exists only for the people who were there. The same decision written in a channel is available to everyone, including the person who joins in three months.

  • Decisions, with the reasoning, not just the outcome
  • Context for a piece of work, before it starts
  • Anything that would otherwise be explained twice
  • The answer to a question somebody is likely to ask again

The test is whether someone could pick up the work tomorrow from what is written. If they would need a conversation first, the writing is incomplete.

Channels rather than direct messages

Direct messageShared channel
Invisible to everyone elseSearchable later
Repeats when someone else asksAnswered once
Creates a single point of knowledgeSpreads context
Fine for personal mattersBetter for work

Moving work conversations out of direct messages is a small change with a large effect on how much repeats.

Make it safe to assume

The most expensive pattern in distributed work is someone stopping because a question cannot be answered until tomorrow. Say explicitly that proceeding on a documented assumption is preferred.

Then honour it. If someone flags an assumption and gets criticised for not waiting, they will wait next time, and you will pay a day per question for the rest of the engagement.

Meetings that earn their place

  1. Use synchronous time for decisions with several options, disagreement, or debugging together.
  2. Handle status, routine questions and code review in writing.
  3. Give every meeting a written outcome, or it did not happen for anyone absent.
  4. Keep a reliable window when people can expect a response.
  5. Cancel recurring meetings that stopped having a purpose.

The habit that matters most

A short end-of-day note: what moved, what is in progress and where it stands, what is blocked and on whom, what is next. Five minutes to write, and it removes most of the friction that distance creates.

It also builds a record. Three months in, the history of those notes answers questions faster than anyone's memory.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly — a senior engineer will get back to you.

Ask about your project

How many meetings should a distributed team have?

Fewer than a co-located one, and each with a written outcome. Use synchronous time for what genuinely needs it.

What if people do not write things down?

It is a habit that needs modelling from whoever leads. If decisions keep happening verbally, writing will not stick.

Is video always better than text?

For disagreement and nuance, usually. For anything someone will need to refer back to, text wins because it persists.

How do we build rapport remotely?

Deliberately, with some unstructured time. It matters and it does not happen by accident when nobody shares an office.

Keep reading

More on Software Strategy

Software Strategy

Machine Learning Myths That Waste Budgets

Eight beliefs about machine learning that quietly inflate project costs, what is actually true instead, and how to spot each one in a proposal.

Start here

Thinking about adding developers to your team?

Tell us what you are building, what your team looks like now and where the gap is. We will come back with an honest view on whether augmentation fits, how many people it would take and what it costs. If hiring directly would serve you better, we will say so.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate — with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →