Remote-first teams work better
summary
Argues that concrete changes improve collaboration: everyone uses video dial‑in with room audio or a moderator controls turn‑taking in meetings, a policy of Slack quiet hours (Tuesdays and Thursdays before noon Eastern) creates long uninterrupted work blocks, and a Slack changelog using the Reacji channeler captures summarized, contextual posts so returning teammates can catch up. Team reports 100–200 daily messages vs ~2 changelog items, fewer missed decisions, better inclusion across time zones, and more deep work and shipped outcomes.
AI-written summary · about
chapters (38)
- 0:00Intro
- 0:35Disclaimer
- 1:12Colocation
- 1:50Sit
- 2:09Everyone has city
- 2:33Remoteness
- 3:31Give up
- 3:55Drop the office
- 4:06Remote first approach
- 4:28About Nassim
- 5:20Todays topics
- 5:49Meetings
- 6:53Caucus Meeting
- 7:23The unwritten caucus rule
- 8:31The folly of rewarding
- 9:05Meeting cues
- 9:29What should we optimize for
- 9:53One remote or remote
- 10:23Video in room audio
- 10:54Moderator
- 11:53Summary
- 12:17An anecdote
- 13:07Collaboration habits
- 14:17Morning routine
- 14:50In Atlanta
- 15:24Our role as leaders
- 16:09Optimize for deep work
- 16:59Its not remote specific
- 17:15The bottom line is
- 17:41Maintaining common ground
- 18:12Biggest takeaway from the workshop
- 19:07Ryan responds the biceps model
- 19:51Common ground
- 20:59Slack Change Log
- 21:44Identify Common Ground
- 22:03Summarize
- 23:15Catching up from PTO
- 24:03Call to action
related talks
55mEffective Communication in a Remote First World
13mManaging Remote Teams
47mRemote Leadership and Asynchronous Management
27mLost on an Island: Building Remote Collaboration in Cross-Continent Distributed Teams
36mHow YOUR scrum team can excel in a remote setting
57mLessons from {distributed,remote,virtual} communities and companies
48mTeam Leadership In The Time Of Remote Silence
46mLeadership for Engineering Teams in Remote Work Era | Panel Discussion