Why can't we all just get along?
summary
Identifies three concrete anti‑patterns: one role across many teams, product versus engineering Wars and X‑led hierarchies, and shows their effects — designers split across teams lose headspace, teams create handoffs and silos, and context switching adds measurable overhead (paper cited: two projects a week can cost up to five hours of switching). Gives fixes: reorganize to one team at all levels, create true multi‑disciplinary teams, disaggregate disciplines from job titles, limit WIP and set clear delivery expectations.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:23Ideal team vision
- 3:07Silos and specialisms trend
- 4:10One role across teams
- 8:02Product versus engineering wars
- 10:28Third anti-pattern xled organizations
- 14:46Anti-pattern problems
- 25:36Enabling structures
- 31:39Shared team responsibility
- 35:53Call for collaboration
- 36:18Q&A
related talks
46mLeading Distributed Teams
36mUX designers /developers collaboration anti patterns
44mA Match Made in Heaven - Instilling Harmony Between Product and Engineering
30mNavigating team friction
01h 00mBuilding a Culture of Healthy Conflict in Tech Teams
11m“Us vs. Them” thinking
27mWho's the Boss? How Tech Managers Can Work Well with Product
48mThe 10 vicious circles at work: detecting and breaking them up