Burnout is your subconscious's way of telling you that you're on the wrong track.
I've found that every time I've felt burned out - whether in writing, coding, startup, life - it's because I was working on something that ultimately was going nowhere. I needed to revisit my assumptions, yet my conscious mind didn't know that. Burnout was a way for my subconscious to say "This isn't going to work, you're not working on the important stuff, take a step back and look at the big picture."
When writer's blocked, I delete the last 3 paragraphs I've written and take the story in another direction. This has almost always cured my writer's block; when it doesn't I delete the last page and take the story in another direction.
When coder's blocked, I revert to my last svn commit and start again, usually with a smaller task. I've thrown away up to a week's worth of work this way, which is another lesson: commit early and often. Commits should be an hourly or minutely process, not something you do after a whole bunch of work.
When blocked in general, I think about the last design decision I made and revisit. Oftentimes, if I'm blocked entirely and can't even get started on implementing a feature, it's because the feature is ill-conceived and needs to be redone. Maybe it's done with incorrect assumptions about how users will use the problem, or maybe it just doesn't serve any purpose. Revisit whether you need the feature at all.
If you find you can't work on your startup at all, maybe it's a sign that your startup is on the wrong track. Revisit your idea. I'm actually at that stage with mine: we scrambled to get a demo ready for YC, but now that I want to procrastinate and avoid work (our market is people who want to procrastinate and avoid work), I find that I don't want to use our product. But I've got some ideas about how to backup and try a different approach, and now I want to try them out and see if they can get me procrastinating with the startup itself.
Interesting -- your hypothesis is almost exactly what I wrote down in my journal just this morning, when thinking about how I let my "commitment to the business" override so many other thoughts/desires/gut-reactions. Some level of compromise is needed to get anything done in real life, but too much is too much.
Burnout is your subconscious's way of telling you that you're on the wrong track.
I've found that every time I've felt burned out - whether in writing, coding, startup, life - it's because I was working on something that ultimately was going nowhere. I needed to revisit my assumptions, yet my conscious mind didn't know that. Burnout was a way for my subconscious to say "This isn't going to work, you're not working on the important stuff, take a step back and look at the big picture."
When writer's blocked, I delete the last 3 paragraphs I've written and take the story in another direction. This has almost always cured my writer's block; when it doesn't I delete the last page and take the story in another direction.
When coder's blocked, I revert to my last svn commit and start again, usually with a smaller task. I've thrown away up to a week's worth of work this way, which is another lesson: commit early and often. Commits should be an hourly or minutely process, not something you do after a whole bunch of work.
When blocked in general, I think about the last design decision I made and revisit. Oftentimes, if I'm blocked entirely and can't even get started on implementing a feature, it's because the feature is ill-conceived and needs to be redone. Maybe it's done with incorrect assumptions about how users will use the problem, or maybe it just doesn't serve any purpose. Revisit whether you need the feature at all.
If you find you can't work on your startup at all, maybe it's a sign that your startup is on the wrong track. Revisit your idea. I'm actually at that stage with mine: we scrambled to get a demo ready for YC, but now that I want to procrastinate and avoid work (our market is people who want to procrastinate and avoid work), I find that I don't want to use our product. But I've got some ideas about how to backup and try a different approach, and now I want to try them out and see if they can get me procrastinating with the startup itself.