How a team that communicates well collaborates well
summary
A team drops repeated handoffs so a few concrete fixes get tried: a style guide to unify voice, three priorities instead of a premature north star, and a tiny decision record template (author, date, rationale) that spawns many writable decisions. A RAD habit (reflect assess do) and a rule that emoji reactions don’t count force solicited dissent. The decision docs quickly produce lively discussion and the new feedback steps reduce hidden objections and unblock engineering.
AI-written summary · about
chapters (6)
- 0:00Introduction and context
- 4:47The baton relay metaphor
- 8:33Strategy and direction
- 14:16Improving decision-making
- 18:48Fostering open feedback
- 24:11Conclusion and resources
related talks
31mHarmonizing Across Product & Engineering (Cross Team Collab)
45mSW Design, Architecture & Clarity at Scale
42mDecision-making for developers
30mCommunicating and documenting architectural decisions
39mWe're Agile, we don't do documentation
29mEffective design and engineering collaboration
32mThe Art of Technical Decision Making
34mBecoming a team, one pixel at a time