6 ms·

Interesting article and makes some good points. But I don't think I'm the only one who has a problem with finishing projects instead of starting them. For me at

Interesting article and makes some good points. But I don't think I'm the only one who has a problem with finishing projects instead of starting them. For me at least, the process of starting a new project is fun and rewarding. But as time goes on I just lose faith in it and just drop what I'm working for some new idea.

easychris 10y ago
That's happening to me often, too. But as I understand it, the habit of just starting applies to continue working on the unfinished work-in-progress project as well: starting a new project is your way of procrastination.
jacquesm 10y ago
Well, look at it this way: if you didn't start you'd never get to finish, those projects that you start at least have some chance > 0 to be finished.
asimuvPR 10y ago
Sometimes we just want to do something new for a short time. It might be to try some new library or language. Thats ok. Learn to identify what is a short term project (I want to learn how to do n with python) and a long term project ( I want to learn Ruby). In the case if building products, use the MVP approach. Then build on it if required.
theprotocol 10y ago
Can confirm. I'm sitting on dozens of near-complete projects that I just cannot bring myself to finish.
- ctrlrsf 10y ago
  Finish the easiest one first to get you started. Rememeber it doesn't have to be perfect.
ourmandave 10y ago
Some of my unfinished projects suffer from, "We all agreed not to talk about that anymore." Combine a vague spec ("Not now kids. Daddy's working on a better Snapchat!") with design-it-while-I-code and you end up with a transporter accident.
Eridrus 10y ago
Same, I find it much easier to start new projects, finishing them after I've done what I consider the core "thing" is much harder. We're clearly not alone. Not all projects are worth finishing, but I find that once the rush of learning new things have worn off and the only thing left to do is rigorous evaluation or polish my desire to work no it fades. I find tying some reason to finishing them usually gets me more willing to do so. Giving presentations about my work has often served as a good forcing function since they have due dates associated with them and the fear of being embarrassed by my work outweighs the boredom of doing the last ~20%. Not a panacea, but it helps me.
Broken_Hippo 10y ago
I do the same. Over time, I've learned to space some of the starts out and have a few things in different stages of production. (for me, artwork is the major one). This spreads out the tedium. I'm not spending 10 hours in one go completing something: I'm spending a couple of hours on it, then moving to a different piece and a different task. When I'm in a good flow, it works out really well. And sometimes I find I finish a few projects in a short time.

easychris 10y ago

That's happening to me often, too. But as I understand it, the habit of just starting applies to continue working on the unfinished work-in-progress project as well: starting a new project is your way of procrastination.

jacquesm 10y ago

Well, look at it this way: if you didn't start you'd never get to finish, those projects that you start at least have some chance > 0 to be finished.

asimuvPR 10y ago

Sometimes we just want to do something new for a short time. It might be to try some new library or language. Thats ok. Learn to identify what is a short term project (I want to learn how to do n with python) and a long term project ( I want to learn Ruby). In the case if building products, use the MVP approach. Then build on it if required.

theprotocol 10y ago

Can confirm. I'm sitting on dozens of near-complete projects that I just cannot bring myself to finish.

ctrlrsf 10y ago
Finish the easiest one first to get you started. Rememeber it doesn't have to be perfect.

ourmandave 10y ago

Some of my unfinished projects suffer from, "We all agreed not to talk about that anymore." Combine a vague spec ("Not now kids. Daddy's working on a better Snapchat!") with design-it-while-I-code and you end up with a transporter accident.

Eridrus 10y ago

Same, I find it much easier to start new projects, finishing them after I've done what I consider the core "thing" is much harder. We're clearly not alone. Not all projects are worth finishing, but I find that once the rush of learning new things have worn off and the only thing left to do is rigorous evaluation or polish my desire to work no it fades. I find tying some reason to finishing them usually gets me more willing to do so. Giving presentations about my work has often served as a good forcing function since they have due dates associated with them and the fear of being embarrassed by my work outweighs the boredom of doing the last ~20%. Not a panacea, but it helps me.

Broken_Hippo 10y ago

I do the same. Over time, I've learned to space some of the starts out and have a few things in different stages of production. (for me, artwork is the major one). This spreads out the tedium. I'm not spending 10 hours in one go completing something: I'm spending a couple of hours on it, then moving to a different piece and a different task. When I'm in a good flow, it works out really well. And sometimes I find I finish a few projects in a short time.