As a couple of others have said, it depends some on what sort of project you're talking about - how to approach a hobby vs. a habit you want to develop vs. a pr

As a couple of others have said, it depends some on what sort of project you're talking about - how to approach a hobby vs. a habit you want to develop vs. a project for work seem like they're pretty different. This week, I'll be releasing an internal project beyond a small beta group that I've been working on since 2017. Here are some of the things that I've found helpful in keeping disciplined in advancing the project: 1. Acknowledge it's going to take time. Unrealistic expectations can frustrate. I knew going in that to get the project to where it is today would take over a year, so when things took longer than I wanted it wasn't so bad. 2. Getting feedback from others. Is this feature I made useful? Is this game I made fun? Does anyone like this story I wrote? This feedback on a project can help fail fast on a project not worth doing. Also, remembering the positive feedback on early states can help stay motivated. I keep all feedback on the project since I first came up with the idea in a giant Org-mode file, and I periodically re-read through it (or at least parts of it). 3. Mixing it up. Even the most exciting projects can turn monotonous. Periodically work on a different facet of the project so that your work seems "new" again, even though you're advancing the same cause. 4. Remembering that it's hard for (pretty much) everyone. All the authors I've ever heard about writing books has said that writing a book was way harder then they imagined. That's because writing books is hard. The same is true for writing programs, launching a product, or finishing any other project like that. It's just hard.