I've had some success with that approach and am considering adopting it as my "goto" approach (over my current approach, Trello, for which I just stare at all t

I've had some success with that approach and am considering adopting it as my "goto" approach (over my current approach, Trello, for which I just stare at all the cards on the board and panic at how much I have to do). When a deadline is coming up, I take a 10 minute "organization break" and list the actual, concrete steps that need to be mechanically performed in order to complete the task. I think the problem is that my mind tends to get hung up on abstract task descriptions and I start overanalyzing. For instance, "Design welcome page" will turn into a wasted day of messing around with colors, fonts, and layout positioning. On the other hand, "Add X, Y, Z to prototype welcome page" is a much more concrete task and it defines completion so that I can move on to the next task on the list. (Btw, you could turn your nested-robotic-link-list into a quick webapp that I bet would get a decent number of users.)