For me, “Step 6” on this page is the first step. I get started working on something! All this organizing and planning would be a great way for me to put off actually working on the projects. I’m constantly working on projects. Multiple nights a week. I suppose I should mention that I have no kids and I work 20 hours a week for my job, meaning I have a lot of “extra” hours in the week for my own personal work.<p>Also I’m not saying the authors view is wrong - everyone is different. And certainly my work situation is rare. I am not a planning person (my job as a prototyping engineer meshes well with this). So if all this Kanban stuff is too much for you, consider just working on stuff! :)<p>Anyway whatever the approach I’m glad this author is communicating what works for them about projects. A lot of people I talk to struggle with this.
For me, the biggest problem seems to be that if there's a break in between (work/travel etc - need not be long - something as short as a couple of weeks is enough) and then I find it hard to pick up the project again where I left off :-(<p>Still haven't found a way to come back to projects once there's any sort of interruption.
I've found a variety of trîcks working for me lately.<p>Kanban has been one. I've started it for things I'm learning, although it's not strictly. I'm using GitHub issues to track various different learning projects. Mostly I'll have an issue that lists a series of videos in a series or blog post series and I'll tick each one off as I do them and take notes in a comment. That has helped with falling off the wagon. I might slow down, but I remember eventually "oh I only got halfway through that series! Let's do the next one now" and continue to make progress.<p>Projects where I make things have been a little different. I've found making an ecosystem of interrelated projects helps with bothering to complete things because as one project drags on and the enthusiasm for it dies, the will to keep going is fueled by the passion and excitement for starting the next project. I think I might call this concept a "Project Stack". The next project just so happens to rely on the current one, so it needs to be finished. Wish I had discovered this hack sooner.<p>The other thing that has worked well is flipping from nights to mornings. And back again. Waking up first thing in the morning and working on my project for 1.5 hrs before work has definitely made me make progress after the enthusiasm wore off and I would have gone in search of shinier things. There's just something about there being no excuses. Not tired. No one needs me to do anything as they're all still asleep. Don't feel the need to entertain myself as it hasn't been a long day. Might as well make another step of progress. But then after awhile I start feeling the mornings become less productive and I slow down because really I'm a night owl at heart. So I switch back! This gives a renewed sense of energy.<p>I'm a few days out from finishing project 2 in a "project stack" about 5 to 8 projects deep. Can't wait to start number 3.
One thing that has helped me: Breaking up steps into smaller ones explicitly. Even if only "trivial" preparation work can be factored out, it will help getting started on bigger tasks and will provide the satisfaction of "checking off" something. And once started, further breakdown may become obvious.
#7 has more to it. It's a big deal. Falling off the wagon can be due to various reasons - lack of prioritization, unfamiliar tooling/technology, not knowing the value, striving for perfection, lack of iterations, and lack of context. These can more often lead to abandoning the projects altogether.<p>If you have time to read more about this, check out my blog post here <a href="https://iam.mt/working-on-side-projects/" rel="nofollow">https://iam.mt/working-on-side-projects/</a>