Remote Leadership and Asynchronous Management
summary
Claims that remote work is already the norm with Gartner numbers (75%→82%→90% interest) and 97% agile adoption, argues for asynchronous by default communication, and gives concrete practices: consolidate tools (Slack Teams Zoom Google Meet Signal Confluence GitLab) into one tool per category, fix transparency by documenting where info lives, solve VPN/equipment shortages (client lacked VPN slots), respect deep-work calendars, and start by making no mandatory meetings with POW (Purpose Outcome Whats in it for them) stated and prework provided.
AI-written summary · about
chapters (12)
- 0:00Remote leadership intro
- 3:40Where real work gets done
- 8:38Leadership qualities to unlearn
- 13:56Synchronous vs async
- 16:46Transparency in remote orgs
- 23:07Tools for transparency
- 23:28Diversity in remote teams
- 29:06Continuous learning & servant leadership
- 32:15Starting with remote leadership
- 38:31No mandatory meetings
- 44:30Building remote-first cultures
- 45:55Closing & Q&A
related talks
43mThe remote leader - distant but not removed
55mEffective Communication in a Remote First World
45mAgile Leaders - Are You Future Ready?
57mLessons from {distributed,remote,virtual} communities and companies
26mRemote-first teams work better
11mTransitioning from synchronous to asynchronous (and somewhere between)
13mManaging Remote Teams
01h 06mLeading successful remote teams