4 ms·

I agree with the other posters. You need to take some time and get re-inspired, and to do so, it helps just talking with somebody about it. The fact that you're

by jsherer 14y ago

I agree with the other posters. You need to take some time and get re-inspired, and to do so, it helps just talking with somebody about it. The fact that you're posting about it here tells me that you're likely to make it through (otherwise, you would have quit already). Seth Godin calls this point "The Dip". It's a trough in the lifecycle of a project/plan/development/etc when the high and excitement of starting something has died off and the rewards don't seem worth the remaining effort. I can tell you, though, that if you put in the time, get inspired, and slog through the toughest part of "The Dip", you'll come out the otherside with something great. Most projects don't make it past, so there's great value in doing so. Here are some links to read more about "The Dip": http://www.slideshare.net/stevecla/pushing-past-the-dip-how-to-become-the-best-in-the-world http://www.slideshare.net/stevecla/pushing-past-the-dip-how-... http://sethgodin.typepad.com/the_dip/ http://sethgodin.typepad.com/the_dip/ http://www.ribbonfarm.com/2007/09/06/seth-godins-dip-and-multi-armed-bandits/ http://www.ribbonfarm.com/2007/09/06/seth-godins-dip-and-mul...

chris_dcosta 14y ago
I'm glad you brought this up, because I'd also read about this, and had always dismissed it thinking "I'm not going to let this happen to me" (don't we all?) - but i recognise it now that you mention it. It must have crept up on me. I'd like to add one more point, in that the project has reached the stage where I was starting to get people excited about it when it was presented, as opposed to the early reactions where the concept wasn't fully formed, and most people couldn't relate to it. I think I am feeling the pressure of expectations as well. People are now asking me when it will be ready, whereas before there was no such anticipation.
- mst 14y ago
  Well then that's a score; if people are excited and asking about when it's ready, that's a perfect opportunity to say "I'm not entirely sure yet, because ..." and try to explain the interlinked problems to them. In the process of explaining them, you'll eventually clarify your own understanding to the point of an "aha" moment. I spent about an hour last night trying to explain the basics of something I've been working on to a (non-programmer) girlfriend, and had several "aha" moments about the much deeper details of the design simply from trying to explain the surface.
- Nervetattoo 14y ago
  I would look really hard for any way to even just release a single feature of it — just get _anything_ released and "working". You need to reinspire yourself here, and one hell of a good way of doing that is being pushed by peoples feedback. I know for myself that at the point you apparently are at its very easy to take a break and think you'll come back to it later — big mistake. If you can't muster the energy to release something now then chances are you wont ever. Try to release something, gather feedback and use that loop as a motivation for doing minor, really minor, fixes and improvements. If you can manage that you can pick up new steam and in the same time learn more about what direction you should be taking.

by jsherer 14y ago

chris_dcosta 14y ago

I'm glad you brought this up, because I'd also read about this, and had always dismissed it thinking "I'm not going to let this happen to me" (don't we all?) - but i recognise it now that you mention it. It must have crept up on me. I'd like to add one more point, in that the project has reached the stage where I was starting to get people excited about it when it was presented, as opposed to the early reactions where the concept wasn't fully formed, and most people couldn't relate to it. I think I am feeling the pressure of expectations as well. People are now asking me when it will be ready, whereas before there was no such anticipation.

mst 14y ago
Well then that's a score; if people are excited and asking about when it's ready, that's a perfect opportunity to say "I'm not entirely sure yet, because ..." and try to explain the interlinked problems to them. In the process of explaining them, you'll eventually clarify your own understanding to the point of an "aha" moment. I spent about an hour last night trying to explain the basics of something I've been working on to a (non-programmer) girlfriend, and had several "aha" moments about the much deeper details of the design simply from trying to explain the surface.
Nervetattoo 14y ago
I would look really hard for any way to even just release a single feature of it — just get _anything_ released and "working". You need to reinspire yourself here, and one hell of a good way of doing that is being pushed by peoples feedback. I know for myself that at the point you apparently are at its very easy to take a break and think you'll come back to it later — big mistake. If you can't muster the energy to release something now then chances are you wont ever. Try to release something, gather feedback and use that loop as a motivation for doing minor, really minor, fixes and improvements. If you can manage that you can pick up new steam and in the same time learn more about what direction you should be taking.