How do you communicate daily when your whole team is remote?
by•
I can safely say that working remotely brings a special kind of challenge.
It sounds ideal until no one knows what the others are doing and progress feels... fuzzy.
From what I’ve seen, the best system is short, daily 15-minute standups.
Each person says three things:
а/ What’s their big focus for the day
b/ What they did yesterday
c/ Where they’re blocked (and who might help)
That way, everyone stays in sync. No guessing, no drifting.
I’ve also learned the hard way:
No meetings = no momentum.
Curious how other remote teams handle this.
What works for you?
43 views
Replies
minimalist phone: creating folders
Something similar to clients.
Slack primarily with the closest team.
5 – 10 min standups (yesterday recap, what is ahead of us)
Biweekly sprints and retrospective
If something is not clear, we schedule a call.
@busmark_w_nika Yes. Calls are great if you have to work/clarify.
Otherwise is such a waste of time.
minimalist phone: creating folders
@byalexai Especially those LinkedIn quick calls :D
We use Slack for most of the day-to-day with our core team.
Quick 5 to 10 minute standups where everyone shares what they did yesterday and what’s coming up next.
We also run weekly sprint planning at the start of the day. If anything feels unclear or stuck, we just hop on a quick call to sort it out. Keeps things moving without overloading the calendar.
TinyCommand
For our remote team, async check-ins have been the sweet spot quick Looms or Slack updates answering the same 3 questions you mentioned. But the real shift happened when we added a weekly “decision log” a shared doc where anyone can note decisions made (big or small). It helps avoid repeat debates and gives context to those who weren’t in the loop.
We’ve also realized that rituals matter more than meetings. Even a 5-min Monday kickoff or Friday wins thread can reset energy and direction.
Would love to hear if others have lightweight rituals that keep momentum going without adding Zoom fatigue.
Can you explain what exactly this decision log is and give a more concrete example of a decision that was recorded in it?