2 things have always worked for me - well almost: 1) listing out the tasks and sub-tasks required for a particular project and crossing them out as I complete t

2 things have always worked for me - well almost: 1) listing out the tasks and sub-tasks required for a particular project and crossing them out as I complete them. Then, when I feeling particularly morose about accomplishing "nothing", I check out my list with crossed-out tasks and realize I've completed something after all. Timing/sprints don't work for me. I'll work on a particular task/sub-task until I've reached a good stopping point or until I'm feeling burnt out or I'm bored out of my skull. (Actually, as I'm writing this, I realize Pomodor or something similar is something I should consider for those boring, but necessary grunt tasks.) 2) When I realize I'm actually at or close to completion (and sometimes adding more tasks), I think of the 80/20 rule and ask myself if I would be merely "polishing the apple" if I continued on that project vs. the more substantive work I could do another. Also, if I "complete" a project and it never really gets any traction, I try to think of the lessons learned from it so that I won't feel like the entire project was a waste of time. Admittedly, that last part can be pretty tough sometimes. . .especially if you paid a price in lack of attention on your "day" job, social interactions/occasions/relationships that got short shrift while you worked on the project, etc.