How To Get Nothing Done
summary
Argues following always be working—grab tasks immediately, keep many tasks in flight, prefer huge batches, volunteer for new work—maximizes context switching and multiplies completion time; cites a 2009 Microsoft analysis where only one third of features improved their intended metrics. Recommends delaying feedback, avoiding short loops, and avoid collaboration (no pairing, no close customer work) so feedback arrives late and changes balloon, producing late, low-impact deliveries that still consume all available time.
AI-written summary · about
related talks
06mHow To Get Nothing Done
44mKeynote - Focus (or Stop Starting, Start Finishing)
01h 01mThe Multitasking Way Forward: Strategies for Success
04mWhy we don't get things done
06mDon't Try
29mThe Undeniable Virtue of Doing Less
58mOptimizing the Programmer: Get More Done Faster
43mYou are not a candle; don't burn out