How to Stay Connected to Teams Without Platform Sprawl

A team does not need you in six apps. It needs one place where decisions live when you are twelve hours out of phase. I have joined groups that ran Slack, a second chat, email, a docs tool, a board, and a “quick” voice channel that was never quick. By the time I found the actual answer, the thread had moved and I looked disengaged. I was not disengaged. I was hunting.

I pick an async home base and I am boring about it. Tickets, a doc, a PR description: somewhere searchable, dated, and not dependent on me scrolling at the right minute. Chat can carry a ping. Chat should not be the archive. If the decision only exists in a disappearing conversation, it does not exist for the person who was asleep in Aotearoa.

Chat is an interrupt channel. I keep it for “the build is on fire” and “can you look in the next overlap window.” I do not keep it for status that belongs in writing. When I travel, interrupt cost goes up. Every ping is a context switch plus a timezone tax. If I answer in real time from a café in a new city, I am training the team to expect a body in the channel. Then I cannot do the work that was the point of being remote.

Client comms are a different note: external people, invoices, the tone you use when you are late. This is internal. Same human, different contract. Internally I want fewer rooms and clearer defaults. Status in the home base. Questions in the ticket. Chat for urgency, with a definition of urgency that is not “I felt like asking.”

Louisiana to Auckland does not require more platforms. It requires fewer, used on purpose. I put local hours in the status, a response window I can actually keep, and I repeat where the source of truth is until people stop asking in the wrong tab.

If a tool does not hold a decision, I log out. Connectivity is not the same as presence. Presence is leaving a trail your teammates can walk without you on the other end of a night.

— JV · Dark Heart Labs.