Managing Remote Teams
summary
Company runs ~1,000 people with no offices and gathers everyone once a year plus occasional team on‑sites; core communication is Zoom and Slack but critical knowledge lives in a Confluence wiki (one searchable source). Decisions use a DASI(E)-style roster and lightweight RFCs as blog posts; micro‑recognition via Bonusly, weekly office hours and virtual happy hours build rapport. Claim: distributed hiring widens talent reach, but it slows ad‑hoc problem solving and requires deliberate overcommunication, extra written records and regular synchronous touchpoints.
AI-written summary · about
chapters (5)
- 0:00Start
- 3:35Social Value
- 4:08The Importance of Writing Stuff Down
- 9:37How Did I Know if I Was Talking to the Right People
- 11:23Weekly Office Hours
related talks
57mLessons from {distributed,remote,virtual} communities and companies
38mDistributed Sys Teams
37mBuilding & Scaling Distributed Teams
42mSustaining Remote – First Teams.
37mBuilding and Maintaining a Remote Team Culture
57mRemote Doesn’t Mean Distant - Managing Teams Effectively from Different Geographies
55mWorking Distributed - How Does It Even Work?
22mRemote Right: How to Thrive in a Post-Office World