4 ms·
a common trap in "deep work only" teams is local optimisation. while interruptions should be minimized and batched, the overall flow of cards and a low average
by wortelefant 4y ago
a common trap in "deep work only" teams is local optimisation. while interruptions should be minimized and batched, the overall flow of cards and a low average cycle time requires focused collaboration and regular slack time to resolve blockers. Otherwise, important issues spend more time waiting than getting completed. Individual deep work with low collaboration while more important work is piling up would be an antipattern.
- Cardinal7167 4y agoI’ve experienced this first hand. When all your colleagues only deep work and you’re tasked with some necessary grunt work, your productivity will plummet when you’re trying to move fast.