Continuous communication in the heat of battle
summary
Line‑fighting analogies show that focusing on fast, local communication turns mediocre individual performers into a reliable unit: after prioritising continuous signals the bike‑parking platform team holds the line longer in events and wins more line fights even without duel champions. Practical takeaways: use the COIN (Context Observation Impact Next steps) feedback format, send meeting invites with goal, expected outcome and prep, put the conclusion up front in written messages and during outages update every two hours even if there’s no fix.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:46Software tester and Viking
- 7:26Line fighting to agile
- 10:15Agile anti-patterns
- 16:41Meeting expectations
- 23:24Written communication
- 28:24Switch to verbal
- 31:54Team updates during outages
- 37:13Ongoing work updates
- 39:00War cry in sprints
- 41:06Q&A
related talks
37mFixing the mistakes we -all- make as developers, leaders and teams
43mLeading teams through times of uncertainty and upheaval
46mCracking the cadence of your software engineering 1:1s
41mBuilding and Leading Remote Teams
05mCommanders, Communication, Context, and Convoys
42mHow to lead change
30mDriving team performance with effective communication
23mManaging diverse engineers for high-impact deliveries