Remote Team Management
summary
Companies run engineering with 90% of engineers remote, use GitHub repos for noncode coordination, Slack + Zoom + Hubot for standups and bots, and Figma for design collaboration. One vendor runs payroll and another handles US coemployment. Teamwork serves 22,000 companies and runs hubs in Belfast, Barcelona, Buenos Aires, Boston, Amsterdam and Cork while keeping 24‑hour coverage by limiting timezone span per team. Culture enforces daily stand-ups required and a “never argue over chat” rule that can be dismissal.
AI-written summary · about
related talks
57mRemote Doesn’t Mean Distant - Managing Teams Effectively from Different Geographies
42mSustaining Remote – First Teams.
13mManaging Remote Teams
55mWorking Distributed - How Does It Even Work?
33mTips for Managing a Widely Distributed Team
48mBuilding A Remote Engineering Culture
57mLessons from {distributed,remote,virtual} communities and companies
37mBuilding and Maintaining a Remote Team Culture