Becoming a team, one pixel at a time
summary
A distributed engineering org of 65 people builds psychological safety through specific rituals: using decision records (ADR github) to circulate proposals, running four‑week experiments instead of permanent mandates, pairing engineers daily for knowledge sharing, and pairing mentors across teams. Remote work grows 91% in a decade, so intentionally documenting context, editing messages for clear ask/expectation, using Donut or regular calendar check‑ins, and celebrating wins in a gratitude channel reduce isolation and surface trust. pair programming and a seven‑word check — “What problem are we trying to solve?” — keep focus.
AI-written summary · about
chapters (15)
- 0:00Introduction to pixels and teams
- 1:54Building distributed teams
- 3:17Five factors of high-performing teams
- 5:04Honing connection in teams
- 9:24Setting expectations and feedback
- 14:43Staying connected to goals
- 15:47Overcoming remote loneliness
- 18:16Collaboration mindset and power dynamics
- 20:04Challenging hero culture
- 21:27Learning from failure together
- 22:31Embracing change as a team
- 23:56Importance of communication in distributed teams
- 27:51Writing well for better collaboration
- 31:22Documentation as team investment
- 32:26Continuity in team building
related talks
21mGetting an engineering team to eat their vegetables
01h 01mPairing, Sharing, Caring - One team's journey to Pair Programming
36mDistributed & Local: Getting the Best of Both Worlds
40mGamifying Dev Effectiveness in a Remote-first Work Environment
23mGad Salner- How to scale a unicorn-building engineering team (and stay sane)
26mHow a team that communicates well collaborates well
56mHow to really work as a team- from sleepy to strong pair programming
32mHow to work as a team, sleepy to strong pair programming