Reading that essay, it sounds an awful lot like "Lean Development"[0], although in my own work I have often found that things that seem super urgent in one particular moment often benefit a great deal from setting them aside as long as you can stand, as that makes the requirements more concrete. It also means that you don't end up doing work on things that probably don't need doing.<p>I've been putting off (for a long time) one big, complicated user requested feature on my mobile app to do with archiving/managing a local database on the mobile device. It turned out that the things I thought I needed 12 months ago I don't really need at all, so procrastinating about it actually improved the delivered experience.<p>I do procrastinate, but I think it's a useful trait when you find yourself dealing with a big organisation that tends to throw off useless tasks because somebody feels like if they aren't producing requests, then they aren't being productive (middle management disease).<p>[0]<a href="https://www.planview.com/resources/articles/lkdc-principles-lean-development/" rel="nofollow">https://www.planview.com/resources/articles/lkdc-principles-...</a>