Spock meets Kirk
summary
Claim: better product decisions come from concrete communication habits not stereotypes. Recommend cultivating humility, respect and trust, determining context and stating goals aloud, and to overcommunicate. Uses video hangouts, Slack channels, Google docs, GitHub issues and quarterly retreats across a 28‑person, 10‑country remote team to reduce data loss. Example: a shipped PDF/media viewer sparks a 10‑hour debate over monetization limits and whether an upload icon points up or down; airing biases resolves it and the feature ships.
AI-written summary · about
chapters (18)
- 0:00Intro
- 1:35What is communication
- 1:55Why is communication important
- 5:55Information optionality
- 6:24Stereotypes
- 9:29Perspective
- 12:09What can we do
- 12:27What you do
- 15:53Content
- 20:03Community
- 25:27Feel important
- 28:03Distributed team
- 29:15hangouts
- 31:06cliff jumping
- 33:30business team
- 36:24recap
- 37:02book
- 38:09business
related talks
40mCommunication & Empathy across Remote & Distributed Teams
55mEffective Communication in a Remote First World
24mKeep talking and no-one explodes – Tips for smooth teams
05mLearning from Captain Kirk...
44mBridging the Gap
37mFixing the mistakes we -all- make as developers, leaders and teams
24mRadical Transparency: Leading Engineering With Openness
46mCracking the cadence of your software engineering 1:1s