Explosive productivity
31fps.com
31fps.com
He was first taught this technique at a high-end athletic training center. They put him on an exercise machine and had him go all out for a few minutes. Then they had him relax and recover -- and the trainers timed it, so he only relaxed for say, 45 seconds. Precisely at the end of 45 seconds, they put him back on the exercise machine again. Over time, his heart rate did not spike up as high, and the amount of time he needed to recover started shortening.
Lest you think this applies to only physical tasks, and not mental tasks, according to the book, Waitzkin was able to successfully apply this during the intense national and international chess tournements he participated in. He takes short mini-breaks, so while it looks like he is able to sustain his focus for long periods of time, that's an illusion.
This idea of recovery time for getting things done isn't a new one. I've always thought I had to go all out, indefinitely. I always exhaust myself and couldn't energize myself to get more done. My bet is that people who appear to be productive all the time are the ones skilled at taking these short mini-breaks.
If I sit in front of my computer and after 15 minutes I can't get anything done on the project that I am wanting to work on, I know I never will. Forcing it will never make anything happen.
I often work alone, so I wonder if having someone else around to help motivate me would help. Talking about the project without any pressure to produce until my creativity start moving again.
For me, I can have entire months where all I do is the bare minimum to keep life moving and then one week I manage to do what it would take most other people an entire month to accomplish. I know that this is part of my cycle and I've learned to life with it and let if flow however it does ...
But days like today I sure wish I could make things move on their own ...
For example, I try to keep a couple of projects going on at the same time - I generally have a major release in development for our team's primary product at all times. This is my "main work".
I also have one or two smaller projects at some stage of design or development as well - perhaps a prototype to try show the business owners a cool new idea or some type of development or administration tool which would help support the primary project. Usually, I try to learn a new technology or language while solving a problem related to our business.
When I find myself become unproductive on my main work, I switch focus temporarily to one of the smaller projects. These projects tend to be personal (although work-related) and don't have fixed delivery dates. Without the pressure of a strict schedule or external expectations, I can more easily work on these projects and rediscover my ambition.
It usually doesn't take more than a day or so to get my motivation back and I return to working on my main project with my usual productivity.
Working like this seems natural to me, big explosive bouts of high productivity, churning out cool stuff, and then days of nothing. I think part of it is that the days of 'nothing' seem like nothing, when in reality they are often 'thinking' days, where you solve problems, but just don't happen to produce code.
However, I have a way to stay productive during the lulls, which has been very effective for me: pair programming. Even if I'm not inspired, or even energetic, if I sit down with someone else to work on a task, pretty soon the conversation gets me focused and triggers ideas.
http://video.google.com/videoplay?docid=-7477852615698435519...