How to drive pace in your team
summary
Claims concrete tactics: set team defaults that put pace at the centre, break work into one to two week projects or smaller slices, pick boring reliable tech so recovery is fast, do the hard unknowns first to avoid long tails, use public Slack channels and regular project updates for visibility, regroup early to relieve pressure and reset scope, favor finished work over started work, keep code quality high, and mark non‑negotiables (security at instant io) so tradeoffs are explicit.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:08Team pace expectations
- 4:16Optimizing projects for speed
- 7:05Individual pace encouragement
- 10:36Risks of pushing pace
- 13:47Team limits understanding
- 15:33Recap and key takeaways
related talks
46mCracking the cadence of your software engineering 1:1s
29mEconomies of Speed
08mTips for part-time project managers
11mEngage teams to achieve high performance
01h 04mHow to Motivate Your Developers
45mAccelerating Software Delivery: Why Your Team Is Slowing Down
26mAgile values and principles for non software teams
45m"Moving Fast at Scale"