The 10 Fuck-ups of Team Collaboration
summary
Explains why team collaboration breaks down when people ignore time and channel choices, giving examples like wasted platform decisions (Nokia/Meego vs Android). Recommends concrete practices: use an explicit synchronous/asynchronous matrix, adopt 90‑minute focus cycles (about three deep blocks per day), replace folders with search, introduce simple interrupt controls (e.g., a one‑euro jar), and roll out sensible tool mixes (Slack/WhatsApp/Google/Office365) with documented rules and measurement.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 3:15Time respect in collaboration
- 5:17Nokia’s internal competition failure
- 8:54Communication as teamwork core
- 10:41Why meetings fail
- 13:28Emotions need sync communication
- 15:31Focus Mode vs Fight Mode
- 18:30Private channels problem
- 20:40Email overrated
- 23:29Bezos’ communication approach
- 25:39Messaging tools over/underused
- 26:01Assumptions and lack of clarity
- 27:04Mandatory presence and office use
- 29:10Tool usage: privacy and infrastructure
- 31:57Tools after collaboration matrix
- 32:38Small steps for efficiency
- 33:20Company culture and open protocols
- 34:24Summary
- 35:53Examples of successful communication
related talks
49mHow to Make People Work Together?
47m3 Ways to Improve Workplace Collaboration and Productivity
01h 10mAgile Cross Team Collaboration How Tos
59mFostering Remote Collaboration
29mClarity in Collaboration
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
24mKeep talking and no-one explodes – Tips for smooth teams
38mHow Collaboration Works or Doesn't
