The Distributed Team Tool Stack

Tool selection consumes disproportionate attention and rarely determines outcomes. What matters is that six functions are covered, that each has one obvious home, and that people know which is which.

The six functions

Real-time conversation. Chat. Fast, informal, ephemeral by nature.

Durable discussion. Threads that persist and can be found months later. Chat is bad at this, which is why organisations that use chat for everything cannot answer why decisions were made.

Documentation. The reference layer: how things work, what was decided, what the process is.

Work tracking. What is being done, by whom, in what state.

Synchronous meeting. Video.

File storage. Where documents actually live.

Six functions. Many organisations run twelve tools and still have no answer to "where is the decision recorded", because the tools cover conversation four times and durability not at all.

One home per function

The failure that matters is not having too many tools. It is having two tools for the same job.

When documentation lives in three places, none is trusted, everyone searches all three, and eventually people ask a colleague instead — which reintroduces the interruption cost the tooling was supposed to remove.

Pick one home per function. Write down which is which. Enforce it gently for a quarter and it becomes habit.

The thing people get wrong

Treating chat as the system of record. Chat is a river. Anything in it is gone in a week — findable in theory, not in practice.

Decisions, agreements and anything a future person will need must be written somewhere durable. The message announcing it can be in chat; the artefact cannot be.

This single distinction accounts for more remote dysfunction than any tooling gap.

Choosing

Fewer, integrated, boring. A stack everyone knows beats an optimal one people avoid.

Search matters more than features. In a distributed team you will spend more time finding things than creating them. A tool with poor search costs you daily.

Mobile access matters. People travel, and being unable to check something from a phone creates unnecessary blocking.

Check what your existing suite already includes. Organisations routinely buy a product for something their current licence covers.

Exit cost is a selection criterion. Ask how you get the data out before you put it in.

What is usually unnecessary

Virtual office software — persistent video spaces simulating an office floor. Some teams like them. Most adopt them enthusiastically and abandon them within two months.

Monitoring tools. Covered elsewhere: they answer the wrong question and cost trust.

A second chat tool because one team prefers it. This is how organisations end up with fragmented conversation and no shared record.

Anything promising to replace documentation with AI summarisation of meetings you should not have held.

Write down the norms

The tools are less important than the conventions around them, and the conventions are almost never written down.

Which channel for what. Expected response time in each. What warrants a direct message rather than a channel. Where decisions go. What gets documented and by whom. Whether a thread is expected or a new message.

Half a page. New joiners describe it as the most useful thing they receive, and most organisations do not have it — which is why every new person learns the norms by breaking one.