Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

My personal hack to get around pre/post completion downers is to have a clear idea of what to do after the project completion.

This can be support for the completed one, another project, vacations, or anything really, as long as it is clearly visualizable and tacit. If there are multiple good options and I cannot pick one of them, I try to clamp them to a maximum of 3. All of them have to be clear and concise.

It is a somewhat simple system, but I have found this to work time and time again, mostly because I came to realize that the core of these downers could be attributed to post completion void. Before this approach, I would find myself delaying completion in order to not face the unknowns of what would happen after getting though the goal line. This led to unneeded anticipation worries and needless time wasting.

On the other hand, having these delimited post project goals took the situation on its head. Instead of delaying completion, I worked even harder to get there fast and jump to the next exciting stage as fast as possible.

Thank you for the post and for sharing your experience with us!



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: