1) http://www.structuredprocrastination.com/ http://www.structuredprocrastination.com/ is amazing when done properly. It should not be confused with productive

1) http://www.structuredprocrastination.com/ http://www.structuredprocrastination.com/ is amazing when done properly. It should not be confused with productive procrastination which is closely related but much less useful. So the idea of structured procrastination is you put at the top some task that is very important but at the same time could possibly be delayed or dealt at the very last minute. Your tasks 2-5 are where the gains lie. This is where you put your writing a book, writing that documentation for your project, writing that game, polishing that UI for your visualization. Recent anecdata: I had to grade 90 algorithms exams, which I had foolishly allowed to submitted in about 10 different languages without an auto-grader. So I was getting PHP, Java,Rust, TS for Deno etc etc. Instead I procrastinated for a few days writing a number of Jupyter Notebooks for munging some data which I had put off for about 4 months. As soon as I received 10 bachelor thesis to review I moved those to the top of my list and I graded the 90 algorithms exams with time to spare. So productive procrastination is the less useful cousin of structured procrastination. In productive procrastination you put in slots 2-5 tasks that seem productive but rapidly reach diminishing returns. So if my slot 2 was going over 40 points on chess Puzzle Rush, it would be better than playing 30 second bullet chess but still not really that productive... So polishing UI could not be that productive at some point, or running 1000 AB tests.