Becoming a team, one pixel at a time
summary
Distributed engineering org of 65 people spends 95% of work time reduced to pixels and scales 50% year over year, so leaders build intentional structures: a career engineering competency matrix tied to hiring and reviews, written decision records, weekly one-on-ones, and documented quarterly plans reviewed in weekly meetings. Practical tools include pair‑programming, a gratitude Slack channel, Donut random one‑on‑ones, and a doc reminder tool to keep knowledge current; emphasis is on clear expectations, blameless post‑mortems, and writing that anticipates questions.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:03How do you turn a system into a team
- 4:49What does it mean to be a leader
- 6:00How we hone connection
- 6:53Making space for our humaneness
- 9:20Values and expectations
- 10:06Organizational expectations
- 11:22Connection
- 13:25Alignment
- 14:43Loneliness
- 15:42Disconnection
- 17:01Power dynamics
- 20:30Communication
- 22:59Open Communication
- 24:43Documentation
- 25:54Writing
- 27:21Editing
- 28:07Asking good questions
- 29:30Conclusion
related talks
46mLeading Distributed Teams
24mHow Engineering Teams can Plan Remotely
20mBuilding Distributed Systems in Distributed Teams
30mEngineer's Lifecycle Management - Remote First Environment
43mScaling Yourself for Managing Distributed Teams...
13mManaging Remote Teams
23mBuilding Distributed Systems in Distributed Teams
47mHow Microteams Change the Way We Collaborate. Again