Transitioning from synchronous to asynchronous (and somewhere between)
summary
A concrete case: a new remote team builds its backlog using a shared Meo board with instructions and a how-to video, collects input asynchronously, then meets to align; outcomes are unified team, more inclusive participation, engineers get thinking time and documentation by default, and a surprising cultural shift toward an asynchronous-first habit. Experiments include reverting to synchronous where needed, an asynchronous day pilot, and learning from GitLab practices and the book Effective Remote Work.
AI-written summary · about
chapters (9)
- 0:00Asynchronous working
- 1:45Async backlog with Meo
- 3:52Async collaboration outcomes
- 5:37Public communication
- 6:40Experimenting async methods
- 7:42Self-management challenges
- 8:44Balancing async and sync
- 9:26Async work resources
- 10:10Call to action
related talks
47mRemote Leadership and Asynchronous Management
36mHow YOUR scrum team can excel in a remote setting
26mRemote-first teams work better
24mHow Engineering Teams can Plan Remotely
30mBuilding and Leading Remote Teams
55mEffective Communication in a Remote First World
46mLeadership for Engineering Teams in Remote Work Era | Panel Discussion
19mAll-Remote UX at Scale